Contracts, prepared with care
Prepare from a PDF, template or finished contract text. Review the signers, fields and exact document before sending. An assistant can prepare it; only you authorize sending, and each person signs for themselves.
Starter bundle
R245 once
25 credits · VAT included
Per envelope sent
1 credit
Unused credits do not expire
Cedar & Finch
PROFESSIONAL SERVICES
AGREEMENT FOR SIGNATURE
A clear scope, agreed terms, and a copy for everyone when complete.
The parties agree to the services and terms set out in this document.
Signature · date
Signature · date
24
Field types
Signatures to calculated formulas
9
Recipient roles
Witnesses and notaries included
18
Agent tools
None of which can sign
R5.70
A document, at volume
No seat, no minimum
The same model at either end
A 25-credit bundle is R245, and larger bundles lower the cost per envelope. If a few people send regularly, the seat calculator shows when a monthly plan costs less.
A practice that signs three a year
Roughly eight years of paperwork, bought in one go. No renewal to forget, no month billed for having sent nothing.
Sends
3 a year
Pays
R245
once — 25 credits, no expiry
Per user, per month
Nothing
A firm running steady deal flow
Everyone who touches a contract has their own login. Nobody shares one to save a seat.
Sends
2 000 a year
Pays
R13 700
a year — R6.85 a document
Per user, per month
Nothing
A lender at industrial volume
The same self-serve product, on a rate that falls as the volume rises. No seat count to negotiate before you can start.
Sends
200 000 a year
Pays
R1 140 000
a year — R5.70 a document
Per user, per month
Nothing
Because seats cost nothing, nobody in your business has a reason to share a login — which is the quiet thing per-seat pricing does to an audit trail, and the reason so many of them name the wrong person.
A clearer way to pay
Buy credits when you need them. They do not expire, and you are not billed for a month in which you send nothing.
See all credit bundlesA credit costs
R6.85at 500
Buy them when you need them. They do not expire, and there is no month in which you are billed for having sent nothing. R5.70 at 2 500.
A product tour, at your pace
Step through a sample agreement workflow. This is an interactive illustration, not a recording: choose each stage, pause as long as you like, and see what stays in your control.
Upload a PDF, reuse a template, or give an assistant the finished wording. Add the people who will sign and keep the draft unsent while you work.
Draft · unsent
Document illustration changes when you select a tour step. The fields and names shown are fictional examples.
No autoplay. Use the step buttons or previous and next controls.
Capabilities
What the service does
Schedule 1
Routing that matches reality. A notary recipient role is available for routing. Remote notary workflows are scheduled for Plan 014.
Twenty-four field types. Signatures and initials, dates, dropdowns, radio groups, calculated formulas, file attachments — with conditional logic and validation on any of them.
Templates and bulk send. Save a prepared envelope as a template with named roles, then send it to one person or a thousand from a CSV.
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.
Certificate of Completion. A standalone PDF recording every event, every IP address, every timestamp, and the hash that ties them together.
Tamper-evident by construction. Audit events are hash-chained, and the finished bundle is sealed against that chain. Alter either one and verification fails.
The record
Each event is hashed together with the one before it. Removing a step, backdating a view, or editing a signed page breaks the chain — and the Certificate of Completion says so in plain language.
Then every completed agreement is entered into a public, append-only log. Anyone holding the certificate can prove the record is in it, and that nothing already in it has been altered — without our help, and without taking our word for it. Most platforms ask you to trust them. This one hands you the arithmetic.
Before the signing
Open a negotiation on a template and settle the numbers first — fees, dates, payment terms — in a structured exchange where every offer and counter is recorded against the side that made it. When both sides ratify, the agreement is drawn up with those values already in it and sent to sign.
Annual fee
R90 000 – R150 000
Then a person ratifies — on each side — and the agreement is drawn up and sent to sign.
Agents
Claude or another MCP-compatible assistant can use a scoped API key to read workspace details, prepare or correct a draft, check readiness and build a review of the exact version. It reports what it changed instead of guessing at the product surface.
Sending is a separate permission and requires an explicit instruction for the reviewed revision. Assistants cannot apply a signature, consent or ratify for a person. Agent actions are attributed in the audit record.
Authority is enumerated per term with hard limits. A term the mandate does not name is one the agent cannot touch, and free text is never delegated at all.
An agent that reaches past what it was granted is stopped, and the attempt is written down — so you can see whether it is misconfigured or your limits are too tight to close.
Agent actions are recorded distinctly from people and from API calls, inside the same tamper-evident chain as the signatures.
Developers
Read company and user profiles, manage scoped contacts, create drafts from documents or finished wording, place fields by text anchors, validate and preview. Draft edits use version checks; sending requires an exact review and an idempotent send request. Embedded signing is not available before Plan 013.
Read the API reference
curl -X POST https://your-app/api/v1/agreements/prepare \
-H "Authorization: Bearer $CURSIV_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"externalId": "support-agreement-example-001",
"source": {
"kind": "contract",
"subject": "Support agreement",
"documentName": "Support agreement",
"contractMarkdown": "# Support agreement\n\nThe provider will supply the agreed support services. Fees and service scope require review.\n\n```signature\nProvider | Example Provider | Representative\nClient | Example Client | Representative\n```",
"recipients": [
{ "name": "Example Provider", "email": "provider@example.test", "type": "signer", "routingOrder": 1 },
{ "name": "Example Client", "email": "client@example.test", "type": "signer", "routingOrder": 2 }
],
"signingOrderEnabled": true,
"signatories": [
{ "role": "Provider", "recipient": 0 },
{ "role": "Client", "recipient": 1 }
]
}
}'Draft creation never sends. Validate and preview the current version; only send after a person reviews it and explicitly instructs an authorized send.
If you already use something else
We are not going to list every feature we have against every feature they have; that is a long table and it is not the reason anyone moves. These two are.
A new workspace opens with 30 credits on it. That is 30 agreements — signed, sealed and in the log — before anyone asks you for a card.
Create your workspace