Journeys & orchestration
How this is scored
Multi-step automation: triggers, branching, waits, goals — and what happens when a contact qualifies for several journeys at once.
0 — No automation; the product sends one-off campaigns only.
3 — Autoresponders or linear sequences started by a trigger such as a sign-up or a tag, with waits between steps.
5 — A visual workflow builder with triggers on behaviour and attributes, if/else branching and waits, and goals or exit conditions that take a contact out of the flow.
8 — Event-driven entry from external systems through an API, frequency capping and suppression across journeys, priority when a contact qualifies for several, per-contact journey state and reporting per step, versioning or safe editing 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 journeys documented and readable months later.
The Lifecycle Marketer
A visual builder with behavioural and attribute triggers, split and branching paths, goals that track funnel progress with follow-up or channel-switch fallbacks, and entry from external systems through site, event, field, segment and deal-stage triggers — a solid mid-level orchestration story. What I look for at the top end — frequency capping across journeys, arbitration when a contact qualifies for several at once, and holdout groups for measurement — we found no public information on any of those, and the entry plan caps each automation at 5 actions. 2 4 5 7 2