Skip to content
Strynal, Digital Agency

Strategy 5 min read

How to Write an Elevator Pitch That Actually Lands

A step-by-step guide to writing and delivering an elevator pitch that people actually remember: clear structure, real trade-offs, and the one test that matters.

By Strynal Team

Most elevator pitches don’t fail because the business is weak. They fail because the speaker treats a 30-second conversation as a product demo. By the time they finish, the listener has heard a lot and understood almost nothing.

Why most pitches collapse

The standard advice is to keep it short and clear. Correct, and almost useless, because nobody thinks they’re being long or unclear while they’re doing it. The real problem is structural. Most pitches are built around the speaker’s perspective: what we built, how we built it, what it does. That’s the wrong frame. The listener’s question is simpler: should I keep paying attention?

A pitch is not a closing argument. It is an opener. Its job is to get one specific person to want to hear more. Everything else, the full story, the demo, the pricing, belongs in the next conversation.

The pitch fails when founders try to compress the whole story into 30 seconds. You can’t compress a pitch. You edit it.

The three-part structure that holds

There is a repeatable structure behind most pitches that land. It isn’t clever. It is an ordering decision that respects how listeners actually process information.

Name the problem first

Start with the situation your buyer is in or the frustration they feel. Not your product. Not your company. The problem.

This matters for a mechanical reason: the listener needs a frame to hang your answer on. If you open with “We’re a platform that manages…” you have put them in the position of decoding what the problem might be while also processing your feature list. Two cognitive loads at once.

Lead with the problem and you give them a choice. They either recognise it (“yes, that’s us”) or they don’t (“not my situation”). Both outcomes are fine. You want the people who recognise it to lean in, and you want the others to self-select out early. A pitch that tries to be relevant to everyone ends up moving nobody.

State what you do, for whom, and to what end

One sentence. Two short ones at most.

The pattern is: we help [specific person] [do or avoid something specific] so they can [specific outcome]. The more exact each slot is, the sharper the pitch. Founders resist specificity because it feels like shrinking the market. In practice, being specific is what makes a stranger feel spoken to. Generic claims slide right off.

This is the same discipline behind solid value proposition design: the goal is a claim your buyer can own, not a claim that covers every possible listener.

A pitch that works for everyone works for no one. The more specific the who, the more the right person feels seen.

Give them one reason to believe

Not three. One.

The reason to believe is the thing that makes your claim credible without asking the listener to trust you on faith. It might be a fact about how you work, the kind of customer who already depends on you, or the specific gap you have closed that rivals haven’t. Whatever it is, it should be a fact rather than a claim. “We’re the fastest” is a claim. “We cut onboarding from six weeks to five days for mid-market finance teams” is a fact.

Don’t stack evidence. Stacking reads as insecurity. One strong, specific, true thing beats three vague superlatives.

Written is not the same as said

A structurally correct pitch can still fall flat in delivery. Reading from memory produces a flat, metronomic cadence that signals rehearsed performance rather than genuine conversation.

The fix is not to memorise the words. It’s to internalise the logic.

Know the three moves: problem, answer, proof. Know roughly one sentence for each. Then speak from the logic rather than the script. The actual words can shift. The moves stay fixed.

Practice out loud with someone outside the industry. A friend, a family member, anyone who isn’t steeped in the context. If they can reflect your pitch back to you accurately in their own words, it has landed. If they shrug or give you something vague, you have found the gap. This test is more reliable than any amount of internal review, because insiders fill in the blanks from prior knowledge and don’t notice when the logic is missing.

When they ask a question

A pitch that works opens a conversation. Expect a question immediately after, and know which category it belongs to.

“Tell me more” means they’re interested and want depth. Move to the mechanism: how does it actually work, at a level above the spec sheet.

“Who else is doing this?” is a social proof question. Name the type of customer and the outcome, not a client name.

“Why you?” is a right-to-win question. Answer it with something real: a specific background, prior work, or the thing you have already shipped that others haven’t.

What to avoid: treating the question as an invitation to pitch again. Answer the specific thing asked, then pause. Founders who talk more than necessary after the pitch tend to undo the clarity they just built.

The pitch also connects to the larger story you want to own in a market. If you have worked through your messaging architecture or a strategic narrative, the pitch is a compressed version of a story you already know cold. Without that foundation, pitches drift between conversations. A different story every room you walk into starts to feel like evasion, even if the underlying business is solid. The same compression logic applies when the position eventually becomes a tagline: one clear idea, stated with precision.

How Strynal approaches pitch and messaging clarity

We treat a sharp pitch as a diagnostic, not an output. When a founder can state the problem, the answer, and the proof in three clean sentences, the positioning underneath is usually clear. When the pitch keeps shifting or runs for a minute before it gets to the point, that is a positioning problem, and writing better sentences won’t fix it.

The work we do in strategy and positioning often starts exactly here: getting the one-sentence version of the company right, then building the fuller message architecture around it. That order matters. A pitch derived from a clear position is stable. One written in isolation tends to drift.

If your pitch is inconsistent between conversations, or you find yourself giving a different answer depending on who is in the room, it is worth looking one level upstream at the strategic decisions the pitch is supposed to express.