{"id":1631,"date":"2026-07-23T07:40:20","date_gmt":"2026-07-23T07:40:20","guid":{"rendered":"https:\/\/maxaeo.ai\/blog\/ai-influenced-pipeline\/"},"modified":"2026-07-23T07:40:20","modified_gmt":"2026-07-23T07:40:20","slug":"ai-influenced-pipeline","status":"publish","type":"post","link":"https:\/\/maxaeo.ai\/blog\/ai-influenced-pipeline\/","title":{"rendered":"AI-Influenced Pipeline: How to Calculate It Without Double Counting"},"content":{"rendered":"

AI-influenced pipeline is the dollar value of open opportunities where an AI assistant touched the buying process before the opportunity was created \u2014 counted once per opportunity, not once per signal.<\/strong> That last clause is where most reporting falls apart. Teams stack three separate AI signals on top of the same deal and hand leadership a number roughly twice the real one.<\/p>\n

This guide gives you the definition, the three credit tiers, a tie-break table for ambiguous cases, a step-by-step calculation, the CRM fields to build it on, and a full worked example from a $6.1M quarter where the naive method produced $3.93M of AI-influenced pipeline and the deduplicated method produced $2.02M.<\/p>\n

What counts as AI-influenced pipeline?<\/h2>\n

AI-influenced pipeline is open opportunity value where at least one verifiable AI touch \u2014 a citation, a referral session, or a documented buyer statement \u2014 occurred inside the qualifying window before the opportunity record was created.<\/strong> It is a coverage metric<\/strong>, not a revenue metric. It never adds to sourced revenue; it overlaps with it.<\/p>\n

The distinction matters because CFOs read "influenced" as "caused." Once you present $3.9M of AI-influenced pipeline against $6.1M of total new pipeline, you have implicitly claimed AI search drove 64% of the quarter. You will not survive the follow-up question.<\/p>\n

The fix is structural. Instead of asking "did AI touch this deal?" for every signal you collect, you ask "which single signal has the strongest evidentiary claim on this deal?" \u2014 and you record only that one.<\/p>\n

\"Diagram<\/figure>\n

AI-influenced vs AI-sourced vs AI-attributed<\/h3>\n

These three get used interchangeably in decks and they mean different things. Fix the vocabulary before you fix the math.<\/p>\n\n\n\n\n\n\n\n
Term<\/th>\nWhat it claims<\/th>\nDenominator<\/th>\nWho should read it<\/th>\n<\/tr>\n<\/thead>\n
AI-sourced<\/strong><\/td>\nThe AI touch was the first<\/em> touch on the record that became the opportunity<\/td>\nNew pipeline created in period<\/td>\nCFO, board \u2014 this is the defensible number<\/td>\n<\/tr>\n
AI-influenced<\/strong><\/td>\nAt least one qualifying AI touch happened in the window before creation<\/td>\nNew pipeline created in period<\/td>\nCMO, demand gen \u2014 coverage, not causation<\/td>\n<\/tr>\n
AI-attributed<\/strong><\/td>\nA fractional model assigned some share of a deal to AI<\/td>\nClosed-won revenue<\/td>\nNobody, yet \u2014 the touch set is too incomplete to weight<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

Use "sourced" when someone asks what AI caused. Use "influenced" when someone asks how far AI reaches.<\/strong> If your deck only has one of the two, it is the wrong one.<\/p>\n

Why AI-influenced pipeline inflates faster than any other channel<\/h2>\n

Three things make this metric uniquely prone to over-counting, and they compound.<\/p>\n

Signals arrive from independent systems that never reconcile.<\/strong> Your AI visibility platform reports citations. GA4 reports referral sessions from chatgpt.com<\/code> and perplexity.ai<\/code>. Your form reports a self-reported answer. Each system is confident, each is measuring the same buyer, and none of them knows the others exist.<\/p>\n

AI touches are invisible more often than they are visible.<\/strong> Referrer analyses of AI-assistant traffic consistently find that a large majority of AI-originated sessions arrive with no usable referrer and land in "direct" \u2014 assistants strip or omit the referrer, and copy-pasted URLs carry nothing at all. So teams over-correct with generous inference rules, then apply those rules on top of the touches they can<\/em> see. This is the same measurement gap behind dark AI search \u2014 buyers who used an assistant but never clicked a citation<\/a>.<\/p>\n

The buyer uses AI at every stage, not just discovery.<\/strong> A buyer who found you through a Google search in March may still ask ChatGPT to compare you against two competitors in May, and again to sanity-check your security posture in July. All three touches are real. Only one of them plausibly created the opportunity.<\/p>\n

Add a fourth accelerant: AI browsers and agentic assistants fetch your pages live and strip referrer data in the process, so the same session can be logged as direct, as an AI referral, and as a self-reported ChatGPT touch depending on which system you ask.<\/p>\n

There is a structural reason the citation count and the session count never line up. A single prompt triggers query fan-out \u2014 the assistant runs a dozen or more hidden searches behind one question<\/a>, so your brand can be retrieved and shown several times inside one buyer session that produces, at most, one click. Citation volume is not session volume, and treating them as interchangeable inflates the count before you even reach the CRM.<\/p>\n

The three credit tiers, defined precisely<\/h2>\n

Every AI touch belongs to exactly one of three tiers. The tiers are ordered by evidentiary strength \u2014 strongest first \u2014 because that ordering is what makes deduplication deterministic.<\/p>\n\n\n\n\n\n\n\n
Tier<\/th>\nName<\/th>\nEvidence required<\/th>\nQualifying window<\/th>\nTypical share<\/th>\n<\/tr>\n<\/thead>\n
1<\/td>\nAI-Sourced<\/strong><\/td>\nFirst-touch session on a tracked AI referrer, or first-touch UTM from an AI-cited URL, on the record that became the opportunity<\/td>\nFirst touch only<\/td>\n8\u201312% of new pipeline<\/td>\n<\/tr>\n
2<\/td>\nAI-Assisted<\/strong><\/td>\nAny AI referral session or tracked AI citation click by any contact on the account, after first touch<\/td>\n\u226490 days before opportunity creation<\/td>\n15\u201325%<\/td>\n<\/tr>\n
3<\/td>\nAI-Self-Reported<\/strong><\/td>\nBuyer states AI use in a form field, survey, or logged discovery call note<\/td>\nStatement captured before or within 14 days of opportunity creation<\/td>\n10\u201320%<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

The share ranges are what we have observed across mid-market B2B SaaS cleanups, not a published benchmark \u2014 calibrate against your own first two quarters rather than treating them as targets.<\/p>\n

Two rules make the table work. First, tier 1 is a first-touch definition and nothing else<\/strong> \u2014 if the AI session was the third touch, it is tier 2, permanently. Second, tier 3 is a residual bucket<\/strong>: an opportunity only lands there when tiers 1 and 2 produced no evidence.<\/p>\n

Self-reported answers are the noisiest input but the only one that reaches buyers who never clicked a citation. You need the tier. You just cannot let it stack.<\/p>\n

The one-opportunity-one-tier rule<\/h2>\n

Here is the entire deduplication principle in one sentence: an opportunity is written into the highest tier for which it qualifies, and is removed from every lower tier's count.<\/strong><\/p>\n

That is it. No weighting, no fractional credit, no W-shaped model. Fractional multi-touch models are fine for comparing marketing programs against each other, but they are the wrong tool here because AI touches are not reliably observable \u2014 you cannot fractionally weight a touchpoint set you know is incomplete.<\/p>\n

The CRM build: one field, one value<\/h3>\n

The practical implementation is a single custom field on the opportunity object.<\/p>\n