The full partnership deck course.
3-5 min, skimmed on a phone before the call. These modules sum to ~3:50 of reader attention. Work through in order or jump to the section that needs the most help.
The one-sentence relationship
20s · w8State exactly what you are proposing before any context, so the reader knows what kind of deck they are in.
The partner's problem, in their language
25s · w9Reframe the pitch around a problem the partner's team is already measured on, not your roadmap.
Overlapping traction
30s · w12Prove the two customer bases already intersect, with a real percentage, before asking for anything.
Mutual math
30s · w11Give the partner a number they can put in their own internal deck: revenue, retention lift, or completeness gap closed.
The named integration point
20s · w8Name the exact team, product tier, or surface where the integration lives, so the deck reaches the right desk.
Technical readiness
20s · w7Show the technical work is already done or scoped, so the partner is not being asked to build anything speculative.
Why now
20s · w7Tie the timing of this pitch to something happening in the partner's market right now, not an abstract trend.
The concrete ask
25s · w10Scope the request down to a specific pilot with a timeline and named resourcing, not an open-ended partnership.
Risk preempt
25s · w8Name the objections the partner's security, legal, and support teams will raise, and answer them before they are asked.
Named next step, both sides
15s · w8End with a specific next action, owner, and date on both sides, so the deck functions as a follow-up email draft.
Each module contributes to your audit score, weighted by how much the reader's decision hinges on it. Total weight = 88.