Indie hackers sit in an awkward research gap. The lean startup canon told everyone to talk to customers. The agency world made research sound like a $40,000, 12-week exercise. Neither description fits a solo builder trying to ship a $19/month SaaS product on nights and weekends. The result: most indie hackers either skip customer discovery entirely and hope the product works, or overspend months recruiting and interviewing in a way that burns their launch window.
This guide defines what lean customer discovery looks like for the indie hacker reality — solo builders, lifestyle businesses, projects under $10K MRR, and the broader Indie Hackers and Hacker News audience that reads this kind of playbook. For context on the broader solo founder research strategy, and the specific idea validation workflow that anchors pre-build discovery, this guide connects to the same canon.
What Does Lean Discovery Mean for an Indie Hacker (vs a VC-Backed Startup)?
Lean discovery for an indie hacker is not a smaller version of the enterprise research playbook. It is a different target function. The VC-backed startup runs customer discovery to reduce investor risk, hit board milestones, and justify a Series A narrative. The indie hacker runs customer discovery to avoid building the wrong thing and to compress the time between idea and paying users.
Those two target functions produce very different research designs. The VC-backed startup can justify a 12-week study with a 200-person sample because the downstream decisions involve millions in burn and multi-year roadmaps. The indie hacker cannot. A solo founder with a six-month runway and no outside capital is solving a different problem: how do I validate enough to justify shipping, without spending so long validating that I never ship?
The honest answer is that indie hacker discovery does not need statistical confidence. It needs signal confidence. Ten interviews where seven participants independently describe the same pain in the same vocabulary is enough to justify building. A hundred interviews refining the segmentation model is not a useful exercise for a founder who has not yet written the first line of code. Velocity matters more than completeness at this stage because the real competition for indie hacker attention is not the market — it is the founder’s own runway.
This is where AI-moderated interviews change the math. Traditional qualitative research requires the founder to run every conversation, which caps the throughput at 2-3 interviews per day and taxes the founder’s most valuable hours. AI-moderated interviews run in parallel on a panel without founder time per conversation, which is what makes 30-interview launch cycles fit inside a 6-8 week build sprint instead of consuming the whole sprint.
The 3-Stage Indie Hacker Discovery Rhythm (Pre-Build / Pre-Launch / Post-Launch)
The lean playbook splits discovery into three stages that map to the indie hacker build cycle. Each stage has one question, 10 interviews, and a binary output that lets the founder make a decision and move on.
Stage one is problem validation, which runs before any code is written. The question: does this problem exist, and is it painful enough that a stranger will describe it unprompted? Ten interviews with people who fit the target user profile are enough to answer this. The output is either a confident yes with specific language about how the problem manifests, or a no with clear reasons to abandon the idea or reshape it. Founders who skip this stage end up building solutions to problems nobody has, which is the most expensive indie hacker failure mode because it burns months of build time with zero revenue signal.
Stage two is solution direction, which runs during the build but before the public launch. The question: which of the possible solution shapes matches how target users actually think about the problem? Ten interviews, this time with people walking through a concept mock or early prototype, surface which features matter and which are founder-brain overbuilding. The output is a prioritized feature list for the MVP and a list of things to cut. Most indie hackers who do stage one but skip stage two end up shipping the wrong version of the right idea, which produces weak early conversion and sends the founder back to rebuild.
Stage three is post-launch activation research, which runs after the product has 50-100 signups. The question: where are new users getting stuck between signup and first value? Ten interviews with recent signups, mixed between users who activated and users who churned, surface the specific friction points in onboarding. The output is a ranked list of onboarding fixes that usually unlock 20-40% activation improvement. This stage is where lean discovery stops being validation and becomes continuous product research.
Thirty interviews across a 6-8 week launch cycle, three decisions made, no analysis paralysis.
Why 10-Interview Sample Sizes Work for Indie Hackers
The traditional objection to small samples is statistical. Ten interviews cannot produce 95% confidence intervals on anything, and they cannot reliably segment a population by behavior or demographics. Both objections are correct and both are irrelevant to the indie hacker decision framework.
Indie hacker discovery is not trying to produce a defensible market size estimate. It is trying to answer build-or-not, ship-or-keep-building, and fix-this-first. Those decisions do not require statistical confidence. They require signal consistency — the same theme emerging from multiple independent conversations with people who did not know each other and were not primed by the same questions.
The qualitative research canon puts saturation — the point at which new interviews stop producing new themes — at roughly 12 interviews for a tightly defined target user segment. Above that threshold, marginal insight per interview drops fast. Below it, the founder is at risk of building a product around idiosyncratic pain from one or two vocal participants. Ten is close enough to saturation for most indie hacker decisions, and the final two interviews can happen as part of the next stage if the signal feels weak at ten.
The second reason 10 works is that indie hackers are not optimizing for the tail cases. A founder launching a niche B2B SaaS for Shopify store owners between $500K and $5M GMV does not need a representative sample of every Shopify store type. They need 10 interviews with people who fit the exact ICP. A well-recruited sample of 10 will outperform a loosely recruited sample of 100 on every decision that matters for the launch.
The third reason is the economic argument. At User Intuition’s $20/interview Pro plan rate, 10 interviews cost $200 per stage and $600 across the full launch cycle. That is a rounding error against a 6-month runway. A founder who runs 30 lean interviews and avoids building one wrong feature has already earned a 10x return on the research spend. Attempting to run 100 interviews per stage turns the math on its head — the research starts costing more than the downside of being wrong.
How to Run Indie Hacker Discovery Without Your Twitter Network
The unspoken advantage most indie hacker research advice assumes is a Twitter audience or a Hacker News front-page post. Founders without those distribution channels face a recruiting problem that is harder than the interview itself. Cold outreach on LinkedIn, Reddit, Slack communities, and niche forums works but burns 10-20 hours per stage just to recruit 10 participants, which destroys the velocity advantage of running lean interviews.
Two paths solve the recruiting problem for indie hackers without distribution.
The first is panel-based AI-moderated research. User Intuition’s 4M+ panel covers most B2C ICPs and many B2B professional segments. The founder specifies the target user profile — demographics, role, behavior, platform usage, problem experience — and the platform recruits matching participants. Interviews return in 48-72 hours without the founder spending time on DM threads, scheduling links, or no-shows. For most indie hacker ICPs, this compresses the recruiting step from 2 weeks to 2 days.
The second is community-based recruiting in places where the target users already post. For developer tools, that is Reddit’s r/programming and r/webdev, Hacker News, and specific Discord servers. For creators, that is Twitter, YouTube comments, and creator-specific newsletters. For small business owners, that is industry subreddits and local business Facebook groups. Community recruiting works when the founder already has weak-tie presence in the community. It fails when the founder is starting cold, because most moderators reasonably ban research recruiting from strangers.
The practical lean answer is usually a mix. Stage one problem validation can often run through community recruiting because the interview is about the problem, not the product, and participants engage with the topic. Stage two solution direction benefits from the panel path because it needs a specific ICP match and cannot wait on community goodwill. Stage three activation research uses the founder’s own signup list, which is the cleanest recruiting pool because participants already care about the product.
The cost split for a typical indie hacker launch cycle: $200 for stage one panel interviews (or $0 with the Starter plan’s 3 free interviews covering the opening conversations and a community supplement for the rest), $200 for stage two panel interviews, and $200 for stage three post-launch research. Total research spend: $600, against a typical indie hacker launch cost structure of $2,000-$5,000 in hosting, tooling, and paid distribution. Research is 10-20% of the launch budget, in line with where the lean playbook says it should sit.
See the bootstrapped startup research tool comparison for the adjacent question of which tools fit best at different MRR stages.
When to Graduate From Lean to Rigorous (and How to Know)
Lean discovery is the right tool for the zero-to-launch and zero-to-first-traction phase. It is the wrong tool for an indie business that has crossed $10K MRR and is making five-figure decisions on pricing, positioning, or major feature direction. The graduation signal is not a revenue number — it is the structure of the decision in front of the founder.
Three signals indicate lean discovery is no longer enough.
The first is when the next decision has multi-segment implications. A pricing change that affects free-tier users differently from paid-tier users cannot be validated with 10 interviews because the sample cannot cover both segments with enough depth. A 50-interview study split across segments becomes the right tool. At $20/interview, that is $1,000 — still reasonable, but an order of magnitude above lean spend.
The second is when the founder is making a decision they cannot reverse cheaply. A major platform pivot, a repositioning that rewrites the homepage and marketing materials, or a pricing overhaul that affects existing customer contracts all fall into this category. Irreversible decisions deserve more rigorous discovery because the cost of getting it wrong is no longer a feature rebuild — it is customer churn, distribution cost re-acquisition, or contractual disputes.
The third is when signal from lean interviews is consistently split. If stage-one problem validation returned a clean yes and stage-two solution direction shows 5-5 splits on every feature question, the issue is probably segmentation the founder has not yet articulated. Running a 30-50 interview study to find the segment boundaries is the right next step, and that is no longer a lean exercise.
Indie hackers who try to run rigorous research too early waste money and lose velocity. Indie hackers who stay lean after crossing $10K MRR start making bigger mistakes because the lean signal threshold is too low for the decisions they are making. The transition is usually around $10K-$25K MRR, though founders with lower-priced subscriptions and higher user counts may cross it earlier because their decisions affect more users even at lower revenue.
User Intuition handles both ends of this spectrum on the same platform. The $0/month Starter plan with 3 free interviews fits the pre-launch indie hacker who wants to validate the problem before committing any spend. The Pro plan at $20/interview supports the 30-interview launch cycle. The same platform scales to 50-200 interview enterprise studies when the indie business graduates to rigorous research, with the 4M+ panel, 48-72 hour fieldwork, and G2 5.0 rating carrying across all tiers. The research tool does not have to change when the business does. The rhythm and sample size do.
The lean answer for most indie hackers reading this: start tonight with 10 problem validation interviews. Ship the MVP in six weeks. Run 10 more interviews on early signups. Do not overthink the research budget. $600 across a launch cycle is a rounding error against the opportunity cost of building the wrong thing — and it is the cheapest insurance an indie hacker can buy.