The invoice arrives for software you no longer recognise. You look up the name, discover it is a team licence three colleagues once requested, and then realise the real problem: the notice period expired two weeks ago. Another year of payments for something nobody uses any more. As an IT manager, you have become the contract owner of dozens of SaaS subscriptions without ever asking for the role. Managing SaaS contracts is a task that crept in unnoticed, usually without an overview and without the means to keep one.
Managing SaaS contracts means keeping control over end dates, notice periods, SLAs and the owner of each subscription. Not licence usage, but the contract terms that determine when money starts leaking away. That is exactly where most organisations have a gap.
How you became the contract owner of dozens of SaaS subscriptions
SaaS sprawl rarely happens on purpose. A marketing team buys a design application on the company credit card. HR takes out a recruitment subscription. Finance starts a trial that quietly rolls on. Each subscription solves a concrete problem, but together they form a collection of contracts that nobody tracks centrally.
Eventually the bill lands with IT. You are technically responsible for integrations, uptime and security, so the contractual responsibility comes with it. Yet you think in terms of connections and uptime, not notice periods. The contracts themselves sit in mailboxes, on SharePoint, in a spreadsheet one colleague maintains, or in the head of someone who has since left.
Your ERP sees the invoice, not the contract
The instinct is: “Surely our spend is already in AFAS or Spendcloud?” True. Your ERP or spend system neatly records what you pay and to whom. But an invoice is not a contract. The system sees the amount, not the terms beneath it.
What your ERP does not show:
- The end date and renewal clause of the subscription
- The notice period and the date by which you have to act
- The SLA terms: the uptime and support you were promised
- Who within the organisation owns the contract
That gap between spend and contract content is where things go wrong. You only see the cost once the invoice arrives, and by then the notice deadline has often already passed. Anyone who recognises this pattern from an old spreadsheet knows how quickly the limits of Excel are reached here.
Automatic renewal: how the money leaks away
Many SaaS contracts renew automatically. When the contract ends and you do not cancel in time, a new term begins, often a full year. For consumer contracts, Dutch law (the Wet Van Dam) protects you against automatic renewal with long terms. That protection does not apply to business contracts. Whatever the contract says stands.
Do the maths once. A fifty-user team licence costs several thousand euros a year. Miss a notice period of, say, three months before the end date, and you pay for the entire year, even if you had already planned to stop. One missed deadline is money you can see leaving straight away. And it lands on your desk.
That makes the notice deadline the most expensive moment in the entire contract lifecycle. Not the signature, but the point at which you must act to avoid paying on.
The four risks of SaaS contracts without an overview
Without a central overview, the risks pile up:
- Missed notice period. The end date passes unnoticed and you are locked into a new term.
- Paying for unused licences. You pay for accounts of staff who have left or for software the team no longer opens.
- No view of SLA compliance. You do not know whether the supplier delivers the promised uptime and support, so you cannot steer on it.
- Vendor lock-in. Without insight into terms and migration arrangements, you miss the moment to renegotiate or switch.
These four are connected. The first risk to solve should be the notice period. As long as that goes unmonitored, you lose money regardless of anything else you put in place.
What getting a grip on your SaaS contracts really means
Control starts with a single overview of all SaaS contracts, showing the end date, notice period, associated SLA and responsible owner for each subscription. To that you add an alert that goes off before the notice deadline, not after. That turns the notice period from a surprise into a planned decision: renew, renegotiate or stop.
This is where GRIP makes the step from contract administration to contract management. GRIP does not measure licence usage and does not replace your ERP. GRIP places a contract management layer over your existing systems: the content of your SaaS contracts becomes visible alongside the spend your ERP already records. Kaia, the AI in GRIP, reads the contract documents and recognises terms, notice periods and KPIs automatically, so you do not have to comb through every PDF by hand. Your data stays within Europe, which is rarely a minor point for an IT manager acting as contract owner.
On the contract dashboard you see at a glance which subscriptions expire when and who is responsible for them. That overview is exactly what is missing the moment finance asks why you are still paying for a subscription.
From Excel to overview in five steps
You do not need to turn this into a months-long project. Start small and concrete:
- Gather every SaaS invoice from the past twelve months from your ERP. That is your starting list.
- Find the contract for each subscription and note the end date, notice period and SLA.
- Assign an owner to each contract. Without an owner, nobody watches the deadline.
- Flag the subscriptions nobody uses any more and plan the next notice moments.
- Set alerts on the notice periods, so that every deadline becomes a decision instead of a missed opportunity.
You can work through the first four steps in an afternoon. The fifth is the difference between losing money every year and steering on it structurally.
Frequently asked questions
What does managing SaaS contracts actually mean?
It is about keeping control over the contract terms of your software subscriptions: end dates, notice periods, SLAs and the owner of each contract. Not measuring licence usage, but the arrangements that determine when you need to act to stop money leaking away.
Why is my ERP or spend system not enough?
Your ERP records the invoice and the amount, not the contract content. Notice periods, renewal clauses and SLA terms sit in the contract documents themselves. Without that content, you only see the cost once the invoice arrives, often after the notice deadline.
Does Dutch consumer renewal law apply to business SaaS contracts?
No. The Wet Van Dam protects consumers against automatic renewal with long terms. That protection does not apply to business contracts. Whatever the contract says about renewal and cancellation is binding.
How much does a missed notice period cost?
It depends on the subscription, but a team licence quickly runs to several thousand euros a year. Miss the notice period and you pay for the full new term, even if you wanted to stop the software. One missed deadline is money you can see leaving straight away.
Does GRIP replace my ERP or a SaaS management tool?
No. GRIP places a contract management layer over your existing ERP and does not measure licence usage. Registration stays in your ERP; managing end dates, notice periods and SLAs happens in GRIP. The two complement each other.
Where is my contract data stored with GRIP?
The contract data you put into GRIP is processed exclusively on European platforms, under European law. GRIP is a Dutch company and holds ISO 27001 certification for information security.
How do I start without setting up a large project?
Gather your SaaS invoices from the past year, find the end date and notice period for each subscription, assign an owner and set alerts on the notice moments. You can do the first inventory in an afternoon.
Want to see what that overview looks like in practice? See how GRIP solves this and place your SaaS contracts alongside your ERP in a single dashboard.