You have an idea. It arrived in the shower, it feels obvious, and part of your brain is already picking the tech stack. This is exactly the moment to spend 30 minutes trying to kill it.
Most builders skip that step because "business case" sounds like a 40-slide deck for a steering committee — so they jump straight to code and learn three months later that the market answer was "no" all along. This guide shows the lightweight version: a one-page template, kill criteria, two worked examples (one that passes, one that fails), and the self-deceptions that sink smart builders.
Why builders skip the business case — and what it costs
A business case is a short structured argument for why a product should exist: the problem, who has it, how big the opportunity is, how it makes money, and what could kill it. Builders skip it because the format has a corporate reputation — committees, sign-off theater — and because writing one risks hearing "no" before the fun part starts. But the cost of skipping is asymmetric: the case takes 30 minutes; an MVP takes 6–12 weeks of nights and weekends. CB Insights' post-mortem analysis found "no market need" among the top reasons startups fail — a failure mode almost entirely detectable on paper, before a single line of code. The lightweight business case moves that discovery from month three to minute thirty.
The reframe that makes it palatable: a business case isn't a permission slip, it's a pre-mortem. The corporate version optimizes for defensibility; the builder version optimizes for speed to a kill decision. Different tool, same name.
What a lightweight business case actually contains
A lightweight business case answers six questions on one page: What's the problem and who has it? How are they solving it today? How big is the reachable market? Why would they pay, and how much? How does this make money? What would have to be true for this to fail? Each answer is 2–5 sentences in plain language, with your confidence marked honestly (guess / anecdote / evidence). The whole document should fit on one screen — if it doesn't, you're padding, and padding is where self-deception hides. The output isn't a grade; it's a decision. If every idea you run through the template survives, your kill criteria are too soft.
Four terms, defined once:
- TAM (total addressable market): everyone who could conceivably use a product like yours, in revenue terms.
- SAM (serviceable addressable market): the slice of TAM you could actually reach with your product and channels.
- SOM (serviceable obtainable market): the slice of SAM you can realistically win in the next couple of years.
- Willingness to pay: the price at which a specific customer actually hands over money — not whether they call the idea "cool."
For solo builders, TAM is nearly useless; SOM is nearly everything.
The 30-minute business case template (copy-paste)
The template below is designed for a strict 30-minute timebox: five minutes per section, no research rabbit holes, guesses explicitly labeled as guesses. The discipline matters more than the accuracy — the first pass's goal is not to be right but to expose which sections you can't fill in without hand-waving. Those sections are your validation to-do list. Copy the markdown into your notes app, set a timer, and write in full sentences: bullets let you hide from your own logic, prose forces the argument to connect. When the timer ends, read it back and make one of three calls: build, test one named assumption first, or kill.
# Business Case: [idea name] — [date]
## 1. Problem (5 min)
Who specifically has this problem? (a person you could DM, not a demographic)
What do they do today instead? (the current workaround IS your competitor)
How painful is it: annoyance, recurring cost, or hair-on-fire?
Confidence: guess / anecdote / evidence
## 2. Audience & reach (5 min)
Where do these people already gather? (subreddits, Slacks, newsletters)
Can I get 20 of them on a call or in a DM this month? How?
Confidence: guess / anecdote / evidence
## 3. Market framing (5 min)
SOM first: how many customers could I realistically win in 18 months?
At what price? SOM revenue = customers × price × 12.
Is that number worth my next year? (Compare to your alternatives, honestly.)
## 4. Monetization (5 min)
Who pays — the user or someone else? One-off, subscription, or usage?
What do they pay for adjacent tools today? (proof of willingness to pay)
What's my price anchor, and why would switching be worth it?
## 5. Competition & alternatives (5 min)
Top 2-3 alternatives, including "spreadsheet" and "do nothing."
Why do people churn from those? (If I can't answer, I haven't looked.)
What's my wedge — the one segment where I'm clearly better?
## 6. Kill risks (5 min)
The single assumption that, if false, kills this. How will I test it?
Distribution: what's my repeatable channel? ("Launch on PH" is an event, not a channel.)
Verdict: BUILD / TEST FIRST (name the test) / KILL
If you'd rather not stare at a blank page, VibeMap's Business Case Generator drafts this first pass from a one-paragraph idea description — a starting point to argue with, not a verdict.
Worked example: a business case that says yes
Here's a full example for a plausible indie SaaS idea, written in about 30 minutes, so you can see what "good enough" looks like — including honest guesses. The idea: RetainerFlow, a tool for freelance designers and developers who bill monthly retainers. It tracks hours against each client's retainer, sends an automatic monthly usage report, and flags overages before they become awkward conversations. What makes this case pass: a specific reachable audience, a workaround that visibly leaks money, proven willingness to pay for adjacent tools, and a SOM number that clears the builder's personal bar. Note what it does not claim — no billion-dollar TAM, no "no competitors" — and that it still exits with a test, not a build order.
Problem. Freelancers on retainers track hours in Toggl or a spreadsheet, then manually assemble a monthly summary — or skip it, eat overages silently, and resent the client. Cost: 1–2 hours/month plus unbilled work. Confidence: anecdote (three freelancer friends, two r/freelance threads).
Audience & reach. Freelance designers/devs with 2+ retainer clients. They gather in r/freelance, Indie Hackers, and freelancer Slacks; I can DM 20 this month via two communities I'm already in. Confidence: evidence for reachability.
Market framing. SOM: 300 paying users in 18 months at $15/month = $54k ARR. Small — but as a solo side product it clears my bar. I'm not claiming the freelance-software TAM; I'm claiming 300 specific people.
Monetization. The freelancer pays; the report is client-facing and makes them look professional — a business expense. They already pay for Toggl and invoicing tools ($10–30/mo each). Anchor: $15/mo — "recover one overage hour and it pays for the year."
Competition. Toggl and Harvest track time but don't do retainer-aware client reporting; spreadsheets do it badly; "do nothing" is the real incumbent. Wedge: retainer-specific, client-facing by default.
Kill risk & verdict. Kill assumption: freelancers will pay rather than tolerate the spreadsheet. Test: 20 DMs about the last overage conversation — past behavior, not hypotheticals. Verdict: TEST FIRST, build only if 6+ of 20 describe recent, painful overages.
Worked example: a business case that says no
A business case that kills an idea is a success, not a failure — it just saved you a quarter. Here's one that fails, written with the same template and the same honesty. The idea: HabitMind, an AI-powered habit tracker that gives personalized coaching nudges based on streak data. It feels compelling — everyone struggles with habits, AI coaching is hot, the builder would use it themselves. On paper it dies in three of six sections, and its failure modes — crowded market with free incumbents, low willingness to pay, no wedge, no channel — are the most common ones in consumer-adjacent indie ideas. If your idea resembles this shape, the template will tell you quickly.
Problem. People abandon habits. True, universal — and mostly solved to the level people will pay for. Alternatives: Habitica, Streaks, Apple's built-ins, free ChatGPT prompts, paper. Pain level: annoyance, not hair-on-fire.
Audience & reach. "People who want better habits" is a demographic, not an audience. There's no room where they gather as buyers — habit-tracker communities mostly compare free apps.
Market framing. SOM math collapses: consumer habit apps churn heavily, and app stores show hundreds of free-tier competitors. $50k ARR at $5/month needs ~830 retained subscribers in a category where retention is the known graveyard.
Monetization. The killer. People say habits matter but pay for outcomes (a gym, a coach), not tracking. My anchor competes with "free," and "AI coaching" is a feature ChatGPT gives away.
Competition & wedge. No wedge. "Mine has better AI" is not a segment; it's a hope.
Kill risk & verdict. The kill assumption — people will pay for AI habit nudges — already has abundant negative evidence in public churn data and the free-tier arms race. Verdict: KILL. Deciding cost 30 minutes; learning it via an MVP would cost a quarter of evenings.
The kill criteria checklist
Kill criteria are pre-committed conditions under which you walk away — written down before you fall further in love with the idea. They convert a fuzzy emotional decision ("but I've already thought about this so much") into a checklist you agreed to while still objective. Run it after filling in the template: one hard fail means kill or fundamentally reframe; two soft fails mean test before building. The checklist deliberately weights distribution and willingness to pay over product cleverness, because startup post-mortems cite market and distribution failures far more often than product failures. Print it, and honor your own pre-commitments.
Hard kills (any one = stop or reframe):
- I cannot name a specific, reachable person with this problem
- The current workaround is free and good enough (pain is an annoyance, not a cost)
- Willingness to pay is unproven and untestable within a month
- SOM revenue at honest numbers doesn't clear my personal bar
- My only distribution plan is a launch event (Product Hunt, HN) rather than a repeatable channel
Soft fails (two or more = test first):
- My confidence column says "guess" in more than three sections
- I can't explain why people churn from the top alternative
- My wedge is a feature ("better AI") rather than a segment, or I'm the only user I've talked to
If the idea survives, the next step is turning the case into a plan — why planning-first development boosts ROI and writing user stories with INVEST pick up from here.
Common self-deceptions (and how the template catches them)
Self-deception in product validation is rarely lying — it's choosing the framing that lets the fun part start sooner. Three patterns account for most of it. TAM theater: citing a giant market ("fitness is a $100B industry") as if size implies capturability; the template counters this by forcing SOM-first math in real customer counts. "No competitors means wide open": if nobody solves this problem for money, the likeliest explanation is that nobody will pay — so the template forces you to list "spreadsheet" and "do nothing" as competitors, which always exist. Solution-first reasoning: starting from a technology you want to use and back-filling a problem; the tell is a problem statement that mentions your solution. Each deception survives vibes but dies on one page of prose.
A fourth, subtler one: validation by compliments. "Everyone I showed it to loved it" is the most dangerous sentence in indie hacking. Rob Fitzpatrick's The Mom Test is the canonical fix — ask about past behavior and current spending, never hypothetical enthusiasm.
Once an idea genuinely passes, move fast on the next artifact — a concrete spec. See how to generate an app spec from a prompt for the fastest path from verdict to buildable plan.
FAQ
How long should a business case take for an indie product?
Thirty minutes for the first pass, with five minutes per section. The first draft's job is to expose which sections you can't fill honestly — those become your validation tasks. A second pass after customer conversations might take another hour. Days on it means you've drifted into corporate territory.
What's the difference between a business case and a business plan?
A business plan is a long operating document: financials, org, multi-year projections. A business case is a short argument for one decision — should this product exist? For builders the case is the useful one: plans age badly, while a one-page case gets re-tested against reality every time you learn something.
How do I validate a product idea without building anything?
Test the kill assumption directly: 15–20 conversations about past behavior and current spending, a landing page with a real price, or pre-sales. Each targets willingness to pay — the thing an MVP is worst at testing, since free beta users tell you nothing about paying customers.
What should a business case template include?
Six sections: problem and who has it, audience and reach, market framing (SOM-first), monetization and willingness to pay, competition including "do nothing," and kill risks with a verdict. Add a confidence label per section — guess, anecdote, or evidence — so optimism can't hide.
What are TAM, SAM, and SOM in plain terms?
TAM is everyone who could conceivably use a product like yours; SAM is the slice you could actually reach; SOM is what you can realistically win in the next 18–24 months. Solo builders should do the math from SOM up, not TAM down.
Is a business case generator worth using?
As a first-draft accelerator, yes; as a verdict, no. A good generator structures a one-paragraph idea into problem, audience, market framing, monetization, and risks — killing blank-page paralysis. You still supply the honesty: correct its guesses against real conversations, and let the kill criteria decide.
What's a good kill rate for product ideas?
If fewer than a third of your ideas die at this stage, your criteria are too soft. Ideas are cheap and abundant; quarters of your life are not. A healthy pipeline kills most ideas on paper, tests a few, and builds the rare one that survives both.
When should I ignore the business case and build anyway?
When you're building for learning or joy rather than revenue — say so explicitly and skip the theater. Occasionally an idea fails on paper but you hold private conviction the market is wrong; the case still helps then, because it names precisely which assumption you're betting against.
Ready to pressure-test an idea? Paste one paragraph into the free Business Case Generator for a directional first draft, then grab the free Spec Kit for when it earns a "build."
