CEDX Forms · Marketing
Forms are scored twice: completion on every field, and spam on every submission. The logic map shows the exact edge where 18% of your demo requests walk away — and the ledger keeps the spam visible instead of pretending it never arrived.
A required phone field after company size costs 28% of a contact form. That is not a hunch; it is an alert with the field named.
Runs on demo data. The chrome itself reads demo seed · no live collectors.
What it is
Describe the form — vendor intake with document upload — and fields assemble from the bank with order and required flags borrowed from the workspace's best-completion layouts. Tax ID, budget range and document upload arrive pre-flagged as high-drop. Deterministic demo, no live model — the screen says so.
The demo-request form, field by field: work email loses 1%, full name 2%, the phone question 3%, company name 6% — and the open use-case text area loses 18%. That edge is marked hottest on the map, with predicted completion of 54% for the form as drawn.
320 rows with channel, status, time-to-fill and spam score. An 18-second popup completion scores 48.9; a one-minute link completion scores 4. Partial stays partial — 53 in the sample — so follow-up has something to work with.
Product tour
Not a mockup and not a concept deck. This is what opens at /app/forms.
01 — Overview
The health ring reads 81 — spam plus completion — and the alerts explain themselves: a disposable-email cluster on the contact form, 14 domains sharing a temporal pattern; the phone field dropping 28%; an orphan owner after an org rotation.
02 — Generate
Three drafts in the queue with predicted completion next to each — 74%, 56%, 28% — and the field bank's drop-risk warnings carried into the draft instead of discovered after publish.
03 — Logic map
Because the map prices each edge, the fix is usually a move, not a rebuild — the screen shows a partner intake shortened by four fields in the chart annotations, and the completion line responding.
04 — Submissions
The disposable-email cluster alert and the spam column are the same system: 67 submissions sit above threshold, scored and visible, so nothing is silently lost and nothing is silently trusted.
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 routing and owners — the orphan-owner alert is theirs to clear before a lead sits unrouted.
route mix · 98 routed
Reads per-edge drop like ad spend: the 18% edge gets fixed before the budget behind the form goes up.
hottest edge · −18.0%Captures on QR and embed channels at booths and counters — the channels are rows in the same ledger as the homepage form.
channels · QR, embed, popupThe 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
Fields come from the bank with order and required flags borrowed from the best-completion layouts in the workspace.
The same form ships as link, embed, popup or QR — every channel lands in one ledger.
Submissions get a spam score and forms get a completion score; both are visible, neither is silent.
Hot field steps are ranked so the worst edge gets fixed first — 23 in the current queue.
One record
A submission is the start of a record, not the end of a widget. Routing, journeys and the CRM read the same people.
The campaigns whose spend drives the form traffic, with cost per lead on the budget line.
CEDX JourneysCompleted submissions enroll straight into nurture paths — spam-scored first.
CEDX CRMThe route mix is the CRM's queue: new, routed, closed — and the 41 nobody worked.
CEDX PagesThe sections the forms live inside, scored by the same conversion lens.
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 forms, your routing
Forms 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/forms. The product chrome itself reads demo seed · no live collectors.
By scoring it, not hiding it. Every submission carries a spam score; 67 sit above threshold in the demo ledger, visible in the same table as the good ones, so review is possible and nothing is silently deleted.
Yes, per edge. The logic map prices each field's loss — 1% on work email, 6% on company name, 18% on the open text area — and flags the hottest edge on the map.
They stay in the ledger as partial — 53 in the sample — with their channel and time-to-fill, so follow-up works from data instead of absence.
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 which field on your contact form would show up at 28% drop.