UX Research on a Startup Budget: A 5-Day Plan to Test Your Product

In short: you don’t need a lab or a big budget to learn what’s wrong with your product. You need clear questions, five of the right people, real tasks and an honest write-up. Here is the 5-day plan we use with startups.
Day 1 — Decide what you need to learn
Write three to five questions the team is arguing about. “Do users understand our pricing?” or “Can a first-time user finish onboarding alone?” are good. “Do people like the app?” is not — it can’t change a decision.
Turn each question into a task: something a person can try, like “Find out how much the premium plan costs per month and sign up for it.”

Day 2 — Recruit five real users
- Pick people who match your target customer — not friends, not the team.
- Use your waitlist, existing customers, community groups or a short screener form.
- Offer a small thank-you (a voucher or free month) and book 30–45 minute video calls.
Day 3 — Run the sessions
Share a clickable prototype or the live product. Ask people to think aloud as they try each task, and resist the urge to help. The most useful moments are the silences, the backtracking and the “hmm, where is…”.
- One person moderates; another takes notes with timestamps.
- Ask “What did you expect to happen?” instead of “Did you like it?”.
- Record (with permission) so the team can watch key clips later.
Day 4 — Make sense of it
Put every observation on a sticky note (physical or on a whiteboard) and group them. Patterns that show up with three or more people are your priorities. Rate each by how badly it blocks the task.
| Severity | Meaning | Action |
|---|---|---|
| Critical | User could not finish the task | Fix before launch |
| Major | Finished, but with real struggle | Fix in the next sprint |
| Minor | Small confusion or wording | Batch with other polish |
Day 5 — Decide and design
Share a one-page summary with three to five findings, each with a short clip and a recommended change. Then redesign the critical issues and test again with a fresh small group. Two quick rounds beat one big study.

Common mistakes to avoid
- Leading questions (“This is easy, right?”).
- Testing with the wrong people, then designing for them.
- Collecting opinions instead of behaviour. Watch what people do.
- Reports nobody reads. Keep it to one page and a few clips.
Want help planning or running a round? See our UX research and UI/UX design services.
FAQ
How many users do I need for a usability test?
For finding the biggest problems, around five people from your target audience is usually enough to see the same issues repeat. Run another small round after you fix them.
What is the difference between user interviews and usability testing?
Interviews explore people’s needs, habits and language. Usability tests watch people try to complete real tasks in your product, so you see where the design gets in their way.
Can we do UX research without a big budget?
Yes. Video calls, a clickable prototype and five well-chosen participants are enough to find the problems that matter most.
Need help testing your product?
We design and build Shopify experiences that sell — and get found on Google and AI search. Custom Shopify coding in 7 days, or a full refund.
Book a call