Build a sales pitch a PM can deliver on a deal call
Sales has been pulling you into customer calls and your demo wanders because you have not actually built a pitch. This produces a 7-slide pitch a PM can deliver in 12 minutes (problem, status quo cost, our take, demo, proof, pricing, next step) so the call moves the deal forward instead of becoming an open-ended product tour.
A PM Without a Pitch Is a Product Tour Looking for an Exit
PMs join customer calls because sales asks them to (or because the deal is strategic enough to need a product voice). The default is to walk through the product, answer questions, and hope the buyer connects the dots. The buyer rarely does. A PM with a sales-grade pitch lands the call inside 12 minutes, surfaces the buyer's objections, and converts the meeting into a specific next step in the deal cycle.
The 7-slide structure trades polish for clarity. Each slide does one job; the slide that does not earn its place gets cut. The structure also keeps the demo to 4-7 minutes, which is the difference between a buyer who remembers three things and a buyer who remembers nothing.
First Round Review collects sales and storytelling writing that informs how PMs frame product narratives for buyers. SVPG's writing on the most important PM skill frames the underlying capability: the PM who can articulate the take in two sentences shapes both the deal and the team.
Why the pitch is not a feature list
Buyers do not buy features. They buy a future where their painful status quo is fixed, with enough proof that they can defend the purchase to their team. A feature-list pitch fails three checks:
- No urgency. Without "why now," procurement files the conversation under "next year."
- No belief. Without a take, the buyer sees a vendor that is fundable, not a vendor that has a point of view.
- No specific next step. Without an ask, the call ends in "let's circle back" and the deal cools.
Intercom's writing on jobs to be done reinforces the framing: buyers hire products to make progress on a job, and the pitch must show that the product is what fires the existing solution.
How the Build a sales pitch prompt works
Slide 1 is the problem in the buyer's words. Not the team's words, not the marketing copy, the buyer's exact language from a recent interview. A buyer who hears their own phrasing in the first 30 seconds is paying attention; a buyer who hears industry jargon is composing a polite email.
Slide 2 is why now. The shift that makes this urgent. The PM who can name the exact regulation, competitor move, or internal restructuring lands more deals than the PM who waves at "the AI moment."
Slide 3 is the take. One or two sentences of point of view, plus one or two anti-claims. The anti-claims matter because they show the team has chosen what NOT to build; buyers find that more credible than buyers who think the product does everything.
Slide 4 is the demo, capped at 4-7 minutes. Three critical moments that prove the take, with pre-loaded data the buyer recognizes. The intentional friction moment is the storytelling trick: show the pain, then fix it in front of them. Buyers feel the relief; that feeling is what they remember.
Slide 5 is proof. Logos that match, a number from a public case, the integration/security/compliance check that closes the "is it real" question. Without proof, the take is vibes.
Slide 6 is pricing and packaging. The starting price the buyer can take to procurement is essential; a vague "let's talk pricing" stalls deals at the procurement step.
Slide 7 is the ask. A specific next step. Procurement intro, security review, pilot scope. Owner on each side. Date.
HBR's foundational essay on strategy frames the underlying discipline: a strategy is a coherent set of choices, and a pitch is the externalization of those choices for a buyer.
The follow-up email is the leave-behind
The buyer takes the meeting back to their team in an email they forward. The PM who writes that email saves the buyer the work and shapes how the deal sounds internally. One paragraph: the single line that captures what you do, the three outcomes the buyer mentioned, the next step both sides agreed to, two pieces of leave-behind material. Without this, internal advocates have to reconstruct the pitch from notes.
When to use it
- Sales is bringing you into customer calls and the calls run long without moving the deal.
- A new market or new buyer persona is being approached and the team has not built a pitch for them yet.
- A previous launch was not converting in pipeline and the diagnosis points to the pitch, not the product.
- A board or CEO is asking how strategic deals are being qualified and the answer is "we wing it."
- A founder PM is going on a customer-discovery road trip and needs a tight artifact instead of a 30-slide deck.
Common pitfalls
- Long demo. Past 7 minutes, the buyer remembers the demo, not the take. Cap it.
- No anti-claims. Buyers find a product that does everything less credible, not more.
- Vague ask. "Let's stay in touch" cools the deal. Specific next step, owner, date.
Sources
- First Round Review - First Round
- The most important PM skill - Silicon Valley Product Group
- Jobs to be done - Intercom
- What is strategy - Harvard Business Review
- Atlassian product management - Atlassian
Sources
- First Round Review — First Round
- The most important PM skill — Silicon Valley Product Group
- Jobs to be done — Intercom
- What is strategy — Harvard Business Review
- Atlassian product management — Atlassian
Prompt details
Ready to try the prompt?
Open the live prompt detail page for the full workflow.