CEDX Sign · Sales & CRM
Every envelope carries a status, a recipient count, days in flight and a stall score — so “waiting on signature” stops being a feeling and becomes a list you can work, with the audit trail already written behind it.
The highest-stall envelope in the demo workspace scores 96 and holds $640K. The suggested fix is not “follow up” — it is: send the nudge, switch to parallel signing if safe, reassign the idle sender.
Runs on demo data. The Northline signature workspace in the chrome is the demo tenant, not a customer.
What it is
The envelope list shows type, party, status, recipient progress, days, value, authentication method and sender. A voided envelope at 0 of 3 recipients and 15 days reads exactly like the story it is — and the auth column shows what was asked: ID check, SMS code, access code, knowledge-based or email.
90 templates, 58 active, with sends over 90 days and completion percentage on every row. The mutual NDA completes at 94% across 112 sends; an evaluation license manages 54% — and the difference is the kind of thing you fix in the template, not in the reminder.
400 events with timestamp, event type, envelope, actor and detail: created, viewed, reminder sent, auth passed, declined, expired. 133 completion certificates exist because the trail does — the evidence is a by-product, not a feature you pay extra to switch on.
Product tour
Not a mockup and not a concept deck. This is what opens at /app/sign.
01 — Overview
320 envelopes: 133 completed, 101 in flight, 38 scored high-stall. The status bars break the book down — sent 28, delivered 24, viewed 24, waiting 25, declined 16, voided 28, expired 17 — and the alerts price what is stuck.
02 — Envelopes
Each row is an envelope with its party, recipient fraction, days in flight and dollar value — $2.40M waiting at 1 of 3 recipients for 14 days at the top. Filter chips cover every state from draft to in flight.
03 — Templates
Templates carry roles, sends and completion rates: board consent at 92%, support SLA addendum at 91%, an amendment renewal at 54%. Low completion on a high-volume template is a design problem the row makes visible.
04 — Audit trail
The event stream is the memory: a decline at 16:46, a reminder sent by the system at 19:28, an auth passed at 08:50. Filter by signed, viewed, declined, reminder, auth failed or voided — or export the lot.
Who runs it
Roles, not references. We have no named customers yet, so nobody in these photographs is quoted, credited or claimed as one.
Watches their own envelopes by stall score. The nudge, the parallel route, the reassignment — the screen suggests the move, they make it.
stall 96 · $640K
Owns the templates and the audit trail. Completion rates tell them which document needs a rewrite; the event stream answers every dispute before it starts.
133 certificates
Reads completion as a funnel metric: 69% of closed envelopes complete, and the gap between sent and completed on the chart is pipeline dying of paperwork.
completion · 69%The 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
Roles, auth method and document come from the library row — which is why its 90-day send count and completion rate matter before you click.
Sent becomes delivered becomes viewed becomes waiting. Each transition is an event with a timestamp, so “did they even open it” has an answer.
The stall score fires the alert; the alert names the move — nudge, switch to parallel, reassign. The 3-day reminder default is one toggle, workspace-wide.
Completion writes the certificate and the event stream stands behind it. Months later, the trail still says who signed, when, after which reminder.
One record
A signature request is the last mile of a commercial record. Sign reads that record, and its events land back on it.
The “out for signature” status on the contract repository is these envelopes, and the signed paper lands back in the repository.
CEDX QuotesThe 77 e-sign envelopes past SLA on the Quotes pulse are this desk's envelopes, with the same clock.
CEDX ProposalsThe mutual action plan's last line — order form plus e-sign packet — is an envelope from this library.
CEDX CRMThe signer is a contact on the account, and a completed envelope is activity that lifts the deal out of the idle column.
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 templates, your envelopes
Sign with the rest of it
Questions
Yes. Every screenshot is a capture of the running build at /app/sign, on demo data. The demo workspace is named in the chrome.
A per-envelope score built from days in flight, recipient progress and views. 38 envelopes score high-stall in the demo workspace, and each alert arrives with a fix — nudge, parallel route or reassign — rather than a red dot and silence.
A completion certificate plus the event stream: created, viewed, reminded, authenticated, signed, each with timestamp, actor and detail. 133 certificates and 400 events are in the demo workspace and browsable on the Audit trail screen.
Per envelope, yes. The list shows email, access code, SMS code, knowledge-based and ID check in use across the demo book — and 50 stalled recipients have an “offer alternate auth” fix attached.
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 how long your own paper sits between sent and signed.