Contract governance without buying software
We ask a simple question in the first week of most engagements: how many contracts does the company have? Almost nobody knows.
Summary
- Most companies cannot say how many contracts they have or where the signed copies are, because contracts are treated as a legal task that ends at signature.
- Before any software, build five things: an inventory, an obligation register, a renewal calendar, an approval matrix with a clause playbook, and a quarterly read of the contract set as data.
- A contract platform inherits whatever order you already have. Buy one when volume is the constraint, not disorder, and only once a named owner is keeping the spreadsheets current.
We ask a simple question in the first week of most engagements: how many contracts does the company have?
Almost nobody knows. Not approximately, not by category, not where they are. The agreements live in inboxes, in three different drives, in a WhatsApp thread, and on the personal laptop of someone who left last year.
This isn't carelessness. It's what happens when contracts are treated as a legal task that ends at signature, rather than an operating system that runs for years afterwards.
The usual response is to look at contract management software, decide it's expensive and premature, and do nothing at all. That's the wrong conclusion. You don't need a platform yet. You need five things, and four of them are spreadsheets.
First, what the software actually does
The category is called contract lifecycle management, or CLM. The name is doing real work: it covers the whole life of a contract, not just the signing.
A CLM platform typically handles the request coming in from sales, drafting from an approved template library, routing for approval based on value or risk, tracking versions through negotiation, e-signature, storage in a searchable repository, alerts for obligations and renewals, and reporting across the whole contract set. Ironclad, Icertis, DocuSign CLM, Agiloft and SpotDraft are common names. You pay a recurring licence, and then for an implementation project.
Two reasons not to start there.
The obvious one is cost. The more important one: a CLM inherits whatever order you already have. If your contracts are scattered across inboxes with no index, the platform gives you scattered, unindexed data in a more expensive place. Implementation consultants will tell you the same thing: the first phase of every CLM rollout is building the inventory you could have built yourself.
So the five things below aren't a cheap substitute for the software. They're the same discipline, done manually, and they're the prerequisite whether or not you ever buy a tool.
One: know what you have
Start with an inventory. One row per contract: counterparty, type, start date, end date, renewal terms, value, who owns the relationship, and where the signed copy lives.
You'll find three things, and every company finds the same three:
- Contracts nobody remembers signing. Usually a vendor commitment or a partnership from two years ago that's still running.
- Contracts with no signed copy. The negotiation happened, work started, and the executed version was never saved. Sometimes it was never signed at all.
- Different versions in different places. Which one is final? Nobody is sure.
Building the inventory takes a couple of days for a company under fifty people. It is the single highest-value thing on this list, because you cannot manage what you cannot see.
Two: extract the obligations
A contract isn't only a record of what you agreed. It's a list of things you have to keep doing.
Reporting commitments. Insurance you promised to maintain. Service levels. rights you granted. Exclusivity you conceded. Data handling you undertook. Notice you must give before certain actions.
These are buried in clauses, and at signature they're read by a lawyer and then by nobody. So a service credit obligation sits in an agreement while your operations team has no idea the commitment exists, until a customer claims against it.
An obligation register pulls each of these out into a trackable list with an owner and a frequency. It's the least glamorous item here and the one that prevents the most avoidable failures.
Three: put renewal dates on a calendar
Auto-renewal is where money leaks quietly.
A vendor contract renews for another year unless you cancel 90 days ahead. Nobody tracks the date. It renews. You've committed to twelve more months of something you'd decided to stop using.
The same mechanism works in your favour on the customer side, and is equally unmanaged: you don't know which customer contracts are approaching renewal, so you don't start the conversation early enough, and you renegotiate from a weak position.
One sheet: contract, renewal date, notice deadline, decision owner, and a reminder set for two weeks before the notice window opens. Review it in the monthly finance meeting alongside collections. Ten minutes.
Four: decide who can sign what
Most companies have no written answer to a basic question: who is allowed to commit the company, and up to what?
The two failure states are equally bad. Either the founder approves everything, which becomes the bottleneck the business grows around. Or nobody approves anything, and a salesperson agrees to uncapped liability to close a quarter.
An approval matrix fits on one page. Thresholds by contract value, by term length, and by risk category: anything with uncapped liability, exclusivity, IP transfer or a non-standard indemnity goes up regardless of value.
Pair it with a short playbook: for each key clause, your preferred position, your acceptable fallback, and the point at which it must be escalated. This is what lets someone other than the founder negotiate. Without it, every deal routes through one person because nobody else knows what can be conceded.
If you want the substance for that playbook, what each commercial contract clause actually does covers it clause by clause.
Five: read your contracts as data
This is the part almost nobody does, and it's where contracts stop being an administrative burden and start being useful.
Your contract set contains answers your MIS doesn't:
- Committed revenue. How much of next year is already contracted, versus hoped for.
- Customer concentration. What share of revenue sits with your top three, and when those contracts end.
- Renewal risk. How much revenue is up for renewal in the next two quarters.
- Price escalators. Which contracts allow you to raise prices, and which lock you in.
- Change-of-control exposure. How many customers can walk, or must consent, if you're acquired.
That last one is worth pulling before you raise, not during. Change-of-control consents scattered across key contracts turn up in diligence and become a lever for the buyer or investor, usually at the point when you have the least room to argue.
Once you have the inventory, a quarterly one-page summary of these five numbers belongs in your board pack. It changes the conversation from "how did sales do" to "what's actually contracted".
What this looks like in practice
For a company under a hundred people, the whole thing is:
- A contract inventory (spreadsheet)
- An obligation register (spreadsheet)
- A renewal calendar (spreadsheet, with reminders)
- An approval matrix and clause playbook (two pages)
- A single repository with a strict naming convention, where only executed copies live
- A named owner: one person who maintains all of it
That last item is the one that fails.
Tools don't fail; ownership does.
If contract governance is everyone's job it's nobody's, and in six months the inventory is stale and you're back to searching inboxes.
When is a CLM worth it? When volume, not disorder, is the constraint. If you're signing a few hundred contracts a year, several people are drafting, and the spreadsheets are genuinely being maintained but creaking, buy the tool. It will pay for itself in approval routing and search alone.
If the spreadsheets don't exist, or exist and aren't maintained, software won't fix that. It'll just cost more.
Where to start this month
- Build the inventory. Two days.
- Pull renewal dates and notice deadlines out of it into a calendar with reminders.
- Write the approval matrix. One page, one hour.
- Name the owner.
The obligation register and the playbook can follow next quarter. Those four steps alone will surface a renewal you'd have missed and a commitment you didn't know you'd made.
Frequently asked questions
What is CLM, and do startups need it?
CLM stands for contract lifecycle management: software that covers a contract from request and drafting through approval, signature, storage, obligation tracking and renewal. Most early-stage companies don't need it yet, and because a CLM inherits whatever order you already have, the manual version comes first.
What is a contract obligation register?
A list of everything a company has committed to do under its contracts, pulled out of the clauses and given an owner and a frequency. Without it, obligations agreed at signature sit unread until a counterparty claims against one.
How do you avoid missing a contract renewal or notice deadline?
Put every renewal date and its notice window into one calendar, with a reminder before the window opens and a named decision owner, and review it monthly alongside collections. Auto-renewal clauses commonly ask for 30 to 90 days' notice, so the decision falls months before the date anyone has in mind.
If you want the five things set up around the contracts you already have, our compliance and governance work starts with the inventory.
Current as at September 2026. General guidance on contract operations and process, not legal advice: take advice on your specific contracts.
How useful was this article?
One tap. It tells us what to write more of.
The next one
Get what we publish next, by email.
Working notes on raising, borrowing, protecting, growing and structuring capital in India. One email a week at most, and you can leave any time.
We use your address only to send this. See our privacy policy.
We store your address to send you these emails and nothing else. See our privacy policy.
Related reading
