Be the business the AI names.
Your next customer types the problem into ChatGPT, Gemini, Claude or Grok and calls one of the businesses the answer names. See whether one of them is you, question by question and town by town across the set your team writes, and which work moves the number.
Do my buyers really ask an AI who to call?
Some do, and those buyers get names, not links. A search engine returns a page of links and the buyer picks. ChatGPT, Gemini, Claude and Grok write one answer, name a handful of businesses, and the buyer calls one of those. With web search on, the apps read the live web to write it: for a local trade that means your Business Profile, the directories and the review sites. A business built on reviews and presence in its towns is exactly the kind an engine can find, or fail to find.
This page is for a business that passes the Command Center's test: a geographic service area, one new customer worth $3,000 or more, and nobody on staff whose job is marketing. The territory makes the question concrete. Your buyer names their town when they ask, and the useful answer covers their address, so whether an engine names you is a question about your trade in your towns, not about the internet in general.
Who decides which questions get asked?
Your team writes them in the second week of setup, when the baselines are taken. The set comes from what your customers actually ask: the trade, the problem, the town, and the words a person uses when they need someone today. Each question goes to the engines bare, the way a person types it. No preamble asks the engine to answer as a procurement manager or a homeowner, because a wrapper like that changes what the engine retrieves and would measure our prompt instead of your buyer's experience.
Add a question whenever you want one. Send it through the keyword request on the screen or by email; the request is logged and your team adds it to your set. Nothing on the screen writes to the set, your listing, your site or your ads account directly.
Why does one phrasing name me and another not?
Because the engines answer different phrasings from different sources. On one measured account, all four engines named the business for one phrasing about its trade in its own town. Two of four named it for another phrasing about the same trade in the same town. None named it for the next town over. The first version of that account's set asked the second phrasing nine times in ten, so it measured one lane and called it the business. A set that spans your buyer's whole vocabulary tells you which lanes you own and which you do not.
Towns behave the same way. You serve more than one, and a buyer names theirs, so the set names the towns you win most of your work in and the ones next to them, and each question is scored on its own. The screen lists every question with how many engines named you on it, won questions first, instead of one number you have to take on trust. The not-named list is your work plan.
What will I see on the screen?
One number: the share of answers in which an engine named your business, with the change since the last run and the run's date beside it. Under it, presence by engine, so you can see that you are strong in one model and absent in another, which is a different fix from being absent everywhere. Under that, the per-question table. Named or not is decided by reading the answer text for your business name. The opening of each answer stays in the run record, so your team can read who the engines named instead and bring that back to you. That is the half you can act on.
The denominator is the answers actually received. When an engine returns nothing, that blank is a measurement error and it leaves the denominator. It is never scored as a miss, because an engine that said nothing has not said it declined to name you. Each run records how many blanks there were. The set is scored at baseline during setup and re-run as the program moves, and the view carries the date of the run it shows.
What moves the number?
The program moves it; the view reports it, and the Command Center keeps the two apart. What moves the number is the same work that moves search, applied to how an engine reads a business: facts about the business that agree everywhere the engine looks, including your Business Profile, the directories and the review sites; pages that answer the buyer's literal question in plain words; structured data that says what you are and where you work; reviews and citations that agree with each other; and answer blocks on your own site written to be quoted rather than skimmed. The trade calls this work answer engine optimization, with generative engine optimization as its near neighbour. The search and answer-engine services page describes the program, and the answer-engine view says whether it worked.
The search and AI visibility program runs on all tiers, and the content engine on Launch, Growth and Command. The tier table has the numbers. Topics are checked for real search volume and for what already occupies the results before they are written, the research step cites current sources, and each piece is filed as a Google Doc in your Drive. Google's AI Overviews are a generated answer too, but they sit on a results page, so the search view measures them through Search Console, two to three days behind. Nothing is metered.
What this use case reads, in one table.
| What | Where it comes from | How fresh |
|---|---|---|
| Questions | Written in setup week two, from what buyers in your towns ask | Additions requested through your team, logged |
| Answers | ChatGPT, Gemini, Claude and Grok, each through its own API, live web search on | As of the run shown, dated on the view |
| Named or not | The answer text, read for your business name | Per run |
| Score | Answers naming you over answers received; blanks recorded and excluded | Per run, with change since the last run |
| Presence by engine | The same run, split by engine | Per run |
| Named instead | The kept opening of each answer | Per run |
| AI Overviews | Search Console, through the search view | 2 to 3 days behind, set by Google |
| Reviews and rating | Google Business Profile, direct, once our account is a manager on your listing | As of the pull stamped on the page |
The set is scored at baseline during setup and re-run as the program moves, and the view shows the date of the run you are reading.
Questions, answered.
Which AI engines are asked?
ChatGPT, Gemini, Claude and Grok, each through its own API with live web search on, so every answer is grounded in the live web the way the apps are, not in what the model memorised. Google AI Overviews are measured in the search view.
Who writes the questions?
Your team, in the second week of setup, from what buyers in your towns actually ask. The set spans the trade's phrasings and your towns on purpose.
Can I add a question later?
Yes. Send it through the keyword request on the screen or by email; the request is logged and your team adds it to your set. Nothing on the screen writes to the set directly.
What happens when an engine gives no answer?
The blank is recorded as a measurement error and left out of the denominator, never scored as a miss. Each run records how many blanks there were.
How often is the score re-run?
At baseline during setup and again as the program moves. The view carries the date of the run it shows.
Which tier includes this?
The AI visibility program is on all tiers. The pricing page lists what each tier adds beyond it.
See it running
before you decide.
The demo is the real product on a fictional company, with no form in front of it. Pricing is three published tiers. Setup on your own accounts takes two to four weeks.
Open the live demo See pricing
New here? See what the Command Center is. Prefer to write? Send us the one thing you want to know.
- Refreshed when you open itLive data on page load, never a monthly PDF
- Counted from your own formsLeads recorded server-side, compared daily with Ads and GA4
- Four answer engines, measuredChatGPT, Gemini, Claude and Grok, with a published denominator
- A review-first queue on every sendEvery draft waits in a review-first queue and every send is logged.