Freelancer builds OpenClaw agent for visual app testing, lands 11 clients

How it started: Identifying a preventable bug

A frontend freelancer was working on a home services marketplace app with around 890k downloads. While rebuilding the search and filter flow, they noticed recurring support tickets about the review system attaching ratings to the wrong service provider. The bug occurred because review submission associated ratings by most recent booking timestamp instead of the booking ID the user actually selected on the review screen. This created a race condition when the booking list order shifted between when the user tapped "leave review" and when the review screen loaded.

The lead engineer had known about the issue for two months but their testing process consisted of opening the app on their phone, tapping through main screens, and shipping if nothing looked broken. They never tested the review flow with multiple bookings because they only ever had one test account with one booking at a time. The bug only showed up when real users had overlapping bookings in the same week, which was most of their active users.

The solution: Building a visual testing agent

Using OpenClaw for three months in their own workflow, the developer built an agent that:

• Takes test steps written in simple statements
• Connects to a cloud emulator
• Runs through the app visually
• Captures every step along the way
• Shows exactly where something breaks and what the screen looked like

After two weeks of practice with friends' small apps to get step writing down, they offered the home services client 5 free test runs. The review flow failed on the second run, exposing the exact bug with screenshots showing where it went wrong.

Business model and client acquisition

The service costs $180/month for 26 flows covering core user journeys. The developer runs the agent, maintains context, adds flows when features ship, and flags anything that breaks, taking about 2.5 hours per month per client.

Initial clients came through professional connections:

• A fleet tracking app (1.4 million downloads) with route logging issues where tracked paths showed gaps when the app lost foreground state during long drives. $320/month.
• A school communication app (1.3 million downloads) with notification routing sending class announcements to wrong parent groups when teachers were assigned to multiple sections. $200/month.

Additional clients included a grocery delivery app ($220/month), inventory sync app ($130/month), and salon booking app ($140/month). Word of mouth from existing clients drove further growth through founder group chats, meetups, and developer communities.

One lead didn't work out: a founder building an AI recipe app saw the trial but was planning a major rewrite and decided testing the current version didn't make sense.

Current metrics

11 total clients: 9 active, 2 finishing onboarding. Total recurring revenue when all are live: $3,840/month. The developer spends about 22 hours per month across all clients, averaging 2-3 hours of maintenance per client. This works out to roughly $170/hour for work that's mostly reviewing reports and writing new flows when features ship.

One-time fees added $1,600 total, including $500 for full flow documentation on the fleet app and $450 for the school app which needed separate flows for 6 different user roles.