Orchestrate multi-party partner bids

Use this when the deal has more than two sides — tri-party orchestration, joint bids and teaming, and the guardrails that keep competitors cooperating. Start from the parties and their roles, the joint opportunity, the existing bilateral terms, and the decision rights per party.

Set the orchestration map

Parties, roles, what each brings and what each gets, decision rights, and a single-threaded owner per workstream.

A workstream with no owner is paused until it has one.

Set the coopetition guardrails

Where the parties compete and where they cooperate, the information barriers between those two, and the conflict path with its SLA.

Name the transaction model per workstream — selling to, with, or through each party — and who leads it.

Guardrails are written and acknowledged before any joint work starts. A party that will not acknowledge them pauses the joint work.

Run the bid or the build

The shaping plan, the teaming agreement spine (scope split, pricing, liability), the milestone dates, and a red-team review before submission.

Every commitment names the party that owns it.

Hold the AI line where it applies

Intellectual property, safety, and delivery guardrails for AI work, with the review gate each output has to pass. Unreviewed AI output never reaches the client.

What you hand back

The orchestration map, the guardrails document, the bid or build plan with its teaming spine, and the AI guardrail checklist when it is in play.

Fallbacks

No bilateral terms on file means drafting the teaming spine from owner-stated intent marked INFERENCE, with Legal review first.

No teaming term, bid submission, or joint commitment goes out without your explicit yes. Where the motion is also regulated, the regulated frame governs and this runs the mechanics inside it.