Results, judgment calls, and the method behind them
Case Studies: What Actually Happened
These are dated, anonymized write-ups of real engagements: what the client asked for, what was built, what the numbers did, and what did not work. Client names, product names and people are left out on purpose. Every figure is dated and comes from Search Console, Google Ads, GA4, a rendered search page or the engagement record, with the method noted under each table.
- Real engagements, not scenarios. Every number is dated and comes from Search Console, Google Ads, GA4, a rendered search page or the engagement record.
- One format on every page: situation, what was done, results with a method note, what made it work, honest limits.
- Client names, products, locations and people are withheld on purpose.
17 of 17
AI Overviews cited
44,133
monthly impressions, from 5,060
$79
Google Ads cost per lead
0
retractions in 68 AI-written posts
Running in real businesses today.
Claude builds for owner-led firms. Client names stay private. The work is described the way it runs.
An AI assistant took over when the human one left.
The owner's longtime assistant was leaving. Mail came into three inboxes, meetings sat in three calendars, and only the assistant knew what was owed.
A custom Claude plugin builds one morning page that leads with what the owner owes, sorts all three inboxes, flags threads going quiet, and drafts replies that never send on their own. Running in 6 days, accepted in 22.
“The dashboard is my window and [Claude] is where the work happens.”
Owner · Small business
Read the case study →Permit status from every agency portal, in one workbook.
The permitting specialist at a civil engineering and survey firm logged into city, county and state portals one at a time to see where each permit stood.
Claude reads the portals in her browser, read-only, and updates one workbook she owns: status, who has the ball, next step, days in house. She reviews every change. Claude never submits, signs or sends.
“I think the [Microsoft] 365 connectors is a game changer for me. Huge.”
Part of a firm-wide Claude rollout. Timesheets, permits and comment letters first.
Owner, an engineering and survey firm
Read the case study →Cited in 17 of 17 Google AI Overviews.
An industrial supplier had a new catalog site, no organic visibility, and zero mentions in ChatGPT answers.
Two to three technical articles a week, each answering one buyer question, structured so AI can read it. By May 2026 the site was the cited source in 17 of 17 AI Overviews checked. The benchmark competitor appeared in none.
“I'd rather get things more organically… let AI help us in that direction.”
Owner · Industrial supplier
Read the case study →Timelines are from these engagements. Yours is set in the planning stage.
The case studies
How these are written
Every page follows the same shape: the situation, what was done, the results with dates and a method note, what made it work, and an honest section on what did not. There are no testimonials without a number next to them and no numbers without a source.
Looking for custom Claude builds rather than search results? See Custom Claude Plugin Development, and the plugin and workspace case studies.
Questions
Why are the clients not named?
Because the results are the point and the clients did not sign up to be marketing. Company type, size and market are described; names, products, locations and people are not.
Where do the numbers come from?
Google Search Console, Google Ads, GA4 and rendered Google search pages, each dated. Build case studies cite the signed acceptance standard and the session record. A method note under every results table says which source, which window, and what was excluded.
Can I get the same result?
Some of it. Each page ends with what made it work and what did not, so you can judge the fit. Book an AI search audit if you want it applied to your site.
Similar situation? Bring one recent piece of work and we will start there.
Book an AI search audit →