Skip to content

Build in Public

Day 138: Your Help Centre Is Already Part of the Sales Conversation

A Marketing Director is evaluating a reporting platform before inviting suppliers into a formal process. She does not ask an AI system which product has the best dashboard. She asks a harder question:

If a scheduled board report fails on deadline day, who can restart it, how will we know what was delivered, and when do we need the vendor?

The campaign page promises automated reporting. The help centre explains the recovery path.

That operational answer may shape the buying conversation before sales knows the opportunity exists. It can reveal who needs administrative access, what the internal team must own, where vendor support begins, and whether the recovery route is acceptable for a high-consequence workflow.

This is a generalised buyer scenario, not a reported customer journey or an observation that every AI system will retrieve the same page. The commercial point is narrower: in AI-assisted B2B research, a serious pre-sale question may be answered by material written for existing users.

Your help centre is therefore not only a support destination. Parts of it may already be participating in evaluation. The response is not to turn documentation into sales copy. It is to preserve the practical answer and give the evaluator an honest route from operational fact to commercial fit.

Day 137: Test Whether an AI Agent Can Finish the Buyer’s Next Step

A procurement lead gives an AI agent a bounded task: compare two suppliers against an approved requirement, confirm whether one serves the UK, and prepare a consultation request for review.

The agent finds the supplier. It reads the offer accurately. It locates the contact page and fills in the visible fields.

Then the journey breaks.

The service selector is a styled element with no clear functional name. A required consent choice appears only after another field changes. The submit control becomes active without exposing why. After activation, the page shows a brief animation but no durable confirmation, reference, or clear statement that the request was received.

The supplier was visible. The content was understandable. The next commercial step was still unusable.

This is a generalised failure-mode scenario, not a reported buyer journey or a claim that AI agents routinely submit B2B enquiries today. It exposes a newer question for CMOs, Marketing Directors, and founders: if a person delegates part of a buying task, can the website represent each action and outcome clearly enough for the agent and the person supervising it?

Day 136: Answer Volatility Is a Citation Supply Chain Signal, Not an Algorithm Bug

A marketing team runs ten identical diagnostic prompts under controlled conditions to evaluate brand recommendations for a priority buyer question.

In four runs, the engine cites your brand as the primary recommendation. In three runs, it suggests a competitor. In two runs, it presents a generic category overview with no brand citations at all. In the final run, it surfaces a niche provider.

The common reaction inside marketing departments is frustration. Someone labels the AI erratic. Someone else calls it hallucination. A third person argues that tracking answer engines is pointless because outputs change across runs.

That reaction misses an operational signal.

While language models operate probabilistically, fluctuating outputs across identical diagnostic runs are not purely random noise to be ignored. When measured systematically under controlled run conditions, answer volatility functions as diagnostic telemetry.

It can signal that neither your brand nor your competitor holds unambiguous entity authority or complete evidence coverage across the retrieved sources for that specific prompt set.

Day 135: If AI Can Answer the Question, What Is Left to Buy?

A CMO asks an answer engine how to improve the company's visibility in AI-led research.

The answer is good. It explains that the company needs clear public information about its offer, accurate category language, useful evidence, accessible pages, and buyer questions worth investigating. It warns against treating one captured answer as market truth. It suggests looking at competitors, sources, and the routes a buyer may be offered.

Ten minutes later, the CMO understands the subject better. She still cannot responsibly decide what her company should change first.

She does not know whether the problem sits in positioning, product information, third-party evidence, technical access, or the questions being measured. She cannot tell which gap affects a live commercial priority. Nobody owns implementation.

That gap is where a credible paid offer begins.

As general explanations become easier to obtain, charging for access to the explanation becomes harder to defend. The commercial value has to survive the summary. It should sit in the diagnosis made under the buyer's conditions, the priority chosen among real trade-offs, the evidence created or verified, the change delivered, and the responsibility carried when the decision has consequences.

Day 134: A GEO Workflow Should Shrink the Decision Queue

Automation can make a GEO programme slower.

The team collects more answer-led observations, classifies more questions, refreshes more dashboards, and produces more frequent summaries. Leadership receives a larger stream of movement to inspect. Each fluctuation invites a meeting. Every absence looks like a task. The monitoring works, but the decision queue keeps growing.

That is not operational maturity. It is observation volume being converted into executive demand.

For CMOs, Marketing Directors, and founders, a mature Generative Engine Optimization workflow should do the opposite. It should absorb routine collection and first-pass classification, keep ordinary movement out of the way, and surface only a predefined exception tied to a commercial choice someone is authorised to make.

The valuable output is not another visibility report. It is a smaller queue of better-bounded decisions.

Day 133: Stop Ranking GEO Tactics Without Naming the Domain

Ask a GEO supplier which tactic works best and you may get a neat leaderboard: add statistics, quote experts, cite more sources, improve fluency, use authoritative language, introduce technical terms.

The list sounds actionable. It is also missing the decision that makes any item useful.

Useful for which content class? Helping which buyer do what? Supported by which source truth? Tested against which question and metric?

A statistic can clarify a research page and distort a service page when the number does not describe the service. Technical language can help a specialist and hinder an executive reader. Fluency can improve a page, but smoother prose does not repair an unsupported claim.

For CMOs, Marketing Directors, and founders, this is a budget-control problem. A universal checklist encourages teams to apply the same edits across unlike pages, then mistake activity for learning. The better question is not, “Which GEO tactic ranks first?” It is, “Which bounded intervention deserves a test on this content class for this buyer job?”

Day 132: Your Case Studies Can Teach AI the Wrong Customer Profile

A company can publish accurate case studies and still present a misleading picture of whom it serves.

The problem is not truth inside each story. It is the shape of the visible sample.

Perhaps the company built its reputation through large enterprise transformation programmes. Those projects generated recognisable logos, approved testimonials, and polished narratives. They became the public portfolio.

The business has since developed a lighter delivery model for mid-market teams. That offer is current, commercially important, and better suited to the buyers leadership wants next. Yet the public examples still show global rollouts, multi-quarter change programmes, complex procurement, and large implementation teams.

A suitable prospect may reasonably conclude that the company is too expensive, too complex, too enterprise-focused, or simply not designed for their situation. An answer-led system encountering the same accessible examples under recorded conditions may also frame the company around the segment that dominates the visible portfolio.

That does not mean the system has discovered the company's ideal customer profile. It means the public sample made one interpretation easier than others.

For CMOs, Marketing Directors, and founders, the distinction is commercially important: the customers you have served, the examples you can publish, and the buyers you want next are three different sets.

Day 131: Do Not Benchmark GEO Only Where Competitors Already Win

A competitive benchmark can make your GEO strategy less competitive.

It happens when the research starts with a rival's public footprint. The team collects the categories the rival names, the comparisons it appears in, the questions where it is already prominent, and the criteria its pages explain best. Those inputs become the benchmark. The resulting report shows where your company trails.

Every finding may be accurate within the recorded checks. The strategic frame can still be wrong.

The benchmark has allowed the competitor to choose the questions, define the vocabulary, and set the boundaries of the contest. Your company is measured inside territory the rival has already shaped. The apparent response is to reproduce the same comparisons, answer the same questions, and compete on the same criteria.

For CMOs, Marketing Directors, and founders, this is not merely a measurement problem. It is a portfolio-allocation problem. A useful benchmark should show where parity matters, where a rival deserves a direct challenge, where buyers face an unresolved decision, and where the company should decline to spend at all.

The goal is not a longer prompt list. It is to stop competitive measurement becoming imitation.

Day 130: Give Every AI-Facing Capability a Product State

A product page can be factually correct sentence by sentence and commercially wrong when summarised.

The page says one capability is generally available. Another works only on an enterprise plan. A third is open to a small pilot group. A fourth is planned for a future release. A fifth has been paused. A sixth has been replaced, although its original launch note remains accessible.

Then the page introduces all six in the present tense: “The platform automates reporting, supports regional analytics, connects to specialist data sources, forecasts demand, manages approval workflows, and exports legacy reports.”

Every phrase came from somewhere real. The combined description still turns six different product states into one apparently current offer.

For CMOs, Marketing Directors, and founders, that is a commercial scope problem. A buyer can build an enquiry, demo request, internal brief, or procurement assumption around work that is conditional, unfinished, unavailable, or no longer sold. An answer-led system may also summarise accessible product pages, documentation, launch notes, and status language under recorded conditions. It cannot see the private roadmap meeting that explains which verb still applies.

The fix is not more promotional copy. Give every AI-facing capability a product state.

Day 129: Method Transparency Is Not Process Disclosure

A serious buyer asks how your GEO method works. The wrong answers sit at opposite ends of the same spectrum.

One company replies with a polished promise and no evaluable method. The buyer cannot tell what will be examined, how conclusions will be bounded, or where human judgement enters. Procurement sees an opaque service wrapped in confident language.

Another company responds by exposing its prompts, scoring logic, internal playbooks, security controls, unpublished experiments, and examples drawn from client delivery. It looks transparent, but much of the disclosure does nothing to improve the buying decision. It only publishes the operating recipe and creates avoidable confidentiality or security risk.

CMOs, Marketing Directors, and founders do not have to choose between those failures.

A credible GEO offer can be legible without being copied line by line. The public material should help a serious buyer understand the decision, evaluate the method boundary, and recognise the limits. The detailed execution can remain inside controlled delivery.

The commercial question is not, “Are we transparent?” It is:

Does this detail help a buyer evaluate the offer, support a bounded public claim, or merely expose execution that should remain private?

That question creates three disclosure layers: the public decision layer, the public method boundary, and the private execution layer.