Indie hacker research: validation under $100

You can validate a product idea before writing any code for under $100. The core approach is five problem-discovery interviews plus a smoke test, using free tools for moderation and a small incentive budget for participants. This article covers the exact methods, tools, and a dollar-by-dollar spending breakdown.

Most indie hackers skip research because they assume it is expensive or slow. It is neither. The expensive part of product development is building the wrong thing. Spending $80 to confirm the problem is real costs far less than two months of wasted engineering.

Why indie validation research is different from enterprise research

Enterprise research teams run multi-week studies with dozens of participants, moderated protocols, and analysis tools that cost thousands per seat. That is not what you need.

Indie hacker validation research has a single job: answer the question “is this problem real and worth solving for people who match my target profile?” Every method and budget choice should be evaluated against that goal alone.

Two constraints define the indie context:

• No audience yet. You cannot recruit from your own users because there are none.
• Time cost is real money. Every hour spent on process overhead is an hour not spent building.

Given those constraints, the best indie research stack is simple tools, small participant counts, and a tight question scope.

The $100 validation stack

Here is a working budget allocation for a full problem-validation cycle:

Item	Tool	Cost
Survey / screener	Tally (free tier)	$0
Interview scheduling	Cal.com (free)	$0
Interview recording	Loom or Zoom (free tier)	$0
Note-taking and synthesis	Notion (free)	$0
Landing page (smoke test)	Carrd ($9/year) or Framer (free)	$0 to $9
Participant incentives (5-8 people at $10-$15 each)	Gift card or PayPal	$50 to $80
Optional: small traffic boost for smoke test	Reddit promoted post or Google Ads	$10 to $20
Total		$60 to $109

You can stay comfortably under $100 if you skip the paid traffic and rely on community sourcing instead.

Step 1: Write one crisp research question

Before recruiting a single person, define the one question this round of research needs to answer. Examples:

• “Do independent consultants have a real problem tracking client deliverables, or is this problem already solved by tools they already use?”
• “Are developers frustrated enough with current API documentation tools to pay for a better one?”
• “Do solopreneurs track their recurring revenue manually because existing tools are too complex or too expensive?”

One question per round. Everything else is noise.

Step 2: Recruit five to eight people

This is where most indie hackers get stuck. Without an existing audience, cold recruitment feels awkward. It does not have to be.

Community sourcing (free):

• Post in relevant subreddits. r/SaaS, r/entrepreneur, r/freelance, r/webdev, and niche product communities are high-signal sources. Be transparent: “I am building something to solve X and want to talk to five people who face this problem. 20 minutes, $15 Amazon gift card.”
• Niche Discord servers. Find communities where your target users congregate and follow the same approach.
• LinkedIn outreach. Search by job title, send ten to twenty short personal notes. A 10 to 20 percent response rate is normal.

For harder-to-reach B2B profiles:

If your target persona is a CFO, a compliance officer, or a specific job title in a regulated industry, community sourcing will be slow. A panel like CleverX lets you filter by exact job title, industry, and company size, and book verified participants in days. Even at this stage, five interviews with the right people is worth more than twenty interviews with adjacent profiles.

The customer discovery interview guide covers sourcing scripts and outreach templates you can adapt.

Step 3: Run problem-discovery interviews

Each interview should run 20 to 25 minutes. You do not need a formal discussion guide. You need four questions:

1. Walk me through the last time you dealt with [problem area].
2. What did you try to solve it? What happened?
3. How often does this come up?
4. What would make this problem disappear for you?

Record every session with Loom or Zoom. Do not rely on notes taken during the call.

What to avoid:

Do not ask “would you use this?” or “would you pay for this?” These questions produce false positives. People say yes because they want to be helpful, not because they would actually buy. Stick to past behavior and current workarounds.

For a deeper primer on the method, the jobs-to-be-done research guide explains how to uncover the real job users are hiring a solution to do.

Step 4: Synthesize in a day, not a week

After five sessions, open a Notion page and list every friction point, workaround, and frustration mentioned across all interviews. Group them by theme. Any theme that appeared in three or more interviews is worth treating as a real pattern.

You are looking for three signals:

• Frequency: How often does the problem occur?
• Severity: How much does it cost (time, money, stress) when it happens?
• Workaround quality: Is the current solution terrible, or just slightly inconvenient?

High frequency, high severity, and poor workarounds = a problem worth solving. Low frequency or a decent existing solution = a signal to reconsider the concept.

Step 5: Run a smoke test to check willingness to pay

Interviews tell you the problem is real. A smoke test tells you whether people care enough to act.

Build a one-page landing page on Carrd or Framer in two to three hours. Include:

• One headline describing the outcome you deliver
• Three bullet points covering how you solve the problem
• A clear call to action: “Join the waitlist” or “Get early access for $X”
• An email capture form

Drive 50 to 100 visitors to the page. Use organic community posts first (free). If you want a faster signal, a $15 to $20 Reddit promoted post or Google Ads spend targeting a narrow keyword gets you there in 48 hours.

A conversion rate above 5 to 10 percent on an email capture is a strong demand signal. Above 2 to 3 percent on a paid waitlist (with a real dollar amount attached) is exceptional for a pre-launch indie product.

The best landing page testing tools for 2026 covers the full toolkit if you want to A/B test messaging variants.

Step 6: Know when to spend more

The $100 budget covers problem discovery. If your smoke test converts and your interviews confirm a real problem, the next questions cost more to answer. Concept testing, prototype validation, and pricing research require participants who match your exact target profile and a more structured protocol.

At that point, investing $200 to $500 in a proper participant panel is rational, not extravagant. The product validation guide for startups covers what comes next after problem discovery.

Common mistakes that waste the budget

Recruiting the wrong people. Five interviews with people who sort of match your target profile costs the same as five interviews with exact matches. The difference is one produces actionable insight and the other produces noise. Spend the extra time on sourcing.

Building a survey instead of doing interviews. Surveys are faster but produce shallow data. At the discovery stage, you need to understand why people feel the way they do, not just what they report. Save surveys for later-stage validation when your hypotheses are more defined.

Optimizing for confirmation. Recruiting from your Twitter followers or personal network introduces selection bias. These people already like you. You need skeptical strangers who have no reason to tell you what you want to hear.

Skipping the smoke test. Interviews confirm a problem exists. They do not confirm people will pay to solve it. Always pair qualitative interviews with a demand test before committing to build.

Frequently asked questions

Can you really validate a product idea for under $100?

Yes. A combination of free tools (Tally, Google Sheets, Loom, Notion) plus a small paid participant incentive of $10 to $15 per person covers the full discovery-to-validation cycle for most early-stage indie products. The key is running five to eight focused interviews, not a broad survey with hundreds of responses.

How many participants do I need for meaningful indie validation research?

Five to eight interviews are enough to identify the patterns that drive a build or no-build decision. For a smoke test or landing page test, 50 to 100 page visitors give you a reliable conversion signal. You do not need statistical significance at the discovery stage.

What is the best free method for indie hackers to test demand?

A smoke test landing page built with Carrd or Framer and a small Google Ads or Reddit spend is the most direct demand signal available for under $50. Pair it with five problem-discovery interviews to understand why people do or do not convert.

How do I find target users without an existing audience?

Reddit communities, niche Discord servers, and LinkedIn are the most reliable channels for cold outreach to target users. For B2B personas like developers, PMs, or operations professionals, a panel like CleverX lets you filter by job title and industry without building your own audience first.

What questions should I ask in a $100 validation interview?

Focus on the problem, not the solution. Ask how respondents currently handle the problem, how often it comes up, what they have tried before, and what they would pay to make it go away. Avoid asking whether they would buy your product. That question produces false positives.

When should an indie hacker stop free research and pay for participants?

Switch to paid recruitment when your target user is hard to reach via communities (B2B decision-makers, regulated industries, senior job titles), when you have already exhausted your network, or when you need participants who match a very specific profile. At that point, the cost of bad data outweighs a $50 to $100 recruitment spend.

Summary

The $100 validation playbook for indie hackers:

1. Write one research question before doing anything else
2. Recruit five to eight people from communities or LinkedIn ($0 to $15 incentive each)
3. Run 20-minute problem-discovery interviews with four core questions
4. Synthesize themes in one afternoon using Notion or a spreadsheet
5. Build a landing page and run a smoke test with 50 to 100 visitors
6. Decide: problem confirmed, demand signal positive, build. Or pivot the concept before spending a week on code.

The tools are free. The incentives are cheap. The only thing this research costs that cannot be recovered is about eight to ten hours of your time, which is still far less than the cost of shipping a product nobody wants.