companies forming a consortium to build infrastructure
Your PE parent company calls. They want the five PE portfolio companies to share a single data platform instead of each paying a vendor $2M/year. You are asked to represent your company in the consortium. Who pays what? Who controls the roadmap? And what happens when one company wants features the others don't need?
A consortium is a binding agreement where multiple companies pool Capital Investment to build shared infrastructure. Operators care because it can slash Cost Per Unit - but only if the cost sharing formula is fair, the governance gives you real influence through weighted voting, and you Budget for the build running over.
A consortium is a group of companies that form a binding agreement to jointly fund, build, and operate infrastructure none of them would build alone. Each member contributes Capital Investment and gets access to the shared Asset.
The key distinction from a merger: consortium members stay independent. They don't combine Balance Sheets or P&L statements. They cooperate on one specific thing - a shared platform, a logistics network, a compliance system - while competing everywhere else.
Think of it as cost sharing with teeth. The binding agreement specifies who pays what, who controls decisions through weighted voting, and what happens when a member wants out.
Consortia hit your P&L in two places:
Cost Reduction. If five companies each spend $2M/year on the same capability, a consortium that delivers it for $4M total drops each member's cost to $800K - a 60% reduction. That flows straight to EBITDA.
Execution Risk. Shared infrastructure means shared dependencies. If the consortium's platform goes down, every member's Revenue is at risk. If governance is slow, your Time to Value on new features stretches from weeks to quarters. And multi-company builds almost always overrun on Budget because requirements negotiation across independent companies is slower than internal prioritization. Plan for 30-50% overruns on the build phase and stress-test your break-even math accordingly.
For PE Operators specifically, consortia across PE portfolio companies are common. The Holding Company sees redundant spend across its Portfolio and wants Efficient Allocation. Your job is to make sure the cost sharing is fair to your company - not just optimal for the Portfolio.
A consortium has four moving parts:
1. Scope - What exactly are we building together? The narrower the scope, the easier the governance. "Shared data warehouse" works. "Shared everything" doesn't.
2. Cost sharing formula - Who pays what share. The principled approach uses the Shapley value: charge each member their average marginal contribution across all possible joining orders. In practice, most consortia use simpler proxies - Revenue-weighted splits, equal shares, or contribution proportional to each member's usage volume.
3. Governance - How decisions get made. Typically weighted voting where voting power tracks financial contribution. Critical: define what requires unanimous consent (scope changes, new members) vs. simple majority (feature prioritization, vendor selection). Also specify resource consumption limits per member to prevent free-riding - members drawing disproportionate support or customization relative to their contribution. This is the most common operational failure mode in real consortia and the binding agreement must address it explicitly.
4. Exit terms - What happens when a member leaves. This is where most consortia fail to plan. Can a member exit? What are their Liquidation Discounts on sunk contributions? Who absorbs their share of Fixed Obligations?
The binding agreement codifying all four parts is the entire structural integrity of the deal. Without it, you have a handshake and a prayer.
Form a consortium when:
Do not form a consortium when:
A PE Holding Company has five PE portfolio companies (A through E) each paying $1.8M/year for separate compliance systems. They propose a shared platform estimated at $3.5M to build and $1.2M/year to operate. Each company's Outside Option is to keep paying $1.8M/year. The platform has a 5-year Time Horizon before it needs replacement.
Total consortium cost over 5 years (base case): $3.5M build + (5 x $1.2M operate) = $9.5M. Per year across all five members: $1.9M/year.
Stand-alone cost over 5 years per company: 5 x $1.8M = $9.0M.
Equal split: $9.5M / 5 = $1.9M per company over 5 years, or $380K/year. surplus per company: $9.0M - $1.9M = $7.1M over 5 years ($1.42M/year).
But equal split may not be fair. Company A has 40% of total Revenue and will generate 50% of the compliance workload. Company E has 5% of Revenue and minimal workload. Revenue-weighted: Company A pays 40% x $1.9M/year = $760K/year (saving $1.04M/year vs. stand-alone). Company E pays 5% x $1.9M/year = $95K/year (saving $1.705M/year).
Sensitivity Analysis on build overruns. Multi-company builds routinely overrun 30-50% because requirements negotiation across independent companies is slower than internal prioritization. At a 40% overrun, the build costs $4.9M instead of $3.5M. Total 5-year cost rises to $10.9M, or $2.18M/year. Company A's share becomes 40% x $2.18M = $872K/year (still saving $928K/year). Company E's share becomes 5% x $2.18M = $109K/year (still saving $1.691M/year). The deal still works - but margins shrink materially, and 40% is optimistic for some multi-company builds.
Governance structure: weighted voting by contribution share. Company A gets 40% of votes, Company E gets 5%. Unanimous consent required for scope changes. Simple majority for quarterly feature prioritization. The binding agreement should also cap resource consumption per member (support tickets, customization requests) proportional to contribution - otherwise heavy users free-ride on light users' contributions.
Exit clause: any member can leave with 12 months notice. Departing member forfeits sunk Capital Investment but is released from future Operating Investments. Remaining members absorb the share proportionally.
Insight: Every member is better off than their Outside Option - that's the minimum bar. But the split matters. Equal cost sharing subsidizes the heavy user and penalizes the light one. Revenue-weighted splits align contributions with usage. Separately, verify stability: check that no subset of members would prefer to pool among themselves or go alone. If any coalition can do better without the full consortium, the allocation needs renegotiating. Fairness of the split and stability of the coalition are distinct requirements - a good binding agreement satisfies both.
Your company (Revenue: $50M) is invited to join a consortium with two larger companies ($200M and $300M Revenue) to build a shared logistics network. Build cost: $8M. Annual Operations: $2M. Your Outside Option is a vendor contract at $900K/year. The larger companies' Outside Options are $2.5M and $3.5M/year respectively.
Revenue-weighted split: your share would be 50/(50+200+300) = 9.1%. Annual cost to you: 9.1% x $2M = $182K/year. Build contribution: 9.1% x $8M = $727K.
Your 5-year consortium cost: $727K + (5 x $182K) = $1.64M.
Your 5-year stand-alone cost: 5 x $900K = $4.5M.
Looks great - $2.86M in savings. But examine governance. You have 9.1% of votes. The two large companies have 90.9% combined. They can outvote you on every feature priority and roadmap decision.
Sensitivity Analysis on overruns: if the build overruns 40% to $11.2M, your build share rises to $1.02M. Your 5-year cost becomes $1.93M - still saving $2.57M vs. stand-alone. The cost math survives realistic overruns. Governance is the real risk here, not the numbers.
Execution Risk assessment: if the consortium roadmap diverges from your needs, you end up paying for a platform optimized for $200M+ companies while your $50M operation needs simpler tooling. Your sunk Capital Investment of $727K plus the Implementation Cost of migrating to your vendor alternative is your real exposure if you need to exit later.
decision rule: the savings are real but governance concentration is a failure mode. Counter-offer: join only if critical decisions (scope changes, technology choices) require unanimous consent, not just majority vote. If they reject that, your Outside Option at $900K/year is cleaner.
Insight: Raw cost savings don't justify a consortium if governance lets larger members capture the roadmap. Your Outside Option is your Bargaining leverage - use it to demand governance protections or walk away.
A consortium is a binding agreement for shared infrastructure - members stay independent but pool Capital Investment on a specific Asset with a defined cost sharing formula. Budget for 30-50% build overruns in your break-even analysis because multi-company requirements negotiation is slower than internal prioritization.
The Shapley value provides a principled fair split based on each member's marginal contribution. Separately, verify that the allocation is stable - meaning no subset of members prefers to break away and go it alone. Fairness and stability are distinct requirements, and a good consortium binding agreement must satisfy both.
Governance structure - especially weighted voting rules and unanimous consent requirements - matters as much as the cost formula because it determines who controls the shared Asset's roadmap and who can free-ride on shared resources.
Ignoring governance in favor of cost savings. Operators fixate on the EBITDA impact and skip the fine print on weighted voting structure and unanimous consent requirements. A 60% Cost Reduction means nothing if the consortium builds the wrong thing because you have 5% of the vote.
Using equal cost sharing when members have unequal usage. Equal splits create a subsidy from light users to heavy users. The light users eventually realize their Outside Option is cheaper and leave, collapsing the consortium. Use the Shapley value or at minimum a Revenue-weighted formula.
Ignoring the free-rider problem. The inverse of light users leaving: some members consume disproportionate shared resources - support, customization requests, roadmap attention - relative to their contribution. Without explicit consumption limits in the binding agreement, heavy consumers extract surplus from the group. This is the most common operational failure mode in real consortia and kills goodwill faster than any cost dispute.
Assuming the build hits Budget. Multi-company builds overrun because requirements negotiation across independent organizations is slower than internal prioritization. If your break-even analysis assumes on-time, on-Budget delivery, run a Sensitivity Analysis at 140-150% of estimated build cost. If the deal collapses under a realistic overrun, the consortium is fragile.
Three PE portfolio companies want to build a shared customer data platform. Company X does $80M Revenue and would pay $1.2M/year alone. Company Y does $40M Revenue and would pay $800K/year alone. Company Z does $20M Revenue and would pay $500K/year alone. The shared platform costs $600K/year to operate. Using Revenue-weighted cost sharing, calculate each company's annual cost and annual savings. Then determine: should Company Z join?
Hint: Revenue-weighted share = company Revenue / total Revenue. Compare each company's consortium cost to their Outside Option. A rational company joins only if consortium cost < stand-alone cost.
Total Revenue = $140M. X's share: 80/140 = 57.1% -> $343K/year (saves $857K). Y's share: 40/140 = 28.6% -> $171K/year (saves $629K). Z's share: 20/140 = 14.3% -> $86K/year (saves $414K). All three save money, so all should join. But Z should verify governance terms - with 14.3% of votes, Z needs unanimous consent clauses on scope changes to avoid the platform being optimized solely for X's needs.
You're negotiating a consortium exit clause. A departing member has contributed $500K in Capital Investment over 2 years. The platform's current market value is $3M and there are 4 equal members. The remaining members propose: departing member forfeits all contributions. Is this fair? What would you counter-propose?
Hint: Think about the departing member's proportional claim on the Asset vs. the cost of disruption to remaining members. Consider what happens to the cost sharing formula when one member leaves.
Forfeiting 100% is punitive and creates a failure mode: members who should leave stay because exit is too expensive, dragging down consortium quality. A fair counter: the departing member receives their proportional share of market value minus Liquidation Discounts reflecting the transition burden on remaining members. Here: 25% of $3M = $750K gross claim. The discount rate is a negotiation variable, not a known constant - typical ranges in infrastructure partnership exits run 20-40% depending on how portable the underlying Asset is, whether a ready replacement member exists, and how much operational disruption the departure causes. At 30% discount: $750K x 0.70 = $525K payout, which exceeds the $500K contribution and reflects Appreciation of the shared Asset. The binding agreement should specify the discount formula upfront - including how the rate is determined and what triggers adjustments - so exit is clean, not adversarial. The remaining members then renegotiate cost sharing three ways.
Consortia sit at the intersection of your two prerequisites. Binding agreements provide the legal scaffold - without an enforceable contract specifying contributions, governance, and exit terms, no rational company would sink Capital Investment into shared infrastructure. Cost sharing provides the economic scaffold - the Shapley value gives you a principled fair allocation, and separately you must verify that no coalition of members prefers to go it alone (the stability condition). Downstream, consortia connect to several PE and Operations concepts: they are a form of Capital Allocation where the investment decision spans multiple entities, they show up frequently in PE Portfolio Operations when the Holding Company pushes for Efficient Allocation across PE portfolio companies, and governance disputes are a natural application of Bargaining theory and weighted voting. Understanding consortia also prepares you for M&A due diligence - when evaluating a target company, ask whether it depends on consortium infrastructure and what happens to access rights post-merger.
Disclaimer: This content is for educational and informational purposes only and does not constitute financial, investment, tax, or legal advice. It is not a recommendation to buy, sell, or hold any security or financial product. You should consult a qualified financial advisor, tax professional, or attorney before making financial decisions. Past performance is not indicative of future results. The author is not a registered investment advisor, broker-dealer, or financial planner.