In a mid-sized company, contracts don't disappear with a bang. They disappear quietly — first the 2019 hosting agreement drops off the radar, then the cold-storage service contract, until finally an email lands saying "your termination window ends next week" and you realise something has slipped.
In one of our projects, a 28-person distribution company discovered that its backup internet line had been auto-renewing for three years at 45% above the starting price. The contract had a silent-renewal clause unless terminated three months in advance — and nobody was watching that date. The annual overpayment on that one line: 7 200 PLN. During the audit we found 14 similar contracts. Nobody stole anything. Nobody was negligent. It was just that the deadline spreadsheet — kept by one person — had not been refreshed for two years, because that person had moved to sales.
Contract management in an SME doesn't have to be an SAP-scale project. It has to be disciplined. Below are the four things that are enough for a small company.
A single contract register
If answering "how many active service contracts do we have" requires three emails to three different people, you don't have contract management. You have a scatter of individual worries spread across mailboxes.
The register — even a simple one, in SharePoint, Airtable or a dedicated ERP module — needs the minimum: counterparty, subject, signing date, end date, notice period, annual value, business owner on your side. Nothing else is required to start. Later you add indexation clauses, exclusivity clauses, attachments — but don't start from completeness, start from people entering anything at all.
The tool doesn't matter. What matters is that it's one tool. An Excel on a network share also works — provided it's actually one file, not "Contracts2024.xlsx" with the bookkeeper and "Contracts current v3.xlsx" with the CEO. A common mistake is buying a contract management system before the underlying process exists at all. The system won't create the discipline. People have to.
- Pick one location, one register owner and a fixed update cadence.
- Enter every contract above a chosen threshold (e.g. 2 000 PLN annually) — the rest can wait.
- Every new contract goes into the register on the day it is signed, not "when there's a moment".
- Once a quarter, someone walks the register top to bottom and looks for gaps.
Alerts before the deadline
A contract without an alert is a delayed-action mine. The notice window slips by quietly, the silent indexation clause tacks another 6–8% onto your invoice, and you find out from the bill.
One alert "a week before" is not enough. You need three: 90 days, 60 days and 30 days before the renewal cut-off. 90 days is the moment for the decision — renew, negotiate, look for alternatives. 60 days is the deadline for having quotes in hand. 30 days is the last window to terminate or amend. Alerts must go to the business owner, not to "the office" — because the office will forward them too late.
Technically this is an hour's work in Outlook, Google Calendar, Power Automate or the ERP itself. Politically it is much more, because it forces you to decide who really owns each contract. That question is valuable on its own: if nobody can answer it, you have just found a real problem.
Categories and priorities
Not every contract deserves equal attention. A paper-supply contract can quietly renew forever. A support contract for your ERP cannot.
A simple split: critical contracts (production, sales or accounting stops without them: ERP, telephony, internet lines, general liability insurance, warehouse lease), important contracts (SaaS subscriptions, machine service, licences, property insurance), routine contracts (office supplies, small services, catering). Each category has a different review frequency and a different set of people who need to hear about a coming deadline.
For most SMEs, two categories are enough: "contracts whose breakage will hurt us" and "the rest". The first list is short — typically 10 to 20 items. The second is long but doesn't need daily attention. Focusing energy on the short list saves more money than any tool.
- Write down the contracts whose mid-week expiry would stop operations.
- Assign named owners to each of these — not "the IT department", a specific person.
- For the rest, an annual bulk review is enough.
- Low-value routine contracts can quietly renew — as long as that is a conscious decision.
Who has access
Contracts contain sensitive data: rates, terms, penalty clauses. The CEO wants visibility across everything, the CFO across most, department heads across their own, salespeople across their customers. A thoughtless "everyone sees everything" leads to leaks. "Nobody sees anything beyond their own patch" leads to nobody watching contracts at all, because everyone assumes someone else is.
A simple rule: at least two people must see every contract. Never one. Someone leaving the company cannot walk out with the only knowledge of a critical agreement. We have seen this more times than we would like — an IT person leaves and with them the information about when the mail server support contract expires. Three months later the company finds out from the first invoice after a rate hike.
- Ensure at least two people have access to every critical contract.
- Revisit access on every personnel change — offboarding is the natural moment.
- Salespeople see their customer contracts, but not procurement.
- The register must survive the departure of any single person.
What next
Contract management in an SME is not SAP and it is not "contract lifecycle management for 80 000 PLN a year". It is a register, alerts, categories and access rules. Four things. Each of them a week's work, if someone sits down and just does it.
If you don't know how many contracts are open and when they expire — start with an hour's conversation where we count the riskiest items together. The first consultation is free.
Contracts in an SME don't disappear with a bang. They disappear quietly — one by one, until an audit turns up 7 000 PLN a year overpaid on a single internet line.