Sales pitch examples: 5 structures for B2B conversations

Most sales pitches fail before the first sentence is finished, because they open with the vendor’s history instead of the buyer’s situation. A prospect who hears “we’ve been helping companies like yours since 2015” has learned nothing about whether the call is worth their next ten minutes.

The five structures below are patterns for what to say and in what order — not a script to read word for word, and not a slide deck. A pitch can use any of these on a phone call with zero slides, in an elevator with zero notice, or as the spoken narrative behind a sales deck. That distinction matters: a sales deck is the visual document a pitch might use as one container; the pitch itself is the argument, and it has to work with or without slides in the room.

1. Problem-agitate-solution: the default for a first call

This structure opens with the buyer’s specific problem, spends one sentence on what it costs to leave unsolved, then introduces the solution in a single line.

When to use it: first calls and cold outreach, where the buyer hasn’t yet confirmed they have the problem you’re describing.

Example opening: “Most enterprise sales teams still send proposals as static PDFs — which means once it’s sent, you have no idea whether the economic buyer even opened it, let alone which section they cared about. That usually means the follow-up call is a guess instead of a fact. We built Zoomforth so that follow-up is based on what a buyer actually did, not what they said on the last call.”

The agitation step is easy to overdo — one sentence on cost is enough. A pitch that spends three minutes describing the problem before mentioning a solution reads as manipulative, not insightful.

2. Before-after-bridge: for buyers who need to see the change

Before-after-bridge describes the buyer’s current state, paints the state after the change, then explains the bridge between them. It works better than problem-agitate-solution when the buyer already knows they have a problem but hasn’t pictured what solving it looks like day to day.

When to use it: second or third meetings, once discovery has established the specific pain — the goal here is to make the future state concrete, not to reintroduce the problem.

Example: “Right now, every proposal your team sends is a PDF that disappears into an inbox with no signal back. After this, each proposal is a link that shows you exactly who opened it, what they read, and how long they spent on the pricing section — before you ever pick up the phone for a follow-up. The bridge is switching the proposal format, not changing your sales process.”

3. The 30-second elevator pitch

An elevator pitch has no room for company history or a feature list — only who you help, the specific problem, and the outcome, in that order.

Example: “We help enterprise sales teams replace static PDF proposals with trackable digital experiences, so reps can see exactly which stakeholder opened what and follow up on facts instead of guesses.”

When to use it: any situation with under a minute of attention — a conference hallway, an unplanned intro on a call, the first line of a cold email. Its job is to earn a second conversation, not to close anything.

4. The reframe: when the buyer is solving the wrong problem

A reframe pitch challenges the buyer’s own framing of their problem before offering a solution — useful when discovery reveals the buyer is focused on a symptom, not the underlying issue.

Example: a buyer says they need “a nicer-looking proposal template.” A reframe pitch responds: “A better-looking template will help for about one deal — the real issue is that you have no visibility into whether any proposal gets read at all, so you can’t tell a strong template from a strong follow-up. Fixing the visibility problem fixes the template problem as a side effect.”

This structure only works if the reframe is accurate and delivered as a genuine insight, not a sales tactic — a wrong or condescending reframe costs more trust than it earns.

5. Role-by-role: pitching a buying committee

A single pitch delivered to a room with an economic buyer, an end user, and a technical reviewer usually serves none of them well, because each cares about a different question. Enterprise B2B deals now average 6 to 10 stakeholders — see the modern B2B buyer journey for how that plays out across a full deal cycle.

Structure: address the economic buyer’s ROI and risk question first, the end user’s day-to-day workflow change second, and the technical reviewer’s security or integration question third — explicitly, by naming who each part is for (“for whoever owns budget on this…” / “for the team that’ll use this daily…”).

Why it works: naming the audience for each section signals that the pitch was built for this specific committee, not recycled from the last call — the same signal a discovery call is meant to earn in the opposite direction.

From pitch to proposal: don’t let the structure disappear

A pitch that lands in the room and then gets followed up with a generic proposal template loses everything the structure just built. If the pitch used before-after-bridge, the proposal that follows should open the same way — current state, future state, the bridge — not switch to a generic executive summary. The same discipline that goes into sales collateral built for a specific deal applies to the pitch itself: the structure is only as good as what carries it into the next document the buyer receives.

Ready to make sure your follow-up matches the pitch that got you the meeting? Request a demo to see how a trackable digital sales room carries a pitch’s structure into the proposal that follows it.