
How to Do User Research for Free as a Solo Founder — 6 Proven Methods for Indie Developers
No budget for deep user research? These 6 zero-cost methods help indie developers gain the most valuable user insights with minimal investment.
Many solo founders and indie developers share a common misconception: that user research is something only big companies need to do. They think if they just build the product, users will naturally come. The result? Months of development on features that no one uses after launch.
User research isn't a nice-to-have — it's the most critical survival skill for a solo company. Building a product without research is like driving with your eyes closed — you might be moving fast, but you're probably going in the wrong direction. For someone bootstrapping on zero budget, every ounce of dev effort is precious. Research ensures your hard work isn't wasted.
The good news? User research doesn't have to cost money. Solo companies with no budget can still gather high-quality user insights using clever, free methods. This article shares 6 proven, zero-cost research approaches, each grounded in real solo founder practices.
Method 1: Social Media Lurking and Conversation Analysis
Social media is a goldmine for zero-cost research. Indie developers can tap into communities where their target users hang out and gather first-hand demand signals.
Find Where Your Target Users Gather
Different industries have different platforms. B2B users might discuss pain points on Zhihu, Xiaohongshu, or industry forums; B2C users might chat in Douban groups, Weibo threads, or niche communities. The key is finding channels where users spontaneously discuss their problems — the pain points and needs paid users frequently mention.
A practical approach: search in WeChat Search or Baidu for queries like "[your product type] recommendation," "[your product type] pitfalls," "why [your product type] sucks," etc. This reveals users' questions and frustrations.
Analyze Negative Reviews
User dissatisfaction is the best product direction. In competitors' comment sections, App Store ratings, and Zhihu Q&As, users openly share what they dislike and what they wish was better. These negative reviews directly point to market gaps.
Case study: A solo founder building a project management tool noticed countless Asana commenters complaining "it's way too complex, I just want a simple kanban board." He built a minimalist project management SaaS tool and saw rapid growth after launch.
Track Keywords and Frequency
Don't just browse — jot down keywords users repeat. Use Excel or Feishu Bitable to record: user identity, the problem they face, desired solution, and mentioned price range. When the same pain point is raised by 50 different users, you've got data to back your decisions.
Method 2: Competitor Comment Sections as Free Focus Groups
Competitors' comment sections are a natural, free research panel. Users tell you in detail what's working and what's broken in similar products.
Collect Comments Systematically
- Product Hunt: Read what users say about competing products, especially "what feature do you wish existed" comments
- Zhihu / Xiaohongshu: Search "[competitor name] experience" for in-depth reviews and comparisons
- App Store: Read ratings — especially 1-star and 4-star reviews (5-star reviews are low-signal; 1-star complaints are gold; 4-star often contain improvement suggestions)
- Social Media Comments: Follow startup and SaaS-related accounts for user discussions
Build a Comment Analysis Framework
Once you've collected comments, don't just read and forget. Analyze using a simple framework:
Demand Type — Is the mentioned feature a must-have or a nice-to-have? Must-haves are features users "can't live without"; nice-to-haves are "good to have" but not critical.
Emotional Intensity — How strongly do users complain? There's a big difference between "this sucks" and "could be better." The stronger the emotion, the more worth your investment.
User Persona — Are the commenters your target users? A finance tool's target user saying "the reports are too complex" and a general user saying "it's too professional" represent different needs.
Validate Product Ideas with Comments
Before building a new feature, check competitor comment sections first. If 10+ users have mentioned wanting that feature, you're likely on the right track.
A practical SaaS ops tip: use a browser extension to batch-export comment data, then import into an analytics tool for text-mining to find high-frequency words and trends.
Method 3: Manual 1-on-1 User Interviews (Free Version)
User interviews are the most direct research method. You can find willing participants without spending a dime.
Where to Find Interview Subjects
-
Your email list: If you already have subscribers, send a direct invite saying you're doing product research and would love their input. Offer a small gift card or product discount as thanks.
-
Social media DMs: Reach out directly to users who actively comment in relevant conversations. State clearly that you only need 15 minutes and won't take too much time.
-
Industry WeChat groups / Knowledge Planets: Post an invite in relevant communities — but engage genuinely first instead of dropping a link cold.
-
LinkedIn DMs: If you're building a B2B product, LinkedIn is a great place to find target users.
Interview Techniques
The key to zero-cost interviews is asking the right questions. Here's a framework:
- Can you describe the last time you encountered [problem area]?
- What solutions did you try at the time? Why didn't they work?
- If a tool/service could solve this, what would it look like?
- How much do you currently spend on this problem — in money and time?
- If a new tool could save you half the time, how much would you pay?
Important: Don't ask leading questions like "what features would you want." Instead, ask about past behaviors and experiences — those are facts, not hypotheticals.
What to Do After Each Interview
Take notes immediately after every interview. Capture the user's original language — their exact words are often more valuable than your summary. For example, "it takes me 3 days to make each report" is much more concrete than "the user thinks report creation needs improvement." These authentic quotes are the raw material for building a product that generates passive income.
After 5–10 interviews, start looking for patterns. If 3+ people mention the same issue, that's your top priority.
Method 4: MVP Testing and Behavior Observation
The most truthful user research isn't in what users say — it's in what they do. Launching a minimum viable product (MVP) and observing real usage is more effective than any interview.
Use a Landing Page for Research
If you don't have a product yet, build a simple landing page describing core features. See how many people leave their email to wait for launch.
Free tools: Use Carrd, Notion, or Feishu for a quick page. Or host a simple landing page for free on GitHub Pages.
Key metrics:
- Landing page visits
- Email signup conversion rate
- Time spent on page
- Most-clicked buttons/feature descriptions
Soft Launch and A/B Testing
Once you have a prototype, open it to a small group and observe their behavior.
You don't need complex A/B testing tools. Simple approach: send 10 users two different versions of a feature preview link and see which gets a higher click rate.
Validate Demand with Search Data
Before launching, check if people are actually searching for the problem you're solving.
Free tools: Google Trends (see search trend changes), Baidu Index, social media topic volume.
If search volume is rising, demand is growing. If nobody's searching at all, either the problem is too niche or you're going down the wrong path.
Method 5: Research Through Content (Content-Research Loop)
Most people think content marketing is only for acquiring users. In reality, content is also a fantastic research tool. After publishing an article, the comments, feedback, and questions from readers become gold-grade user research data.
Publish Content First, Watch Reactions
Before building in your target direction, write 1–2 in-depth articles and publish them on your blog, WeChat account, or Zhihu.
- High readership and active comments = demand in this direction
- If readers keep asking about one specific point — that's your product direction
- If readers ask "is there a tool that does this?" — you've found your product idea
Case study: An indie developer first wrote "How to Build Automated Workflows as a Solo Founder (Full Practical Guide)" and noticed readers were most interested in "automated customer service." He focused on building a customer service automation SaaS tool.
Collect Structured Feedback with Surveys
Use Feishu Forms or Tencent Questionnaire for free. Create a simple survey — no more than 10 questions, under 3 minutes to complete.
Survey design tips:
- First 2 questions: basics and pain points (filter quality respondents)
- Middle 4 questions: specific needs and willingness to pay (gather key data)
- Last question: "Anything else you want to add?" (catch unexpected insights)
Distribution channels: Your social circle, relevant communities, and at the end of your articles.
Reverse-Engineer Product Direction from Content Data
Content performance data is itself research data. Which articles got the most reads and bookmarks? Which feature mentioned in your article drew the most questions? These numbers tell you what users are most interested in.
Method 6: Build a User Feedback Flywheel
The final method is to systematically build an ongoing feedback mechanism. One-off research has limited value — user perceptions shift over time. A feature they don't need today could become essential tomorrow.
Set Up a Feedback Portal
Place a simple feedback entry in your product or website. You don't need a complex tool — a Feishu form link or an email address works.
Key: Reply to every single piece of feedback — even a one-line thank you. That's what keeps users coming back with more input. An automated reply system is nice, but combining it with personal responses is better.
Monthly User Discussion Sessions
Host a monthly online user discussion via Tencent Meeting or Feishu Meeting (free tier works).
Invite your active users (5–10 people) to discuss:
- How's the product been this month?
- Any difficulties?
- What features would you like next month?
Real-time feedback like this is more valuable than any survey.
Build a User Research Dashboard
Create a dashboard in Feishu Bitable or Notion to track:
- Feedback source (comments, interviews, surveys, meetings)
- Feedback summary
- Priority (high / medium / low)
- Corresponding action items
Review this dashboard regularly to ensure every valuable piece of feedback is addressed.
Summary: Keep Researching to Keep Growing — Passive Income Comes from Continuous User Insight
For a solo company, user research isn't a one-time task — it's a continuous loop. The more you research, the deeper your understanding of users, and the more accurate your product direction becomes.
Combine these six methods to build a complete zero-cost research system:
- Social media lurking: Monitor daily
- Competitor comment analysis: Review weekly
- User interviews: 5–10 per month
- MVP testing: Before every new feature launch
- Content-research loop: Treat every article as research
- User feedback flywheel: Maintain daily
For a solo founder running the whole show alone, user research is your biggest competitive advantage. Big companies have massive product teams — your agility and small scale are your edge. You can talk directly to users, iterate quickly, and build products that truly solve problems.
Finally, remember this: Your users have already told you the answers. You just haven't learned to listen yet.