Outcome. A contact gets messaging pitched at the right altitude, strategic framing for a senior title and hands-on detail for an individual contributor, based on a seniority level derived from their job title.
Workflow map
Enrollment, branches and actions at a glance
lead-nurturing-028
flowchart TD
A[Filter: seniority known, not customer] --> B{Seniority value?}
B -- C-Level --> C1[2-email strategic track] --> H[Set completed = true]
B -- VP or Director --> C2[2-email dept-outcomes track] --> H
B -- Manager --> C3[2-email team-rollout track] --> H
B -- Individual Contributor --> C4[2-email hands-on track] --> H
When to use it, when not to
- UseUse when the product genuinely reads differently to different seniority levels, for example an executive cares about outcomes and an implementer cares about setup detail.
- UseUse it together with a classification step that maps raw job title text into a small number of seniority buckets, since branching directly on free-text job title is not practical.
- SkipDo not use it if job title data is mostly blank or unreliable. A branch fed by an unreliable field mostly falls into the "Unknown" bucket, undercutting the point.
- SkipDo not build more than 3 or 4 seniority buckets. A finer split multiplies content work without a proportional gain in relevance.
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.18 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, and the custom coded action ships as a ready-to-paste .js file.PDF, Markdown, JSON, code
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.
