Skip to content
Module 01 · The partnership deck~20s dwell · weight 8

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.

Include
  • 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
Cut
  • Company origin story
  • Full product tour
  • Vision statements about the category
Red flags a reader notices
  • The sentence describes a feature request, not a partnership
  • No mention of what the partner gets
Pitfalls behind them
  • Burying the ask in paragraph three instead of stating it first
  • Using internal jargon the partner's team will not recognize
60-second self-test
  • · Could someone forward this sentence to their VP without translating it?
  • · Does it name a concrete mechanism, not just a hope?
Template
We want [specific integration/program] with [partner team/tier] so that [partner's users] get [specific outcome].
Weak

"We think there's a huge opportunity to synergize and unlock value together."

Strong

"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

1. What should the first slide of a partnership deck do?
  • Introduce the company's founding story
  • State the specific relationship being proposed in one sentence
  • List every feature of the product
  • Show the full funding history

A partnership manager sorts decks fast; a clear opening sentence gets you past the first filter.

2. Which opening line is stronger?
  • "We want to synergize and unlock mutual value."
  • "We want to embed Nimbus Payroll inside your Slack App Directory for your distributed-team admins."

It names the mechanism, the segment, and the outcome instead of vague language.

Sources