Journeys & orchestration
How this is scored
Multi-step automation: triggers, branching, waits, and — the part that decides whether it survives contact with reality — what happens when journeys collide.
0 — Autoresponders on a single trigger; no branching, no waits, no conditions.
3 — Linear sequences with simple conditions, one entry trigger per journey, and no visibility into where a contact currently sits.
5 — A visual builder with branching on attributes and behaviour, waits and goals, entry and exit conditions, and per-contact journey state visible.
8 — Event-driven entry from external systems, frequency capping and suppression across journeys, priority when a contact qualifies for several, versioning of a live journey, and testing against real records.
10 — Orchestration is coherent across the whole programme: one decision layer deciding what a person receives next regardless of which journey wants to send it, holdout groups for measurement, and a journey a colleague can read months later without a diagram.
The Lifecycle Marketer
The visual journey builder with event, date and segment triggers, per-journey re-entry control and suppression rules is genuinely lifecycle-minded — the win-back-after-six-months re-entry example is exactly right, and CRM events can start a journey. But the collision layer that decides survival is unevidenced: I found no public information on frequency capping across journeys, priority when a contact qualifies for several, versioning of a live journey, holdout groups for measurement, or wait steps and per-contact journey state. The soft-launch cohort advice is good rollout practice, not a control group. 2 3 10 1