Twenty-four field types
Signatures and initials, dates, dropdowns, radio groups, checkboxes, calculated formulas, file attachments, approve and decline — with conditional logic and validation on any of them.
Features
The work before the signature matters.
Prepare the agreement, check the details, then review exactly what will be sent. Use Cursiv yourself or give an authorised assistant a scoped role. Sending and signing remain separate human decisions.
Plan access and provider setup can affect individual capabilities. Check the live capability guide.
Prepare
Get the document ready without placing every field by hand.
Start from a PDF, a Word file, a reusable template or finished contract text. Add the signers, place fields, then check the draft before anyone sends it.
Reads the document for you
Finds the signature blocks and works out who signs where. It never invents a coordinate: it picks from what the text layer actually contains, and anything it cannot attribute is handed to you rather than guessed.
Templates with named roles
Save a prepared envelope once and send it for ever after. Building a template costs nothing, however many you make.
Bulk send from a CSV
One prepared template to a thousand recipients, each with their own fields filled in, tracked separately from the first send to the last signature.
PowerForms
A link anybody can open and sign without you sending anything — the form fills in who they are and starts the envelope on their behalf.
Word and Excel, converted
Office files become PDFs with the text layer intact, so anchor placement still works on a document nobody exported properly.
People and company details stay distinct
Keep private contacts, signer details and represented-company records separate. Unknown or unverified legal details remain clearly identified instead of being filled in by assumption.
Document branding separate from email
Choose a printing profile for logo, type, colour, margins, header, footer and company details. Invitation email branding is configured separately.
Send and sign
Routing that matches how the agreement actually moves.
Sequential, parallel, or both at once, with the roles real agreements need rather than the two most products offer.
Nine recipient roles
A notary recipient role is available for routing. Remote notary workflows are scheduled for Plan 014.
Signer verification
Access codes and email OTP are available. Advanced identity and liveness verification are scheduled for Plan 014. Email delivery is available. SMS and WhatsApp delivery are scheduled for Plan 014.
Draw, type or upload a signature
Typed signatures are set in a real hand and recorded as typed, so the certificate says which kind it was rather than implying the other.
Reminders and expiry
Chase on a schedule you set, with a cooldown so nobody is mailed twice in an afternoon. Envelopes can expire on their own.
Signing groups
Address a step to a group and let whoever gets there first sign for it — useful when any of four directors will do.
Correct and void in flight
Fix a wrong address or a misplaced field after sending. Void within an hour, before anyone has opened it, and the credit goes back.
Prove
A record the other side can check without asking us.
The part most platforms ask you to take on trust, and the reason this one exists.
Tamper-evident by construction
Every audit event is hashed together with the one before it, and the finished bundle is sealed against that chain. Alter either and verification fails.
Certificate of Completion
A standalone PDF recording every event, every IP address, every timestamp, which kind of signature each person applied, and the hash that ties it together.
Published to a public log
Every completed agreement is entered into an append-only RFC 6962 transparency log with Ed25519 signed tree heads. Anyone holding the certificate can prove it is in there, and that nothing already in it was changed.
A verifier you can run yourself
About two hundred lines of plain JavaScript that shares no code with anything that produced your document, needs nothing but Node, and holds no secret.
Agents
Hand the paperwork to a model. Keep the pen.
An assistant can prepare, revise and check a draft, then show you the exact review. Sending is a separate authorized action; signing and consent stay with each person.
MCP, with a published guide
MCP tools expose company and user profiles, contacts, templates, contract and document draft creation, versioned corrections, readiness checks, previews and exact-revision reviews.
It cannot sign
Not a permission you could switch on. There is no endpoint that applies a signature, and a test in the build refuses to let one appear.
Mandates, not instructions
Authority is enumerated per term with hard limits. A term the mandate does not name is a term the agent cannot touch, and nothing binds until a person on each side ratifies it.
Every agent action is attributed
Writes by an agent are recorded distinctly from people and from ordinary API calls, inside the same tamper-evident chain, naming the key it borrowed.
Negotiation
Settle the commercial terms before anybody signs.
Most platforms start when the document is final. Often the argument is about what the document should say.
Terms, offers and counters
Move on price, dates, quantities and free text in a structured exchange, with every move recorded and nothing agreed until both sides ratify.
Ratification stays human
Accepting ends a negotiation and ratifying binds it. Both are reserved for a person, on both sides, whoever or whatever did the negotiating.
Build on it
An API that reads like the product.
Everything the interface does, minus the one thing nothing may do.
REST, keys and webhooks
Create unsent drafts from templates, PDFs or finished contract text. Read profiles and contacts, place fields by text anchors, check readiness and preview, then correct with version checks.
Embedded signing
Embedded signing is not available before Plan 013.
Your brand, not ours
Brand colours, logos and wording are available. Custom sending domains, addresses and email white-labelling are scheduled for Plans 005 and 014.
Send one and see.
Core signing evidence is not held behind an upgrade. For every other item, the live capability registry separates plan entitlement from operational readiness.
Create your workspace