Skip to content

Form-field answer based nurture branch (e.g. company size)

One of 565 written HubSpot workflow specs, by a collective of independent HubSpot consultants.

Professional

Seat pricing: Professional edition. To build it, a GTM Seat or an Ops Seat (an Ops Seat cannot create marketing emails or sequences). Per-hub plans: Marketing Hub Professional.

Contact13 stepsUpdated for HubSpot seat pricing
OutcomeA contact who answered a company-size question on a form gets a nurture sequence framed for their size bracket, smaller teams see fast setup and lower cost, larger ones see governance and scale, instead of one generic message for every company.
Workflow maplead-nurturing-029
Filter: company size known, not customer leads to Size bracket?. Size bracket? leads to 1-10 or 11-50: Small-team track; 51-200 or 201-1000: Mid-market track; 1000+: Enterprise track. Small-team track leads to Set completed = true. Mid-market track leads to Set completed = true. Enterprise track leads to Set completed = true. 1-10 or 11-50 51-200 or 201-1000 1000+ Filter: company size known, not customer Size bracket? Small-team track Mid-market track Enterprise track Set completed = true
Filter: company size known, not customer leads to Size bracket?. Size bracket? leads to 1-10 or 11-50: Small-team track; 51-200 or 201-1000: Mid-market track; 1000+: Enterprise track. Small-team track leads to Set completed = true. Mid-market track leads to Set completed = true. Enterprise track leads to Set completed = true. Filter: company size known, not customer Size bracket? 1-10 or 11-50 Small-team track 51-200 or 201-1000 Mid-market track 1000+ Enterprise track Set completed = true

One of 565 written HubSpot workflow specs, by a collective of independent HubSpot consultants.

When to use it, when not to

Use it

  • Use when a form already asks a company-size question (or a similar segmenting question) with a small, fixed set of answer options, not free text.
  • Use it for products where the buying conversation genuinely differs by size, pricing tier relevance, implementation complexity, team rollout.
Read more on when to use itShow less

Skip it

  • Do not use it if the form question is optional and mostly skipped. A branch built on a mostly-blank field falls through to the smallest data set possible.
  • Do not use this same pattern for two different segmenting questions on the same contact at the same time; pick the one field that best predicts the messaging difference, or the branches multiply unmanageably.
Read more on when to skip itShow less

The rest of this spec

Prerequisites · 2 items

Every property with its label, internal name, type and options, plus the assets the workflow needs.

Enrollment · 4 parts

The trigger, the criteria as ticked in the UI, the re-enrollment rule and the suppression list.

Steps · 13 numbered actions

Each action in order with its parameters, branches and delays.

Known pitfalls · 4

Traps seen in production, each with what breaks and what to do instead.

Test plan and UAT script · 4 cases, 3 variants

How to prove it works in a test portal, one case per branch, and a sign-off sheet.

Files · PDF, Markdown, JSON, CSV

The properties JSON creates the fields in one call. The workflow JSON documents the build.

Install · 1 click, switched off

The installer creates the properties and the workflow, switched off, then opens a task for what it cannot create. Nothing is deleted, enabled or enrolled.

Unlock all 565 specs, 149 EUR

One-time, excl. VAT. 30-day refund. Installs in 3 portals. Founding price until 30 November.

Read the free Lead nurturing spec

Read 12 complete specs before you pay.

One per category, same format as the paid ones. Email only, no card.

We email the link, then a short note when specs change. Nothing else.

149 EUR199

Full library, 565 specs
Get the full library