The three startup idea validation frameworks that actually work.

Startup idea validation frameworks are useful only when they survive contact with the evidence. This guide builds the framework that does.

A validation framework is only useful if it is capable of producing a negative result. Most popular validation frameworks (Lean Canvas, Business Model Canvas, Jobs to Be Done, etc.) are thinking tools: they help founders structure their understanding of a business. That is valuable. But they do not generate disconfirming evidence, because they are not designed to test falsifiable hypotheses. They are designed to describe the business as the founder imagines it.

The frameworks below are designed to test. Each one is built around a specific failure mode that accounts for a large portion of startup failures. Each one produces a clear pass or fail result. And each one can be executed in five to ten days of structured research.

The kill criterion test is the most direct method for identifying the conditions under which a startup idea fails before building. The process has three steps.

Step one: write three to five specific, testable conditions that, if true, mean the business cannot work as described. These are not risks. They are binary conditions with clear criteria for truth or falsity.

Step two: for each condition, identify the best available evidence that would indicate whether the condition is true or false. Assign a source: government data, industry association reports, product review analysis, or customer interviews.

Step three: find the evidence. For each kill criterion, research whether it is true using the specified sources. If the criterion is "no compliance officer at a 100-to-500-employee company controls a budget above $10,000 for new software tools," test it by asking three to five compliance officers about their budget authority and by reviewing job postings for the role to find salary and budget responsibility descriptions.

A kill criterion test that reveals two of the five criteria are true does not mean the idea is dead. It means the model as currently designed does not survive those two criteria, and the founder needs to either redesign the model or decide whether the evidence is strong enough to warrant further investigation.

This framework is the basis for every Verdikt research report. The output of the kill criterion test is not a score. It is a map of which critical assumptions hold and which do not, with the evidence cited.

The switchability test is designed to catch the failure mode that accounts for 19 percent of startup failures according to CB Insights' 2023 post-mortem data: being outcompeted by incumbents. The test does not evaluate whether your product is technically better than the competition. It evaluates whether a rational buyer would actually switch to your product given the full economic picture.

For a target buyer, calculate three numbers:

Total switching cost: the all-in cost for this buyer to stop using their current solution and start using yours, including data migration, integration work, training time, contract termination penalties, and productivity loss during the transition.

Annual value delivered: the annual economic benefit your product provides to this buyer, measured in time saved, errors reduced, revenue generated, or cost eliminated.

Payback period: total switching cost divided by annual value delivered. This is how long it takes for the buyer to break even on the decision to switch.

A rational buyer will switch when the payback period is short relative to their planning horizon. For a typical mid-market B2B product, a payback period below 12 months is a strong signal. A payback period above 24 months is a weak signal unless the buyer is in acute pain with the current solution.

Run the switchability test for three different buyer profiles. If two out of three produce payback periods above 24 months, either the price needs to come down, the value proposition needs to be sharpened around the most acute pain point, or the buyer profile needs to change.

The economics-first test inverts the typical product development sequence. Instead of building a product and then figuring out pricing, it starts with the price the market will bear and works backward to determine whether a business with those economics is viable.

Step one: identify the price your target buyer will actually pay. Not the price you intend to charge. The price your five customer interviews suggest they will pay. If your ideal price is $500 per month and three out of five buyers say $200 per month is their ceiling, the economics-first test uses $200.

Step two: estimate the CAC for your planned go-to-market motion using comparable company benchmarks. For a sales-assisted B2B motion at $200 per month ($2,400 ACV), the median CAC from OpenView's 2023 benchmarks is approximately $1,800.

Step three: calculate LTV at a realistic churn rate. For a $200 per month product serving small businesses, 25 percent annual churn is a conservative but realistic benchmark based on Recurly's 2023 subscription industry data. At 25 percent annual churn, the average customer life is 4 years and LTV is approximately $9,600.

Step four: calculate the LTV to CAC ratio. At $9,600 LTV and $1,800 CAC, the ratio is 5.3:1. That is a viable ratio. The payback period is 9 months, which is acceptable for a SaaS business.

Step five: calculate whether the business reaches contribution margin positive at achievable customer counts. If your first 18 months produces 50 customers (a reasonable target with one salesperson and a 12-month selling cycle), monthly revenue is $10,000, and your monthly operating cost is $35,000, you are not at contribution margin positive. You need to either grow faster, reduce costs, or increase price.

The economics-first test surfaces these constraints before you have built anything. A model that only works at 200 customers is not invalidated by this finding: it means you need a plan to reach 200 customers within the runway you have.

The kill-criterion framework is the highest-leverage when the founder cannot articulate a clear failure mode. It forces the founder to write down a falsifiable threshold before doing more work. Use it when the founder is still in conviction mode and has not done customer interviews.

The switchability framework is the highest-leverage when the founder has a credible product but is unsure why a customer would leave the current solution. Switchability isolates the friction. Use it when the product hypothesis is solid and the GTM is unclear.

The economics-first framework is the highest-leverage when the unit-economics math is the constraint. Most founders skip this because the numbers feel abstract pre-launch, but a16z has written that CAC payback and gross margin are the metrics that predict survivability more than topline growth. Use this framework when the wedge is plausible and the question is whether the math can ever work.

The three are complementary, not alternative. A serious validation plan uses all three, in order: kill criterion to define what failure looks like, switchability to test the offer against reality, economics to confirm the math survives.

Day 1 to 7: define the ICP at job-title granularity. Write the cold email. Source 50 to 75 contacts from a defined list (LinkedIn search, state licensing board, community directory). Total cost: $0 to $99 for a Apollo or Hunter.io credit pack if needed.

Day 8 to 21: send the cold emails in batches of 10 per day. Aim for 8 to 15 first conversations across the two weeks. Use The Mom Test interview framework. Take handwritten notes, then transcribe into a single document with one row per interview. Total cost: $0.

Day 22 to 28: build a one-page memo. Cover with verdict and kill criterion. Sections: ICP definition, top three pain points with frequency counts from interviews, switching cost analysis (what they use today, what they would have to give up to use you), pricing hypothesis with three comparable wedges, named falsifier. Total cost: $0.

Day 29 to 30: stress-test the memo with two outside readers (another founder, a friendly investor, a customer who said yes). Their unprompted questions reveal the gaps. Total cost: a coffee.

Total: under $500, 30 days. The output is a defensible memo, a validated ICP, and a kill criterion you can disprove with the next batch of conversations. That is enough to decide whether to spend the next 90 days building or to walk.

Founders who use validation frameworks as comfort blankets, running interview after interview to confirm a wedge they have already decided to build, get the worst of both worlds. The frameworks only produce signal when the founder is genuinely uncertain about the answer. Confirmation interviews produce confirmation. The discipline is to enter every interview with a hypothesis you would update on the right answer.

The second failure mode is sample composition. Twenty interviews with friends-of-friends produce 20 friendly responses. The validation has to be against the real ICP, sourced from a real list, with cold conversations that earn the right to ask hard questions. The frameworks are only as good as the sample. See customer discovery interviews for the operational detail on running this batch well.

The third failure mode is the missed pivot signal. If the interview cohort consistently surfaces a different pain than the one you set out to solve, that is a customer-need pivot. Founders who stay focused on the original wedge miss the company that the interviews were pointing them toward. The Slack pivot from Tiny Speck started with interview signals their team was ignoring. The framework only works if the founder lets it work.