CEDX Engagement · Product engagement
Engagement scores product usage the way a finance team scores cash: a composite 0–100 per user, bands from Champion to Dormant, sessions with depth and outcome — and a monitoring digest that attaches a cause and a next step to every metric that moved.
The digest does not say “score down 2.1”. It says the ingest lagged 18 minutes, skewing the recency component — and to pause score-cliff alerts for 24 hours. A cause and a next step, or it is not an alert.
Runs on demo data. The workspace labels itself Harbor Production · score lag ~2m · demo seed.
What it is
Twenty-four thousand six hundred users sorted into Champion 3,420, Engaged 6,840, Passive 7,920, At risk 3,960 and Dormant 2,460 — with a high-LTV at-risk list that pairs each score with the value it protects, down to a score of 7 against 16K.
Three hundred twenty seeded users with score, band, plan, session count, last-active and a 30-day sparkline per row. Champions average 52.3 across the workspace; eighty-six sit at risk or dormant with “need play” attached.
Four hundred twenty sessions with duration, depth, channel and outcome per row — 19 minutes, 13 screens, desktop, converted. One hundred seventy-three ended engaged or converted: 41% of the view.
Product tour
Not a mockup and not a concept deck. This is what opens at /app/engagement.
01 — Overview
Score and sessions trend across the quarter while the watched-metrics digest investigates what moved: a silent-14-day cohort up 48 users traced to trial day-5 inactivity; win-back conversion up 0.6 points traced to a subject-line variant, with “promote to 100%” as the next step.
02 — Users
Search by id, email, name or company across the seeded users. A champion at 97 with 66 sessions reads beside one at 91 on a free plan — band and plan are separate columns, so value and usage never blur.
03 — Sessions
Sessions list duration, depth, channel, outcome and score, with the moment they started. Converted sessions at 19-plus minutes sit beside bounced ones — depth and outcome are the columns the bands are built from.
Who runs it
Roles, not references. We have no named customers yet, so nobody in these photographs is quoted, credited or claimed as one.
Runs the plays the digest recommends: promote the win-back variant, route revoked push users into the email re-permission series.
convert 4.8% · +0.6pp win-back
Reads the bands against the roadmap — the boards tip lifting Passive-band depth is why champion share is up 0.8 points.
champion share +0.8pp
Works the digest: every moved metric needs a cause and a next step before it reaches the weekly review.
5 watched metrics · causes attachedThe shape of it
Every figure below is legible in the captures above. Nothing here is a projection of your product — it is the state of the demo seed.
How it runs
Sessions roll into a composite 0–100 per user — the demo seed runs with a two-minute lag, printed on screen.
Scores sort users from Champion to Dormant, so the play is chosen by band, not by hunch.
The watched-metrics digest attaches a cause to every change — ingest lag, a variant, a feature tip — before anyone acts on it.
Next steps are specific: boost the trial day-3/5 drip, promote variant B to 100%, extend the boards tip to all Passive workspaces.
One record
Engagement scores the users; the campaigns and journeys that move the score live next door.
The win-back canvas whose variant lifted conversion 0.6 points is a campaign; the digest promotes it from here.
CEDX JourneysThe trial day-3/5 drip the silent-cohort alert recommends is a journey — band changes are its trigger.
CEDX Product AnalyticsSessions, depth and channels here are the raw material the composite score is built from.
CEDX CRMThe accounts behind the users are the same record sales works — high-LTV at-risk is a shared list.
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 events, your bands
Engagement 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/engagement. It runs on a demo seed, which the workspace labels on screen.
No. The captures are unambiguous: this scores product usage — sessions, depth, bands, plays. Staff-side engagement in this estate runs through People and Performance.
A 0–100 composite over seeded session, campaign and churn signals, with the lag printed on screen. The digest shows the components moving — recency, depth, campaign response — rather than hiding them.
The next step attached to a watched metric: promote the winning win-back variant, route push-revoked users into the email re-permission series, extend a feature tip to all Passive-band workspaces.
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 seed, no card. Then ask what your own silent-14-day cohort looks like this week.