Home/PE Portfolio Software/Value Creation Thesis
PE Portfolio Software

Building a software value creation thesis.

A software value creation thesis names the savings, sizes them, sequences them, and assigns them an owner, before the deal closes.

Building a software value creation thesis means turning the licensing and spend findings from diligence into a sourced, sized, and sequenced plan that the deal team can underwrite and the operating team can execute from day one. A thesis is not a vague belief that software cost can come down. It is a specific set of actions, each with a number, a timeline, and an owner, that together explain how much margin the software estate will yield over the hold and how that value will be captured.

The discipline matters because software is one of the most reliable and least competitive value creation levers available to a sponsor. It does not depend on market growth, pricing power, or operational heroics. It depends on knowing what the company runs, what it pays for, and where the two diverge, then acting on that knowledge methodically. A thesis built on that foundation can be underwritten with confidence at entry and delivered with discipline through the hold.

What building a software value creation thesis involves

A complete thesis has four layers. The first is the baseline: a clear picture of current software spend and the effective license position, so every claim is measured against reality rather than assumption. The second is the opportunity, sized and sourced: each saving, shelfware retirement, duplication removal, edition right sizing, renewal renegotiation, with a number attached and the evidence behind it. The third is the sequence: when each action happens, mapped to renewal dates and integration milestones, so the plan is executable rather than aspirational. The fourth is the risk: the audit exposure that must be remediated and protected, so the thesis captures value without creating a liability.

The risk layer is what separates a credible thesis from an optimistic one. Software savings done carelessly can create compliance gaps that a publisher prices in an audit, so the thesis must show how cost comes out without deployment falling below entitlement. The publishers that drive that risk, Oracle, SAP, Microsoft, IBM, and increasingly Broadcom for VMware, Salesforce and ServiceNow, are named in the thesis with their specific exposure, because as of June 2026 inherited and disputed licensing has produced eight figure claims such as SAP pursuing AB InBev for a reported 600 million dollars, reported by Reuters as of 2017. A thesis that ignores that risk is not a plan, it is a hope.

The four layers of a software value creation thesisA build from baseline to sized opportunity to sequenced plan to a protected, audit aware position.Building the thesis layer by layer1Establishthe baselineSpend and ELP2Size theopportunitySourced savings3Sequencethe actionsTo renewals4Protect thepositionAudit aware
A software value creation thesis built in four layers, from a measured baseline to a sequenced, audit aware plan.

Why the thesis must be built at entry

A software value creation thesis built after close is built late. The best moment to size the opportunity is during diligence, when the deal team is already reading the contracts and modelling the business, because the findings can then be underwritten into the deal and the price. A thesis built after the deal closes has to start from scratch, rebuilding the understanding that diligence already had, and it loses the months of the hold where the early savings could have been captured.

Entry is also when the thesis carries the most weight. A sourced, sized software opportunity in the investment case gives the deal team a concrete, defensible component of the value creation plan, one that does not depend on the market or the management team to deliver. Where other levers are contested or uncertain, software cost is measurable and within the buyer control, which makes it one of the more dependable lines in an underwriting and one of the first the operating team can show progress against.

The layers of a software value creation thesis and what each must show
LayerWhat it establishesEvidence requiredWhen built
BaselineCurrent spend and license positionContracts and deployment dataDiligence
OpportunitySized, sourced savingsUsage analysis per leverDiligence
SequenceWhen each action landsRenewal and integration calendarPre close
ProtectionAudit exposure remediatedEffective license positionDiligence to day one

Key takeaways

  • A software value creation thesis is a sourced, sized, sequenced plan, not a belief that cost can come down.
  • It has four layers: a measured baseline, sized opportunity, executable sequence, and protected audit position.
  • Software is a dependable lever because it is measurable and within the buyer control, unlike market dependent levers.
  • The thesis must be built at entry, during diligence, so it can be underwritten into the deal and the price.
  • The risk layer, naming the audit publishers and their exposure, separates a credible thesis from an optimistic one.

Recommendations for buyers

  1. Build the thesis during diligence. Size the opportunity while the contracts are already open so it can be underwritten into the deal.
  2. Source every number. Tie each saving to usage evidence so the thesis survives scrutiny from the investment committee.
  3. Sequence to the calendar. Map actions to renewal dates and integration milestones so the plan is executable, not aspirational.
  4. Include the protection layer. Name the audit risk publishers and their exposure so savings do not create a compliance gap.
  5. Assign owners before close. A thesis with no owner is a forecast, not a plan, and forecasts do not get delivered.

From thesis to delivered value

A thesis only matters if it is delivered, and delivery depends on continuity from the team that built it to the team that executes it. The diligence advisor who sized the opportunity holds the dataset, the contract analysis, and the savings logic. Handing the thesis to a fresh team after close means rebuilding all of that, losing time and detail, so the strongest delivery comes when the same understanding carries from diligence into the first hundred days and through the hold.

Delivery also depends on tracking. Each saving in the thesis carries a number and a date, so progress can be measured against the plan and reported to the board. That tracking is what keeps the thesis honest: a saving that slips can be chased, a saving that proves larger can be banked, and the cumulative delivery against the thesis becomes the evidence of value creation that the fund will present at exit. Without tracking, the thesis is filed at close and quietly forgotten, which is the most common reason a sound software opportunity is never realised.

How the thesis ties the programme together

The value creation thesis is the plan that the rest of the programme delivers. See the PE portfolio software advisory hub and the PE portfolio advisory service for the full approach. Related reading includes software cost as a value creation lever, reducing software spend to lift EBITDA, and the PE buy side software diligence playbook. This is commercial and licensing advisory, not legal advice.

Sizing the opportunity without overstating it

The credibility of a thesis rests on its numbers, and the temptation is to inflate them to make the investment case look stronger. That is a mistake. A thesis that overstates the opportunity sets a target the operating team cannot hit, damages trust with the investment committee when it misses, and can lead the deal team to overpay on the strength of savings that were never real. The discipline is to size conservatively, sourcing each number to evidence, and to present a range that distinguishes the savings that are near certain from those that are possible but contingent.

The near certain savings, retiring measured shelfware, removing clear duplication, are the floor of the thesis and can be underwritten with confidence. The contingent savings, larger consolidations, major renegotiations, depend on execution and negotiation and should be presented as upside rather than baseline. Separating the two gives the investment committee an honest view and gives the operating team a credible plan, and it protects the deal team from underwriting value that turns out to be conditional on outcomes outside their control.

A well sized thesis is therefore both ambitious and honest: ambitious in identifying every legitimate source of value, honest in grading those sources by certainty and sourcing each to evidence. That combination is what lets a software value creation thesis survive the investment committee, guide the operating team, and stand up at exit as a delivered track record rather than an unmet forecast. The work of building it well at entry pays back across the entire hold, which is why it deserves senior attention rather than a line in the diligence report.

Frequently asked questions

What is a software value creation thesis?
It is a sourced, sized, and sequenced plan that turns licensing and spend findings into specific actions, each with a number, a timeline, and an owner, explaining how much margin the software estate will yield over the hold and how it will be captured.
Why build the thesis at entry rather than after close?
Because diligence is when the contracts are already open and the business is being modelled, so the opportunity can be sized and underwritten into the deal and the price. A thesis built after close starts from scratch and loses months of the hold.
What makes software a dependable value creation lever?
It is measurable and within the buyer control. Unlike growth or pricing levers that depend on the market or management, software cost depends on knowing what the company runs versus what it pays for, then acting methodically on the gap.
How do you size the opportunity credibly?
Source every number to usage evidence and grade savings by certainty. Near certain savings like measured shelfware form the underwritable floor, while larger consolidations and renegotiations are presented as contingent upside, not baseline.
What stops a thesis from being delivered?
Loss of continuity and lack of tracking. If a fresh team inherits the thesis after close it must rebuild the understanding diligence already had, and without tracking each sized saving against its date, the thesis is filed at close and forgotten.

Build a software thesis you can underwrite

Book a confidential software M&A risk assessment and we will turn your diligence findings into a sourced, sized, and sequenced software value creation thesis.

Book a confidential call