Is SDR Pilot Named in AI Answers?

Mention rate per engine

Share of engine runs whose answer named the brand, from 10 run tests.

Imported baseline: measured before the brand was tracked in the product, then imported with the engine version of every run. It is drawn as its own segment and never joined to the product trend line.

Google AI Overviews are fetched 3 times per prompt rather than 10, because the overview is a search result page, not a chat answer.

Mention rate over time

One point per engine per measurement date. Imported and engine change periods are marked.

Imported points are the baseline. No engine change has been recorded so far. A period is marked as one when an engine changes its model version or the control prompts move by more than 10 points, and it is then not credited to any fix.

Every prompt, every engine

The consistency label from the latest 10 run test, with the runs that named the brand.

STRONG, MODERATE, WEAK and INVISIBLE are the 10 run labels explained on the methodology page. A 0 of 10 counts only when every run finished and the engine searched the web. Control prompts get no page, post or pitch; their movement is our estimate of engine drift.

Against the competitors

Runs that named the brand versus runs that named each competitor, same prompts.

Where the brand is missing

The prompts no measured run named it for, and any answer that got it wrong.

• best LinkedIn SDR automation tool for agency owners: not named on ChatGPT, Claude, Gemini, Google AI Overviews
• LinkedIn outreach tool to run multiple client accounts for my agency: not named on ChatGPT, Claude, Gemini, Google AI Overviews
• HeyReach alternative with AI that answers LinkedIn replies: not named on ChatGPT, Claude, Gemini
• white label LinkedIn outreach automation for agencies: not named on ChatGPT, Claude, Gemini, Google AI Overviews
• AI SDR for LinkedIn I can drive from Claude Code: not named on ChatGPT, Claude, Gemini, Google AI Overviews
• LinkedIn MCP server that sends connection requests safely: not named on ChatGPT, Claude, Gemini, Google AI Overviews
• Claude Code plugin for LinkedIn outreach: not named on ChatGPT, Claude, Gemini, Google AI Overviews
• safest LinkedIn automation for client accounts, residential IP, own session: not named on ChatGPT, Claude, Google AI Overviews
• What is SDR Pilot (sdrpilot.ai)?: not named on Google AI Overviews
• SDR Pilot pricing: not named on Google AI Overviews
• SDR Pilot agency plan price: not named on Google AI Overviews
• Does SDR Pilot have a free trial? How many days?: not named on Google AI Overviews
• SDR Pilot vs HeyReach: not named on Google AI Overviews
• SDR Pilot vs Dripify: not named on Google AI Overviews
• SDR Pilot reviews: not named on Google AI Overviews

Sources the engines cite that include the brand

Pages an engine cited in an answer that also mention the brand.

The fix log

Every change we shipped for this brand, dated, with the link and commit where there is one.

No fix has been logged for this brand yet. Each fix gets a dated entry here the day it goes live, so the next 10 run test can be read against it.

How this was measured

The same engines, labels and rules every customer gets.

Day 0 is the baseline we froze on 30 September 2026, before any page was written for these prompts. It was measured outside the product with the same engine versions the product uses, then imported, so it is drawn as an imported segment.

This case starts at zero on purpose. The prompts are the questions an agency owner asks when shopping for LinkedIn outreach, and the brand was not named for most of them on day 0.

LinkedIn posts, outreach and site work run in parallel. The case claims all changes since day 0 as a set, with the fix log below as the record, and never credits one fix with a change on its own.

What we wrote down as success before the first measurement, and do not edit afterwards:

• Primary metric: the mention rate on the targeted discovery prompts, per engine, from 10 run tests.
• Success at day 90: at least 30% on at least two engines, and the targeted prompts at least 20 points above the control prompts on those same engines.
• Control prompts get no page, post or pitch. Their movement is our estimate of engine drift.
• If the controls move by more than 10 points in a period, or an engine changes its model, that period is marked as an engine change and not credited to any fix.
• Day 30 is a checkpoint, not a gate: any result is reported as it is, zero as zero.

Each engine is asked through its API with web search or grounding switched on, the way a buyer's question is answered today. A run counts as a mention only when the answer names the brand itself, not an echo of the question and not a different company with a similar name. The engine version shown is the model id the engine reported for that run.

What the measurement on this page cost us in engine fees: $0.22.