Outcome. Contacts with a known buyer persona get a short nurture built around content relevant to that persona, instead of one generic sequence for everyone.
Workflow map
Enrollment, branches and actions at a glance
lead-nurturing-008
flowchart TD
A[Filter: persona known, not customer] --> B{Persona value?}
B -- Economic Buyer --> C[ROI case study] --> D[Delay 4d] --> E[Executive summary] --> F[Set completed = true]
B -- Technical Buyer --> G[Technical deep dive] --> H[Delay 4d] --> I[Integration docs] --> J[Set completed = true]
B -- End User --> K[Quick win use case] --> L[Delay 4d] --> M[Product tour] --> N[Set completed = true]
B -- Unknown/blank --> O[No action]
When to use it, when not to
- UseUse once persona is captured somewhere upstream (form field, manual sales input, or a scoring model) and at least two persona values have distinct enough content to justify separate tracks.
- UseUse for a team that can maintain 2 to 3 content variants per persona. A one-person marketing team may not have the assets yet.
- SkipDo not use it as a substitute for lifecycle-stage logic. Persona changes the content angle, not the deal stage.
- SkipDo not build more than 3 or 4 persona branches for a first version. Every extra branch multiplies the emails to write and keep current.
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.2 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.14 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.
