Private equity and family office technology spend

Your companies are probably buying the same things separately. I build a portfolio view of shared vendors, prove the savings at one company first, then take the terms to the rest.

The portfolio Diagnostic

Each portfolio company signs its own point-of-sale, payments, ERP, telecom and ecommerce contracts, with its own renewal dates and its own pricing. Nobody at the sponsor sees the list. The same vendor often sells to three of your companies at three different prices.

I start with one company. The Technology Spend and Contract Diagnostic runs five weeks for a fixed fee and produces a renewal calendar, a spend baseline reconciled to the ledger, and a sized savings and risk register. The vendor list is built so it can be laid next to the next company's. Once the first company proves the savings on its invoices, the terms and the calendar go to the rest of the portfolio.

After an add-on acquisition, the same work runs as post-acquisition integration: two of everything, an integration playbook, and an independent owner of the technology side of the deal. I owned the technology workstream that put 265 locations, three legal entities and 3,000+ users on one ERP after a merger, and led the technical cutover on a nine-month deadline, on time and on budget.

If you are still pre-close

Most PE technology diligence reports get the technology right and the operating model wrong. They catalog the stack, identify risks, produce a heatmap, and recommend consolidation. What they miss is whether the technology organization can actually execute on the investment thesis over the hold period.

A clean tech stack means nothing if the team cannot ship. An ugly tech stack can be fine if the operating model is healthy. The gap between what a diligence report typically delivers and what the operating partner actually needs to decide is wider than most people admit.

I have sat in the technology seat of a large North American retail network during and after an acquisition, on both sides of the same transaction: sell-side diligence, then the technical cutover on the buy side. Diligence usually asks what is in the stack. The operating partner actually needs to know whether this technology organization will deliver the value creation plan, and what it is committed to paying while it tries. The PE technology diligence checklist covers the pre-close questions.

What PE technology diligence actually needs to surface

The standard diligence report answers a set of technology questions that almost never make it into the investment committee conversation. It documents the stack. It lists vendors. It flags risks using a red-yellow-green heatmap. All of that is fine. None of it is the answer the operating partner is trying to reach.

The questions that actually matter on day one of ownership are operational.

Is the technology spend aligned with the investment thesis? In most portfolio companies I have looked at, a meaningful share of the technology budget funds legacy debt that is not producing forward value. Whether that matters depends entirely on the thesis. A margin-expansion thesis cares about it more than a revenue-growth thesis.

Does the team have the capability to execute the value creation plan? Or will new leadership be required, and if so, in which roles, by when, with what reporting line. This is the question most diligence avoids because it is uncomfortable to answer. It is also the one that most often separates a thesis that ships from one that does not.

Where are the hidden integration and data debts? The kind that will constrain future growth, acquisitions, or carve-outs. Point-to-point integrations nobody fully understands. Master data that cannot support reporting at the level the board will expect by year three.

What technology decisions must be made in the first 100 days to make the thesis deliverable, and who will make them? Deferring these decisions is the most common failure pattern in post-close technology execution. Not bad decisions. Deferred decisions.

Pre-close diligence

Standard window is 2 to 3 weeks from kickoff to final deliverable. The deliverable is a technology risk and opportunity assessment tied to the investment thesis, not a generic IT audit. Coverage includes the stack, spend profile, team capability, integration surface, data maturity, and vendor concentration risk. The output is a document the operating partner can actually use in the IC memo and the first 100-day planning conversation, not a 60-page deck that gets filed.

The depth varies by thesis. A platform acquisition where the target will absorb three future add-ons needs a sharper read on integration architecture than a standalone majority investment. A thesis that depends on digital commerce growth needs real diligence on the data layer, which is often where the thesis actually breaks.

My experience leading the technical cutover of a cross-border retail acquisition is operationally relevant here, without requiring anything confidential to be shared. The questions that surfaced during integration are the same ones a sharper pre-close read would have surfaced before the papers were signed.

Post-close value creation

The first 100 days is where most technology value creation either takes shape or quietly dies. The organization is open to change, the thesis is fresh, and decisions that would be politically impossible in year two are straightforward in month one. Operating partners who know this compress the work accordingly.

The interventions that typically matter inside those 100 days: operating-model redesign where the thesis requires it, vendor rationalization where spend is clearly misaligned, data foundation work to enable the reporting the board will expect by quarter two, ERP consolidation scoping if multiple ERPs exist, and selective modernization tied to specific thesis levers like e-commerce acceleration, margin expansion through pricing and inventory, or cross-portfolio shared services.

None of these are generic. All of them need to be tied to a specific thesis lever, owned by a specific executive, and tracked on a cadence that the board will actually review. Anything else is theater.

Portfolio monitoring and quarterly reviews

For PE firms with multiple portfolio companies, a quarterly technology review cadence across the portfolio creates visibility that most operating partners currently lack. The format is simple: one standardized read per company, reviewed on a rotating cadence, focused on the three or four metrics that actually matter for the thesis at that stage of the hold.

What separates a useful review from a slide-reading session is whether the questions on the agenda are ones the CIO cannot answer from a dashboard. Open the conversation with what is behind schedule, what decision is stalled, and what would unblock it. Close with a clear next-quarter commitment. Skip the status-update pantomime.

How I help sponsors

Three steps, each earning the next. The sponsor usually opens the door; the portfolio company CFO is the buyer of each Diagnostic. Pre-close reads are scoped separately, two to three weeks against the thesis.

For CFOs

Technology Spend and Contract Diagnostic

In five weeks you get a renewal calendar, a spend baseline, a risk inventory and a sized list of what is recoverable, for a fixed fee.

You provide the contracts, 12 months of accounts payable data and six to eight interviews.

Learn more

Frequently asked questions

What is a portfolio Diagnostic?

The Technology Spend and Contract Diagnostic run at one portfolio company first, with the vendor list built so it can be compared across the others. Once the first company proves the savings, the same terms and the same calendar go to the rest. Each company keeps its own readout; the sponsor gets the portfolio view.

How quickly can you turn around a diligence engagement?

Standard window is 2 to 3 weeks from kickoff to final report. Compressed timelines under 2 weeks are possible for a narrowly scoped tech review, but affect depth. Timelines longer than 3 weeks usually indicate scope that has expanded beyond technology into operational or commercial territory.

What industries do you cover for PE diligence?

Multi-site retail, consumer manufacturing with retail or wholesale channels, and distribution are where the operational depth is deepest. I ran technology reporting to the CFO at a 184-location home furnishings retailer and led the technology function at an apparel manufacturer. Other multi-site sectors are possible with appropriate scoping.

Do you work under NDA?

Yes. Standard practice. Most diligence engagements are under NDA from the first call, and I will sign the fund's standard mutual NDA without negotiation on non-material terms.

Do you advise on CTO or VP Technology searches post-close?

Yes, both on the search criteria and on the interview process. The Fractional Technology Executive role covers the gap: a fixed number of days a month in the first months after close, when the value creation plan needs technology decisions made before a permanent leader is in seat.

Your companies are probably buying the same things separately. Find out at one company first. Start with a 30-minute call.

Technology Spend and Contract Diagnostic

Before you sign or renew, know what you are committed to.

The Technology Spend and Contract Diagnostic takes five weeks, for a fixed fee. You get a renewal calendar with every notice date, a spend baseline reconciled to your ledger, and negotiation positions for your top five vendors.