Sales deck template for B2B startups (2026)
A 9-slide sales deck template for B2B startups: problem, outcome, how it works, proof, pricing, mutual next step. Built for founder-led demos, not VCs.
sales-deck-template-b2b.txt
Slide 1. Title and outcome promise
{{COMPANY_NAME}} helps {{BUYER_TITLE}}s {{OUTCOME_METRIC}}.
Subline: one sentence on who you are. No tagline poetry.
Slide 2. The pain you fix
{{BUYER_TITLE}}s lose {{PAIN_COST}} every {{TIME_UNIT}} to {{PAIN_TRIGGER}}.
One sentence on why the current workaround fails.
Slide 3. The outcome they get
After {{COMPANY_NAME}}: {{OUTCOME_METRIC}}.
Show the metric as a number with a unit. Verbs without numbers do not count.
Slide 4. How it works
Three boxes, one sentence each.
1. {{INPUT_STEP}}
2. {{CORE_MECHANISM}}
3. {{OUTPUT_STEP}}
No architecture diagram. No data-flow arrows.
Slide 5. Proof (the case-study slide that closes)
{{CASE_STUDY_COMPANY}} went from {{CASE_STUDY_BEFORE}} to {{CASE_STUDY_AFTER}} in {{TIMEFRAME}}.
One named pull quote from their {{CASE_STUDY_ROLE}}.
No logo wall. One customer told in depth beats twelve told in pixels.
Slide 6. Why now, why us
The shift in {{MARKET_TRIGGER}} that makes the old approach untenable.
One sentence on the unfair advantage you have that competitors do not.
Slide 7. Pricing
{{PRICING_TIER_1}} for {{TIER_1_USE_CASE}}.
{{PRICING_TIER_2}} for {{TIER_2_USE_CASE}}.
Two tiers maximum. No "contact us" unless you want this slide screenshotted for the wrong reasons.
Slide 8. The mutual next step
"To know if this is worth your team's time, I will {{YOUR_COMMITMENT}} by {{YOUR_DATE}}, you will {{BUYER_COMMITMENT}} by {{BUYER_DATE}}, and we meet again on {{NAMED_DATE}}."
Put the calendar invite on screen. Send it before the call ends.
Slide 9. Appendix
Security and SOC2 status, integrations list, second case study, common objection rebuttals.
Never shown in the main flow. Always sent in the follow-up.
Variables · fill before sending
- COMPANY_NAMEYour company name
- BUYER_TITLEJob title of the decision-maker, e.g. VP Engineering, Head of RevOps
- PAIN_TRIGGERThe specific operational pain the buyer feels weekly, e.g. failed deploys, manual reconciliation
- PAIN_COSTQuantified cost of the pain in hours, dollars, or percentage churn
- TIME_UNITThe cadence of the pain, e.g. week, sprint, month
- OUTCOME_METRICThe single metric you move, e.g. cut deploy time by 60%, lift activation by 22 points
- INPUT_STEPWhat the buyer's team has to do or send to start, in one verb phrase
- CORE_MECHANISMWhat your product does in the middle, in one sentence a non-technical buyer understands
- OUTPUT_STEPWhat comes out, where it lands, who acts on it
- CASE_STUDY_COMPANYNamed customer with permission to reference, ideally in the buyer's industry
- CASE_STUDY_BEFORETheir metric before adopting your product
- CASE_STUDY_AFTERTheir metric after adopting your product, with timeframe
- CASE_STUDY_ROLETitle of the person at the customer who said the pull quote
- TIMEFRAMEHow long the case study took to land, e.g. 60 days, one quarter
- MARKET_TRIGGERThe market shift creating urgency, e.g. AI-agent traffic, new compliance rule
- PRICING_TIER_1Headline price for the smaller tier, e.g. $1,500 per month flat
- TIER_1_USE_CASEThe team or use case the smaller tier serves
- PRICING_TIER_2Headline price for the larger tier
- TIER_2_USE_CASEThe team or use case the larger tier serves
- YOUR_COMMITMENTThe specific deliverable you will produce, e.g. send a custom ROI sheet for their stack
- YOUR_DATEWhen you commit to deliver it, e.g. Thursday EOD
- BUYER_COMMITMENTThe specific action the buyer commits to, e.g. loop in their head of security
- BUYER_DATEWhen the buyer commits to do it
- NAMED_DATEThe exact date and time of the next meeting, already on the calendar
How to use it
- Open on outcome, not company. Slide 1 is the buyer's metric, not your logo. If they only read one slide, they should know what changes for them.
- Quantify the pain in their unit. Hours per sprint, dollars per quarter, percentage churn per cohort. Vague pain reads as a fishing expedition.
- One case study, told in depth. A named role with a before/after metric outperforms a logo wall. If you cannot get one customer to go on record, you do not yet have the proof slide.
- Show pricing. Hiding pricing signals you do not know what you are worth. Two tiers, anchored, with a clear use case for each.
- Land the mutual next step in writing. Send the calendar invite before the call ends. Mutual action plans close because they remove the awkward follow-up dance.
- Do not reuse your investor deck. TAM, team pedigree, and your roadmap to a billion-dollar outcome do not belong in a customer call.
- One deck per persona, not per company. A deck pitched to a VP of Engineering will not resonate with a CFO. Build two if you sell to both.