Quote to cash
A contract template that re-renders is a template that eats your edits.
Somebody rewrites a liability clause for one customer. Something touches the record. The document regenerates from the template and the clause is gone — and nobody finds out until the dispute.
Resolve the placeholders once, store the result, and stop.
Drafting
Placeholders are filled once, and the text becomes the contract.
Six kinds ship with a default each — a master agreement, a statement of work, a mutual non-disclosure, an order form, a client agreement, and everything else. Bodies are written in plain text with placeholders for the workspace, the customer, the deal, the order, the contact and the date.
They are resolved at the moment the contract is created and the result is stored. From then on it is a document, not a template — so a rep can edit any clause and nothing will ever overwrite them.
A placeholder with nothing behind it resolves to nothing, on purpose, so saving a half-finished draft never breaks.
This agreement is made between your legal entity and
Smoke & Co Logistics B.V. of Rotterdam,
for the services described in order SO-2026-00311,
commencing 1 October 2026.
- The substitution is deliberately unsophisticated —
Contract bodies are written by people, and a full template language in that position is an attack surface nobody needs. The reasoning is recorded in the code rather than left implicit.
- Revision supersedes, it does not overwrite —
The source is snapshotted — its body and the state it was in — and a new numbered draft is created with the link between them. The old one is marked superseded rather than replaced.
- Voiding kills every outstanding link in the same act —
A signing link that was forwarded on stops working the moment the rep voids the contract.
- Approval is the same machinery as everything else —
With the drafter barred from approving or rejecting their own, unless the workspace has deliberately allowed it.
Renewal
The renewal opens itself, before anybody has to remember it.
A daily lookahead finds every signed contract whose term ends within four months and starts tracking it. Five reminders fire, once each. At ninety days your renewal playbook is applied; at sixty the renewal deal is opened.
So the renewal exists as a deal, in the pipeline, being forecast, while there is still time to do something about it — rather than appearing in a spreadsheet the week it expires.
- A contract out for signature with no live link expires itself —
Swept nightly, and the owner is told. Rather than sitting as "sent" forever.
- Wet ink is recorded as evidence too —
A contract signed on paper leaves a real record, marked as such so it is never confused with a cryptographic signature.
- A signed contract cannot be revised —
It can be superseded by a new one. The signed document itself is final.
›Where do the numbers come from?
Each contract is numbered from its own sequence, and revising one mints a new number with the link back to what it supersedes — so a chain of revisions reads in order rather than as unrelated documents.
›How many signers?
One. There is no countersignature on a CRM contract, no signing order and no parallel signers. If your process needs a counter-signed document, plan for that — statements of work elsewhere in the platform do support it.
›Can a customer decline a contract?
The signing page offers signing. A customer who does not want to sign tells you, and the contract is voided or revised. Quotes do have an explicit decline with a reason.
›Can I resend or extend a signing link?
The link is shown once when it is sent. Today, minting a fresh one means revising the contract — worth knowing before closing that dialog.
›Can I link a contract to an order?
The relationship exists on the record. Setting it from the order screen is a gap we would rather name than have you find.