The Workflow Library

Library / Lead nurturing / lead-nurturing-016

Case study / social proof nurture by industry

Lead nurturingContactMarketing Hub ProfessionalIntermediate~35 min to buildFull spec

Outcome. A contact who is already mid-nurture and has a known industry gets one targeted case study, then one customer-quote follow-up, instead of the same generic proof point every contact sees.

Workflow map Enrollment, branches and actions at a glance lead-nurturing-016
flowchart TD
    A[Filter: active nurture + industry known] --> B{Industry value?}
    B -- Healthcare --> C1[Send healthcare case study]
    B -- Financial Services --> C2[Send finserv case study]
    B -- Retail --> C3[Send retail case study]
    B -- Manufacturing --> C4[Send manufacturing case study]
    B -- Technology --> C5[Send technology case study]
    B -- Other/unknown --> C6[Send general case study]
    C1 --> D[Delay 5 days]
    C2 --> D
    C3 --> D
    C4 --> D
    C5 --> D
    C6 --> D
    D --> E[Send customer quote follow-up]
    E --> F[Set case_study_nurture_completed = true]
action or delay branch public on every spec, paid or not

When to use it, when not to

  • UseUse as a drop-in proof module for a contact already inside another nurture track (lead-nurturing-008, 009, or the welcome drip), once at least one qualifying industry has a real, published case study.
  • UseUse it to add a credibility beat mid-sequence, not as a standalone first-touch nurture. A cold contact with no context does not need a case study before an introduction.
  • SkipDo not use it if fewer than two industries have a published case study. A near-empty branch table just falls through to the generic proof point for almost everyone, see lead-nurturing-009 for the same tradeoff at a bigger scale.
  • SkipDo not run this at the same time as lead-nurturing-009 for the same contact. Both branch on industry_segment and sending two industry-branched sequences back to back is redundant. Sequence them, or pick one.
The preview ends here. Six sections are in the library. counted, not blurred
PrerequisitesEvery property with its label, internal name, type and options, plus the assets the workflow needs before you start.3 items
EnrollmentThe trigger, the criteria exactly as they are ticked in the UI, the re-enrollment rule and the suppression list.4 parts
StepsEach action in order with its parameters, its branches and its delays, written as you tick them.25 numbered actions
Known pitfallsTraps seen in production, each with what breaks and what to do instead.4 pitfalls
Test plan, variants and build specHow to prove it works in a test portal, where to look when it does not, the variants for other objects or tiers, and the YAML build spec.3 variants, 3 sections
FilesThe properties JSON creates the fields in one API call, the workflow JSON documents the build.PDF, Markdown, JSON
Install1 click. The installer creates the properties this spec declares and the workflow itself, switched off, then opens a task for the prerequisites that are assets rather than properties, such as a team, a static list or a marketing email. What it created is listed on the install page.1 click, switched off
Unlock the full library, 149 EUR

or the lead nurturing pack, 39 EUR

One-time, excl. VAT. 30-day refund, no questions asked. Founding prices until 31 October, then 199 and 59 EUR. Includes every spec added later, up to the full 500, and the one-click installer on the full library. Building on client portals? The agency licence at 449 EUR covers unlimited client portals.