User Research on a Budget
You don't need a research team or expensive tools. Here's how to learn about users with limited resources.
User research often gets skipped at startups. It seems expensive, time-consuming, and like something big companies do. But research doesn’t require a budget or a dedicated team. It requires talking to users and paying attention.
Here’s how to do effective research with almost no money.
Why Research Matters
Building without research is building based on assumptions. Assumptions are often wrong. Research:
•
Reveals problems you didn’t know existed
•
Validates (or invalidates) your hypotheses
•
Shows you how users actually behave
•
Prevents building features nobody wants
•
Reduces wasted development time
The cost of research is always less than the cost of building the wrong thing.
The Five Research Methods
1. User Interviews
Talk to users one-on-one. This is the most valuable research method and costs only your time.
How to do it:
•
Reach out to existing users for 20-30 minute calls
•
Prepare 5-7 open-ended questions
•
Focus on their problems and current behavior
•
Record (with permission) for later review
What to ask:
•
“Walk me through how you currently handle [problem]”
•
“What’s the most frustrating part?”
•
“What have you tried before?”
•
“Show me how you use our product”
Sample size: 5-10 interviews usually reveal major patterns. You don’t need hundreds.
Cost: Free (your time only)
2. Usability Testing
Watch users try to complete tasks in your product. This reveals UX problems you’d never notice.
How to do it:
•
Define 3-5 tasks for users to complete
•
Ask them to think aloud while working
•
Don’t help or guide—observe
•
Note where they struggle or get confused
Remote tools:
•
Zoom (free) – Simple screen sharing
•
Loom (free) – Users record themselves
•
Maze (paid) – Unmoderated testing at scale
Guerilla testing:
•
Find users at coffee shops (offer $5 or coffee)
•
Post in relevant communities asking for feedback
•
Ask friends who match your target profile
Sample size: 5 users catch ~80% of usability issues.
Cost: Free to $50 (incentives)
3. Analytics and Behavior Data
See what users actually do, not just what they say.
Free tools:
•
Plausible, Umami, Fathom – Simple analytics
•
PostHog – Full product analytics (free tier)
•
Google Analytics – Comprehensive but complex
What to track:
•
Where users drop off
•
Which features get used
•
Time on task
•
Conversion funnels
•
Retention patterns
Questions analytics answer:
•
Are users reaching the core value?
•
Where do they get stuck?
•
What features are unused?
•
When do users churn?
Cost: Free (most tools have free tiers)
4. Surveys
Collect structured feedback at scale.
Free tools:
•
Tally – Beautiful, free survey tool
•
Google Forms – Basic but effective
•
Typeform – Good UX (limited free tier)
Best practices:
•
Keep surveys short (5-10 questions)
•
Use a mix of multiple choice and open-ended
•
Ask about specific experiences, not hypotheticals
•
Include an open “anything else?” at the end
Good survey questions:
•
“How would you feel if you could no longer use [product]?” (PMF test)
•
“What’s the main benefit you get from [product]?”
•
“What would you improve?”
•
“How did you discover us?”
Sample size: 30-50 responses minimum for patterns.
Cost: Free
5. Customer Support Mining
Your support inbox is a goldmine of research data.
What to look for:
•
Repeated questions (documentation/UX issues)
•
Feature requests (unmet needs)
•
Complaints (pain points)
•
Workarounds users mention (gaps in functionality)
How to analyze:
•
Tag tickets by category
•
Track frequency of each category
•
Look for trends over time
•
Connect support data to user characteristics
Cost: Free (you’re already doing support)
Low-Budget Research Process
Step 1: Define Your Questions
What do you need to learn? Be specific:
•
“Why do users drop off after signup?”
•
“What triggers users to upgrade?”
•
“How do users discover our product?”
Step 2: Choose Methods
Match methods to questions:
Question
Best Methods
Why users behave a certain way
Interviews
Where users struggle
Usability testing
What users do
Analytics
User satisfaction/preferences
Surveys
Common problems
Support analysis
Step 3: Execute
For interviews:
1.
Email 20 users asking for 20-minute calls
2.
Expect 3-5 to respond yes
3.
Schedule via Calendly or similar
4.
Conduct and take notes
For usability testing:
1.
Define tasks
2.
Recruit 5 users (email, community, friends)
3.
Run sessions (in-person or Zoom)
4.
Document issues
For surveys:
1.
Write 5-10 questions
2.
Send to user list
3.
Wait 3-5 days
4.
Analyze responses
Step 4: Synthesize
After research:
1.
Review all notes/recordings
2.
Look for patterns (3+ people saying similar things)
3.
Prioritize insights by impact
4.
Share with team
Step 5: Act
Research without action is wasted time:
•
Update product based on findings
•
Test hypotheses from research
•
Share insights across the team
•
Track whether changes help
Research Questions by Stage
Pre-launch
•
What problems do target users have?
•
How do they currently solve them?
•
What would make them switch?
Early Users
•
Why did you sign up?
•
What almost stopped you?
•
What’s confusing?
Growing
•
Why do users stay/leave?
•
What triggers upgrades?
•
What features are ignored?
Scaling
•
How do different segments differ?
•
What drives word of mouth?
•
What limits growth?
Making Time for Research
“We don’t have time for research” is the most common excuse. Counter it:
Continuous research: 2-3 user conversations per week. 30 minutes each. Part of the routine, not a special project.
Attached to features: Before building, talk to 3-5 users. After launching, test with 5 users. Built into the process.
Support as research: Read support tickets weekly. Already happening.
Analytics review: 30 minutes per week reviewing dashboards. Already should be happening.
Research doesn’t require dedicated time blocks. Integrate it into how you work.
Common Mistakes
Asking leading questions: “Wouldn’t it be great if…” leads the witness. Stay neutral.
Small samples for surveys: 5 survey responses isn’t data. Get at least 30.
Ignoring what you don’t want to hear: Confirmation bias. Seek disconfirming evidence.
Research paralysis: Researching forever instead of building. Time-box it.
Not talking to churned users: They have the most valuable feedback. Ask why they left.
Key Takeaways
•
User research doesn’t require budget—it requires talking to users
•
5 user interviews reveal most major insights
•
5 usability tests catch ~80% of UX issues
•
Analytics show what users do; interviews show why
•
Support tickets are free research data
•
Integrate research into your weekly routine, not as special projects
•
Act on what you learn—research without action is waste
Put your context to work.
Keep your project’s decisions, next steps and proof together as your agents work.
Explore the agent workflow →