Built from clauses, not from copy-paste
There is a clause library and a builder that assembles the contract from it, plus your own templates and a template marketplace. The difference from a Word document copied off the last deal is that you know which clause is in which contract — and when a clause changes, you know who it affects.
What the contract commits you to, as dated items
Obligations are recorded explicitly: what must be done, by when, by whom. Milestones and payment schedules likewise. The contract calendar shows what falls due, and recurring billing runs from the contract rather than from a parallel list someone else maintains.
Amendments and change requests have their own flow — a contract has a history, not just a current version.
Electronic signing, with a defence for disputes
Sending for signature runs as an envelope flow, with signers and order. The verification screen is built for the scenario that actually matters: document hash, seal present and valid, timestamp from the accredited authority, certificate identity and the signer audit trail.
It is not a "signed" tick — it is what you produce when the other side disputes it.
The dossier, printed as one thing
The contract, its amendments, its obligations and its history print as a complete dossier. That is the form in which a contract is presented to an auditor, a lawyer or a court, and it is not assembled by hand from eight files.
Worth knowing
The risk in a signed contract is rarely the clause you did not read; it is the date you missed — a renewal notice, a milestone, an indexation. That is why obligations are dated records in the system rather than sentences in a file.