CEDX Journeys · Marketing
Pulse reads 21 live journeys against enrolment, conversion and drop — then goes further: the wait cost of a slow path, in dollars, and the exact step where 35.7% of a win-back path walks away.
A drop rate next to a step name is a to-do list. A wait cost in dollars is a budget conversation. This product prints both.
Runs on demo data. The workspace, paths and revenue figures are the demo's.
What it is
The cart-recover canvas reads like a flow and measures like a ledger: 18,420 enrolled, entry on cart abandoned, wait one hour, email reminder one, wait 22 hours, an SMS urgency step, then a split on engaged — 71% yes, 29% else. Every edge carries its drop count.
Every step across every path in one table: type, entered, dropped and drop rate. Wait 72h loses 37.4% of the 4,932 who reach it. The win-back email we miss you has dropped 7,900 of 22,100 — and the salvage score says it is still worth fixing.
320 enrollments with the person, the journey, the status, the step they are on, days in path, the exit reason and LTV. Exited on a suppression list, failed on a channel opt-out, completed on goal met — the reason is a column, not a mystery.
Product tour
Not a mockup and not a concept deck. This is what opens at /app/journeys.
01 — Pulse
The root-caused alerts do not say engagement is down. They say a five-day wait on the win-back path costs $1.79M in opportunity, that the payment-fail SMS experiment won by 15.2 points, and that the Q3 holdout cohort locks in week 11 for measurement.
02 — Canvas
The cart-recover path loses 1,100 people at the entry edge, 2,440 at the first wait and 2,700 before the SMS step. Edge heat is coloured from cool to critical, so the leak is visible before a single report is opened.
03 — Steps
Sorted by drop rate, the table mixes waits, emails and splits from a dozen different paths — because a 37.4% drop hurts the same wherever it lives. Average drop across the filtered view: 13.9%.
04 — Enrollments
The ledger shows who is in, who finished, and why the rest left — 60 active right now, 154 exited or suppressed. A failed row names the step and the reason: channel opt-out at wait short, 59 days in.
Who runs it
Roles, not references. We have no named customers yet, so nobody in these photographs is quoted, credited or claimed as one.
Designs the paths on the canvas and reads drop per edge — then moves the email that loses 7,900 people, instead of rewriting the whole journey.
21 live · 26.2% avg drop
Watches conversion and LTV by path, and defends the holdout cohort when someone wants the win-back volume back.
holdout cohort · week 11
Keeps suppression, opt-outs and exit reasons clean in the ledger, so a suppressed contact stays suppressed everywhere.
154 exited/suppressed of 320The shape of it
Every figure below is legible in the captures above. Nothing here is a projection of your estate — it is the state of the demo data.
How it runs
An entry trigger puts a person on the path — cart abandoned, one hour. The ledger opens a row the same moment.
Timed steps hold people between touches, and the wait cost of every slow edge is priced in dollars, not hand-waved.
Splits read engagement — 71% yes, 29% else on the cart path — and send each side down a different sequence.
Experiments run inside live paths and holdouts stay frozen for measurement, so the lift claim survives the meeting.
One record
Enrollment, suppression and conversion are not journey-private state. The same people, forms and revenue show up in the rest of the estate.
The audiences journeys enroll from, with overlap already scored before a path spends on them.
CEDX FormsThe capture points that feed journeys — submissions arrive spam-scored before they enter a path.
CEDX ReferralsThe advocacy stage after retention: converted customers become the people who refer.
CEDX CopilotAsk the ledger questions in plain language — answers cite the journeys data they came from.
Limits
Finding this out on the third call is worse for you than reading it here, and worse for us.
Start
Open it right now
Your paths, your people
Journeys with the rest of it
Questions
Yes. Every screenshot is a capture of the running build and you can open the same build at /app/journeys. It runs on demo data — the paths and people are the demo workspace's.
The dollar price of slow steps. The Pulse prices a five-day wait on the win-back path at $1.79M in lost opportunity, so a timing argument becomes a budget argument with a number on it.
Yes, per person. The enrollment ledger carries an exit reason on every row — suppression list, unsubscribed, channel opt-out, hard bounce, goal met — alongside the step and the days in path.
Inside live paths, with holdouts. The Pulse reports the payment-fail SMS experiment at +15.2 points and keeps a control cohort frozen for the quarter's measurement.
No certification has been issued. What we can evidence about hosting, encryption, tenant isolation and production access is written up on the security page.
Live build, demo data, no card. Then ask where your win-back path would leak.