Outgrace, home
StrategyExplainer

Why strategic alliances fail, and how to write their exit terms

The public sources we checked say nothing about why alliances fail. They do set the rules any exit clause must work within, and that is where drafting starts.

Two companies sign an alliance agreement because each needs something the other has. The agreement is usually drafted for the start of the relationship and says little about its end. The sources we checked for this piece contain no research on why alliances fail, so the diagnosis below is our judgement, not a finding. What the sources do contain are the rules that govern how partners behave and how they answer to a buyer. Those rules limit which exit terms are possible at all.

Three public sites were checked: the European Commission's competition pages, the UK Competition and Markets Authority's pages on gov.uk, and subpart 9.6 of the US Federal Acquisition Regulation on acquisition.gov. Only the last describes a partnering arrangement in any detail. The Commission and the CMA set out general competition rules, and neither page, as checked, discusses partnerships. A reader who wants alliance research will need to look beyond these sources, and should do so before drafting anything that depends on it.

How it works

The Federal Acquisition Regulation describes two forms of team arrangement. In the first, two or more companies form a partnership or joint venture to act as the potential prime contractor. In the second, companies hold potential prime contracts with other firms, and those firms act as subcontractors under a specified government contract or programme. The regulation says such arrangements may suit government and industry, because they aim to offer the best mix of performance, cost and delivery.

The regulation says team arrangements are particularly suited to complex research and development acquisitions, and that they may also be used in production acquisitions. Teams are normally formed before an offer is submitted, but they may be formed later, including after contract award. Either way, the government recognises the arrangement only if the relationships are disclosed. That means disclosure in the offer, or, for a team formed after the offer, before the arrangement takes effect.

On dissolution, the regulation is direct about the government's own position.

The Government will not normally require or encourage the dissolution of contractor team arrangements.

Federal Acquisition Regulation, subpart 9.6, acquisition.gov

That sentence matters less for what it promises than for what it leaves to the partners. If the government will not push a team apart, the team must decide how it ends. The regulation also keeps several levers for the buyer. It may require consent to subcontracts. It may hold the prime contractor fully responsible for performance, regardless of the team arrangement. And it keeps the right to pursue competitive contracting and component breakout policies after initial production, or at any other time. An exit plan that ignores these levers will fail at the first point where the buyer uses one.

The competition side sets the outer limit. The Commission's competition policy, as its page states, aims at lower prices, efficiency and innovation, and it requires firms to act independently of each other to keep competition effective. The FAR is equally plain that nothing in it authorises team arrangements that violate antitrust statutes. An alliance that coordinates prices, divides markets or exchanges competitively sensitive information has left the procurement rules and entered the competition rules, which is a harder problem. The Commission's page also says anonymous sharing of cartel or antitrust knowledge is possible with it, for the purpose of detecting, stopping and punishing infringements. A partner who suspects the alliance is being used for collusion should take legal advice before using that route.

Who it affects

The FAR provisions apply to government contractors and to the defence and research and development acquisition teams that buy from them. The European Commission and UK competition rules apply to firms within their competition-policy scope. The sources do not name sectors or companies in the alliance context, so a reader should not assume a particular industry is either covered or exempt. The more useful question is which jurisdiction governs each partner, and which rules the buyer applies to the work itself.

The regulation's remark that team arrangements suit complex research and development work deserves attention from anyone in that field. Complex work is where exits are most expensive, because specifications, test data and subcontract terms build up over several years. A partner who leaves in year three may take design knowledge with it, or leave the buyer waiting for a replacement. That is our judgement rather than a finding in the sources. It is also the reason the exit deserves as much drafting time as the entry.

The CMA states its end goal as economic growth and household prosperity. Its page also cites a speech by its Chief Executive, Sarah Cardell, at the Chatham House Competition Policy Conference 2026. The text of that speech is not in the source we checked, so this article does not quote or characterise it. A leader who wants the CMA's current view on partnerships should read the speech and the authority's guidance directly, rather than rely on secondary summaries.

What leaders get wrong

  • Writing the agreement for the start only. In our experience, the signing version describes roles and the revenue split, and says nothing about who may stop the work.
  • Leaving disclosure to the bid team. The FAR recognises a team only where relationships are disclosed in the offer, or before the arrangement takes effect. A partner who learns this after award has a problem the agreement never planned for.
  • Assuming a partner can leave while the prime stays liable. The government can hold the prime fully responsible for performance, whatever the team arrangement says. An exit clause that lets a subcontractor walk away without a replacement plan leaves the prime carrying the risk.
  • Treating a dissolution clause as an exit plan. A line saying the alliance ends on notice does not say who owns the subcontracts, the work in progress or the shared know-how.
  • Sharing data without a competition check. An alliance that exchanges pricing or customer information can move into competition law, and the FAR is explicit that it does not authorise antitrust violations.

What to do about it

Write governance as a schedule, not a paragraph. Name what each partner may decide alone, what needs joint consent, and who breaks a tie. In our experience, the decisions that go wrong are the ones nobody wrote down as decisions: a change of key personnel, a subcontractor swap, a price revision after a change in scope. A sensible test is to list the ten most likely decisions in the first year and check that each one has an owner and a route to resolution.

Tie performance milestones to things the partners can observe, such as a delivered prototype, an accepted test report or a signed subcontract, rather than to effort or intent. Give each milestone a date, an owner and a stated consequence if it is missed. The consequence should be the first step of the exit, not the start of a dispute. That way the agreement says in advance what happens when the work runs late, and nobody has to argue about it under pressure.

Write the exit as a sequence. Define the triggers: a missed milestone, a change of control, a breach of the competition rules, or a buyer decision to withdraw consent. For each trigger, set the notice period, the handover of subcontracts and any consent the buyer must give, the treatment of shared know-how, and who remains liable for work already delivered. Because the FAR's consent and prime-liability provisions apply regardless of the team arrangement, this sequence has to work with the buyer's rights, not around them. A workable test is to name who can stop the work, on what trigger, and who then owns each subcontract.

Competition and procurement counsel in each relevant country should review the draft before signature. Because these terms touch competition law, procurement rules and possibly several national systems at once, a general corporate lawyer is unlikely to be enough on their own. Put specific questions to counsel: which rules govern each partner, what must be disclosed and when, and what the exit does to the prime contractor's liability.

Where to start this week

Pull the alliance agreement and find the clauses that deal with the end of the relationship. Check whether each one names an owner, a trigger and a handover. Where one does not, redraft it first, because that clause is where a dispute will start. Then send the revised draft to counsel with the questions listed above, and ask for written answers on the disclosure timing and the competition position before the first joint bid goes in.

Newsletter

The Briefing

One email a week: the leaders we profiled, the ideas worth stealing, and nothing else.

Weekly, free, one click to leave. Read our privacy policy.