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
Architect is a real decision layer: multi-branch journeys in a zero-code builder, a Living Profile refreshed in milliseconds from CDP, CRM and offline systems, A/B testing of entire journey flows, and next best action picked across thousands of variables. I found no public information on versioning of a live journey, per-contact journey state, priority when several journeys want the same person, or holdout groups for measurement, and the frequency caps that are documented appear on the web push page rather than programme-wide. 3 4 6 8