A 3.5-7 hour client audit, done by Claude in 0.5 hours
A technical SEO and UX audit for a new client site normally takes the writer 3.5 to 7 hours. Claude pulled client info from OneDrive, ran the audit, drove a remote PageSpeed tool, and produced a Word report in 0.5 hours.
Done withClaudeSpotted· by HN user Festro· Oct 21, 2026
Result Left about 1 hour of review and writing
“Doing that report myself is 3.5-7 hours depending on what's found. Claude did it in 0.5 hours.”
Spotted: found in the wild. Details are as reported by the source above and have not been independently verified.
What they did
For a technical audit of a new client site, the writer prompted Claude using its skills for UX and SEO audits. Claude connected to an SEO tool, pulled client info from OneDrive, and output the report to Word from the agency’s template, even driving a remote PageSpeed testing tool in Chrome since there was no MCP server for it yet.
How it went
Doing that report by hand normally takes the writer 3.5-7 hours depending on what’s found; Claude did it in 0.5 hours, leaving them maybe 1 hour of review and writing to do, by their own estimate.
Try it yourself with Claude
Run a technical SEO and UX audit for [client site]. Pull their info from [OneDrive/our client folder], use our SEO tool and skills, test page speed since there's no MCP server for that yet, and output the finished report to Word using our agency template.
A starting prompt written by Agents in the Wild. Fill in the [brackets], and check what the agent does before it sends, pays for or deletes anything.
Public government data is hard to get at. Claude built sites that present it clearly and email it weekly, then review their own SEO and fix the day's glitches. Subscribers are trickling in.
A client needed posts going out on schedule to about 9 social networks. Built with Claude layer by layer and tested as it grew, it has run for months without a single error.
In a meeting about a bug in an app they didn't own, they told Claude to find out if it was user error, notify the user, and tell the developer what to fix. Fifteen minutes later, the developer asked: today or Tuesday?
After $45 in GitHub Actions overage in one month, a solo founder put an idle homelab to work as CI runners, with Claude making it easy to set up. Daily spend dropped from $2-4 a day to under $0.25.
A first homemade synth has 36 hall-effect keys and buttons and 7 rotary encoders. The firmware started by hand, then gentle prodding at Claude got everything needed much faster. Rev 2 of the PCB is nearly done.
A browser game where you answer with a power of ten leans on Claude for code and content: fact checking answers, writing explanations, and inventing new questions.