
We told Claude not to sugar-coat us. It didn't.
Why we tell our AI tools not to sugar-coat how an account is tracking, and how more visual reporting helps clients ask sharper questions.

We started adding a specific AI section to every client's quarterly report a couple of quarters ago, and the reaction told us something worth sharing. Clients don't just glance at it. They ask about it, often before they ask about anything else in the report. In a year where AI Overviews and AI-powered search have genuinely changed how people find things online, that section is the one answering the question a client actually has, which is "what is this doing to us specifically", rather than the industry-wide version of that question they can read anywhere.
Before this, building that picture for a client meant going to Search Console for one part of the story, GA4 for another, and a separate keyword tool for a third, then manually stitching it together into something coherent. That process alone was time-consuming. Now it is pulled into one place as a baseline, which frees up time that used to go into assembly for the part that actually needs a person: working out what the numbers mean for that specific client and what to do about it next quarter.
It is fair to call this an assistant rather than a replacement, and a genuinely good one. It does the retrieval and the first pass at structure. It does not decide what matters, nor does it know a client's history, their competitors' quirks, or why a particular page has always underperformed for reasons outside SEO. That judgement still comes from someone who has worked the account for a while, which is exactly where we want it to sit.
The other change is less about AI and more about what AI made possible: every technical report now follows the same clear structure, client to client, quarter to quarter. That consistency sounds like a small thing until you have sat across from a client trying to make sense of a report that reads differently every time depending on who wrote it. A familiar layout means less time spent orienting and more time spent on the actual conversation, which is the same principle we have applied to reporting across other parts of the business this year.
None of this changes the fact that AI-generated analysis can be confidently wrong, and a technical SEO report is a bad place to discover that the hard way. Every section is still reviewed by someone who knows the account before it reaches a client. The tool gathers and formats faster than we could manually. It does not get the final say on what a client should actually do about their rankings, their content plan, or their site structure, because that call needs someone who has been doing this long enough to know when a number is telling the truth and when it needs a second look.
The AI Overviews and search shift we wrote about last quarter is not going away, and clients are right to want to know exactly where they stand against it. Building that answer into the report itself, rather than leaving it as a side conversation, is a small change that has made the quarterly review a meeting clients actually want to have.

Why we tell our AI tools not to sugar-coat how an account is tracking, and how more visual reporting helps clients ask sharper questions.

How an AI-built diagnostic tool caught two hidden checkout bugs on a busy online store in hours, and why an engineer still makes the fix.

AI design tools in Canva and Photoshop let us show clients real options in the room. Why a designer still makes every final call on brand.
Book a free call and we will show you where AI-native marketing can grow your business.
Book a call ↗