Fields
Layout that already knows where people sign
Signature, initials, date, title, and custom text boxes are proposed from headings and from phrases like “IN WITNESS WHEREOF.” You lock a field so a packet cannot close without it.
Platform
The desk behind the seal.
Signed-ai is not a chat that happens to attach a PDF. It is a signing desk with five working parts: reader, fields, route, identity, and vault. People still sign. The software remembers why.
Reader
A one-page brief before anyone is asked for ink.
The reader names parties, governing law, money, term, termination, liability, data, and anything that looks unusual next to your playbook. It does not rewrite the contract. It refuses to let a signature be the first time someone looked.
Sample brief · MSA 1842
What the desk would show
Parties: Northline Studio and Hale Freight. Term: 24 months, auto-renews 12. Cap: none on indemnity — flagged. Governing law: Delaware. Data: subprocessors listed in Exhibit C. Signature blocks: two, pages 11 and 12.
Working parts
Everything that happens around the mark.
Route
Order, parallel, or a human gate
Send to both founders at once, or require counsel before the CEO. Watchers receive the executed copy without being asked to sign. Reminders are quiet and dated.
Identity
Enough proof for the stake
Email link for routine NDAs. One-time code for offers. Optional ID check and liveness when the packet is a deed-adjacent form or a high-value order. The certificate records which bar you set.
Vault
The file and the story stay together
Executed PDF, original, brief, and certificate sit in one packet. Search by counterparty, hash, or matter. Export a zip that counsel can keep offline.
Certificate
What the audit trail actually contains.
A pretty signature image is not evidence. The log is. Every packet writes a timeline you can produce without reconstructing email.
16:01:12 ETPacket created · MSA-1842.pdf · SHA-256 9f3c…a12esealed
16:01:19 ETReader brief generated · 4 flags · 2 signature blocksok
16:08:44 ETRoute: counsel gate → CEO · SMS code requiredset
17:22:03 ETM. Hale viewed pages 1–12 · consented to electronic recordsintent
17:22:41 ETElectronic signature applied · method: drawn · IP hashedbound
17:40:09 ETCountersignature complete · certificate attached · copies sentclosed
Next
See how an electronic signature is supposed to work.
The law cares about intent, consent, and association. The platform is built to capture all three.