{{ heroSub }}
Cepter helps prepare documents carefully, shows exactly what each recipient will see, and sends only when an authorised person decides to.
Six stages, all of them working in the pilot. Open any one of them in the prototype — each opens the real screen with sample data.
Each step below opens the real screen with sample data — a simulated preview of the preparation, signing and evidence experience.
A complete simulated walkthrough on fixed sample data: suggestions arrive as dashed review overlays, you accept, edit, reassign or dismiss each one, and the recipient preview proves that only accepted fields ever appear. No upload, no real document, no access granted.
Suggested fields are coming next, not available in Early Access. This is the distinction that will govern them: a suggestion will never become a recipient-visible field until a person accepts it.
Each one opens its own request, keeps what you asked for, and tells you where that capability actually stands.
{{ pageIntro }}
{{ pageIntro2 }}
The pilot is controlled and approval-based: you pick a plan, describe the workflow, and a person reviews it and sets you up — with an honest answer about whether Cepter is the right tool for the paperwork you actually have.
The v4 placement prototype is in this project and I read it directly, so this audit is from the source rather than from a status label. It is a single working Design Component: state, handlers and keyboard bindings are real. What it was not is connected — no navigation, no shell, no signer. This prototype now carries that placement work inside a connected application, and the rows below track what was kept, improved, consolidated or replaced.
Contrast: v4's muted grey #8b93a6 is 3.08:1 on white and fails AA. Everything here uses #657086 at 4.9:1.