ContrayoAn approval matrix built from your own rules
Most contract tools ship a single approval workflow and call it customizable because you can reorder a couple of steps. Contrayo works differently: your organization sets the criteria (contract type, dollar value, signing entity, business unit), and the delegation-of-authority engine decides, contract by contract, exactly who has to approve and who has to sign.
Contract created
Type, value, signing entity, and business unit are set on the record.
Policy evaluates the criteria
Your org's current DoA policy version matches those criteria to a routing rule.
Routed to the right people
Approvers and signer are notified, including any delegate covering someone out.
The delegation-of-authority engine
A policy is a versioned set of routing criteria, approval steps, and named actors — authored once, then applied automatically to every contract that matches. Change the policy and the next version routes differently, without touching the contracts already in flight under the old one. Coverage for someone out of office is handled the same way: a configured delegation grant makes their approvals available to a stand-in for a defined window, without changing the underlying policy at all.
Segregation-of-duties and sequential step gating are enforced automatically — the same person who approves a contract's approval step can't also be the one who signs it, and a step doesn't become actionable until the ones ahead of it in sequence clear.
Everything else a contract needs, without a separate tool for each piece
Contract records
Type, status, counterparties, signing entity and business unit, and every key date — effective, expiry, auto-renewal, cancellation deadline — in one record, not scattered across a shared drive.
E-signature routing
The same policy that decides who approves a contract also decides how it gets signed — routed automatically once the approval chain clears, instead of a manual handoff to a separate signing tool.
Notifications
The moment a contract reaches someone's step — including a delegate standing in for an absent approver — they're notified. Nothing sits waiting on a step nobody knows is theirs to act on.
Admin controls
Org admins manage roles, deactivate accounts, and author new policy versions through a real graphical builder — not a support ticket to a vendor to change a workflow.
Reporting, integrations, and a couple of newer additions
More pieces that ship alongside the engine, at different levels of maturity — said plainly here rather than folded quietly into the list above.
Tenant analytics dashboard
Cycle time, contract volume by type and status, DoA approval bottlenecks, and a renewal pipeline — one page, computed from your own org's real contract and routing history. Available to any member of your organization, on every plan; nothing on it is AI-generated.
Email filing, Outlook, and Zapier/Make
File an email and its attachments onto a contract record straight from Outlook, or through the same API endpoint via Zapier or Make. Bulk-import your users, counterparties, and contracts too, on every tier including self-serve.
Outbound webhooks
Subscribe an endpoint to contract-created, routed, approved, rejected, and fully-executed events. Deliveries are signed so you can verify they really came from Contrayo, retried automatically on failure, and an endpoint that keeps failing gets disabled with an admin notification rather than dropping events silently. Part of the public API — available to any org with an API key today, on every plan.
Installable as an app
Add Contrayo to your phone or desktop home screen and it opens like a real app, not a browser tab, with the shell available even on a spotty connection. It never queues an approval, rejection, or signature offline, though — anything that changes a contract needs a live connection, on purpose, so the audit trail stays honest.
AI chat assistant
Ask about your own contracts and approvals in plain language — what's stuck, what's waiting on you, how a policy routes a given deal — including a short Renewal Brief for a contract coming up for renewal. The same assistant can also walk you through the product itself: ask how to do something and it can highlight the actual button or panel on your screen, not just describe where it is. Off by default: an org admin turns on the AI capability behind it before anyone in that org sees the chat launcher, and its answers haven't yet been checked against a live model response, so treat early output with the same judgment you'd apply to any new assistant.
English-language contracts only. Contrayo's AI features reliably understand English-language contract content — a contract written in Spanish or French isn't read or evaluated accurately yet, regardless of which language your Contrayo interface is displayed in.
English, Spanish, and French
The Contrayo interface — navigation, settings, contracts, and approvals — works in all three languages. The policy builder, in-app help, and legal documents stay English-only for now.
See it from where you sit
The same engine looks different depending on whether you own the policy or you're the one driving a deal through it.
For Legal
How the approval matrix, segregation of duties, and delegation answer the questions in-house counsel keeps running into.
For Procurement & Ops
How notifications, signing routing, and published pricing help the person driving a contract through the process, day to day.
What a seat costs
Every tier above is priced and published. Check the number that matches your team size.
View pricing