Segment the mid-market audience
Unlocks 1 task
Rebuild the top of the pipeline before the Q4 forecast locks, without publishing a single claim we cannot source.
Paused at Budget release — is waiting on Dai Okonjo. Release £180k media spend against a pipeline coverage ratio of 2.7x.
Who we are talking to and what they already believe.
The narrative, the asset set and the landing page.
Approve the narrative and asset set for clearance.
Held by Juno Prieto
Every number traced to a source we can show.
Confirm every published claim traces to a source.
Held by Citation
Approved on the second pass. Rejected first time — two retention figures had no source and were cut rather than softened.
Commit the spend against the pipeline it is meant to move.
Release £180k media spend against a pipeline coverage ratio of 2.7x.
Held by Dai Okonjo
Waiting. The CFO wants the coverage ratio recomputed excluding deals with a single contact.
Publish, monitor, report against target.
Segment the mid-market audience
Unlocks 1 task
Test the message hypothesis
Unlocks 1 task
Assemble the claim evidence pack
Unlocks 1 task
joins from Audience research
Write the core narrative
Unlocks 1 task
Produce the asset set
Unlocks 1 task
Build the landing page
Unlocks 1 task
joins from Creative
Verify every stated claim against source
Unlocks 1 task
File the evidence pack
Unlocks 1 task
joins from Claim clearance
Model the spend against pipeline coverage
Unlocks 1 task
Release the £180k media budget
Ready — every dependency closed
Unlocks 1 task
joins from Budget release
Publish across paid, owned and lifecycle
Waiting on 1: Release the £180k media budget
Monitor early response by segment
Ready — every dependency closed
Report measured response against target
Ready — every dependency closed
One column per stage, in routing order. Tasks inside a stage run in parallel; the first task of each stage joins from every task of the one before it, which is the hand-off between departments made explicit.
Publish across paid, owned and lifecycle
Monitor early response by segment
Report measured response against target
Empty
Empty
Release the £180k media budget
Empty
Segment the mid-market audience
Test the message hypothesis
Assemble the claim evidence pack
Write the core narrative
Produce the asset set
Build the landing page
Verify every stated claim against source
File the evidence pack
Model the spend against pipeline coverage
Approve the narrative and asset set for clearance.
Confirm every published claim traces to a source.
Approved on the second pass. Rejected first time — two retention figures had no source and were cut rather than softened.
Release £180k media spend against a pipeline coverage ratio of 2.7x.
Waiting. The CFO wants the coverage ratio recomputed excluding deals with a single contact.
Deciding a gate writes the decision and nothing else. The status change, the release of downstream stages and the “ready to close” state are all derived from it on the next render — which is why an approval here is one field rather than a transaction.
2.7x coverage is fine if it holds. Recompute it without the single-contact deals and I will sign.
Open in the Hub →Claims cleared on the second pass. We cut both unsourced figures rather than soften them.
Open in the Hub →Rejected. Two retention numbers have no source I can reach. They do not go out.
Open in the Hub →Task-weighted, not stage-weighted. A two-hour approval stage and a two-hundred-hour build stage are not half the work each, and treating them as such is the usual way a project dashboard reports 50% before anything has been built.
Closed when the launch stage reports measured response against the stated target.
Every stage reaches complete or skipped.
Held at Dai Okonjo's finance gate.
Computed by engine.peekAdvance(), which returns the next stage rather than moving to it. The Task Orchestrator owns the write; keeping this side pure is what lets a card show “next: Engineering” with no risk that rendering a page advances a workflow.
Nothing here executes. There is no scheduler, no queue and no writer — these are evaluations of the current state, refreshed on every render. Adding a trigger is one row in AUTOMATION_TRIGGERS; it appears on every workflow immediately so a rule can be checked against real data before anything is built to act on it.
Dai Okonjo Held the budget gate pending a recomputed coverage ratio.
Workflow Engine Routed from Claim clearance to Budget release.
Citation Approved claim clearance on the second pass.
Citation Rejected claim clearance — two retention figures had no traceable source.
Juno Prieto Closed Creative — narrative, assets and landing page delivered.
CEO Opened from the Marketing Campaign template — 5 stages, 3 approval gates.