Skip to content

Generative Engine Optimization

Day 178: The Supplier Exit Rehearsal

At the next automation renewal, reserve a session for leaving.

Not a cancellation negotiation. A rehearsal in which someone other than the incumbent supplier takes over a small, working part of the business process. The commercial question is whether enquiries can keep moving when the supplier relationship ends.

For Zero-Shot Agency, this is a proposed acceptance requirement, not a handover we have delivered. The exercise below uses a hypothetical lead-routing workflow and synthetic records. No migration, response time or revenue outcome has been measured.

Day 177: An Enquiry Is Not a Customer Dossier

An optional home-address field still needs a reason to exist—even if an assistant could fill it effortlessly.

Imagine a B2B advisory enquiry whose only job is to route a request and arrange contact by email. A home address does neither. I would remove that request, not make it optional or save it for the next conversation. The reply email stays: without it, the firm cannot respond.

For Day 177, my proposed ZSA operating rule is to judge each requested detail by what it enables, not how easy it is to supply. The walkthrough below concerns that fictional enquiry. It is not a deployed form, client practice or measured conversion experiment.

Day 176: Three Brands Are Not Three Independent Suppliers

The buyer wants a second supplier outside the group it already depends on. Another brand from that group will not meet the requirement, however different its offer looks.

That does not make the second brand a bad choice. It makes it a different kind of choice: another service, not another controlling owner.

For Day 176, I am separating those decisions in ZSA's proposed commercial reading of an answer-led shortlist. The example is fictional, not a captured AI response, client engagement or finding about how often engines omit ownership.

Day 175: Budget for the Buying Season, Not a Flat Year

A buying guide delivered after the shortlist closes can be useful and still miss the sale it was funded to support.

An annual content allowance does not prevent that mistake. The team can deliver every promised article while putting the preparation after the decision.

For a CMO funding GEO, I would start with the customer's buying window, then work backwards to the research and material that need to be ready. That means buying different work at different points in the year—not simply ordering the same monthly output more urgently when demand arrives.

The calendar below is a proposed planning approach for Zero-Shot Agency, not a tested programme or an observed seasonal campaign.

Day 174: Give Each Language Edition Its Own Address

A reader sends a colleague the French guide. The colleague opens the link and gets English.

The translation exists. The link simply did not carry the reader's choice with it.

That is the publishing problem I would put ahead of a language-selector demonstration. A marketing team funding translated content needs more than a screen that changes language. It needs editions people can open directly, pass to someone else and return to later.

The reading path below is hypothetical, not a ZSA implementation or an observed visitor journey. It sketches one English–French guide and the difference between selecting a language for a session and publishing a reachable edition.

Day 173: Make Custom Automation Earn Its Place

“Before we price the agent, what can the platform we already use do?”

That is the opening question I would bring to an automation discussion at Zero-Shot Agency. A request to stop losing enquiries is a business problem. It is not yet a reason to buy a separate application, model connection and orchestration service.

Here is a proposed conversation between a marketing director and an implementation lead. The company and dialogue are invented; the Airtable capabilities cited are documented, not tested here. The decision is whether to configure an existing platform or introduce custom software—not which approach sounds more advanced.

Day 172: Buy Research You Can Use Again

The research budget pays for a report. The distribution agreement may decide whether your team can turn it into anything else.

Before buying a publisher's audience, ask what remains available for your own website, sales presentations and future partnerships. A campaign can end while restrictions on the asset continue.

At Zero-Shot Agency, this is the purchasing position I would take, not a completed licensing engagement. The redline below annotates one invented proposal. It sets out commercial questions for negotiation, not legal terms to copy. The legal background is UK guidance; obtain advice for the actual works, parties and jurisdictions involved.

Day 171: Cancelling a Booking Does Not Rewind the Business

The appointment is cancelled. The preparation has already been done. The confirmation has already been read.

An Undo button cannot make all three disappear.

For founders and marketing leaders commissioning agent-assisted booking, recovery belongs in the commercial budget. A successful booking creates commitments; reversing it can require new work, leave costs behind and finish somewhere other than the original starting point.

This is not the retry problem. Retrying asks the service to complete the same intended action without duplicating it. Cancellation asks for a different outcome after that action succeeded.

Day 170: Compare the Item, Not the Product Family

The cheapest price and the largest capacity can belong to the same product family without belonging to the same product.

Put both in one comparison row and you have created something the buyer cannot order.

For a marketing director approving a competitor comparison, the first question is therefore not “Who wins?” It is “What exactly occupies each row?” A brand, a family and an individual variant answer different questions. Treating them as interchangeable can make the price judgement meaningless before anyone starts debating features.

Here is a procurement redline: an explicitly fictional buying comparison, not a captured AI answer, live catalogue or ZSA client result.

Day 169: More Prompts Do Not Create More Treated Cases

A team rewrites one product guide, then asks an answer engine about it repeatedly. The report grows with every capture. The number of separately treated guides stays at one.

That distinction matters when a CMO asks whether to fund the same rewrite across a catalogue. More observations of one intervention are not more independently assigned cases of that intervention.

For Day 169, the design choice is where to spend an evaluation budget: deeper observation of one changed unit, or a comparison across separately assigned units. The two sketches below are fictional methodological planning—not an observed test, client case or validated ZSA method.