The wedge to platform pitch: prove expansion, keep focus

A wedge to platform pitch works as a two-slide sequence: slide one shows the wedge with traction, slide two shows the adjacency map ordering the next two or three expansions. Leading with the platform before the wedge is proven is the fastest way to fail the "are you actually doing anything?" test that seed partners run in the first 90 seconds.

Most founders pitching expansion blow it the same way: they open with the platform vision and treat the wedge as an afterthought. That flips the order seed investors need to see.

Show the wedge first, with numbers. Show the platform second, as a dated sequence. Everything else is noise.

The two-slide sequence that works

Slide one is the wedge plus traction; slide two is the adjacency map. No third slide tries to do both.

Slide one names a specific user, a specific workflow, and the metric that proves capture. Slide two is a dated roadmap of the next two or three adjacent products, ordered so each one reuses the distribution or data of the one before it.

✅ Good, slide one: "140 mid-market sales teams use us for outbound sequencing. $62k MRR, 8% monthly growth." Why it works: proves the wedge is owned before any vision is claimed.

❌ Bad, slide one: "The operating system for modern revenue teams." Why it fails: claims platform status before traction, triggering the "where are the actual numbers?" reflex in every partner reading it.

How to build an adjacency map in 5 steps

A clean adjacency map is the single most useful slide in a platform pitch. Build it in this order.

1. Name the core workflow the wedge owns. One sentence. If you cannot write it, the wedge is not owned yet.
2. List every user pain within two clicks of that workflow. Ten to twenty items, unfiltered.
3. Rank each adjacency by data leverage. Which ones can reuse the data the wedge already captures? Those go first.
4. Eliminate anything that requires a new buyer. Same user, same budget line, same login. Cross-buyer expansions belong in year three or later, not on a seed deck.
5. Plot the top three on a timeline with dated quarters. Specific ship targets. Vague "future modules" read as cope.

First Round Review frames this as sequencing: each new product builds on the data or distribution of the previous one. Copy that logic directly into the map.

The narrow to broad startup anti-pattern

Pitching platform before wedge is the fastest way to look unfunded and unfocused at the same time. Y Combinator tells founders to lead with a specific problem and a narrow solution before expanding into the vision, for a reason: a partner reading a platform-first deck has no way to tell whether you shipped anything.

The signal VCs actually read: platform language without traction means the founder does not know what the product is yet. a16z is explicit that platform status is earned by capturing a core workflow, not by listing multiple features simultaneously.

When to expand from your wedge

Expand when you own the workflow, not when the seed pitch is coming up. Owning a workflow means users open your tool first in the morning for that task, and you can name who those users are by segment.

Kruze Consulting benchmarks show that top-quartile Series A companies often have two or more revenue-generating features. That is the bar for a credible platform narrative at Series A. At seed, one revenue-generating feature with hard traction beats three half-shipped ones.

Do not ship adjacency two until adjacency one has its own cohort of paying users. Anything less and the map is fiction.

What land and expand startup pitches get right

The best decks treat current reality and future potential as separate slides, not one slide. Sequoia notes that effective pitch decks clearly distinguish between the wedge (what is working now) and the platform (what it becomes).

OpenVC recommends placing a traction slide immediately before a vision slide, for the same reason: the traction earns the vision. Flip the order and the vision reads as a wish list.

One more data point worth building into the deck: AngelList reports that 26.2% of active startups raised a follow-on round within 12 months. The ones that do almost always have adjacency one already in beta by the Series A conversation, not still on a roadmap slide.

If you are preparing a dozen of these decks for different partners, tools like Causo handle the per-fund adjacency framing so the map reads differently for an infra fund versus an application fund, without rewriting the slide from scratch.

FAQ

How do you pitch platform expansion at seed? Lead with the wedge on slide one and use slide two for the adjacency map. Show a specific workflow you own, then sequence two or three adjacencies by data leverage, each with a dated ship target. Platform framing before traction is an instant credibility hit.

When should you expand beyond your wedge? When users open your product first in the morning for the core workflow, and you have a paying cohort to prove it. Owning the workflow, not just shipping a feature, is the gate. Most seed founders move too early, which fragments the traction story.

What's the best way to show expansion potential? An adjacency map ordered by data leverage, with dated milestones for the next two or three products. Each adjacency should reuse the wedge's users, data, and buyer. Platform language without a sequenced map reads as hand-waving to any partner who has seen a hundred decks.

Do VCs want wedge or platform? Both, in that order. They want a provable wedge today and a credible platform path on the next slide. A platform pitch without a wedge fails the traction test; a wedge pitch without a platform fails the ambition test.

Examples of successful wedge to platform transitions. Stripe started with payments APIs and expanded into billing, tax, and capital. Figma led with multiplayer design files, then added FigJam and Dev Mode. Both sequenced adjacencies rather than pitching the full platform from day one, which is the pattern VCs actually fund.