Ask anyone who’s spent real time in legal ops or procurement what actually goes wrong with contracts, and signature is rarely the answer. Getting the right people to approve and sign something is a bounded problem — it has a clear start, a clear end, and a clear list of who’s supposed to act at each point. What happens after signature is the part that’s genuinely open- ended, and it’s where the real damage in this category tends to happen: an auto-renewal clause nobody flagged, a cancellation window that closed three weeks before anyone noticed, a vendor SLA nobody was tracking because the person who signed the contract left the company eight months later and took the context with them.
None of that is a signature problem. It’s an ownership problem. A contract gets signed by whoever the approval chain routed it to, and then, structurally, it belongs to no one — until a deadline arrives and it suddenly, urgently, belongs to whoever gets the angry email.
Why this is a genuinely different problem than routing
It’s tempting to think of this as the same kind of problem a delegation-of-authority engine already solves — after all, it’s still “who’s supposed to act, and when.” But the shape is actually different in a way that matters. An approval step exists only while a contract is being routed, before it’s fully executed, and it’s typically gated by sequence: step two doesn’t matter until step one clears. A post-signature obligation — renew the insurance certificate by March, deliver the SOW milestone by Q2, review the auto-renewal sixty days out — fires after execution, isn’t blocked on anything else finishing first, and can recur on its own schedule indefinitely. Treating it as a smaller version of the approval-routing problem would be solving the wrong shape of thing.
What’s real in Contrayo today, and what isn’t
We’d rather say this plainly than let a features page imply more than is true. Contrayo does not have automated obligation tracking yet — no renewal reminders, no recurring compliance tasks, no assignee separate from whoever approved the contract. That’s a real, open gap, not a hidden or half-built feature we’re quietly not mentioning.
What does exist today is smaller, but real. A contract’s key dates — effective date, expiry, auto-renewal date, cancellation notification deadline — are visible right on the contract list, not buried in a document someone has to open and read. That’s visibility, not automation: nothing proactively tells you a deadline is coming, but the information is no longer something you have to go looking for contract-by-contract.
We also already have a working notification system, built first for a different purpose: the moment an approval step becomes actionable, whoever’s eligible — including someone temporarily standing in for an absent approver — gets notified automatically, computed from the exact same eligibility logic that decides whether they’re actually allowed to act, not a separate, looser copy of it. That system was deliberately built as a generic hook, not a routing-specific one-off, specifically so a different kind of event — a deadline approaching, an obligation coming due — could plug into the same mechanism later without a redesign. That’s real, working infrastructure. It is not, today, obligation tracking. Using it for that is future work we haven’t built, and we’re naming that distinction directly rather than letting “we have a notification system” quietly stand in for “we solved the renewal problem.”
Why we’re saying this now, instead of waiting until it’s built
It would be easier to write this post once obligation tracking exists and skip straight to “here’s how we solved it.” We’re writing it now because the problem is real and worth naming honestly even before the solution is, and because we’d rather a prospective customer know exactly what’s built today and what isn’t than discover the gap themselves after they’ve already signed up. If tracking what happens to a contract after signature is the thing costing your team real money today — a missed cancellation window, a renewal nobody meant to let happen — start a free trial and see where tracking after signature stands today.
