Jobs to be done · Prove · Ecom

How to prove AI search ROI to leadership.

Your CEO asks: "Why are we paying for another SEO tool?" You need a two-slide story — how many AI answers you won, which products moved, what revenue that implies — without inventing a single number. Narrative without numbers loses the budget conversation; invented numbers lose it worse.

Quick answer

Use the before/after/attribution framework: capture a dated baseline, track per-SKU lift across engines, join to Shopify session data, and export the two-slide summary with every number labeled attributable, contributing, or illustrative. For the forward-looking frame, the free ROI calculator models revenue at risk from your own inputs.

The slow way: three data sources and a prayer

The manual version stitches three disconnected sources. Shopify analytics for traffic by landing page. A handful of ChatGPT and Perplexity screenshots where the brand appears. A paragraph in the deck arguing that AI is driving traffic. Then someone asks "how much," and you have two bad options: invent a percentage (the deck dies under scrutiny) or argue that AI attribution is impossible because chat referrers are scrubbed (true, but it sounds like excuse-making).

The structural problem: every AI-visibility story needs two anchors — a visibility metric (citations) and a commercial metric (sessions, revenue) — joined at the same grain. Brand-level mentions joined to site-level traffic proves nothing; the correlation has to live at the SKU, where a specific product's citations rose and that product's sessions rose with them. Without per-SKU joins, the narrative stays impressionistic no matter how many screenshots it carries.


The eCommerce Insights way

  1. Establish the dated baseline. The moment optimization begins: catalog scores, per-SKU citation counts, Shopify session volumes by landing page. Recorded automatically; export the dated PDF so the "before" is on the record.
  2. Track per-SKU lift. For each optimized SKU, citation-count deltas across ChatGPT, Perplexity, Google AI Overviews, Gemini, Claude, and Copilot, plotted per SKU. The measurement methodology behind this is in measuring AI visibility: what actually matters.
  3. Join visibility to sessions. The Shopify integration pairs each SKU's visibility delta with its session and revenue delta. Where both rose in the same window, the lift is flagged attributable. This is the closest honest proxy — perfect attribution does not exist, and the report says so.
  4. Convert to a labeled range. Session deltas times each SKU's historical session-to-revenue rate, reported as a range: "$35K–$85K this quarter" is credible; "$62,341" is not. Labels: attributable where correlation is tight, contributing where causation is murkier, illustrative for the model-based pieces. Never "certain."
  5. Build the two slides. Slide one: score before/after, cited-SKU count before/after, the revenue range. Slide two: three to five named SKUs — what changed on each PDP, what moved. Branded PDF export. A framing that reads well in a boardroom: "Cited SKUs grew from 12 to 34 this quarter; based on session deltas on those SKUs we attribute $35K–$85K of revenue to AI visibility lift. AI attribution science is still developing; we refine as the data matures."

The spend side of the equation is public: plans run $99–$349/mo (pricing), which makes even the conservative end of a defensible range an easy multiple. The complementary GA4 work — making AI referrals visible at all — is its own job: track AI referral traffic in GA4.

What "good" looks like

Every number anchored to a dated baselineyes
Revenue reported as a labeled range, not a pointalways
Named SKU stories on slide two3–5
Reporting rhythm (the real ROI shows over four quarters)quarterly

The counterintuitive rule: honest hedging strengthens the deck. "Attributable vs. contributing vs. illustrative" labeling reads as rigor, and leadership funds rigor. The confident single number gets one meeting; the cautious range gets a standing line item.

Ask AI about this job

Have your favorite AI engine apply this walkthrough to your numbers.

Frequently asked questions

How do I attribute revenue to AI search when referrers are scrubbed?
You don't get perfect attribution — chat assistants pass cleaned or empty referrers — so the honest method is correlation at SKU grain: where a specific SKU's AI visibility rose and its direct/unattributed sessions rose in the same window, the lift is flagged attributable; weaker correlations are labeled contributing. Leadership trusts the cautious number more than the confident one.
What numbers go in the board deck?
Three. Score movement ("58 to 71 this quarter"), cited-SKU count ("12 to 34 SKUs appearing in at least one AI answer weekly"), and an attributable revenue range ("$35K–$85K this quarter, labeled as a range"). One slide. The second slide is the SKU-level story — named products, named changes, named lift.
What if I have no baseline from before we started?
Start the baseline this week and build forward — a quarter of real data beats a reconstructed history. A retroactive estimate based on your schema and content state at a prior date is possible but is an estimate, and the deck should say so. The clean path: baseline now, story next quarter.
How long before there's a credible story?
One quarter. Weeks one to four are baseline plus early fixes; five to eight is where citation lift appears; nine to twelve is where the revenue join stabilizes. Showing ROI at week two reads as marketing and burns credibility you'll want later.
What does the ROI calculator add to this?
The forward-looking half: a revenue-at-risk model from your GMV, AOV, catalog size, and an AI-traffic assumption — clearly labeled illustrative until connected to store data. The calculator frames the budget conversation before results exist; the before/after framework replaces it as real data accumulates.

Baseline today. Two slides next quarter.

Per-SKU before/after with honest labels. 14-day trial, no credit card.