User research is 5 conversations with the right people.
That's it. Not a focus group. Not a $50K market research study. Not a 40-question survey sent to your mailing list. Five conversations with people who actually have the problem you're trying to solve — conducted with genuine curiosity, structured to surface real behavior, and synthesized into decisions you can act on.
One of the most commonly cited findings in CB Insights' analysis of startup failures is that founders build products without sufficient understanding of whether customers actually need them. The antidote isn't more market data — it's talking to the people whose problem you're trying to solve before you build the solution.
Market research is secondary data — industry reports, TAM/SAM calculations, competitor analysis, search volume. Useful for understanding the landscape. See our TAM/SAM/SOM guide and competitor analysis guide.
User research is talking to actual people who have the problem. It tells you things market research can't: how they currently solve it, what language they use to describe it, what they've tried and abandoned, how much it costs them in time and money, and what "good enough" would look like.
Most founders skip user research because they confuse the two. They read industry reports, look at search volume, and conclude there's a market. That's not the same as understanding the customer well enough to build something they'll actually use.
The most common user research mistake isn't methodology — it's who you talk to.
Not your friends and family. They'll be supportive, not honest. Their feedback is shaped by their relationship with you, not their experience of the problem. It produces false confidence, which is worse than no data.
Not people who "might" have the problem. You need people who currently have it and are actively dealing with it. "I sometimes think about this" is different from "I spent three hours on this last week."
Your exact ICP — not a loose approximation. If you're building for e-commerce operators between $1M–$10M in revenue, interview that exact profile. Not solo Etsy sellers. Not enterprise retail. The specificity is the point. See our ideal customer profile guide.
Where to find them: LinkedIn (search by title and industry), communities where your ICP hangs out, your existing network, subreddits, Slack communities, cold outreach. Offer 20–30 minutes of their time and genuine value — you're asking for something real. Be direct about what you're doing and why.
How many: 5 to start. After 5 well-conducted interviews with the right people, patterns emerge. The 5-conversation threshold is grounded in Nielsen Norman Group's foundational research on usability testing — 5 users surface the vast majority of usability problems. Applied to customer discovery, it's an orientation, not a hard rule. The point is you don't need 50 interviews. You need to start.
User research fails in one specific way: the founder turns it into a sales conversation. The moment you start explaining your product, you've broken the research. Everything they say after is shaped by what you've told them, not their actual experience.
The four-part structure:
1. Open with the past "Tell me about the last time you dealt with [problem]. What happened?"
Specific past events ground the conversation in real behavior. "Last Tuesday I spent four hours manually cross-referencing spreadsheets" is data. "I'd probably want something automated" is speculation. You want the former.
2. Go deep on the current solution "What do you do right now to handle this? How did you find that approach? What do you like about it? What frustrates you about it?"
The current solution reveals everything: switching costs, what's already solved (don't rebuild it), what's genuinely broken. "I do it in a spreadsheet" and "I pay $50K/year for an enterprise tool that only half-solves it" are both valuable — but they lead to completely different product decisions.
3. Understand the stakes "How often does this come up? What happens when it goes wrong? Who else in your organization is affected?"
Stakes determine urgency. Urgency determines willingness to pay and switch. A problem that costs two hours every week with real downstream consequences is a different opportunity than one that's mildly annoying once a month.
4. Close with the magic wand question "If you could wave a magic wand and have this problem completely solved tomorrow, what would that look like?"
Reveals the desired outcome without anchoring on any specific solution — including yours. The gap between their current reality and their magic-wand answer is your product opportunity.
Leading questions produce data that confirms what you already believed rather than revealing what's actually true.
❌ "Would you use a product that solved this by doing X?" (You just described your solution) ✅ "How would you ideally want to handle this?"
❌ "How frustrated are you with the current options?" (Primes them to say frustrated) ✅ "Tell me about your experience with how you handle this today."
❌ "Would you pay $X/month for a product that solved this?" (Hypothetical willingness-to-pay is unreliable) ✅ "What have you paid for solutions to this kind of problem in the past?"
Past behavior predicts future behavior. Hypotheticals don't. If they've never paid for anything related to this problem, that's important data. If they're currently paying for a half-solution, that tells you something real about price tolerance.
Write up each interview immediately — within an hour while memory is fresh. Capture: what problem they described, current solution, main frustrations, ideal outcome.
Look for themes, not outliers. After all interviews, organize notes by theme — not by interview. What came up in 4 out of 5 conversations? That's signal. What came up once? Build for the patterns.
Use the jobs-to-be-done frame. User research is the input; JTBD is how you structure what you learned. See our jobs-to-be-done guide.
Write a one-paragraph synthesis:
"Our target user is [specific person] who currently [does X] to solve [problem Y]. They're frustrated by [specific friction]. Their desired outcome is [Z]. The current best alternative is [A], which they use because [B], but it falls short because [C]."
One paragraph. If you can't write it after 5–8 interviews, your target profile is still too broad or your interviews didn't go deep enough. This paragraph is worth more than 50 pages of market research.
Feature prioritization: Pain points that came up in most interviews = first features. Single-mention pain points = hypotheses to test later. See our product roadmap guide.
Messaging: The language your users used to describe the problem is your marketing copy. Literally. If three different people said "I'm constantly putting out fires because I can't see what's coming," your headline should use that language. Real user words beat clever copy every time. See our content marketing guide.
Pricing: What are they currently paying for adjacent solutions? How severe is the pain? This tells you more about price tolerance than any survey. Know which situation you're in before setting a price.
Retention: Understanding what "success" looks like for users shapes onboarding and retention strategy directly. See our customer retention guide.
What not to build: If a feature you were excited about never came up across five interviews, it's not a priority. Build for the problems people actually have.
After you've already decided. Research conducted to validate a decision you've already made is confirmation bias with steps. You'll ask leading questions, ignore contradicting signals, and build false confidence. Do user research before you decide, or don't do it.
Using surveys as a substitute for interviews. Surveys validate patterns at scale after you understand the problem. They're poor for discovering it. Surveys tell you what people say. Conversations tell you why they say it and what they actually mean. Don't substitute; sequence.
Recruiting too broadly. "Anyone who has ever had a problem like mine" produces interesting but unactionable data. If your product is for e-commerce operators between $1M–$10M in revenue, interview that exact profile. Specificity is the point.
When speed matters more than depth. Sometimes a competitor is moving or a window is closing and you need to ship fast. Do it — ship, observe real usage, research the next iteration. A legitimate strategic choice; just make it consciously.
For how user research fits into the broader validation process, see our idea validation guide.
No lab. No recruiting firm. No 40-question moderator guide. Five conversations with the right people, structured around past behavior, conducted with genuine curiosity.
The mistake isn't doing user research wrong. The mistake is not doing it at all.
Five conversations before you build will save you months of building the wrong thing. Talk to people.
User research tells you whether you're solving the right problem. DimeADozen.AI tells you whether you're building in the right market — competitive landscape, market sizing, and growth opportunities in minutes. Get yours →
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