The one-sentence relationship
State exactly what you are proposing before any context, so the reader knows what kind of deck they are in.
A BD manager scans the first slide to sort the deck into a folder: yes, maybe, no. Elad Gil's growth handbook argues partnerships fail when neither side can name the deal in one sentence.
- The specific relationship type: integration, reseller, co-marketing, data share
- Who does what, in one sentence
- The tier or team inside their org this affects
- Company origin story
- Full product tour
- Vision statements about the category
- The sentence describes a feature request, not a partnership
- No mention of what the partner gets
- Burying the ask in paragraph three instead of stating it first
- Using internal jargon the partner's team will not recognize
- · Could someone forward this sentence to their VP without translating it?
- · Does it name a concrete mechanism, not just a hope?
We want [specific integration/program] with [partner team/tier] so that [partner's users] get [specific outcome].
"We think there's a huge opportunity to synergize and unlock value together."
"We want to embed Nimbus Payroll inside your Slack App Directory so your 41% of workspace admins running distributed teams can run contractor payroll without leaving Slack."
Names the mechanism (App Directory embed), the partner segment (41% of admins running distributed teams), and the outcome, all in one line.
Quick quiz
Pick an answer. Nothing is graded, and correct answers stay hidden until you choose.