ContrayoKnow who has to approve it, before anyone has to ask
If you're in-house counsel, this is probably familiar: a contract lands, and figuring out who needs to sign off (especially once there's more than one legal entity or business unit involved) means checking a spreadsheet, digging up an old email thread, or just asking around. Contrayo's approval-matrix engine makes that question answer itself.
One policy, applied automatically to every contract
Your organization defines the criteria — contract type, value thresholds, jurisdiction, and which legal entity or business unit is involved — and Contrayo decides, contract by contract, exactly who has to approve and who has to sign. Nobody has to remember the rule or maintain it in their own head, because the engine is the thing enforcing it.
The business-unit and legal-entity matching is ancestry-aware, not exact-match: a routing rule written for "Finance" also applies to everything under Finance in your org's structure, and the same is true on the legal-entity side for subsidiaries signing under a parent. If your company has real structure — subsidiaries, divisions, cost centers — the policy follows that structure instead of forcing you to write one rule per leaf node.
Controls that hold whether or not someone remembers them
Segregation of duties, enforced automatically
When your org turns it on — the default — the same person who approved a contract's approval step is blocked from also being the one who signs it, within that contract's routing. That's a control that used to depend on someone catching it manually; here it's enforced by the system every time.
Sequential and parallel steps, in one policy
A real approval chain often isn't one flat list — two people need to sign off in parallel, then one person needs to sign after both of them clear. Contrayo expresses that in a single policy, and a step can't be acted on until everything ahead of it has cleared.
Coverage that doesn't require a policy edit
When someone's out of office, an admin grants a colleague coverage for their approval steps over a real date range. The delegate becomes eligible automatically for that window, and who was authorized to act on a given day stays reconstructable later, including after a correction.
A rejected contract doesn't lose its place
If a contract gets rejected and comes back revised, it resubmits into the routing already in progress by default — only the affected steps reset, not the whole chain. An org that wants a full re-evaluation against the current policy instead can configure that too.
What's in a Contrayo contract record
Type, a status your org names and orders itself (not a vendor's fixed pipeline), counterparty, signing entity, business unit, value with an explicit provenance — manually entered, extracted-but-unconfirmed, or confirmed — and every key date: effective, expiry, auto-renewal, cancellation-notification deadline. An SOW can reference the MSA that governs it. It's one place to look, not a search across a shared drive and a dozen inboxes. That provenance distinction is tracked on every record today; using it to gate routing decisions is real groundwork the engine was built to support, not something it enforces yet.
Your policy, your builder — not a vendor's support queue
Policies are authored through a real, structured builder in the app itself. Changing how approvals route is something your org does directly, versioned, with the previous policy staying exactly as it was for contracts already routed under it — not a change request filed with a vendor and a wait for it to land. Before anything is even created, the same engine can also answer a hypothetical question directly: given a contract's shape, who would have to approve it and how would it get signed.
Go deeper on how it works
The DoA engine
How versioned policies, priority-ordered templates, and delegation fit together.
E-signature routing
How the native/third-party signing decision gets made, and today's real limit.
For Procurement/Ops
The same engine, from the perspective of the person driving a deal through it.
What it costs your legal team
Real per-seat pricing, published now — nothing for in-house counsel to chase down.