Running a portfolio-wide vendor program: what actually works
Shared vendors, group purchasing and a common renewal calendar can pay off. Master agreements, data sharing and ownership are where programs stall.
Every operating partner has had the same idea. Twenty portfolio companies all buy software, cloud, telecom, freight, travel and insurance. Pool the volume and the price drops. Some programs deliver exactly that. Many end up as a slide in the annual meeting deck and a preferred vendor list nobody opens.
The difference is rarely the vendors. It is how the program handles contracts, data and ownership.
Why the pressure is on
Operating improvement now carries more of the return. Preqin, citing Bain & Company's 2024 private equity report, noted that margin improvement had contributed "practically nothing" to industry returns, which Bain said is no longer sustainable as rates weigh on multiples. Accenture's December 2024 research found 84% of PE leaders want to drive operational value through procurement, and 58% admit it is difficult.
That gap between intent and execution is where most portfolio programs live.
Three models, in order of ambition
A common renewal calendar. One view of every material contract across the portfolio: vendor, annual value, term end, notice window, owner. No pooled buying, no shared contracts. Just visibility.
Group purchasing through an outside GPO. The portfolio joins an existing purchasing organization and companies opt into its pre-negotiated contracts. CoreTrust, for example, says it has more than 4,000 members, 125 or more pre-negotiated contracts and no membership fees, describing its model as "supplier-funded."
Sponsor-negotiated master agreements. The firm, or a team it appoints, negotiates a framework with a vendor, and each portfolio company signs its own order under it.
What works
The calendar works almost every time. It is cheap, it does not require anyone to switch vendors, and it changes behavior. When you can see that five companies renew the same CRM within 12 months, each renewal gets a benchmark and an earlier start. In our view most of the value in a portfolio program comes from this step, and it is the one most often skipped in favor of a vendor announcement.
Cross-company benchmarks work. Price per seat, per user, per circuit, per shipment. Companies inside one portfolio pay very different prices for the same product, and nothing gets a CFO's attention faster than seeing a sister company pay less.
Pooled buying works in commodity categories. Where the product is the same for everyone and switching is cheap (parcel shipping, travel, office supplies, mobile, some collaboration software), aggregated volume gets real discounts and nobody's operations change.
Opt-in with a visible price advantage works. Companies adopt a program contract when it beats what they have. They resist when told to.
What doesn't
Assuming a GPO price is the best price. Supplier-funded means the supplier pays the GPO. In healthcare, the GAO reported in 2003 that GPO administrative fees were generally expected to be 3% or less of the purchase price, with 2% the most common level in 2002, and that an earlier GAO pilot found using a GPO contract "did not guarantee" a lower price. Different industry, same economics. Treat the GPO price as a reference point, and benchmark it.
Mandating vendors. The portfolio company CEO owns the P&L and the operational risk. Forcing a switch to save a few points creates resistance, integration cost and a ready excuse when results slip.
Master agreements priced on volume nobody committed. Vendors price aggregate tiers on the assumption the volume shows up. When companies opt out or are sold, the tier breaks. Every master agreement should state what happens to pricing for a company after it leaves the portfolio. Without that, a buyer inherits a price that disappears at close, which becomes a diligence finding against you.
Cross-liability. Each company should contract in its own name, for its own volume, with no guarantees across companies and no obligations at the fund. A master agreement that makes one company responsible for another's minimums will be unwound by the first lawyer who reads it.
Data sharing is the hard part
Benchmarks need prices, and prices are confidential. Two problems come up.
First, vendor contracts often include confidentiality clauses that restrict sharing terms with third parties, including a sister company. Check before you circulate a spreadsheet. A program run by one party under NDA with each company, reporting anonymized benchmarks, solves most of this.
Second, some portfolio companies compete with each other or have different co-investors and minority holders. Pooling their supplier pricing raises questions that belong with counsel before the first data request, not after.
Our rule: collect contract terms and prices centrally, share benchmarks in ranges, and never show one company another's contract.
Who owns it
This is where programs drift. If everyone owns it, the calendar goes stale within two quarters.
The split that holds up: the firm owns the calendar, the benchmarks and the category strategy. Each portfolio company owns its contract, its decision and its savings. One named person at the firm runs the program. One named person at each company (usually the CFO) owns that company's renewals and answers for the notice dates.
Funding matters too. If the program is paid for by supplier fees, portfolio CFOs should know that, because it shapes which vendors get recommended. Eighty Twenty is paid only by clients, never by vendors, for exactly that reason.
For more on why this lever matters to the value creation plan, see the next lever is the vendor stack and our PE value creation work.
Start with the calendar. Ask each portfolio company for its top 25 contracts by annual value, with term end and notice dates, and build the combined view in 30 days. Then pick the three categories where four or more companies overlap. That is the scope of our Portfolio Vendor Desk, and it is a sensible first quarter whether you use us or not.
Sources: Preqin, VSS banks on Treya, profiting from private equity's struggle, Accenture, Driving outsized returns from procurement in private equity, CoreTrust, Private equity, GAO, Group Purchasing Organizations (GAO-03-998T).
Do private equity group purchasing programs actually save money?
In commodity categories where switching is cheap, pooled volume usually earns real discounts. A GPO price is not automatically the best price, so benchmark it before adopting it.
Should portfolio companies be required to use the sponsor's preferred vendors?
Usually not. Opt-in programs with a visible price advantage get adopted; mandates create resistance and give management an excuse when results slip.
What should a portfolio master agreement include?
Each company contracting in its own name, no cross-guarantees or fund-level obligations, and clear terms for what happens to pricing when a company leaves the portfolio.
Who should own a portfolio vendor program?
The sponsor owns the renewal calendar, benchmarks and category strategy. Each portfolio company owns its contracts and decisions, with a named owner, usually the CFO.
We would rather look at your numbers than talk about ours. Tell us the stage of the deal and we will tell you within a day whether the vendor base is worth a look.