Recap
- Your buyers ask ChatGPT, Perplexity, Gemini, Claude, and Google AI Overviews what to buy. Those answers name someone. Today you find out who.
- We are launching Radar: weekly measurement of the questions your buyers actually ask, across all five engines, with the receipts for every answer.
- Radar does not stop at the dashboard. For every question you lose, it drafts the page that can win it, publishes on your domain once you approve, and recommends the off-site mentions worth earning.
- Measurement without execution is a subscription to bad news. The loop is the product.
Somewhere today, a buyer you will never meet asked an AI assistant which product solves the problem you solve. The assistant answered in a paragraph. It named two or three companies, cited a handful of pages, and the buyer moved on with a shortlist. You were on it or you were not, and nothing on your analytics dashboard even flinched.
Today we are launching Radar to put you in that paragraph. It measures how the five big answer engines respond to the questions your buyers actually ask, shows you exactly where the answers come from, and then does the part no monitoring tool does: it drafts the work that changes them.
Why does AI visibility suddenly matter?
Because the shortlist moved. Buyers used to type a query, scan ten blue links, and build their own comparison. Now the assistant builds it for them. One synthesized answer, a few citations, done. When a category question gets answered without you, you did not lose a click. You lost the deal before you knew it existed. And unlike a search ranking, you cannot see it happen from inside your own tools.
What did the existing tools get wrong?
The first wave of AEO tools got measurement right and stopped there. They hand you a mention rate, a trend line, and a list of prompts you are losing, and then the work lands back on your desk: figure out what to write, write it, publish it, earn the mentions, wait, re-check. The dashboard tells you that you are invisible on a Tuesday. You are still invisible on Friday, just better informed. For a solo founder that gap between insight and action is not a workflow problem. It is the whole problem.
What does Radar actually measure?
Radar drafts a panel of prompts from your ICP: the questions a real buyer would ask when they are trying to get the job done, in the words they would actually use. You edit the panel, add prompts, and weight what matters. Then every week Radar runs the panel against ChatGPT, Perplexity, Gemini, Claude, and Google AI Overviews and records what came back.
For every answer you see whether you were mentioned, whether you were cited as a source, which of your pages carried the citation, and who showed up instead of you. Movement is tracked week over week, per engine, so you can tell a real shift from noise. Nothing is a black box: every data point traces to a real answer you can read.
How does Radar change the answers instead of just reporting them?
This is the part we built Radar for. Answer engines cite pages that answer a question directly, make specific claims, and come from sources they can reach. So for the questions you lose, Radar drafts that page: grounded in the actual engine answers it is trying to displace, aimed at the exact question, written in your voice. The draft lands in your approvals queue. You edit or approve, it publishes on a blog Radar maintains on your own domain, and the authority accrues to you.
Off your site, Radar reads where the winning answers get their sources (the communities, directories, and publications the engines trust for your category) and recommends the specific mentions worth pursuing, with outreach drafted for your approval. On-site, it checks the plumbing: whether AI crawlers can reach your pages at all, and how your classic search performance looks next to your AI visibility once you connect Search Console.
| The loop | A monitoring dashboard | Radar |
|---|---|---|
| Ask your buyers' questions weekly | Yes | Yes, across five engines |
| Show mentions, citations, competitors | Yes | Yes, with the full answers |
| Decide what would change the answer | You | Radar |
| Write and publish the page | You | Drafted, you approve, published on your domain |
| Earn the off-site mentions | You | Recommended and drafted, you approve |
| Verify the needle moved | You, manually | Next week's measurement, automatically |
Why should the measuring tool also do the work?
Because the loop only compounds when it closes. A dashboard plus a separate content workflow plus a separate outreach effort means three tools and one very busy founder gluing them together, which in practice means the glue never happens. When the same system measures the gap, drafts the fix, and re-measures, every week makes the next week smarter: it learns which pages earn citations in your category and which questions are worth fighting for. We built Radar into the same Operator that runs your outbound, because being findable when buyers ask and reaching buyers who are ready were never really separate jobs.
What should you do first?
Look at your first snapshot before you form a strategy. Most founders guess wrong about which questions they win. You may be cited on the niche comparisons and invisible on the category question, or strong on one engine and absent on the other four, and each of those calls for different work. Get measured, read the answers your buyers are reading, and let the first week of data pick the first fight.