By Mehdi HassanStartups rarely fail at research because they picked the wrong tool. They fail because they bought a stack before they had a habit. This guide recommends a stack for each stage, names what each tool is for, and is blunt about what to skip. Plans and limits change often, so check each vendor's current plan page before you commit.
What user research tools do startups actually need?
Startups need tools for four jobs: talking to people, finding people, testing designs and seeing behavior in the product. Everything else, including repositories, AI synthesis and survey panels, is optional until research is a weekly activity.
Job | What it covers | Free or cheap option | Upgrade when |
|---|---|---|---|
Interviews | Calls, recording, transcripts | Zoom, Google Meet, Microsoft Teams | You need searchable transcripts across many calls |
Scheduling | Booking and reminders | Cal.com, Calendly free tiers | Several people run sessions |
Recruiting | Finding participants | Your own users, LinkedIn, communities | You need strangers who match a niche profile |
Design testing | Prototype, first-click, preference tests | Maze or Lyssna free tiers | You test every month |
Behavior | Funnels, session replays, heatmaps | PostHog, Microsoft Clarity | Event volume outgrows the free tier |
Synthesis | Tagging, clustering, decisions | Spreadsheet, FigJam, Notion | Several researchers share one repository |
If you haven't decided which methods fit your stage, our user research playbook for startups maps methods to budget first. Choose the method, then the tool.
Which UX research tools fit a pre-launch startup?
Before launch, the right UX research tools are free ones: a video call tool, a booking link, a short screener form and a spreadsheet. Your bottleneck is finding the right people and asking good questions, and no paid tool solves either.
- Calls: whichever video tool your participants already use. Record with consent and turn on built-in transcription.
- Screener: Google Forms or Tally with three to five questions that filter for the job you're designing for.
- Prototype testing: share a Figma prototype link in a moderated call. You learn more from watching five people struggle than from an unmoderated dashboard.
- Synthesis: a spreadsheet with columns for participant, observation, tag and cluster. It makes counting easy, which our guide to research synthesis and decision logs depends on.
The paid line item that's often worth it at this stage isn't software. It's incentives and recruiting. If you have no users yet, read how to recruit research participants with no users before you spend anything.
Maze vs Lyssna: which usability testing tool should you pick?
Pick Maze if you mostly test interactive Figma prototypes and product flows; pick Lyssna if you mostly run quick design tests such as five-second, first-click and preference tests. Both are credible usability testing tools, both have free entry tiers, and both change their plans often enough that you should compare current limits yourself.
Factor | Maze | Lyssna |
|---|---|---|
Best at | Prototype and flow testing | Fast design and message tests |
Typical test | Can users complete this task in the prototype? | Which headline is clearer? Where would you click? |
Figma prototypes | Core use case | Supported |
Participant panel | Paid; check current pricing | Paid; check current pricing |
Good fit | Product teams iterating on app flows | Marketing and early design decisions |
Use either for unmoderated tests where you need volume and speed. Use moderated calls when you need to understand why. If you're running your first tests, our guide to usability testing with five users in an afternoon works with nothing more than a call link.
What interview tools help with recording and transcripts?
For interview tools, the call software you already pay for usually records and transcribes well enough. Dedicated tools earn their place when you run many interviews and need to search across them, tag clips and share highlights with the team.
A practical path: start with built-in recording and transcripts, save them to one shared folder with a consistent naming scheme (date, segment, participant ID), and paste key quotes into your synthesis sheet. Move to a dedicated repository such as Dovetail only when two or more people run research and you keep re-asking 'didn't someone say this already?'
What to check before you record any interview
Ask for consent to record at the start of the call and again on the recording. Say who will see it and how long you'll keep it. Don't record people who decline; take notes instead.
Store recordings somewhere access-controlled, not in a public link. Delete them on the schedule you promised.
If you research users in regulated industries such as healthcare or finance, check your data handling obligations before the first session, and avoid collecting details you don't need.
Which product analytics tools work for UX research?
Free product analytics such as PostHog and session replay tools such as Microsoft Clarity are the cheapest way to see where real users struggle. They tell you where people drop off; interviews and tests tell you why. You need both.
PostHog combines events, funnels, session replays and feature flags in one tool, which suits developer-led teams. Clarity is free and quick to add, and it's good for heatmaps and replays on marketing pages and simple apps. The setup matters more than the brand: track the five or six events that define activation and nothing else at first. Our overview of conversion research methods shows how analytics, surveys and tests fit together, and if you're choosing an experimentation tool next, see our roundup of A/B testing tools for startups.
Which user research tools should startups skip?
Skip anything that solves a problem you don't have yet. For most early teams that means enterprise research suites, standalone repositories, large survey panels and AI tools that promise to replace interviews.
Pros
- Free and cheap tiers cover nearly every early-stage method
- Fewer tools means research data lives in one place
- Money saved goes to incentives, which improve data quality directly
Cons
- Manual tagging in a spreadsheet gets slow past a few dozen interviews
- Free tiers cap tests, responses or replays, so heavy months hit limits
- Without a repository, insights from earlier studies are easy to lose
Upgrade on a trigger, not a feeling. Typical triggers: you hit a tier limit two months in a row, a second person starts running research, or you can't find a past finding when you need it.
What's the right user research tools stack for startups at each stage?
The right stack of user research tools for startups grows with how often you research: free tools pre-launch, one paid testing tool once you test monthly, and a repository only when research becomes a team habit.
Stage | Stack | Skip for now |
|---|---|---|
Pre-launch | Call tool, booking link, form, spreadsheet, Figma prototypes | Any paid research software |
Early users | Add PostHog or Clarity, plus a free tier of Maze or Lyssna | Repositories, survey panels |
Product-market fit search | Paid testing tool, recruiting panel when needed | Enterprise suites |
Growing team | Add a shared repository and AI transcription | Tools that duplicate what you have |
If your research has stacked up and you need it turned into screens, our $3,000 fixed-price design sprint produces a redesign direction and 10 product or website explorations in Figma. Our UX audit vs usability testing comparison can also help you decide which comes first.
