154. Startup Frameworks

Frameworks are useful when they help a founder see a decision more clearly. They are harmful when they become a substitute for judgment.

Use a framework only when you can answer:

What decision are we trying to make?
What evidence will we put into the framework?
What will we do differently after using it?

Strategy and business model frameworks

Framework	Use it for	Watch out for
Lean Canvas	Quickly mapping problem, customer, solution, channels, revenue, costs, and unfair advantage.	Filling boxes with guesses and treating the page as proof.
Business Model Canvas	Understanding how value creation, delivery, and capture fit together.	Too broad for very early idea validation unless paired with customer discovery.
Jobs to Be Done	Understanding the progress customers are trying to make.	Asking abstract questions instead of studying real situations and behavior.
SWOT	Summarizing strengths, weaknesses, opportunities, and threats.	Becoming generic and obvious.
Porter’s Five Forces	Studying industry structure, supplier power, buyer power, substitutes, rivalry, and entrants.	Overusing it for tiny early markets where customer learning matters more.
Blue Ocean Strategy	Looking for differentiated value instead of direct competition.	Confusing “no competitors” with “no market.”

Product and prioritization frameworks

Framework	Use it for	Watch out for
RICE	Prioritizing features by reach, impact, confidence, and effort.	Fake precision. Confidence should punish guesses.
ICE	Ranking ideas by impact, confidence, and ease.	Easy ideas can crowd out hard but important work.
Kano	Distinguishing basic expectations, performance features, and delight features.	Delight does not matter if basics fail.
North Star Metric	Aligning the team around delivered customer value.	Choosing a vanity metric that grows without retention or revenue quality.
Cohort analysis	Seeing whether customers who start together retain, expand, or churn.	Looking only at averages and missing segment differences.

Growth and funnel frameworks

Framework	Use it for	Watch out for
AARRR	Acquisition, activation, retention, referral, revenue funnel thinking.	Optimizing acquisition before activation and retention are healthy.
Pirate metrics by segment	Comparing funnel health across segments and channels.	Treating all users as equal.
Growth loops	Identifying how usage, content, data, referrals, or networks create more growth.	Mistaking one-time campaigns for loops.
Channel scorecard	Comparing channels by lead quality, CAC, payback, retention, and learning.	Declaring a channel bad before messaging and targeting are tested.

Sales frameworks

Framework	Use it for	Watch out for
SPIN	Asking about situation, problem, implication, and need-payoff.	Turning discovery into a script instead of listening.
MEDDICC	Enterprise sales qualification around metrics, economic buyer, decision criteria, decision process, pain, champion, and competition.	Too heavy for simple low-ticket sales.
BANT	Budget, authority, need, timeline.	Rejecting early buyers too quickly when budget or timeline is still forming.
Win/loss review	Learning why deals close or fail.	Accepting surface reasons like “price” without investigating value, urgency, trust, or qualification.

Finance and scale frameworks

Framework	Use it for	Watch out for
Rule of 40	Balancing growth and profitability in later-stage SaaS.	Using it before revenue is meaningful.
Burn multiple	Understanding how much net burn creates net new recurring revenue.	Treating one unusual month as trend.
LTV/CAC	Comparing lifetime value to acquisition cost.	Using fantasy LTV before retention history exists.
CAC payback	Seeing how quickly customer acquisition cost is recovered.	Ignoring collections and gross margin.
Unit economics	Understanding contribution per customer, transaction, or workflow.	Averaging across segments with different behavior.

Which framework should you use?

Use this quick map:

Founder problem	Good first framework
”We do not know who the customer is.”	Jobs to Be Done plus customer discovery
”We have too many product ideas.”	RICE or ICE plus customer evidence
”Traffic is up but revenue is not.”	AARRR funnel by segment
”Sales calls feel random.”	SPIN for discovery and win/loss review
”Enterprise pipeline is bloated.”	MEDDICC or a lighter qualification checklist
”Revenue is growing but cash is tight.”	CAC payback, burn multiple, collections review
”We are unsure whether to scale.”	Cohort retention plus unit economics

Useful framework combinations

Most useful founder work combines two or three lightweight frameworks, not one giant workshop.

Situation	Combine	Output
New idea	Jobs to Be Done + customer discovery + risk map	A sharper problem hypothesis and next test.
Too many segments	ICP scorecard + market map + channel scorecard	A beachhead segment and refusal list.
Product feels bloated	RICE + MVP scope + cohort review	A smaller roadmap tied to evidence.
Sales feels random	SPIN + win/loss review + pipeline stages	Better discovery, qualification, and follow-up.
Growth is noisy	AARRR + cohort analysis + channel quality	A view of which channels create retained customers.
Fundraising story is weak	Bottom-up market sizing + wedge thesis + use-of-funds milestones	A more credible investor narrative.
Cash is tight	Runway + burn multiple + collections review	A decision on cuts, sales focus, or fundraising timing.

If the combination does not produce a decision, simplify it.

Framework worksheet

Before using a framework, fill this:

Question	Answer
What decision are we making?
Which framework will help?
What evidence will we use?
Which assumptions are still guesses?
Who owns the decision?
What will change if the answer is clear?
When will we review the result?

After using it, write one sentence:

Because of this framework, we will [decision/action] by [date].

That sentence is the test. Without it, the framework was theatre.

India founder notes

For Indian startups, frameworks often need local reality added:

Framework	India adjustment
ICP	Include payment behavior, trust path, language/geography, and support expectations.
CAC/payback	Count founder travel, WhatsApp follow-up, procurement time, and delayed collections where relevant.
Sales qualification	Identify the real approver: owner, finance, department head, family, procurement, principal, doctor, or promoter.
Product adoption	Account for onboarding, training, phone support, and offline-to-online behavior.
Market sizing	Separate formal, informal, metro, non-metro, English-first, and regional segments when they behave differently.
Unit economics	Include support, implementation, payment gateway, field operations, and collection cost.

Do not force a Silicon Valley framework onto an Indian market without translating the buying behavior.

Founder rule

One framework, one decision, one next action.

If a framework creates a beautiful slide but no operating change, drop it.

When not to use a framework

Sometimes the best founder move is a direct conversation, a small test, or a clear decision.

Situation	Skip the framework and do this
You have not spoken to enough target customers	Run customer discovery before filling strategy boxes.
A decision is urgent and reversible	Decide, document why, and review quickly.
The team is using frameworks to avoid conflict	Name the disagreement directly.
The inputs are mostly guesses	Run a smaller experiment to create evidence.
The output will not change roadmap, sales, hiring, pricing, or cash decisions	Do not spend time on it.
A customer is waiting for a concrete next step	Send the proposal, scope the pilot, or schedule the decision call.

Frameworks are tools for judgment. They are not a hiding place from judgment.

Stage-based framework stack

Use fewer frameworks than you think you need.

Stage	Primary framework	Supporting tool	Output
Idea	Jobs to Be Done	Problem hypothesis	A clear problem statement and interview list.
Discovery	Customer discovery pattern review	Pain scoring	Continue, change, or stop decision.
MVP	Assumption map	MVP scope	Tiny build plan with success and kill criteria.
First customers	Sales pipeline stages	Win/loss review	Better qualification and next-step discipline.
Early revenue	Cohort analysis	Unit economics	Decision on segment, pricing, retention, or support.
Hiring	Role scorecard	30/60/90 plan	Clear first employee or next role decision.
Fundraising	Use-of-funds milestones	Risk memo	Clear round logic and investor narrative.
Scaling	OKRs	North Star and guardrail metrics	Focused operating cadence.

If a stage has weak evidence, do not jump to later-stage frameworks. A pre-revenue company does not need a complex Rule of 40 discussion. It needs customer proof, pricing proof, and runway discipline.

Framework misuse detector

Use this checklist before running a workshop or creating a slide.

Warning sign	What it usually means
Every box is filled with broad words like “SMBs”, “AI”, “scale”, or “community”	The team is avoiding specificity.
Nobody can name the decision the framework supports	The work is theatre.
Customer evidence is missing	The framework is built on founder imagination.
The founder already knows the answer but wants validation	The framework is being used for politics.
The output creates more projects than constraints	The framework made the company less focused.
No owner or review date exists	The work will not change behavior.

Good framework output should make the company narrower, clearer, or more decisive.

Worked example: choosing an ICP

Question: which first segment should we focus on?

Segment	Pain	Reachability	Budget	Sales cycle	Founder fit	Support load	Score
Export manufacturing CFOs	High	Medium	High	Medium	High	Medium	Strong
Small retail shops	Medium	High	Low	Short	Low	High	Weak
VC-backed SaaS finance teams	Medium	Medium	High	Medium	Medium	Low	Medium

Decision sentence:

For the next 6 weeks, we will focus on export manufacturing CFOs because the pain is repeated, the buyer owns budget, and founder credibility is strongest there. We will reject small retail requests unless they reveal reusable product insight.

That sentence matters more than the scoring table.

One-hour framework review

Use this format when the team needs clarity but cannot afford a strategy workshop.

Minutes	Activity	Output
0-10	Name the decision and deadline.	One decision sentence.
10-20	Pick the simplest framework.	One worksheet, not five.
20-35	Fill only with evidence and clearly marked assumptions.	Evidence/assumption split.
35-45	Discuss what would change the answer.	Top uncertainty list.
45-55	Choose action, owner, and review date.	Decision record.
55-60	State what will not be done.	Refusal list.

This keeps frameworks practical. The output should be a decision, a test, a refusal, or a sharper question.

Framework output standards

A framework is complete only when it creates operating output.

Framework output	Good standard
Decision	Specific, owner named, date named.
Test	Small enough to run quickly, strong enough to change belief.
Refusal	Names what the company will not pursue for now.
Metric	Connected to customer value, revenue, retention, or learning.
Assumption	Labelled with confidence and review trigger.
Communication	Easy enough for team, advisors, or investors to understand.

If the output is “we need to think more,” the framework did not finish the job.

Framework-to-artifact map

Every framework should produce an artifact that can be reviewed later.

Framework	Useful artifact
Jobs to Be Done	Customer situation, trigger, desired progress, current workaround, interview list.
ICP scoring	Segment choice memo with accept/reject criteria.
Assumption mapping	Riskiest assumption list with test plan and review date.
RICE or prioritization	Roadmap decision memo and not-now list.
Funnel analysis	Stage conversion table with one bottleneck owner.
Unit economics	Contribution margin and payback review by segment/channel.
OKRs	Quarterly focus with owners, metrics, and explicit non-goals.
Pre-mortem	Risk register and stop-loss rules.

If the artifact is not useful next month, the framework probably produced workshop residue rather than operating knowledge.

Framework conflict resolver

Sometimes frameworks disagree. Resolve the conflict by returning to the decision.

Conflict	Resolution
Market size says one segment, customer pull says another	Start with the segment where evidence and access are strongest, then map expansion.
RICE says build a feature, strategy says narrow focus	Prefer the strategic constraint unless customer evidence says otherwise.
Funnel data says volume, sales notes say poor quality	Segment leads by quality, not only count.
Unit economics says stop a channel, brand says keep it	Keep only if there is a deliberate learning or strategic reason.
OKRs say growth, runway says survival	Cash reality wins until options improve.

A framework is not the boss. The founder is responsible for judgment.

Founder framework hygiene

Keep a simple record:

Field	Notes
Decision
Framework used
Evidence used
Assumptions labelled
Decision made
What we will not do
Review date

This prevents the team from rerunning the same debate with a different framework every month.

Framework picker cheat sheet

Use the smallest framework that can improve the next decision.

Founder situation	Use	Do not use
We do not know which customer to serve	ICP scoring, Jobs to Be Done, customer segmentation	A broad market-size deck
We are debating features	Assumption map, RICE/ICE, scope cut line	A full roadmap workshop
We have traffic but weak conversion	Funnel analysis, message-to-market review	Brand strategy theatre
Sales calls are vague	MEDDICC-lite, SPIN, buyer map	More demo polish
Metrics are noisy	North Star, cohort analysis, activation definition	Too many dashboards
Cash is becoming tight	Runway, burn multiple, scenario plan	Optimistic annual forecast only
Team is scattered	OKRs, decision log, weekly operating review	More meetings without owners

Quick rule:

If the framework does not produce a decision, refusal, test, owner, or metric, it was probably entertainment.

The best founder use of frameworks is not intellectual elegance. It is better judgment under uncertainty.

Founder Framework Failure Review

When a framework produces a bad decision, do not simply switch to a new framework. Review why the old one failed.

Failure mode	What happened	Fix
Wrong evidence	The team used opinions, anecdotes, or investor logic instead of customer facts.	Rebuild the framework with real evidence and label confidence.
Wrong unit	The framework treated all customers, channels, or features as one group.	Segment before deciding.
Wrong time horizon	The team optimized for this week’s pressure while pretending to make strategy.	Separate urgent survival decisions from durable strategy.
Wrong owner	A workshop produced insight but nobody owned the next action.	Every framework output needs an owner and review date.
Wrong incentive	The framework was used to justify a decision already made.	Ask what evidence would change the decision.
Too much complexity	The framework made the team feel smart but did not clarify action.	Use a smaller framework or write a plain decision memo.

Use this prompt after any major decision:

Did the framework improve the quality of the decision, or did it only make the decision look structured?

Founders do not need more frameworks. They need better loops between evidence, decision, action, and review.

Five-minute framework decision filter

Use this before opening a canvas, spreadsheet, or whiteboard.

Question	If the answer is weak
What decision are we making this week?	Do not use a framework yet. Write the decision first.
What evidence do we already have?	Run customer, sales, product, or finance evidence collection first.
What evidence is missing?	Use the framework only to identify the missing evidence.
Is the decision reversible?	If yes, prefer a small test over a large workshop.
Who owns the decision?	Assign one owner before starting.
What will we stop doing if the answer is clear?	If nothing will stop, the framework may not matter.

Decision filter output:

We are using [framework] to decide [decision] by [date].
The evidence we trust is [evidence].
The assumption we still need to test is [assumption].
The output must be [decision/test/refusal/metric].

This keeps frameworks attached to action. A founder should be able to explain the framework in one minute to the team, an advisor, or a co-founder.

Framework recipes by founder symptom

Sometimes founders know the symptom before they know the framework. Use this map.

Symptom	First move	Useful framework
”Customers like it but do not buy.”	Separate politeness, pain, budget, and urgency.	Buyer discovery + sales qualification.
”Users sign up but disappear.”	Find the first-value drop-off.	Activation funnel + cohort review.
”Every customer wants something different.”	Decide whether the segment is real or too broad.	ICP scoring + roadmap refusal list.
”Our pitch keeps changing.”	Identify the most repeated customer pain and outcome.	Jobs to Be Done + positioning.
”Marketing creates leads but sales hates them.”	Compare channels by qualified next steps, not lead volume.	Channel scorecard + funnel by segment.
”Revenue is growing but cash feels bad.”	Inspect collections, gross margin, implementation load, and burn.	Unit economics + runway review.
”The team is busy but nothing compounds.”	Name the one operating priority and non-goals.	OKRs + weekly founder review.
”Investors do not understand the story.”	Tie capital to milestone and risk reduction.	Use-of-funds milestone map + investor memo.

The symptom is a clue, not a diagnosis. If the framework output does not make the next week clearer, return to raw evidence.

Founder evidence standards

Use different standards for different decisions.

Decision type	Minimum useful evidence
Choose customer segment	Repeated real pain, reachable buyers, willingness to engage, believable payment path.
Build MVP	Riskiest assumption, success metric, kill criteria, first users ready to observe.
Change pricing	Customer value evidence, comparable alternatives, buyer reaction, collection reality.
Hire	Repeated bottleneck, role scorecard, manager readiness, cash runway, first 30-day outcome.
Fundraise	Milestone logic, current metrics, risk memo, cap table, data room, investor fit.
Scale channel	Retention or revenue quality by channel, CAC/payback, support load, repeatability.
Pivot	Evidence current path is weak, evidence new path has pull, cost of change understood.

Do not demand perfect evidence for every decision. Demand the right evidence for the cost of being wrong.

Framework Decision Stack

Founders often use too many frameworks at once. A better pattern is a small decision stack: one frame for the decision, one artifact for the output, and one review loop for whether the decision worked.

Use this stack:

Layer	Purpose	Example
Decision frame	Clarifies the question.	ICP scorecard, RICE, unit economics, customer discovery pattern review.
Evidence source	Keeps the frame honest.	Interview notes, sales calls, cohort data, support tickets, cash view.
Artifact	Turns thinking into something inspectable.	Segment memo, roadmap decision, pricing test, hiring scorecard, runway plan.
Review loop	Checks whether the decision improved reality.	Weekly metric review, win/loss review, postmortem, stage gate.

Example for a founder choosing a first customer segment:

Stack layer	Choice
Decision frame	ICP scorecard.
Evidence source	30 customer conversations, 10 pricing asks, current workaround notes.
Artifact	One-page beachhead memo with accept/reject criteria.
Review loop	Four-week sales and activation review by segment.

Example for a founder deciding whether to hire:

Stack layer	Choice
Decision frame	Bottleneck map and role scorecard.
Evidence source	Founder calendar, missed commitments, customer response time, revenue stage, runway.
Artifact	Role memo with first 30-day outcomes and manager owner.
Review loop	30/60/90-day performance and founder delegation review.

If a framework does not connect to an artifact and review loop, it will be forgotten. The output should survive the meeting.

Copy-paste framework decision memo

Use this whenever a framework is used for a material decision: customer segment, pricing, roadmap, hiring, fundraising, GTM channel, pivot, or cost cut. The memo keeps the framework from becoming a workshop artifact with no owner.

Decision:

Why this decision matters now:

Framework used:

Evidence used:
- Customer evidence:
- Sales/revenue evidence:
- Product/usage evidence:
- Finance/runway evidence:
- Team/operations evidence:

Assumptions we are making:
1.
2.
3.

Confidence level:
High / medium / low because [reason]

Decision:
We will [do / not do / test / defer] [choice].

What we will stop or refuse:

Owner:

First action by:

Success signal:

Failure or reversal signal:

Review date:

Memo quality test

Before sharing the decision, ask:

Test	Good answer
Is the decision clear?	A team member knows what changes tomorrow.
Is the evidence labelled?	Facts, assumptions, guesses, and opinions are not mixed together.
Is there a refusal?	The memo says what the company will not do now.
Is there an owner?	One person owns follow-through, even if many people contribute.
Is there a review loop?	The company knows when and how to judge the decision.
Is the language plain?	A smart advisor or new team member can understand it without attending the meeting.

If the memo cannot be written, the framework probably did not clarify enough. Return to evidence, reduce the scope, or run a smaller test.