---
id: ins_pain-solution-proof-interleaved-pitch
operator: Mihika Kapoor
operator_role: Product manager (design-engineering hybrid), Figma
source_url: https://www.lennysnewsletter.com/p/vision-conviction-hype-mihika-kapoor
source_type: podcast
source_title: Vision, conviction, building hype, scope is the world
source_date: 2026-04-28
captured_date: 2026-05-01
domain: [pmm, product, gtm]
lifecycle: [messaging-narrative, sales-enablement, launch]
maturity: applied
artifact_class: framework
score: { originality: 4, specificity: 4, evidence: 3, transferability: 5, source: 5 }
tier: B
related: [ins_setup-follow-through-pitch]
raw_ref: raw/podcasts/mihika-kapoor--zero-to-one-vision-conviction-hype--2026-04-28.md
---

# Pitch a vision as pain → solution → proof, interleaved per beat, not three sequential acts

## Claim
Vision pitches land harder when each pain claim is paired with its own solution claim and a concrete proof point, testimonial, prototype, demo, rather than presenting all pains, then all solutions, then all proof. Words alone get you part of the way; visual or working artifacts close the gap.

## Mechanism
Sequential pain-then-solution-then-proof structure asks the audience to hold abstract claims in memory for too long. By the time the proof arrives, the original pain has faded and the proof reads as a feature list. Interleaved structure compresses the rhetorical loop: each beat builds belief on the previous. The proof artifact also doubles as a feedback object, reviewers can react to the artifact, not the deck.

## Conditions
Holds when:
- The team can produce a real proof artifact for each major claim (prototype, mock, customer quote).
- The audience is forum-shaped (a meeting, a demo) rather than async-doc-shaped.
- The product or initiative is concrete enough to demo, not pure strategy.

Fails when:
- Proof artifacts do not exist yet and you fake them; the audience smells it.
- The audience needs a written record they will read later; interleaved decks are harder to skim.
- The pitch is for an inherently abstract policy or strategy decision with no demoable surface.

## Evidence
> "Words will only get you so far... Figma practices what it preaches in terms of the future being visual communication."

Mihika built FigJam launches and her current zero-to-one product launch using this structure. Single shared artifact across the team replaces parallel research / design / product decks.

· Mihika Kapoor on Lenny's Podcast, 2026-04-28

## Signals
- Demos are inserted at every internal forum even when not polished, and audience feedback shifts from abstract to artifact-specific.
- One canonical packet replaces parallel team-specific decks.
- Pitch-to-greenlight cycles shorten because reviewers see the work, not the argument.

## Counter-evidence
April Dunford's setup / follow-through model argues the opposite for B2B sales, establish the frame fully before any product detail. The right read is conditional on audience: internal stakeholders want artifacts; cold buyers want framing first.

## Cross-references
- `ins_setup-follow-through-pitch`, the contrasting B2B sales model