MoneyForge
All Posts
Freelance Skills

How to Make Money With UX Usability Testing

MoneyForge Team 2026-09-07 13 min read

Plenty of websites look fine to the people who built them. The moment a stranger tries to complete a task, the confusion appears: unclear pricing, hidden buttons, broken mobile layouts, forms that erase work, checkout steps nobody understands.

UX (User Experience) covers how a person feels while using a product. Usability is narrower: can a person finish a task without unnecessary confusion? A usability test therefore tries to answer one practical question: what prevents someone from booking, buying, signing up, or finding the information they need?

The simplest beginner service looks like this:

  1. Pick one website journey, such as booking an appointment.
  2. Write five realistic tasks.
  3. Record yourself trying to complete them on desktop and mobile.
  4. Document every hesitation, missing label, broken state, and unnecessary step.
  5. Deliver a short report with screenshots, severity ratings, and fix recommendations.

That version is technically an expert review rather than research with multiple users. It is still useful, but you must describe it honestly. A marketplace review observed related project prices from roughly $80 to $500 depending on scope; treat that as a marketplace observation, not a guaranteed rate.

Start Here: Three Different Routes

This article covers three routes that sound similar but are not the same job:

RouteWho Performs the TestWhat You DeliverIncome Style
Platform testerYou are the participant on UserTesting or a similar siteA recorded session for the platform's client$10-60 per task
Expert UX reviewYou audit the website yourselfTask walkthrough, evidence, and a prioritized report$80-250 per project
Moderated usability testYou recruit and observe 3-5 target usersSession recordings, cross-user patterns, and recommendations$300-500 per project

Start with expert UX reviews. You control the scope, do not need to recruit participants, and can build portfolio samples immediately. After five clean projects, add moderated testing.

The buyer is not paying for "I like this design." They are buying four things:

  • An outside perspective from someone who has not learned their product's quirks
  • Repeatable tasks instead of random clicking
  • Evidence: screens, timestamps, confusion points, and failed actions
  • Prioritized fixes the team can turn into development tickets

Good clients already know their product has problems. They lack fresh eyes and time. Your job is to reduce uncertainty before they spend weeks building the wrong improvement.

Market Scope and Pricing

Usability work is global by default. Any business with a website, SaaS product, mobile app, checkout flow, booking system, or onboarding sequence can benefit. Your best early clients are usually small product teams, independent SaaS founders, local service businesses, ecommerce stores, and agencies that need an outside review before a launch.

A practical package structure is:

PackageWho Is TestedWhat You DeliverSuggested PriceWorking Time
Expert landing-page reviewYou, using five realistic tasksAnnotated screenshots, severity table, PDF report$80-1203-4 hours
Expert website or app auditYou, across the full journeyDesktop and mobile checks, recording, 8-15 findings, fix list$150-2505-8 hours
Moderated usability test3-5 target usersTest plan, participant recordings, summary deck, prioritized recommendations$300-50010-15 hours

Name the first two packages "UX audit" or "expert review." Reserve "usability test" for projects in which real participants attempt the tasks. Accurate positioning prevents disputes and makes the premium package easier to justify.

These prices are starting ranges based on visible marketplace bands and the scope of work, not official industry rates. A marketplace review showed thousands of sellers offering related services, with basic listings around $30-50, fuller projects in the hundreds, and specialist accessibility work higher. That means the category is competitive, but there is still room for sellers who explain their method clearly.

Fiverr charges sellers a 20% commission, so a $150 project nets about $120 before withdrawal costs. Upwork also charges marketplace fees, so check the current fee schedule before pricing direct projects. For direct clients, invoice through PayPal, Wise, or another method available in your country.

Do not underprice the work to $15. A report that requires real testing, screenshots, severity ratings, and clear recommendations is worth more than a template of generic advice.

The Skills That Make You Credible

You do not need a design degree to start. You need a structured way to evaluate an interface.

Your credibility comes from method, not vocabulary. An opinion says, "I don't like this layout." A finding says, "The pricing button moved below the comparison table on mobile, so I had to scroll past unrelated content before I could compare plans." The second sentence gives the client something to test and fix.

Use Nielsen's ten usability heuristics as a review framework. They include system status visibility, language that matches the user's world, user control and freedom, consistency, error prevention, recognition instead of recall, flexibility, minimal design, error recovery, and help documentation. These are widely accepted evaluation principles, and they give you a professional vocabulary.

Turn them into plain questions:

  • Can I tell where I am and what happens next?
  • Is the next action obvious without guessing?
  • Can I recover from a mistake?
  • Does the page explain the offer in the user's language?
  • Can I complete the task on a phone without zooming or hunting?
  • Are error messages specific and actionable?
  • Is important information available at the moment I need it?

A useful UX insight from user research teams is to work with the client's cadence. A small test every week or every two weeks is often more useful than a giant quarterly report. You can package that as a monthly mini-audit: one core journey, one short recording, and one prioritized fix list.

Build Three Portfolio Samples

Do not wait for a client to prove you can do the work. Create three sample projects in a week.

  • Sample one: a SaaS free-trial signup flow
  • Sample two: a local service business booking flow
  • Sample three: a small ecommerce checkout

For each sample, produce:

  • One page explaining the target user and business goal
  • Five to eight task scenarios
  • A screen recording with timestamps
  • Annotated screenshots
  • A findings table with severity and impact
  • A short list of prioritized fixes

Use your own demo pages, public open-source templates, or clearly labeled concept reviews. Do not expose private client data. If you use a real public website, label it as an unsolicited demonstration review rather than a paid client project.

Your portfolio should show evidence, not adjectives. "The pricing CTA disappears below the comparison table on mobile, which may send users back to search instead of signup" is stronger than "the design needs better hierarchy."

Run an Expert Review or Moderated Test

Before you open the website, define the business goal. "Make the site better" is not a test objective. "Book an appointment in under three minutes" is.

In an expert review, you are the person completing the tasks. That gives you speed and a fresh perspective, but it does not prove what every target user will do. In a moderated test, participants complete the tasks while you observe and ask non-leading questions. That produces stronger behavioral evidence, which is why it costs more.

Your intake questions should be:

  • What is the primary conversion action?
  • Who is the target customer?
  • What device matters most: desktop, mobile, or both?
  • Which pages are most important?
  • What part of the journey worries the team most?
  • Are there access restrictions, test accounts, or staging links?
  • What is the deadline?

Then create task scenarios. Write them as goals, not instructions.

Weak TaskBetter Task
Click PricingFind out what the service costs for a five-person team
Go to checkoutBuy one product using standard shipping
Open settingsFind where to change the account email address
Test supportContact support about a delayed order

As you run each task, record:

  • The exact screen
  • What you expected before you clicked
  • What actually happened
  • The time or number of steps required
  • Where you hesitated
  • Whether you recovered without help
  • The business consequence

Use a spreadsheet, not memory. A strong findings table has these columns: finding, evidence, severity, user impact, recommendation, and client effort.

A specific row might look like this:

FindingEvidenceImpactRecommendation
Mobile checkout button is below the order summary on a 375 px screen02:14 in recording; three downward scrolls requiredAdds friction on the highest-value actionMove the primary button above the summary and test the new layout

Do not summarize everything as "high priority." A useful severity scale separates a broken checkout from a slightly confusing label. A minor copy change and a payment failure do not belong in the same priority bucket.

For moderated tests, recruit participants who match the target customer: the client's existing users, an email list, a niche community, or a research panel. Get consent before recording. Explain that you are testing the product, not the person. Avoid asking leading questions such as "Did you find that confusing?" Ask "What did you expect to happen there?" or "What are you looking for right now?"

Deliver a Report People Can Use

Your report is the product. Make it specific enough that a developer, founder, or designer can act without another meeting.

Use this structure:

  • Business goal and test scope
  • Method and device setup
  • Task list
  • Findings by severity
  • Evidence screenshots with annotations
  • Prioritized recommendations
  • Quick wins versus larger structural changes
  • Recording or timestamped clips
  • What you did not test

The last section is underrated. If you did not test accessibility compliance, payment failure, security, or backend workflows, say so. It protects you and makes the scope easier to renew.

Share raw evidence where possible. A 90-second clip of a user repeatedly missing a button is often more persuasive than three paragraphs of analysis. Add timestamps so the team can jump to the moment.

Accessibility can be a valuable adjacent offer, but be careful with wording. Automated tools can flag common issues, but they do not prove full compliance. Do not promise legal compliance unless you are qualified. A safer deliverable is an accessibility-focused usability review with manual checks and clear recommendations.

Get Clients and Repeat Work

On Fiverr, use the buyer's language:

I will perform a UX audit or usability test and deliver an actionable report

If your package does not include real participants, sell it as a UX audit or expert review. Use "usability test" only for the moderated package.

Use search tags such as usability testing, UX audit, website testing, user testing, and UX research. Your gallery should show your method, report sample, severity table, and before-and-after recommendations. A generic "I do UX" graphic will not convert.

On Upwork, search for UX audit, usability testing, user research, conversion optimization, website feedback, and app testing. In proposals, include:

  • The client's stated goal in your own words
  • The exact journey you would test
  • Your deliverables and timeline
  • One observation from their public website, if appropriate
  • A question that shows you understand their users

Direct outreach works better when it is narrow. Pick ten SaaS products with a free trial, booking sites with multi-step forms, or ecommerce stores with mobile checkout friction. Send a short message identifying one public observation and offering a paid mini-audit. Do not send a full free report to strangers.

Agencies are better repeat buyers than one-person founders. They need outside reviews before launches, client-facing evidence, and people who can deliver consistently. A monthly package could include one website journey audit, one mobile audit, and one 30-minute findings call. Price it based on scope rather than hours.

Use AI Without Destroying Quality

AI can help with the parts that slow you down:

  • Turn your spoken notes into structured findings
  • Improve grammar and clarity
  • Generate a first draft of the report structure
  • Convert technical observations into plain client language
  • Summarize session transcripts
  • Create questions for a follow-up call

AI cannot replace the actual test. It did not click the button, lose the form input, or wonder why the label says "Continue" when the next step is actually account verification.

The fastest way to fail is to deliver generic AI suggestions such as "improve navigation" or "optimize page speed." If a finding applies to every website in the world, it is not a finding. Delete it unless you have evidence from this product.

Use AI after the evidence stage, not instead of it. That boundary is what separates a useful UX report from an empty AI document.

Realistic First Month

This is a projection based on the workflow and marketplace pricing above, not a typical-income promise.

PeriodFocusRealistic Output
Week 1Learn the expert-review framework and create three samplesDemo reports and recordings
Week 2Publish marketplace gigs and send 5 tailored proposals per dayFirst conversations
Week 3Deliver one small project wellFirst review and testimonial
Week 4Refine package, FAQ, and intake formClearer offer and fewer bad-fit inquiries

Month one may produce zero to three paid projects. That is normal because trust is the main barrier. After five completed reports, you can raise prices and move from landing-page reviews to full journeys.

The long-term opportunity is better than one-off reports. A product team that ships every two weeks needs recurring feedback. Three monthly clients at $250 each produce $750 gross before fees. That is not passive income, but it is a more stable service base than random low-value tasks.

Common Mistakes

Reporting opinions instead of evidence. Attach the screen and timestamp.

Testing without a task. Random browsing produces noise.

Calling an expert review a user test. If you did not observe target users, sell it as a UX audit or expert review.

Turning every issue into an emergency. Severity loses value when everything is high priority.

Promising conversion increases. You can identify friction, not guarantee results.

Overpricing beginner moderated research. If you have never recruited participants, practice first or partner with someone who has.

Skipping mobile. Many journeys fail only on a smaller screen.

Sending a 40-page document. Most clients want priorities, proof, and next steps.

Start with one narrow journey, one clear report template, and three strong demo samples. Once clients see that your findings save development time, usability testing becomes easier to sell as a repeat service.