Here's how most customer discovery goes:
You schedule a 30-minute call. You walk through your idea. You ask "would you use something like this?" The person says "oh yeah, definitely — this sounds really useful." You hang up feeling validated. You do ten more calls. They all go roughly the same way.
Then you build the thing. And nobody buys it.
The problem wasn't the conversations. The problem was what you were asking. You asked about the future, not the past. You asked about opinions, not behavior. You were running a validation exercise dressed up as discovery — and because humans are fundamentally nice and don't want to disappoint you, you got exactly the answer you were looking for.
Not a sales call. Not a pitch. Not a product demo with a feedback survey.
Customer discovery is a structured conversation to understand your potential customer's world — not to explain yours. You're there to learn: what problems they actually have, how they're currently solving them, what they've tried before, how they make decisions, and what it costs them when nothing changes.
If you're spending most of the call talking, something has gone wrong.
In The Mom Test, Rob Fitzpatrick makes the observation that should be required reading for anyone building a product: people will lie to you, but not on purpose.
Most people are kind. They don't want to crush your enthusiasm. So when you pitch your idea and ask "would you use this?", they say yes — even when they wouldn't. They're not deceiving you; they're being polite.
Fitzpatrick's insight: you have to make it impossible for people to lie to you — not by confronting them, but by asking questions they can't answer politely. Specifically, questions about the past and present, not the future.
"Would you use this?" is a hypothetical about a future that doesn't exist. Compare it to: "Tell me about the last time you dealt with this problem. What did you do?"
That question has a real answer. If they can't recall a specific recent instance, that's extremely important information about how acute the problem actually is. Past behavior doesn't lie the way future intent does.
If you want a copy-and-paste set, here are 20 customer-discovery questions to ask, grouped by what each one is designed to reveal.
To understand the problem:
To understand current solutions:
To understand what's been tried:
To understand cost and priority:
To understand the decision:
Questions to avoid: "Would you use X?" / "Do you think X would be valuable?" / "Would you pay for X?" / "What features would you want?" — all hypothetical, all produce invented answers.
The most valuable thing you learn is often not what you expected.
Workarounds are the strongest signal a problem is real. If someone has built an elaborate spreadsheet, a multi-step manual process, or a hack involving three tools duct-taped together — that's not just a problem. That's a problem painful enough that they built their own solution. Workarounds are a far stronger signal than "yes, that's annoying." They tell you the person cared enough to do something about it.
The buyer isn't always who you assume. Many founders discover mid-interview that the person they're pitching isn't actually the decision-maker — and the person who controls the budget has completely different priorities. "Who else would need to be involved in a decision like this?" asked every time prevents you from building a product for the wrong person.
Price reveals itself through context, not direct questions. "Would you pay $X/month for this?" is a hypothetical that produces an invented answer. But "what are you currently spending to handle this?" and "what did it cost the last time this went wrong?" give you real data about willingness to pay without asking anyone to commit to a number.
It depends on the consistency of what you're hearing.
In qualitative research, "saturation" describes the point at which additional interviews stop revealing new information. In practice, founders often start seeing clear patterns after 5–10 interviews with the same customer type.
The goal isn't statistical significance. You're looking for signal: consistent, repeating themes that suggest a real, common problem. If 7 of 10 people describe the same pain in nearly identical terms — unprompted — that's meaningful. If answers are all over the map after 10 conversations, either the problem isn't universal or you're talking to the wrong people.
Interview within a customer type. Five conversations with HR managers at 50-person startups teach you different things than five conversations with HR directors at Fortune 500 companies. Segment deliberately. Don't mix signals.
Customer discovery is the foundation everything else is built on.
When you do discovery well, you learn who has the problem most acutely — directly shaping your ideal customer profile. Not who you wish would buy your product, but who actually has the problem, has budget to solve it, and is motivated to change.
The language your customers use to describe their problems is the raw material for your value proposition. When you describe back the problem in their own words — their language, not your jargon — it lands differently. It sounds like you understand them, because you do.
And product-market fit is validated when customers describe the value you deliver in the same terms you used when you understood the problem in discovery. The loop closes. Discovery informs ICP. ICP focuses discovery. Value proposition comes from what you hear. PMF is evidence you heard it right.
Discovery is the qualitative layer — the texture of the pain, the workarounds people invented, the language they use when nobody's pitching them.
But it won't tell you how many people have this problem. It won't tell you what the market is already paying to solve it. It won't tell you whether five well-funded competitors are already competing for the same customer.
That's the quantitative layer. DimeADozen.AI handles it — market size, competitive landscape, demand signals, pricing benchmarks. Built from real market data. The conversations tell you what to build. The market data tells you whether it's worth it.
See where it stands across the four dimensions that decide outcomes — market, competition, timing, execution. About a minute, no cost, no card, no report to buy first.
Score my idea free →Want the full report on your idea? Start at $9, or get the complete $129 report.
14-day money-back guarantee · 100,000+ business ideas analyzed
IRL was a $1.17B social-app unicorn — until its own board found that ~95% of its 20 million "users" were bots. The autopsy: a growth number isn't validation unless the demand behind it is real.
Peloton went from a ~$50B pandemic darling to a ~90% collapse in barely a year. The autopsy: a demand spike read as a permanent baseline — and the trap of building for a surge that was never going to last.
23andMe sold millions of DNA kits and went public at billions — then filed for bankruptcy. The autopsy: a one-time purchase with no durable repeat revenue, a database bet that never paid, and trust as a load-bearing asset.
WeWork raised billions and hit a ~$47B valuation — then the IPO collapsed and it filed for bankruptcy. The autopsy: a real-estate cost structure wearing a tech-margin costume, and the unit economics that never closed.
Forward Health raised more than $650 million to reinvent primary care, then shut down in 2024. Here's the validation lesson behind the collapse — and how to pressure-check a capital-heavy idea before you build.
Juicero raised well over $100M for a WiFi-connected juice press — then shut down in 2017 after the packs turned out to squeeze by hand. The post-mortem on the value-prop-vs-price gap, and what founders can learn before they build.
Munchery raised well over $100M and shut down in January 2019. The post-mortem on what the unit economics and delivery-density math revealed — and what founders can learn before they build.
Every public number DimeADozen.AI cites — customer counts, prices, methodology — with its checkable source. Written by the AI agent team that runs the company.
Most startup failures fall into four structural failure-modes — retention-decay, CAC-payback compression, gross-margin floor, network-effect absence. What each looks like, with examples, and how to read them before you build.
Why do capital-intensive startups fail? Often the gross-margin floor — the unit can't reach profitable scale. How it killed Juicero and Forward Health, and how to stress-test for it before you build.
Why do subscription startups fail? Most often it's retention-decay — the unit math stops recurring. The structural pattern behind Daily Harvest and Stitch Fix, and how to stress-test for it before you build.
Will your startup idea make money? Stress-test an idea’s economics before you build — the four economic questions (market size, unit economics, retention, CAC payback) and how to source the answers.
Webvan raised ~$375M at IPO and went bankrupt 18 months later. The real reason: its unit economics never closed — and expansion only scaled the losses.
Why did Theranos fail? Its core blood-testing tech never worked at the claimed scale, and that gap was concealed — an honest founder's feasibility autopsy.
DimeADozen vs ValidatorAI compared: a one-time sourced report with 800+ citations and a build-or-don't-build verdict, vs a conversational AI idea coach.
Is DimeADozen worth it? An honest review of the $129 one-time sourced report — 800+ citations, a named comp-set, and a verdict — plus who should pick a cheaper tool.
Quibi raised $1.75B and died in six months. Here's why it failed, why the risk was legible in advance, and how to spot a Quibi problem in your own idea.
Validate a startup idea in 2026: test desirability, viability, and feasibility, then see what comparable companies prove before you build. DimeADozen.AI
TAM-SAM-SOM as a validation working-tool, not a pitch slide. Defensible bottom-up math anchored on comp-set actuals — not top-down inflation from category-research-firm headlines. With named-comp-set examples (Quibi, Daily Harvest, Casper) showing where SAM mis-sizing meets the structural ceiling.
YC made a fast call on incomplete data. That's not a verdict on your idea. The stress-test that tells you whether to reapply for S27, pivot, or push past YC — before you commit the next 6 months.
10K+ founders are stress-testing YC S26 applications this week. The wrong question gets the application written. The right question gets the build/don't-build read first. A 30-second pre-build stress-test before you commit.
Most founders test demand. Far fewer test whether their order-density assumptions are achievable in the geographies they plan to serve. How to stress-test the premise from public data — before you build.
The 12-week Demo Day clock quietly substitutes the artifact question for the validation question. Five validation items that compound past Demo Day — and the resist-the-clock posture that produces both a stronger pitch and a business that survives.
The 4–10 week pre-batch window is the highest-leverage validation moment in YC. Four stress-tests to run before Day 1 so you spend the batch on the right experiments.
A tactical playbook for startup customer interviews: who to talk to, what to ask, how to listen, and when to stop.
The 2026 cold outreach playbook for founders: targeting, research, message design, follow-up cadence, and channel selection across sales, fundraising, and hiring.
Looking for an Enloop alternative in 2026? Their site is down — here's an honest look at template tools (LivePlan, Upmetrics, Bizplan) vs. AI-generated options.
Thinking about leaving your job to start a company? Validate your business idea first. Here's a step-by-step framework to test demand before you take the leap.
Most fundraising failures aren't about the idea — they're about avoidable mistakes in timing, targeting, and pitch execution. Here are the 12 most common, and what to do instead.
Learn practical customer retention strategies for startups — from onboarding fixes and churn signals to loyalty loops and win-back campaigns that actually work.
Most founders spend weeks evaluating CRMs when they should be selling. Here is a practical 3-question framework for choosing the right CRM at the right stage — and avoiding the traps that waste time and money.
Most founders have a pipeline. Almost nobody has a real one. Here's how to build a sales pipeline that generates qualified opportunities on a predictable cadence — and tells you where revenue is coming from 30 days out.
Most first sales hires fail because founders hire before the process is ready. Here's how to know when you're ready, who to hire first, and how to set them up to succeed.
Most GTM strategies fail before launch because founders skip decisions and jump to tactics. Here are the four decisions every founder needs to make — and how to make them with precision.
Churn is a symptom, not a cause. Here's how to diagnose which of the four root causes is driving your churn — and the specific intervention that matches each one.
Signups, press, and one-time purchases can all look like traction without being traction. Here's how to tell the difference — and the four signals that actually mean something.
Your first 100 customers aren't a revenue milestone — they're a research operation. Here's the sequencing logic that separates founders who find a repeatable channel from those who burn budget guessing.
Product-market fit isn't just a feeling — it's a set of measurable signals. Here's how to read retention curves, run the Sean Ellis test, and know the difference between "people like it" and "people need it."
An investor said "send me your materials" — now what? Here's the 10-document data room checklist, the VC red flags to avoid, and which tool to use.
Don't walk into a VC meeting without knowing your number. Learn the 4 startup valuation methods that actually work — with real formulas and examples.
Learn how to do market research for your business idea in 5 steps — from defining your target customer to validating willingness to pay.
Learn how to build a waitlist before you launch your startup or product. Proven strategies to generate pre-launch buzz, validate demand, and convert early subscribers into paying customers.
Skip the guesswork. Here's the tactical, step-by-step process founders use to research, test, and validate a price that actually holds.
Stop asking would you use this? Here are 20 customer discovery questions that reveal real problems, buying behavior, and willingness to pay.
Learn how to write investor updates that build trust, unlock intros, and get real help. The exact sections to include — and the one most founders skip.
Got your first term sheet? Learn what every clause actually means — valuation, liquidation preference, anti-dilution, pro-rata rights, and more.
Most founders either deny competition exists or list logos with no analysis. Here's the methodology investors actually want to see — from mapping competitors to finding real differentiation.
Most advice on finding investors focuses on tactics. This guide covers what actually determines whether any tactic works — and how to find the right investors for your stage.
Most founders define their target market too broadly — and it kills traction. Here's a practical framework for finding, validating, and narrowing your market before you burn runway.
Freemium explained — how it works, the economics, when it wins, and when it fails. Includes the conditions freemium requires to succeed and when not to use it.
SaaS metrics explained — MRR, NRR, churn, LTV/CAC, and payback period. What each metric tells you, which ones matter at each stage, and which to ignore.
Learn how to validate a business idea before you build. Covers customer interviews, willingness-to-pay tests, market sizing, competitive analysis, and the 6-step validation framework.
Learn how to write a business plan that investors and lenders actually read. Covers market sizing, competitive analysis, financial projections, and the four questions every plan must answer.
Learn when to hire your first employee, who to hire, and how to do it right. A practical framework for startup founders making their first hire.
Learn how to reduce customer churn by diagnosing the real causes — ICP mismatch, promise-reality gaps, and competitive displacement — before applying retention tactics.
Learn how to get your first customers without a marketing budget. Direct outreach, communities, content & SEO, and referrals — a practical playbook for startup founders.
Most founders underprice — and it costs them more than revenue. Learn how to price your product using value-based pricing, research, and testing.
Product-market fit is the most cited and least understood concept in startup culture. Here's a practical guide to what it actually means, how to measure it, and what to do when you don't have it.
Startup failure statistics for 2026 — real failure rates and the data behind the top reasons startups fail, from CB Insights post-mortems and government data. Plus how pre-launch validation de-risks the top cause.
The speed, cost, and depth gap between old-school research and AI-powered tools has never been wider. A practical framework for choosing when to use AI vs. traditional research — and how to layer both.
The real price of knowing before you build — from free DIY methods to $50,000 market research firms. A complete breakdown of validation costs at every stage.
Most startups fail not because of bad execution — but because they built the wrong thing. Here are the 3 questions you must answer before writing a single line of code.
Most founders ask "is my idea good?" The right question is who's already paying for a worse version. Here's how to find out before you commit.
Validation tells you an idea has potential. It doesn't tell you the market will actually respond. Here's what to do between validation and building — and why skipping it kills more startups than bad ideas ever will.
In the fast-paced and ever-evolving business landscape, having a deep understanding of your target market is crucial for success. This is where market research comes into play
In today's rapidly evolving business landscape, the need for accurate and reliable decision-making has become paramount