A signature that knows what it signed
Any product can collect a signature. This one arrives attached to the decision it came out of, and leaves behind a sealed record of both.
Signing order
What is left on the day somebody disputes it
Every open, every view, every signature, and a seal that breaks if the document changes. The least glamorous screen in the product, and the one that decides whether a signature holds.
It knows what it is for
A signature envelope carries the decision it came out of. Open a signed document and the reasoning, the approvals, and the stage history are one click away, not in somebody's inbox.
Counterparties need nothing
People outside your tenant sign by link, with no account and no download. A template decides, per role, who signs in the app and who follows a link.
It ends with a record
Every completed envelope produces a sealed, timestamped certificate with a full audit trail. Retention and legal hold apply to it like anything else on the platform.
What is actually in it
Four areas, and the details that decide whether a signing programme runs itself or eats somebody's week.
Sending, and knowing what will happen first
Most signing mistakes are made at the moment of sending. The send screen answers the questions people usually discover afterwards.
- See exactly what sending will do, who it reaches, and in what order, before it is done
- Send to many recipients in one pass, with names and roles resolved as you type
- Set a signing order per role, or let everyone sign at once
- Decide per role whether somebody signs in the app or follows a link
- Attach a Decision Sheet by name rather than by identifier
- Delegate a signature to somebody else, and the invitation follows them
Templates that survive contact with reality
A template is only useful if the tenth send behaves like the first. Fields, rules and formats travel with it.
- Conditional rules, field formats and radio groups survive being saved into a template
- Template folders, versions, and a way back to one you archived
- Manage a template from its card, or look at one without opening the editor
- Prefill fields from platform data, so a signer confirms rather than retypes
- Field level attachments, so a signer can hand back a document of their own
- Saved views, reminder schedules, and escalation when a signature goes quiet
Identity, evidence, and the seal
The part that matters when somebody disputes it, years later.
- A signing certificate with the full event trail: opened, viewed, signed, and by whom
- Cryptographic sealing with an RFC 3161 timestamp from a trusted authority
- Notary sessions somebody can join, check on, and get out of
- Attestation and acknowledgement flows for policies, not just contracts
- A counterparty can verify a signed document later without an account
- Retention schedules, legal hold, and write once storage for what has been signed
Running a signing programme, not a document
One envelope is easy. Two hundred a month is the actual problem.
- A queue that shows what is outstanding and who it is waiting on
- One Reports and Export tab, with the window you are looking at exported as you see it
- Reminders swept by a single worker, so nobody gets the same nudge four times
- Blocked and corrected envelopes handled explicitly rather than silently reissued
- Signatures surfaced on mobile, where people already look for their work
- Everything an agent can do over MCP, gated by the same permissions a person has
It is not a separate product
Signing sits inside the platform, so the signature lands where the reasoning already lives.
Decisions
The envelope names the decision it implements, and the decision shows what was signed.
Board portal
Resolutions and minutes go out for signature and come back sealed.
Compliance
Attestations and acknowledgements become evidence automatically.
Canvas
Drop a signature envelope onto a board and see its status beside the work.
Built for the day somebody disputes it
Sealed certificates, RFC 3161 timestamps, a complete event trail, retention schedules, legal hold, and verification that works years later without an account.