Field Note · Capital, boards, and transactions
Is This Partnership Actually Worth Building?
The temptation in a promising partnership is to make it feel important before it has become useful. I prefer to let one real proof earn the next layer of commitment.
A thinking frame by Andrew Moss
The questions I get
Usually some version of these:
- Is this strategic partnership worth pursuing?
- Should we commit resources, exclusivity, or equity?
- How do we test a channel partner before building around them?
What a lot of people seem to think
Many teams treat a large brand, a friendly executive, a signed agreement, or an announcement as proof that the partnership has strategic value.
How I look at it
Partnership depth should be earned. Start with one real user or operating problem, accountable owners, a short proof period, and a result both sides can recognize. Close the handoff. Then decide whether the evidence justifies more access, integration, reputation, or relationship capital.
Why the decision matters
The cost is rarely confined to the line item.
If the sequence is wrong
The partnership absorbs attention, creates dependency, damages trust, or consumes exclusivity and reputation without entering a repeatable workflow.
If the sequence is right
Both sides know the job, owners, economics, proof points, and next commitment; value and trust grow together.
How reversible is it?
Moderate. Contracts can end, but lost time, confused customers, and weakened relationships linger.
The short answer
Earn the next layer with one useful proof.
Define the smallest test that would teach both sides something consequential. Give it owners, a user, a result, a deadline, and a decision at the end. A partnership becomes strategic through repeated responsible handoffs, not through the size of the announcement.
A useful pictureBuild the bridge one tested span at a time.
A broad agreement can describe the bridge. A proof shows whether the first span can carry weight. Each larger commitment should rest on something the relationship has already carried together.
Move fromExecutive enthusiasm and an announcement→Move towardProof, closed handoff, and earned depth
The order I would use
Take the right steps in the right order.
- 01
Name the user and problem
Identify who becomes better off and which customer or operating problem the partnership will solve.
- 02
Choose the smallest meaningful proof
The test should be narrow enough to run and strong enough to change the next decision.
- 03
Assign one owner on each side
Make the handoff, authority, resources, and escalation path visible.
- 04
Define the evidence before the work
Agree on the result, timeframe, costs, dependencies, and what would count as a stop signal.
- 05
Close the proof
Record what happened, what each side learned, which commitment was kept, and what remains unproven.
- 06
Earn or refuse the next layer
Expand only when the result and working relationship justify more integration, access, reputation, or capital.
Questions worth answering
Before the next irreversible move:
- What one proof would materially change the next decision?
- Who owns the work and the handoff on each side?
- What relationship or reputation capital is being spent before it is earned?
- What evidence would justify expansion, redesign, or a clean stop?
What not to do
Do not spend the whole relationship on the first promise.
Do not begin with the broadest agreement, the largest integration, or a public announcement. Do not mistake access for distribution, goodwill for operating ownership, or a signed document for a working partnership.
Keep the perspective
Trust compounds when each side closes the last handoff.
A small proof is not timid when the next commitment is expensive. It is how two organizations learn whether their incentives, speed, standards, and people can actually work together.
Common follow-up questions
Should every partnership start with a pilot?
Not every arrangement needs a formal pilot, but most uncertain partnerships benefit from a bounded, reversible proof before larger commitments.
When can exclusivity make sense?
When scope, term, performance obligations, remedies, economics, and the value exchanged are clear enough that both sides understand the cost.