You know something is wrong with your product. Users sign up but don’t stick. Features go unused. Support tickets repeat the same confusion. Running a UX audit sounds like the right move, but hiring a research team or buying expensive analytics tools is not happening this quarter. The good news is you can identify most critical UX problems with tools you already have and a structured approach.
Start With Your Support Tickets and User Feedback
Your support inbox contains the clearest signal about where your product fails users. Export the last 90 days of tickets and sort them by topic. Look for patterns in confusion, workarounds users have invented, and features people ask about that already exist. If five users cannot find your export button, that is a discoverability problem. If ten users ask how to do something your product does not support, that is an expectation mismatch set somewhere earlier in their journey.
Aggregate feedback from sales calls, onboarding emails, and cancellation surveys the same way. You are building a list of friction points reported in users’ own words, not assumptions about what might be wrong.
Map Your Core User Flows
Pick the three flows that matter most to your business model. For most SaaS products, these are signup and onboarding, the primary value action (the thing users pay you to do), and account or billing management. Walk through each flow yourself as if you have never seen your product before. Use an incognito browser. Clear your cookies. Do not skip steps because you know the workaround.
Document every screen, every click, every decision point. Count the steps. Note where you have to think hard about what to do next. If you run into an error or dead end, write down exactly what happened and what you expected instead. This is not subjective opinion work. You are cataloging the objective experience of moving through your product.
Run a Heuristic Evaluation
A heuristic evaluation is a structured way to spot usability problems using known principles. You do not need a PhD in human-computer interaction. Use Jakob Nielsen’s 10 usability heuristics as a checklist. Go through each screen in your core flows and ask whether it violates any of the principles: visibility of system status, match between system and the real world, user control and freedom, consistency, error prevention, recognition over recall, flexibility, aesthetic and minimalist design, error recovery, and help documentation.
If your product saves changes automatically but never tells the user, you are violating visibility of system status. If your delete button sits next to your save button with no confirmation, you are violating error prevention. Write down every violation with a screenshot and the heuristic it breaks. This gives you a prioritized list of problems grounded in research-backed principles, not personal taste.
Use Free Analytics You Already Have
If you have Google Analytics, Mixpanel, or any product analytics installed, you already have data. Look at your funnel drop-off rates. Where do 50% of users bail? That screen has a problem. Check your feature usage stats. If nobody uses a feature you spent three months building, either they cannot find it or it does not solve the problem you think it does.
Session recordings (Hotjar has a free tier, so does Microsoft Clarity) let you watch real users struggle in real time. Watch 10 recordings of new users going through onboarding. You will see the same stumbles repeatedly. That repetition is your priority list.
Test With Five People
You do not need a research panel. You need five people who match your user profile and 30 minutes of their time. Give them a specific task: sign up and complete your onboarding, or find and use a particular feature. Do not help them. Do not explain anything. Just watch and take notes on where they hesitate, where they click the wrong thing, where they give up.
Nielsen’s research shows that five users will uncover 85% of usability problems. You are not trying to achieve statistical significance. You are trying to find the breaks in your experience. Five people will show you where those breaks are.
Compile and Prioritize
You now have a list of problems from support tickets, flow documentation, heuristic violations, analytics, and user testing. Group them by theme. Prioritize by frequency and impact. A problem that affects every new user during signup outranks a problem that affects power users in an advanced feature.
This is your UX audit. It cost you time, not money, and it gives you a concrete list of fixes ranked by business impact. At Tensai Design Studios, we run this exact process with clients before recommending interface changes. It cuts through opinions and gives you evidence.
What to Do With Your Findings
Pick the top three problems and fix them. Then measure whether the fix worked. Did support tickets about that issue drop? Did funnel conversion improve? Did feature adoption increase? A UX audit only matters if it leads to changes that improve outcomes. Treat your findings as hypotheses, make the changes, and validate the results. That cycle is more valuable than any expensive research report that sits in a folder.