PRISM

A Concurrent Product Launch Framework · 0 to 1

PProblem Discovery

RResearch

IIdeation

SSolution Build

MMarket Execution

How to Use This Framework

PRISM is a concurrent product launch framework. Unlike stage-gate linear models, phases P through M can overlap and run in parallel. Two decision gates and one continuous feedback loop create structure without creating bottlenecks. This document is a working instrument — blank table rows are editable directly in your browser.

Use Save Edits to persist your work across sessions, and Print / Export PDF to share with stakeholders.

Framework at a Glance

	Phase	Core Question	Key Output
P	Problem Discovery	Is there a real, acute, human problem worth solving?	Hypothesis · Persona · Pain map · WTP signal
R	Research	What does the landscape look like and where is the white space?	Market sizing · Competitive map · Industry analysis
I	Ideation & Evaluation	What is the strongest concept, and can we actually build it?	Problem statement · User stories · North Star
S	Solution Build	Does the MVP prove the core value hypothesis?	Functional MVP · User signals · Gate 2 decision
M	Market Execution	How do we reach the right people, convert, and retain them?	GTM plan · PnL model · Feedback system

Concurrent Flow

Problem Discovery

Research

Ideation

Gate 1

Solution Build

Gate 2

Market

Phase P

Problem Discovery

GoalGround the product idea in a real, acute, human problem before any solution thinking begins.

Runs concurrently withPhase R (Industry Research) — both start on Day 1

OutputsValidated hypothesis · Target persona · Pain point map · Desperation score · WTP signal

P1 · Hypothesis Statement

Begin with a falsifiable hypothesis, not a conviction. Write it before any customer conversations so you can measure how much it changes.

Hypothesis Template

"[Target audience] struggles with [problem] because [root cause]. We believe [solution type] will [outcome], which we will know is true when [measurable signal]."

Your Hypothesis

P2 · The People Problem

Every problem has three layers. Stop at the functional layer and you build a tool. Solve the emotional layer and you build a brand.

Layer	Definition	Example
Functional	What they cannot do, or cannot do efficiently	"I can't track expenses across accounts in one place"
Emotional	How the problem makes them feel	"I feel out of control and anxious about money"
Social	How it affects their identity or perception by others	"I'm embarrassed I don't have my finances together"

P3 · Target Persona

Draw a specific person, not a demographic segment. Specificity here prevents every subsequent phase from being pulled in too many directions.

Dimension	Your Notes
Name / Archetype
Demographics
Goals
Current Tools & Workarounds
Key Frustrations
A Day in Their Life

P4 · Pain Point Mapping

Map the full landscape of pain, ranked by severity. For each pain point, identify the current solution and its specific failure mode.

Pain Point	Current Solution	Gap / Failure Mode	Severity (1–5)

P5 · Desperation Score & WTP Signal

Desperation Score

Rate 1–10: how urgently do people need a solution? Gather from interviews. Below 7 is a warning — people may acknowledge the problem but not act to solve it.

WTP Signal

What are they currently paying to manage this problem? What would they pay to eliminate it? Let them name numbers first. Warning: High desperation + low WTP usually signals an awareness problem, not a product problem.

Signal	Your Finding
Desperation Score (1–10)
Current Spend (proxy WTP)
Stated WTP
Interpretation

P6 · Discovery Interviews

Minimum 5–10 conversations with people matching the target persona. These are listening exercises — not demos, not validation sessions.

Tell me about the last time you [experienced the problem]. Walk me through exactly what happened.
What did you do to deal with it? Why that approach and not something else?
What is the most frustrating part of how you handle it today?
How much does this cost you — in time, money, stress, or missed opportunity?
If this problem disappeared tomorrow, what specifically changes for you?

P + R Sync Point

Before opening Phase I: (1) Hypothesis tested against 5+ conversations and meaningfully updated. (2) Research findings reviewed against persona and pain assumptions. (3) Contradictions between market data and user interviews resolved.

Phase R

Research

GoalMap the landscape — market, competitors, trends, and analogues — before committing to any solution direction.

Runs concurrently withPhase P (Problem Discovery) — both start on Day 1

OutputsMarket sizing (TAM/SAM/SOM) · Competitive landscape · Industry analysis · White space identification

R1 · Industry Landscape

Dimension	Your Research
Tailwinds
Headwinds
Regulatory / Compliance
Timing Signal

R2 · Market Sizing

Bottom-up estimates from your persona are more credible than top-down industry reports.

Level	Definition	Your Estimate & Basis
TAM	Everyone globally with this problem at meaningful severity
SAM	Those you can realistically reach with your GTM motion
SOM	Realistic capture in years 1–3 given your constraints

R3 · Competitive Landscape

Map three types of competition. The status quo is almost always the most dangerous competitor and the most overlooked.

Type	Player	Key Strength	Key Weakness	Pricing
Direct
Direct
Indirect
Status Quo

R4 · White Space Analysis

Question	Your Answer
Underserved segment?
Poorly-solved job-to-be-done?
Genuine differentiation path?
White space ceiling?

R5 · Analogous Markets

How was this problem solved in adjacent industries? Pattern recognition across categories accelerates good judgment.

Analogue	What They Did	What You Can Borrow or Invert

Phase I

Ideation & Evaluation

GoalDefine the solution space, select the strongest concept, and stress-test it before any building begins.

Starts afterP + R Sync Point — both phases converged, contradictions resolved

OutputsProblem statement · User stories · Selected concept · Early adopter profile · Principles · North Star metric

I1 · Problem Statement & User Stories

HMW Format

"How might we [help target persona] [achieve goal / eliminate pain] so that [meaningful outcome]?" The HMW format keeps the problem open enough for creative solutions while specific enough to rule out irrelevant ones.

Your Problem Statement (HMW)

User Stories

Map one story per validated pain point. Format: "As a [persona], I want to [action] so that [benefit]." If a story can't be traced to a pain point from P4, it is a feature idea, not a user need.

User Story	Maps to Pain Point

I2 · Solution Ideation

Diverge before you converge. Generate a minimum of 10 concepts. The discipline is to generate options before committing to one.

What if it were entirely free — how would it sustain itself?
What if there were no technology involved at all?
What if the user did nothing and the problem solved itself?
What would a platform company (Amazon, Google, Apple) build?
What if you solved it perfectly for one person instead of adequately for many?

Concept	Impact Potential	Feasibility

I3 · Early Adopter Definition

Early adopters are not your target audience. They're the subset who will use an unfinished product, give honest feedback, and tolerate friction. Define them separately.

Dimension	Your Notes
Profile
Pain Intensity
Tolerance for Rough Product
Feedback Quality Signal
Acceptance Criteria

I4 · Principles, Pillars & North Star

Product Principles

Principle — "We will always... / We will never..."

Product Pillars

Pillar	What It Means for Product Decisions

North Star Metric

North Star Test

If this number goes up, does user life genuinely get better? Revenue is not a north star — it's a lagging outcome. The north star is a leading indicator of real value delivered.

Component	Your Answer
North Star Metric
Why this metric
How measured

Gate 1 · Evaluation Checkpoint

Before proceeding to Phase S — all five criteria must be assessed. Where you loop back depends on what specifically failed.

Criterion	What to Evaluate	If Fail → Route To
Feasibility & Ops	Can current team, time, budget, and technical capacity build and sustain this?	I2 — Re-ideate within constraints
Moat Assessment	Is there defensibility? Network effects, data moat, switching costs, IP, brand?	I2 — Redesign for defensibility
Market Potential	Does your SOM validate the business model? Is demand real, confirmed through P interviews?	P1 — Re-examine hypothesis
Business Alignment	If existing business: does this extend the core or dilute it? Aligns with stated strategic vision?	Escalate or Stop
Retention Potential	Why would users come back? What is the recurring need, habit loop, or switching cost once adopted?	I4 — Revisit north star & pillars

Phase S

Solution Build & Validation

GoalBuild the smallest thing that proves or disproves the core value hypothesis.

Starts afterGate 1 cleared across all five criteria

OutputsFunctional MVP · Quantitative + qualitative user signals · Pivot or Persevere decision (Gate 2)

S1 · MVP Scoping

An MVP is not a bad version of the product. It is a focused version — deliberately incomplete in ways that do not compromise the core value test.

Dimension	Your Definition
Core Job (one sentence)
Explicit Scope Cut
Build Time Boundary
Success Benchmark

S2 · Prototype & Build Sprint

Start with the lowest fidelity that generates a real signal. Progress in order of build cost — never skip ahead.

Fidelity Level	Use For
Paper prototype / Figma	UX validation — before any engineering time is spent
Wizard of Oz	Demand testing — human-powered backend tests the concept before infrastructure is built
Concierge MVP	Value testing — do it manually for a small group before automating it
Functional MVP	Core job only — build what the one job requires and nothing else

S3 · User Signal Capture

Signal Type	What to Measure	Your Findings
Behavioral	Task completion, return visits within 7 days, engagement depth
Attitudinal	Post-use interviews, session recordings, support tickets
Referral Signal	Did they tell someone? Did they bring someone else?

S4 · Signal Evaluation

Evaluate signals against acceptance criteria from I3. Answer these three questions before the Gate 2 decision.

Question	Answer + Evidence
Is value understood without explanation? (Not after a demo — without any guidance.)
Is the core problem measurably reduced?
Is there an early retention signal? (Returned within 7 days, unprompted.)

Gate 2 · Pivot or Persevere

Before proceeding to Phase M — diagnose why before routing. Each failure mode routes differently.

Diagnosis	What It Means	Route To
Value not understood	Messaging and positioning failure — not a product failure. The product may work; the explanation doesn't.	Work M1 (Positioning) first, then re-test
Core problem not solved	Solution approach is wrong. Problem definition is likely still correct.	I2 — Solution redesign
Wrong audience engaging	Product attracts users but they are not the persona designed for. Conversion and retention will be structurally poor.	P3 — Persona re-examination
Product not used at all	Severe signal absence. Awareness, onboarding, or problem acuity is the issue. Requires deep diagnosis first.	P1 or escalate to Stop
Signals are strong	Value understood without explanation. Core problem measurably reduced. Early retention signal exists.	✓ Proceed to Phase M

Phase M

Market Execution

GoalTake a validated product to market systematically, profitably, and with a clear path to scale.

Starts afterGate 2 cleared — signals are strong

NoteM9 (Unit Economics) and M10 (Continuous Feedback) run continuously from launch forward — not a one-time step.

M1 · Positioning & Messaging

Positioning is the strategic foundation. Everything downstream — messaging, creative, sales, pricing — derives from it.

Category Play Decision

	Enter Existing Category	Create New Category
Meaning	Compete on differentiation within a defined, understood space	Define the rules of a new game — you name and own the frame
Advantage	Faster to explain, lower education cost, existing demand	Own the frame; competitors always play on your terms
Risk	Always compared to incumbents; commoditization pressure	Higher market education cost; slower initial adoption
Choose when	You're meaningfully better on the dimension ICP cares most about	Your product fundamentally changes how the problem is understood

Component	Your Work
Category Play
Positioning Statement
Primary Message
Proof Points (3)
Differentiation Wedge

M2 · ICP Sharpening for GTM

Your Phase P persona was for product-market fit. Your GTM ICP adds four commercial filters.

Filter	Definition	Your ICP Profile
Pain	Acute problem — high desperation score, not mild inconvenience
Budget	Financial capacity to pay your price point without slow procurement
Authority	Can make or directly influence the purchase decision
Urgency	Needs a solution now — deadline, cost, competitive pressure

M3 · Brand & Category Perception

Component	Your Work
Mental Real Estate
Category POV
Brand Voice
Credibility Signals

M4 · Pricing & Packaging

Pricing is positioning. It signals who the product is for and how serious you are. Connect directly to the WTP signal from Phase P.

Component	Your Decision
Pricing Model
Tier 1 (Entry)
Tier 2 (Core)
Tier 3 (Scale / Enterprise)
Price Anchor

M5 · Acquisition Strategy & Channel Mix

Choose a primary motion before spreading across channels. Attempting three motions simultaneously is how companies waste year one.

Motion	How It Works	Best Fit
Product-Led Growth	Product acquires users itself — viral loops, freemium, in-product upsell	High-frequency, natural virality or network effects
Content / Community-Led	Trust and authority before conversion — SEO, thought leadership, community	Products where education and trust precede purchase
Sales-Led	Human in the loop from first contact — outbound, demos, enterprise	High ACV, complex buying decisions, regulated industries

Decision	Your Choice + Rationale
Primary Motion
Channel 1 (Deep)
Channel 2 (Activate when)

M6 · Launch Architecture

A launch is not a single moment. It is a phased progression with defined success criteria at each stage before advancing.

Phase	Audience	Goal	Gate to Advance
1 · Soft Launch	Closed beta — early adopters only	Proof points, testimonials, edge cases, acceptance criteria met	I3 acceptance criteria achieved
2 · Limited Public	Expanded ICP — controlled access	Conversion data, CAC first read, unit economics baseline	LTV:CAC trending toward 3:1
3 · Full Launch	Public — go loud	Scale awareness, press narrative, growth engine activated	Phase 2 metrics stable and repeatable

Component	Your Plan
Launch Narrative
Phase 1 Date + Beta List
Phase 3 Target Date

M7 · Distribution & Partnerships

Distribution is how the product reaches scale beyond direct acquisition. Consistently the most underleveraged dimension of a launch.

Channel Type	Specific Opportunity	Priority
Marketplace / Platform
Integration
Channel Partner
Creator / Community
Highest-Leverage Bet

M8 · Sales Motion

Component	Your Definition
Motion Type
Key Conversion Moment
Sales Enablement Needs
Escalation Trigger

M9 · Unit Economics & PnL

Model before launch. Validate with actuals post-launch. The goal is to understand which assumptions are wrong and update quickly.

Metric	Target (Baseline)	Your Model	Post-Launch Actuals
CAC	Depends on ACV + motion
LTV	LTV:CAC > 3:1
Payback Period	< 12 months
Gross Margin	> 60% (SaaS)
Net Revenue Retention	> 100%

M10 · Continuous Feedback System

Component	Your Setup
North Star Dashboard
Supporting Metrics
Qualitative Cadence
Feedback Triage Rule

M11 · Evolution & Scale (1 → N)

Scaling is not a continuation of launching. It requires different thinking, different metrics, and often different people. Recognize the transition and plan for it now.

Component	Your Definition
Expansion Trigger
Scale Criteria (3 conditions)
Kill Criteria
Roadmap Handoff