Skip to content

AILast updated 25 August 20265 min readBy The PixelCrayons team

What we tell clients who ask us to “just do
what ChatGPT recommended”

In one answer

What we tell clients who ask us to “just do what ChatGPT recommended” AI search now hands every buyer a confident, specific-sounding answer before they talk to anyone. That's genuinely useful, and also occasionally wrong in ways that are expensive to act on unchecked. This is the actual pattern behind that increasingly common conversation, what we check before agreeing or pushing back, and why the answer isn't to dismiss the AI recommendation on principle.

Why is this happening more often now?

Because AI search has genuinely changed the starting point of a marketing conversation. A prospect used to arrive with a problem and a vague sense of what might fix it. Increasingly they arrive with a specific, confidently-worded plan (a platform recommendation, a channel mix, sometimes exact tactics) because they asked an AI assistant first and got a fluent, plausible-sounding answer in seconds.

That’s a real improvement in how informed a first conversation can start. It’s also created a new, specific failure mode: the recommendation can be fluent and confident while being generic, out of date, or simply wrong for the client’s actual situation in ways that aren’t obvious from reading it.

Why would an AI-generated marketing recommendation actually be wrong?

Three reasons show up repeatedly. It’s answering the general version of the question, not the specific one: a genuinely good generic answer to “how should an ecommerce brand approach SEO” can be a poor fit for a specific brand’s actual competitive position, technical debt or budget. None of that was necessarily visible to the AI when it generated the answer.

It can be confidently out of date. Search algorithms, ad platform mechanics and even AI search itself change fast enough that a plausible-sounding recommendation can describe how something worked a year ago rather than how it works now, with no obvious signal in the answer’s tone that it might be stale.

And it doesn’t know the client’s actual constraints: budget, existing tech stack, brand restrictions, a previous vendor relationship that limits options, because none of that context was necessarily in the prompt that generated the recommendation.

What do we actually check before agreeing or pushing back?

Whether the recommendation matches the client’s specific competitive and technical situation, not just the general category it’s in. That’s usually a quick, honest gut-check for someone who does the work daily, even before a full audit. Whether it’s current: some of what circulates in AI answers about SEO and paid media specifically lags real platform behaviour by months, because training data has a cutoff and the platforms don’t wait for it.

And whether it accounts for constraints the AI didn’t have: budget size, an existing contract, a brand guideline that rules out an otherwise-sound tactic. Where the recommendation holds up against all three, we say so plainly and build the plan around it. Where it doesn’t, the job is explaining specifically why, not dismissing AI search generally. AI Overviews and answer-engine visibility are genuinely reshaping how buyers find and evaluate agencies, us included.

What does the general-versus-specific gap actually look like in practice?

The shape recurs often enough to describe generally, without needing a specific client anecdote to make the point. A brand asks an AI assistant “how should we improve our SEO,” and gets back a fluent, entirely reasonable answer built around general best practice: improve page speed, build topical authority, fix technical issues. All true, all sound advice for the average site in that category.

What that answer structurally can’t know is whether this specific site’s biggest problem is actually one of those things, or something the general advice doesn’t mention at all. It could be a cannibalisation issue between two pages competing for the same query, a crawl budget problem specific to how the site’s architecture is built, or a content gap in exactly the queries that convert best for this business. A generic answer optimises for being true on average across many sites; a specific site’s actual highest-leverage fix is frequently not the average answer.

The useful move isn’t discarding the AI’s answer (it’s usually a reasonable checklist to start from). It’s checking each item against the specific site before spending budget executing all of it, because the item missing from the list is often worth more than every item on it combined.

How has this actually changed what a first conversation with a prospect looks like?

It moves faster to the specifics, which is a genuine improvement. A prospect arriving with a general question (“how do we get more traffic”) and one arriving with a specific AI-generated plan are having different first conversations. The second one skips the education step and goes straight to “here’s what’s right about this for you, and here’s what isn’t,” which is a more useful use of the first call’s time for both sides.

What it hasn’t changed is the underlying work of actually verifying a recommendation against a real site. That still takes a review of the actual site, a competitive read, or direct platform experience, none of which the conversation itself can shortcut. The same applies when the recommendation is “build an agent”: what that word actually means decides the brief. The AI-generated starting point makes the conversation more efficient; it doesn’t make the verification step optional.

Questions

Frequently
asked.

More often directionally reasonable than wrong outright. The failure mode is rarely a completely bad idea; it’s a generically good idea applied without the client’s specific constraints. That’s exactly the gap a second opinion is useful for closing.

No. It’s genuinely useful as a starting point, and clients arriving with a specific plan rather than a vague problem is a better conversation to have. The point isn’t that AI recommendations are unreliable; it’s that a confident tone isn’t the same as being current or client-specific, which is true of any source, human or otherwise.

The same way any practitioner does: by running the platforms directly rather than only reading about them, which surfaces changes faster than most published content does, AI-generated or not.

That’s their call to make, and we’ll say clearly what we’d do differently and why before executing it. The job is an honest second opinion, not a veto. Occasionally the AI recommendation turns out fine anyway; the point of checking is knowing which case you’re in before spending the budget.

Have a process
to automate?

Tell us the job. A senior engineer scopes a pilot and prices it, with the limits stated up front.

Reply inside 48 hours · Free · No retainer required

May we run analytics (Google Analytics via Google Tag Manager) to see which pages are useful? Nothing loads unless you accept, and declining means no analytics script runs at all. No advertising cookies either way. Cookie policy · Privacy policy