Turn AI visits into pipeline

What does it cost us when AI recommends someone else?

We take the buying questions where AI names someone else and run them through your own numbers. You get a yearly range, every input behind it, and the questions to fix first.

Revenue at Risk section showing lost buying questions count, estimated annual revenue range, input list tagged measured/entered/benchmark, and table of lost prompts with AI recommendations and fix links
One view: how many questions you lose, what it costs, and which to fix first.
  1. 1How many buying questions you're losing
  2. 2The yearly estimate, shown as a range
  3. 3Each lost question, who AI named, and a link to fix it

What you do with it

  • Put a number on the gap when you ask for budget
  • Fix the lost questions with the most searches behind them first
  • Change your deal value or close rate and watch the estimate move

What it can't do

  • It's an estimate, not a forecast. Nobody knows how many buyers would have picked you.
  • It shows nothing until you enter your deal value and close rate. We won't guess them.
  • One step uses our starting assumption until your own traffic can replace it. It's labelled.
  • It counts buying questions. Early research questions are left out.

How revenue at risk is calculated

The estimate is five steps, each shown, so anyone can point at the step they disagree with.

First, the yearly searches behind the buying questions where AI names someone else. Each is weighted by how often you actually lose it. Second, the visits that demand would send you if AI named you. Third, your visit-to-lead rate. Fourth, your lead-to-close rate. Fifth, your average deal value.

Buying questions are pricing questions, head-to-head comparisons, and "best tool for" questions. A question counts as lost after we've asked it more than once. A question you lose half the time is priced at half.

A range, not one number

We can't know how many of those buyers would have chosen you. So the same steps run three times: a low case, a likely case and a high case. Take the likely case into a planning meeting.

Every input is labelled. Measured means it came from your connected analytics and tracked questions. You entered means it came from your setup. Benchmark means our starting assumption, used for one step until your traffic can set it.

Kept apart from what AI already earned you

AI revenue attribution measures revenue that arrived. Revenue at risk estimates revenue that didn't. One is measured and one is estimated, so we never add them together.

Frequently Asked Questions

Questions about revenue at risk

Your average deal value and your lead-to-close rate. Also your visit-to-lead rate, if we can't measure it from your traffic.

No, it's an estimate shown as a range. We can't know how many buyers would have chosen you, so we show a low, likely and high case.

We ask each question several times, because the same question can name different companies each time. A question asked once is left out.

Pricing questions, head-to-head comparisons and "best tool for" questions. These are what people ask when they're close to choosing.

Find out what the gap is costing you

Start with a free audit of where AI recommends you today, and where it names someone else.

Get a free audit

Free AI visibility audit

Find out what ChatGPT tells your buyers about you.

Where you're named, what AI gets wrong, and the first three things to fix. Emailed within two hours.

  • Within 2 hours
  • No credit card needed
  • Free
Prefer to talk? Book a 30-minute call
  1. Your site
  2. Your market

We'll send your report to this address