Agree the metric before week one.
A business outcome, recorded before anything changes: completed applications, recovered carts, verified transactions, retained customers.
After the demo
One use case. Six to eight weeks. A number you agreed first.
The honest test of whether a business team can complete the loop unaided is to let one try, on a journey that matters, against a baseline. The pilot is optional and starts after a demo.
The eight weeks
How the weeks run, and what ends each phase.
CAPTUREASK YOUR TEAM DRIVES →ACTMEASURE
| Weeks | What happens | Exit condition |
|---|---|---|
| 1–2 | Turn on event capture. Agree the baseline metric. | Events arriving, schema visible, baseline recorded. |
| 3–4 | Build audiences. Ask real questions. | Your team is querying without help. |
| 5–6 | Build and test the journey. Dry-run and preview. | Journey approved, execution traces reviewed. |
| 7–8 | Run live against the audience. Measure. | Result compared to baseline, decision made. |
Your business team drives from week 3. Scope and timing are agreed around your integration and approvals.
If it fails to beat the baseline, that is a real answer, and worth having in eight weeks rather than after a platform commitment.
What makes the test fair
Your team drives from week three.
If the pilot succeeds only because our engineers built the journey, it has tested the wrong thing.
Pick a use case where response matters.
A journey that branches on a keypress, a reply or a button shows what the platform is for.
What we need from you
- A developer to place the SDK or call the ingest API.
- One business owner for the use case.
- Agreement on the baseline.
- Whatever internal approval the journey needs.
Everything after event capture is portal work.
Next step
Book a Demo