Contract monetisation: recover the revenue your contracts already allow
A contract is signed for 200 users. Three years later 260 are logged in, and the invoice still says 200. Multiply that across seats, modules, API calls, indexation clauses and uplifts nobody applied, and you get the distance between what your contracts entitle you to and what you actually bill. Veridian Revenue Partners reconciles the two, sizes the gap in pounds, and shows your own team how to recover it: as true-ups, as upsell, and as new contracts on terms built for how software is bought now.
Part of our operator-led GTM advisory work, contract monetisation connects the contract book to the revenue it should produce.
Is this you?
Signs this is for you
- Your contracts carry usage terms, tiers, indexation or uplift clauses
- Billing has never been reconciled against entitlement, or not for years
- Your charging model was written before the product became what it is now
Signs it is not
- Below roughly £5m ARR, the recoverable figure rarely funds the work
- Perpetual-licence books with no usage, growth or indexation terms to work
The problem
Poorly managed contracts give up 8.6% of their value on average. That is World Commerce & Contracting and Deloitte, from a survey of more than 1,200 organisations. The 2014 study put the figure at 9.2%, so a decade of contract-management software has barely moved it. The best performers hold the loss to around 3%. The worst lose more than 20%.
Treat those as benchmarks rather than audited fact. The conservative numbers are bad enough: EY puts leakage at 1% to 5% of revenue, and MGI Research narrows it to 3% to 5% for most companies. For a £30m ARR software business that is £900,000 to £1.5m a year. Already earned. Never invoiced.
The causes are small and boring, which is why they survive. Simon-Kucher found only 35% of SaaS businesses apply annual escalators to multi-year contracts, and three quarters of those that do set them below 3%: a quiet 2% to 5% of revenue given away at signature. BCG, surveying 2,000 business leaders, found 59% of companies have nobody whose actual job it is to catch any of this.
And the money is nearly all margin. The product has shipped and the cost is spent, so recovered leakage lands almost whole on EBITDA. As an illustration: at a seven-times revenue multiple, every £1 of annual leakage you recover is worth around £7 of enterprise value. That is why investors ask about this before they ask about pipeline.
Where it hides
We reconcile what your contracts entitle you to charge against what you have billed, recover the difference, and install the rules that catch it next time. The usual places:
Missed billing
Live agreements where delivery outran invoicing.
Indexation never applied
CPI and RPI clauses written into the contract, forgotten at every anniversary since.
Unbilled entitlements
Seats, modules, API calls, storage and usage delivered against a contractual right to charge, never invoiced.
Uplifts never actioned
Annual increases the contract permits and the customer accepted, which the business never applied.
Read-only and archive licences
Access that carries a price and a right, routinely given away for free.
Dormant expansion rights
Pre-agreed growth triggers, ramps and true-ups that nobody ever pulled.
How it works
Four stages, in order. Each one pays for the next.
Reconcile
The contract lives in one system, usage in another, billing in a third. We put the three side by side and size the gap: by contract, by cause, in pounds.
Recover
We build the recovery process and coach your team to run it: who to approach first, what evidence to bring, how the conversation goes. Your people stay the face of the relationship. The customer sees their own usage against their own contract, and a confrontation becomes a true-up. Done properly, historic over-use converts into forward commitment rather than a one-off invoice, and customers stay customers.
Recontract
Every recovery conversation is an opening to reset the commercial relationship: longer terms, made an easy yes by the pricing and incentives behind them, and charging models that fit how customers actually consume, including the usage-based, outcome-based and AI pricing much of the sector is now introducing. A price rise is a design problem before it is a conversation. Timed and packaged well, it lands as value, not friction.
Embed
The rules, the cadence and the ownership stay with you, so the business keeps finding, recovering and recontracting long after we step back.
Built at scale, not borrowed from a textbook
In 2017 our partner started the commercial contracts function at a PE-backed UK business software group (20 operating companies, c.£1.6bn of ARR) as a team of one, and built it into the group's main engine for growth from existing customers: a £1.2m first-year target grown to £26.9m in the final year, nine consecutive years above plan, £142.7m booked against £123.7m of target.
Back-dated usage fees converted historic over-use into forward commitments, and upsell and cross-sell typically made up 30% to 40% of order value, because the conversation was about what the customer should be on, not what they owed. Relaunched as an adoption-led retention and expansion engine, the same programme held 120% net revenue retention and 90% gross across c.£375m of engaged ARR.
Churn shows up in adoption first
Protecting the contract book does not stop at billing. Churn risk shows up in usage months before it shows up in a renewal call, which is why that programme monitored 50,000 customers on adoption, usage and renewal signals: high usage pointed to the next product, low usage triggered a module swap to protect the renewal, and 70% of accounts engaged on a trigger converted. Customers who use what they bought renew what they use.
How engagement works
We scope every engagement to the problem: a fixed-term reconciliation to size the gap, a recovery and recontracting programme run with your team, or a capability build that leaves the discipline owned in-house. Where it fits, recovery work is paid as a share of what is recovered. No win, no fee. Deliverables and terms are agreed before we start, in writing.
What this is not
Not a billing system: software bills what it is told to bill, and the problem is what it is being told. Not a licence audit: no settlement letters, no enforcement, and your customer relationships come out stronger, not scorched. Not a strategy deck: the work happens in your contract book, with your team, and it stays when we leave.
Related insights
Start with a conversation.
Tell us what the commercial picture looks like and we will tell you, honestly, whether and how we can help. 30 minutes, no deck, no obligation.