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

Outcome. A 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 map Enrollment, branches and actions at a glance lead-nurturing-029

flowchart TD
    A[Filter: company size known, not customer] --> B{Size bracket?}
    B -- 1-10 or 11-50 --> C1[Small-team track] --> H[Set completed = true]
    B -- 51-200 or 201-1000 --> C2[Mid-market track] --> H
    B -- 1000+ --> C3[Enterprise track] --> H

When to use it, when not to

• UseUse 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.
• UseUse it for products where the buying conversation genuinely differs by size, pricing tier relevance, implementation complexity, team rollout.
• SkipDo 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.
• SkipDo 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.