Opportunity-to-Alliance
A run starts when there is a strategic reason to work with another company rather than to sell to them or through them: a technology to embed, a product to offer jointly, a market neither can enter alone, a capability better bought than built. The processes here explore the fit, model what the arrangement would be worth to both sides, run the diligence, structure the agreement with legal and finance, and plan the technical and commercial integration that has to follow. A run here takes quarters rather than weeks, and what comes out is a new thing the company can offer. Selling it belongs to the other streams.
vs/prt/opportunity-to-alliance v1The processes
The processes in this stream
Explore an Alliance
Starts witha capability the company cannot offer alone is written down
Ends whena joint thesis, and a named decision to run diligence or stop
Activities inside
- State the Strategic Reason
- Test Build, Buy or Ally
- Scan the Field
16 activities · 58 blanks to fill · 4 human gates
Plan the Integration
Starts withan alliance agreement is signed
Ends whenthe joint offer is being sold and somebody manages the alliance
Activities inside
- Take in the Signed Terms
- Name the Owners on Both Sides
- Define the Joint Offer
16 activities · 63 blanks to fill · 3 human gates
Run Alliance Diligence
Starts witha joint thesis is sent to diligence
Ends whenone dated report saying go, go with conditions, or stop
Activities inside
- Take in the Thesis
- Set What Must Be Proved
- Agree Access with the Other Side
17 activities · 64 blanks to fill · 5 human gates
Structure an Alliance
Starts withdiligence reports go, or go with conditions
Ends whena signed agreement, and a list of what each side owes
Activities inside
- Take in the Diligence Result
- Set What Each Side Must Get
- Choose the Shape
16 activities · 61 blanks to fill · 8 human gates