CEDX Onboarding · Customer onboarding
Onboarding runs new customer accounts as a managed queue: each one carries a stage from kickoff to go-live, a health score, a predicted time-to-value and a named owner — and the tasks that slip are counted in days late, not vibes.
The overview does not hide its worst number. Median predicted time-to-value is 61 days against a 42-day target, and the card is flagged watch. A product that shows you that on page one is showing you everything.
Runs on demo data. The workspace names itself Customer Onboarding · Northline Launch Q3 2026.
What it is
Three hundred twenty accounts with segment, stage, health, predicted time-to-value, blocker count, go-live date and owner on every row. Stage chips run Kickoff, Setup, Training, Integration, Pilot, Go-live — and Adopted for the ones that made it.
Forty-eight plays with steps, average days, completion percentage and accounts attached per row. A Growth Starter 30-day play runs 18 steps in 28 days at 84% completion across 62 accounts; the Enterprise Platform Fast Path holds 91% across 50.
Four hundred twenty tasks — 313 open, 94 overdue — with type, priority, due date and days late on every row. The top of the queue is a playbook swap 25 days late at P0, next to a security questionnaire close 20 days late. This is where launches actually slip.
Product tour
Not a mockup and not a concept deck. This is what opens at /app/onboarding.
01 — Overview
Active accounts 261, value target 62% attained, median predicted TTV 61 days against the 42-day target, 140 at risk and 94 overdue tasks. Root-caused alerts price the rest — a playbook mismatch at $168K, a compliance-gate hold at $132K.
02 — Accounts
Search across 320 accounts by playbook or product. Health, predicted TTV, blockers and go-live date sit on the row, so an account at health 95 with a 78-day predicted TTV is visible before its renewal is.
03 — Playbooks
Forty-eight plays by segment and product — Starter, Payments, Platform, WMS, Analytics — each with steps, average days and completion. Migration plays sit next to fast paths, and the completion spread from 40% to 91% is the argument for fixing one playbook at a time.
04 — Tasks
The queue behind every stage: SSO configuration, environment setup, cutover rehearsal, pilot success criteria, champion check-ins. Each task shows type, status, priority, due date and exactly how many days late it is.
Who runs it
Roles, not references. We have no named customers yet, so nobody in these photographs is quoted, credited or claimed as one.
Owns the playbook: 18 to 54 steps, and the completion percentage that says whether the play itself is the problem.
48 plays · 65% avg completion
Works the at-risk list — 140 accounts — and the champion check-ins before a quiet sponsor becomes a lost launch.
140 at risk · health to 26
Lives in the config queue: SSO, security questionnaires, environment setup — the P0 tasks counted in days late.
94 overdue · 25d worstThe shape of it
Every figure below is legible in the captures above. Nothing here is a projection of your book — it is the state of the demo data.
How it runs
An account enters with a segment and a playbook attached — 41 accounts sit at kickoff in the current view — and the clock on predicted TTV starts.
SSO, environments and security questionnaires land in the task queue with owners and due dates; 94 of them are late right now, counted in days.
Pilot success criteria and training move the account through integration and pilot while the predictor re-scores its time-to-value.
Cutover rehearsals precede the window — 64 go-lives are inside 30 days — and readiness is a percentage, not a hope.
One record
Onboarding is the first ninety days of the same record the rest of the estate serves after go-live.
The account record onboarding runs against is the one sales closed — playbook and segment carry forward.
CEDX DeskAfter go-live, the same account's questions become tickets; the launch history is the context.
CEDX LearningThe academy catalog carries a “Customer education” path — training the account's team is a play, not a webinar invite.
CEDX ProjectsLarger implementations read as project plans; the task queue here is their day-to-day edge.
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 playbooks, your accounts
Onboarding 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/onboarding. It runs on demo data, which the workspace labels on screen.
No — and we would rather say so here than on a call. The captures show customer onboarding: accounts, playbooks, go-lives. Employee onboarding in this estate runs through Recruiting, People and Learning.
By a demo model over seeded account data — stage, blockers, task lateness. The 61-day median against a 42-day target is the demo portfolio's figure, shown because it is legible in the capture.
Three signals, on screen: low health, open blockers, or a predicted TTV running long. One hundred forty accounts in the demo portfolio trip at least one.
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 find the task that is quietly 25 days late in your own launches.