Brand audits, competitive narrative studies, customer sentiment refreshes, the “how is the market actually framing us” project, the messaging validation work that used to precede every launch. Every one of those was historically either a $100-300k engagement with an outside research firm, or a six-to-eight-week internal sprint that produced a static deck most of the org never opened twice. Both took months, and both were already stale the day they shipped.

Now you build a private market intelligence app yourself, in a weekend, for around thirty dollars in API spend. The app scrapes every public mention of your company and your competitors across Reddit, G2, Capterra, TrustRadius, podcast transcripts, LinkedIn, Hacker News, comparison content, and operator newsletters. It clusters what it pulls into a structured narrative: positioning gaps, messaging opportunities, competitive scoring across the dimensions you actually care about, sentiment heatmaps by theme, and the verbatim quotes that hold up when someone pushes back on a finding. You ship it as a private, password-gated URL the team can scroll through and re-run on demand.

The tool is Lovable, the artifact is yours, and the work that used to take months and burn cash now ships in a weekend for about the price of dinner.

I built one for Clay (the GTM data orchestration platform) as the worked example for this piece. I don’t work with Clay. I picked them because they had the right conditions for a useful teardown: loud sentiment in both directions, a crowded and rapidly evolving competitive set, and an unusually deep public data trail across Reddit, G2, operator podcasts, and LinkedIn ambient commentary. If Vibe Market Research works for Clay, it works for anything.

You can play with the live Clay Narrative OS at before reading the rest. What follows is a walkthrough of the artifact, the full prompt I used to build it, and instructions for adapting that prompt to your own company by the end of this weekend.

How the practice actually works

The signal was never the bottleneck. It’s been sitting in plain sight for years on Reddit, on G2 and TrustRadius, in every podcast transcript your buyers actually listen to. The bottleneck has always been synthesis, the analyst hours required to pull thousands of public mentions into a coherent narrative a CMO can act on. That layer is what a build in Lovable now eats.

If anything, the work matters more than it used to because category lines are being redrawn faster than any annual planning cycle can track. The difference is that one person with the right prompt can now produce something better than what a research firm would have shipped, in a weekend for thirty dollars instead of two months for sixty thousand.

Brand and PMM teams get something specific out of this practice that other functions don’t.

First, the deliverable is alive. It’s a URL, not a PDF, and you re-run the synthesis whenever you want. The narrative refreshes with the market because there is no static deck to update.

Second, the output is grounded in verbatim evidence. Every claim sits next to a sentence someone actually wrote on a public forum, with attribution and a source link. That changes how the conversation goes. You stop arguing positioning from gut, and senior stakeholders engage differently when the evidence is on the screen instead of in your head.

Third, you own the artifact. You’re not renting it from a firm, waiting on a contract, or hoping the renewal gets approved next year. It belongs to your team forever, and it gets sharper every time you run it.

The Clay Narrative OS

I picked Clay as the worked example because of the public data depth I mentioned above, and because it’s a company most PMM and Brand operators reading this will already have an opinion on. Easier to test the artifact against your own gut when the subject is familiar.

The Clay Narrative OS scraped 1,247 public sources, pulled 564 verbatim quotes, scored eight competitors across five dimensions, mapped sentiment to nine themes, and surfaced three positioning gaps that were not on my radar going into the build. Total build time was about 3 hours of actual work spread across a weekend, with around thirty dollars in API spend.

The OS has five screens, and each one does a specific job in the analysis. The structure matters as much as the data, because the screens compound. The Briefing forces the synthesis to commit to a thesis. The Market Moment grounds that thesis in category context. The Competitive Landscape shows where the subject sits relative to alternatives. The Customer Voice provides the evidence layer. The Strategic Implications convert all of it into the moves you can actually run on Monday morning.

The Briefing

What this section is for: to force the synthesis to commit to three claims the rest of the OS has to support. If your research doesn’t end in a clear point of view, you don’t have research, you have a literature review.

The Briefing opens with three headline findings the synthesis surfaced. These were not findings I went looking for. I wrote the prompt, ran the synthesis, and read what came out. The OS pulled these directly from the clustered evidence:

1. Clay is bought as a system, not a database. Buyers frame the purchase as enrichment-plus-orchestration. Apollo is bought as a database. That distinction is the entire competitive wedge.

2. The onboarding tax is real and underdiscussed. It’s the single most consistent negative theme in the dataset. Median time-to-full-ROI mentioned in the reviews is around six weeks.

3. Community advocacy is the moat competitors cannot copy. The Clay Slack, the template library, and the certification program get referenced in customer language more often than the product itself.

The 4-up stat row at the top (sources analyzed, quotes surfaced, net sentiment score, top competitor by share of voice) gives the reader a one-glance sense of the dataset’s depth before they read a single finding. The “Run new synthesis” button at the bottom is the architectural point of the whole OS, because the artifact is alive instead of frozen.

The Market Moment

What this section is for: to set the category context so the subject’s positioning gets judged against the right backdrop. Most positioning work fails because it analyzes the company in isolation. The Market Moment fixes that by forcing the analysis to name the forces reshaping the category before it touches the company itself.

Four sourced stats on the GTM data category establish that the ground is moving. Three forces reshaping the category (deliverability collapse, signal-based selling becoming table stakes, RevOps shifting from cost center to revenue lever) name the actual movement underneath the noise. The synthesized pull-quote that closes the screen is “Clay is not winning the data war. It is changing what the war is about.” That sentence did not come from me. The clustering surfaced it, and it does more work in one line than most positioning decks do in twenty pages.

The Competitive Landscape

What this section is for: to remove the option of arguing positioning in a vacuum. Buyers compare, boards compare, investors compare. The Competitive Landscape forces the analysis to do the same in three different formats so no one in the room can claim the comparison wasn’t structured.

The 2D positioning map plots Clay against Apollo, Smartlead, Instantly, Clearbit, ZoomInfo, Common Room, Outreach, and Salesloft. Two axes (point tool to platform, self-serve to enterprise) define the category space, and the dots are sized by mention volume. The scoring table runs across five dimensions (data breadth, workflow power, ease of use, price perception, community advocacy) and uses synthesized signal weights from the dataset. The three head-to-head comparison cards (Clay vs Apollo, Clay vs Smartlead, Clay vs ZoomInfo) hold the verbatim quotes that justify each claim, so a skeptical reader can drop into the evidence from the map and the table on demand.

The Customer Voice

What this section is for: to put the evidence layer on the screen. This is what turns the OS from “interesting deck” into “irrefutable artifact.” Every claim earlier in the OS is anchored to quotes that live here, with attribution and source links. If a stakeholder challenges a finding, you scroll here. Most board rooms have never seen a positioning argument that holds up under that pressure.

The sentiment heatmap maps nine themes (pricing, onboarding, data quality, integrations, workflow power, support, ROI, ease of use, scale) against five sentiment buckets, with every cell sourced. Twelve verbatim quotes carousel across the top with full attribution. Below them sit nine theme deep-dives, each with three example quotes and a sentiment ratio bar showing the positive-to-negative split. The reason the heatmap is the most screenshot-worthy artifact of the entire OS is that it compresses thousands of public mentions into a single visual a CMO can scan in ten seconds.

The Strategic Implications

What this section is for: to convert analysis into moves. Without this screen the OS is interesting but inert. With it, you walk out of the read with a brief for what your team should do next quarter.

Three positioning gaps name where the subject is under-credited in the market relative to what the data shows. Three messaging opportunities pull verbatim phrases buyers already use that the subject isn’t echoing back. Three competitive plays prescribe specific moves against the three main competitors, each with a two-sentence rationale and a supporting quote. The closing pull-quote is “ZoomInfo is the incumbent we are paid to replace. Clay is the tool we use to replace it. The narrative is already written.” Someone in the dataset said something close to that, and the clustering pulled it through as the closing argument. That single line is the entire competitive thesis, surfaced not written.

The architecture under the design

Perplexity scrapes the sources in parallel, one call per source type, returning verbatim quotes with attribution. Claude synthesizes everything into a JSON payload that follows a schema defined in the prompt. Supabase persists the results and runs the API calls through edge functions so the keys never touch the client. End-to-end run takes under two minutes once it’s wired up.

I’m not a developer and haven’t written code in over a decade. Lovable scaffolded the entire app from one initial prompt and a few rounds of iteration after that.

Where this earns its keep

This isn’t a one-time party trick. It’s a new tool slot in how Brand and PMM teams operate, and here’s where it pays for itself in the first week.

Board decks. When the board asks where the moat is, you don’t say “community advocacy.” You show them the heatmap, quote the buyer who said it, and hand them the live URL. The conversation changes because the evidence is no longer abstract. Same dynamic for any board question about competitive position, pricing perception, category framing, or churn drivers. The room engages differently when the evidence is on the screen.

Internal presentations. Sales kickoffs, all-hands meetings, QBRs, leadership offsites. The artifact lands anywhere the company gathers and needs a shared view of the market. Project the top twelve verbatim quotes on the wall and the whole company starts speaking buyer language instead of internal language. I’ve watched CROs change how they open the next QBR after sitting with one of these for ten minutes. It reframes what the team thinks it’s actually selling.

Roadmaps. The onboarding tax finding the OS surfaced for Clay didn’t come from anyone’s gut. It came from forty reviews saying the same thing. Take a finding like that to product and the prioritization conversation changes shape in real time, because product can see the volume of the complaint instead of hearing it once secondhand from sales.

Interview prep. This is the one I’d quietly tell anyone going after a senior PMM or CMO role. I built a version of this OS for a CMO interview process I went through earlier this year at a B2B SaaS company. I walked into the final round with a synthesized narrative on the company, its competitors, and the exact language its buyers were using in the wild. The interviewers asked me how I built it, I told them, and I sent them the URL after the conversation. It was the most prepared I have ever been for a senior interview. I got the offer but ended up walking from it for unrelated reasons, but the artifact changed the conversation while I was in it.

Messaging tests. Before you ship new positioning, run the OS. Does the market already use the language you’re about to claim? If yes, you’re echoing back, which is what you want. If no, you have an uphill battle ahead of you, and you should know that before the campaign budget is committed.

Important: The displacement window

Most competitive displacement runs on stale inputs. The win/loss program reports once a quarter. The battlecard gets updated when someone remembers to update it. By the time the deck reflects a competitor’s weakness, the weakness is three months old and the competitor has had a full quarter to patch the narrative around it.

The OS collapses that delay to days. You re-run the synthesis on a schedule. When a competitor stumbles, the signal shows up in the heatmap before it shows up anywhere else you’d look. A price increase, a botched release, a support backlog, a security incident, a founder departure the forums are picking apart. Each of those opens a window where the competitor’s own customers are saying out loud, in public, why they’re unhappy and what they’d switch for. The window stays open for a few weeks and then it closes, because the competitor fixes the issue or the thread cools and the buyers move on.

Catching the window the week it opens is the entire game.

Here is the sequence I’d run. Re-run the synthesis weekly. Watch the negative cells in the heatmap for a competitor you’re targeting. When a cell spikes, drop into the quotes and confirm it holds across two runs, so you’re acting on a real shift and not one loud thread. Pull the verbatim phrases buyers are using. Then move on three fronts while the window is open. Hand sales the exact language so the talk track lands the day a prospect is already feeling the pain. Stand up a comparison page that mirrors the complaint back in the buyer’s words instead of your marketing’s words. Point outbound at the segment complaining loudest, timed near the competitor’s renewal window when switching cost is lowest.

Take ZoomInfo, since it’s the incumbent in the Clay set. The recurring complaint in the data is contract lock-in and price at renewal. That part is not a secret. What the OS gives you is the moment the complaint volume spikes, the phrases buyers use when it does, and the segments where it’s loudest right now. You’re not running a generic “switch from ZoomInfo” campaign that’s been live for a year. You’re running the play that matches what their customers are upset about this week, in the words they’re using this week.

The competitor cannot respond at your speed. Their win/loss program still reports quarterly. You’re on a weekly clock against an opponent on a quarterly one. That gap is the displacement.

The honest limits

A few things to know before you put one of these in front of an executive.

It’s directional, not statistically valid. Public data has selection bias. Loud users post more than satisfied users, and churned customers leave louder reviews than active ones. You’re seeing a slice of the truth, not the whole truth, and you should say so when you present it.

You still need real customer conversations. The OS surfaces patterns. Conversations tell you what the patterns mean and which patterns matter most for the decision in front of you. The OS is upstream of the customer interview, not a replacement for it.

The competitive scoring is synthesized signal weights, not benchmarks. Treat the numbers as sentiment proxies. Don’t put a synthesized 84/100 in front of a board and call it a Gartner score.

Real-time means real noise. If you re-run the synthesis on a day when one negative thread is going viral, the sentiment heatmap will tilt with it. Run it weekly, not daily, and look at trend rather than a single snapshot.

Public data is not all data. Your CRM, your call recordings, your closed-lost notes, your renewal survey responses are all richer than anything on Reddit. Wiring those in is the next move and the architecture above supports it. That’s a follow-up post.

The point

The research firm just got Napsterized, and the eight-week internal sprint went with it. What replaced both is a one-person operating practice that costs almost nothing, ships in days, and refreshes whenever you want.

The work Brand and PMM exists to do hasn’t gotten easier. The cost and time required to do it well has collapsed. The teams that internalize this first will buy themselves two or three quarters of compounding advantage before their competitors notice the playbook changed. The rest will keep paying firms forty to a hundred thousand dollars for a PDF that goes stale before it ships.

Play with the Clay Narrative OS at if you haven’t already. The full prompt is below, versioning it for your own company is about an hour of editing, and the math is in your favor on every dimension that matters.

Build one this week. Send me what your OS surfaced about your category that you didn’t already know. I read every reply.

The full prompt I used

This is the part most posts about AI tools never give you. Here is the full prompt I pasted into Lovable as the first message to scaffold the Clay Narrative OS. It defines the design system, the data model, the five screens, the API integrations, the synthesis logic, the voice rules, and the lockdown. Adapt the four sections I’ll call out below the prompt and it becomes yours.

Build me a private, single-operator market intelligence app called Clay Narrative OS. It is a synthesized competitive and customer-sentiment narrative for Clay (clay.com, the GTM data orchestration and workflow automation platform), generated by analyzing thousands of public mentions across Reddit, G2, Capterra, podcast transcripts, LinkedIn, Hacker News, newsletters, and comparison content. This is an internal research artifact, not a marketing site. It must never be indexed by search engines and should sit behind a lightweight passcode gate.

THE FEELING I WANT

Premium operator dashboard. Dark, editorial, calm, expensive. The reference points are a Bloomberg terminal crossed with a modern research firm’s interior dashboard: near-black canvas, one confident electric chartreuse accent, sharp typographic hierarchy, lots of negative space, subtle depth, smooth motion. It should feel like a tool a CMO is proud to project on a boardroom screen. Avoid the default AI-generated look: no purple gradients, no generic rounded-everything cards, no emoji in the UI, no clip-art icons, no bubbly drop shadows. Specifically no Clay-style purple anywhere. This is our analysis of Clay, not Clay’s brand.

DESIGN SYSTEM (use these exact tokens)

Colors

- Canvas: #0A0B0D

- Surface 1: #131418

- Surface 2: #1B1D22

- Border: #2A2D34

- Text primary: #F4F5F7

- Text secondary: #9CA0AB

- Text tertiary: #5E626D

- Accent: #C8FF3D (electric chartreuse, use sparingly)

- Accent dim: #8DB52A

- Positive sentiment: #6BE3A0 (mint)

- Negative sentiment: #FF6F5E (coral)

- Neutral / mixed: #FFD45E (warm amber)

Typography

- Display: Space Grotesk, weights 500 / 600 / 700

- Body: Inter, weights 400 / 500 / 600

- Mono (numbers, citations, timestamps): JetBrains Mono, weights 400 / 500

- Type scale: 12, 14, 16, 18, 24, 32, 48, 64

Layout

- Max content width 1280px, centered

- 96px between top-level sections

- Cards have 1px solid border, no drop shadow, optional 2px accent rail on left for emphasis

- Radius: 6px on cards, 4px on inputs, 999px on pills

Motion

- All transitions 200ms cubic-bezier(0.2, 0.8, 0.2, 1)

- Fade-in-up on scroll via Framer Motion, 24px translate

- No bouncy spring animations

- Page transitions: 400ms cross-fade with slight slide

- Number counters animate up on scroll for stat blocks

No-go list

- No emoji in the UI

- No clip-art icons (Lucide outline icons only, 1.5 stroke)

- No drop shadows (use borders for depth)

- No purple or violet anywhere

- No gradients except one optional subtle radial behind the hero

- No fully rounded cards, no playful microinteractions

TECH STACK

- Vite + React + TypeScript

- Tailwind for utility styling

- Framer Motion for transitions

- Supabase for persistence and edge functions

- Lucide React for icons

- Recharts for data viz

API INTEGRATIONS

Prompt me for three API keys before any live scraping:

1. Perplexity API (primary intelligence workhorse)

2. Anthropic API (Claude for synthesis, model claude-sonnet-4-6)

3. Optional Firecrawl or Apify (only if direct scraping of G2 pages is required)

Every API call must be proxied through Supabase edge functions. Keys never appear in client code. If a call fails, surface a clean inline error inside the relevant card and do not break the page.

DATA SOURCES TO SCRAPE, IN PRIORITY ORDER

1. Reddit via Perplexity queries: r/sales, r/SaaSMarketing, r/marketing, r/SaaS, r/B2BSaaS, r/RevOps, r/coldemail, r/Entrepreneur, r/Startups

2. G2 reviews and comparison pages

3. Capterra and TrustRadius reviews

4. Podcast transcripts: 20VC, Lenny’s Podcast, GTMnow, Topline, SaaStr Podcast, RevOps Co-op, The Marketing Millennials

5. LinkedIn ambient public discussion (public posts and threads only, no private data)

6. Hacker News threads

7. Operator newsletters: Lenny’s Newsletter, Stacked Marketer, Demand Curve, Pavilion, GTM Partners

8. Comparison content (vs pages, alternative listicles, head-to-head reviews)

THE SUBJECT AND COMPETITIVE SET

Subject: Clay (clay.com). GTM data orchestration and workflow automation. Lets revenue teams enrich, dedupe, and orchestrate outbound across hundreds of data sources.

Competitors:

- Apollo.io (volume and coverage)

- Smartlead (outbound execution and deliverability)

- Instantly (deliverability and volume)

- Clearbit, now part of HubSpot (enrichment heritage)

- ZoomInfo (enterprise data incumbent)

- Common Room (community and signals)

- Outreach and Salesloft (sequencing platforms with enrichment bolted on)

- LeadMagic, Findymail, Datagma (point tools at the data layer)

DATA MODEL

type Source = {

id: string

type: ‘reddit’ | ‘g2’ | ‘capterra’ | ‘trustradius’ | ‘podcast’ | ‘linkedin’ | ‘hn’ | ‘newsletter’ | ‘comparison’

url: string

author: string | null

date: string

raw_text: string

retrieved_at: string

}

type Quote = {

id: string

source_id: string

text: string

sentiment: ‘very_negative’ | ‘negative’ | ‘mixed’ | ‘positive’ | ‘very_positive’

themes: string[]

competitor_mentioned: string | null

attribution: ‘verified’ | ‘synthesized’

}

type CompetitorScore = {

competitor: string

data_breadth: number

workflow_power: number

ease_of_use: number

price_perception: number

community_advocacy: number

overall: number

source_quote_ids: string[]

}

type Synthesis = {

id: string

run_at: string

source_count: number

quote_count: number

payload: object

}

BUILD THESE FIVE SCREENS, IN THIS ORDER

1. The Briefing (landing and command center)

Eyebrow at top: CLAY NARRATIVE OS in accent chartreuse, mono, 12px, uppercase. Below it, headline in Space Grotesk 600 at 64px: “What the market is actually saying about Clay.” Subhead at 18px in text-secondary: “Synthesized from [N] public sources across Reddit, G2, podcasts, and community forums. Last run [timestamp].”

Below the hero, a 4-up stat row in JetBrains Mono:

- Sources analyzed

- Quotes surfaced

- Net sentiment score (positive minus negative, out of 100)

- Top competitor by share of voice

Below the stat row, a “What we found” section with three large stacked cards. Each card carries a step number (01, 02, 03), a one-line claim in display 32px, a two-sentence elaboration, and one verbatim supporting quote with attribution chip. The first card carries an accent rail.

At the bottom, a primary button “Run new synthesis” and a secondary “View raw sources.” Show last run timestamp.

2. The Market Moment

Three modules:

- Why this category matters now: a 2x2 stat grid with sourced numbers about the category. Each stat carries a source citation in mono 12px.

- The three forces reshaping the category: three vertical cards in a row, each with a force name, two-sentence explanation, and one-line implication in accent color.

- Where the subject sits: a single paragraph synthesis with one pull-quote in accent color, large.

3. The Competitive Landscape

Three modules:

- Module A: A 2D scatter plot in Recharts. X axis: “Point tool” to “Platform.” Y axis: “Self-serve” to “Enterprise.” Each competitor is a dot sized by mention volume. The subject is highlighted in accent chartreuse with a label. On hover, show competitor name, total mentions, net sentiment.

- Module B: A scoring table with rows per competitor and columns for the five dimensions plus an overall. Use thin horizontal bars in chartreuse with the score number in mono. Subject row has an accent rail. Footnote: “Scores synthesized from clustered signal weights across ingested sources. Directional, not benchmarked.”

- Module C: Three side-by-side comparison cards: subject vs main competitor 1, subject vs main competitor 2, subject vs main competitor 3. Each card has two text logos, three rows (”Where subject wins,” “Where the competitor wins,” “Where they tie”), and one representative verbatim quote underneath.

4. The Customer Voice

Three modules:

- Sentiment heatmap: rows are themes (pricing, onboarding, data quality, integrations, workflow power, support, ROI, ease of use, scale), columns are sentiment buckets. Each cell shows a count in mono, shaded by intensity using a coral-to-chartreuse gradient. Cells are clickable, opening a modal with every quote in that cell.

- Top quotes carousel: a horizontally scrolling row of quote cards with quote in display 24px, attribution beneath (source type, author handle, date, link icon), sentiment pill, theme tags. 12 quotes default with “Show all” expand.

- Theme breakdown: vertical stack of theme sections. Each has theme name, one-line summary, three example verbatim quotes, and a horizontal sentiment ratio bar.

Every quote shows its source as a chip beneath it. Verified verbatim quotes get a small chartreuse checkmark. Synthesized quotes get a SYNTHESIZED FROM CLUSTERED LANGUAGE eyebrow tag and no checkmark. Never invent attributions.

5. Strategic Implications

- Three positioning gaps: each with a name, description, and one-line “what to do about it.”

- Three messaging opportunities: phrases buyers actually use, pulled verbatim from the dataset.

- Three competitive plays: specific moves against the three main competitors. Each with a two-sentence rationale and one supporting quote.

- One closing pull-quote: the single most clarifying verbatim quote from the dataset, displayed large in accent color, full-bleed.

At the very bottom: “Last synthesized [date]. Re-run from the Briefing screen.” in mono 12px.

THE SYNTHESIS ENGINE

When the user clicks “Run new synthesis,” a Supabase edge function runs the following pipeline.

Step 1: Parallel scraping via Perplexity. Fire eight Perplexity API calls in parallel using these query templates.

Reddit query: “Search Reddit for the 50 most recent and substantive discussions about [SUBJECT] (the [CATEGORY] tool). For each discussion, extract direct user quotes about pricing, complexity, data quality, integrations, ROI, and direct comparisons to [COMPETITOR LIST]. Return verbatim quotes with username, subreddit, and link. Do not paraphrase. Do not summarize. Return raw text only.”

G2 query: “Find the most recent and informative G2 reviews of [SUBJECT]. Extract 20 quotes covering both positive and negative experiences. Include reviewer role, company size, and review date. Return verbatim text only, no summary.”

Capterra / TrustRadius query: “Find recent Capterra and TrustRadius reviews of [SUBJECT]. Extract 15 most informative verbatim quotes with reviewer context.”

Podcast query: “Search podcast transcripts for substantive discussion of [SUBJECT] in the last 18 months. Prioritize [PODCAST LIST]. Extract direct operator commentary about how the product is used, who uses it, what works, what fails. Include episode title and approximate timestamp.”

LinkedIn query: “Search LinkedIn for public posts and public comment threads discussing [SUBJECT] in the last 6 months. Focus on posts by [TARGET AUDIENCE]. Extract verbatim quotes about deployment, ROI, and comparison to alternatives. Do not access private data.”

Hacker News query: “Search Hacker News for threads mentioning [SUBJECT]. Extract substantive technical and commercial commentary verbatim.”

Comparison content query: “Find comparison content (vs pages, alternative listicles, head-to-head reviews) covering [SUBJECT] against [COMPETITOR LIST]. Extract specific claims and data points verbatim, with source URL.”

Newsletter query: “Find operator newsletter mentions of [SUBJECT] in the last 12 months. Focus on [NEWSLETTER LIST]. Extract substantive analysis verbatim with publication and date.”

Store every returned source row in the sources table with its raw text.

Step 2: Synthesis via Claude. Pass all raw extracted text to Claude (claude-sonnet-4-6) in a single call with this synthesis prompt:

“You are a senior PMM analyst synthesizing public market intelligence about [SUBJECT]. You have been given raw extracted quotes and discussion threads from Reddit, G2, Capterra, podcasts, LinkedIn, Hacker News, comparison content, and operator newsletters. Synthesize this into a structured narrative analysis.

Return only JSON. No prose, no markdown fences. The JSON must follow this shape exactly:

{

briefing: { headline_findings: [3 cards with claim, elaboration, supporting_quote_id] },

market_moment: { category_stats: [4 stats with source], forces: [3 forces], position_paragraph: string, position_pullquote: string },

competitive: { scores: [CompetitorScore array], positioning_map: [...], head_to_head: { subject_vs_competitor1, subject_vs_competitor2, subject_vs_competitor3 } },

customer_voice: { heatmap: { themes, sentiments, cells }, top_quotes: [12 verbatim], themes: [9 themes] },

strategic: { positioning_gaps: [3], messaging_opportunities: [3], competitive_plays: [3], closing_quote_id: string }

}

Voice rules: No em dashes anywhere. Short declarative sentences. Operator-to-operator tone. No consulting jargon (no leverage, unlock, paradigm, best-in-class, thought leader, synergy, robust). No marketing words (no revolutionary, game-changing, transformative). Proof before explanation. Every numeric claim needs a source. Every quote shown must be verbatim with attribution. If you must synthesize a representative quote, mark its attribution as ‘synthesized’ rather than ‘verified.’

Be honest. If the subject has clear weaknesses, name them. If competitors have clear advantages, name them. This is for an operator making positioning decisions.”

Step 3: Persist the synthesis JSON to the synthesis table with a timestamp. The UI always reads from the most recent synthesis row.

VOICE AND COPY RULES

These apply to every string in the UI:

- No em dashes anywhere

- Short declarative sentences

- Banned words: leverage, unlock, paradigm, holistic, best-in-class, world-class, thought leader, ecosystem, synergy, robust, revolutionary, game-changing, transformative, cutting-edge, next-generation

- No emoji

- Proof before explanation

- Use numbers when available

- “Synthesized from clustered language” label on non-verbatim content

LOCKDOWN

- robots.txt with Disallow: / for every user agent

- noindex, nofollow meta tags on every page

- No social meta tags

- Passcode gate on entry, default passcode “narrative-os-2026,” validation through a Supabase edge function so the passcode is never in client code

- All API calls proxied through Supabase edge functions, keys never client-side

- No public share functionality

BUILD ORDER

1. Scaffold the five screens with placeholder synthesis JSON so design is locked first

2. Build the passcode gate and lockdown

3. Build the Supabase edge function for Perplexity scraping

4. Build the Supabase edge function for Claude synthesis

5. Wire the “Run new synthesis” button to the pipeline

6. Persist synthesis runs in Supabase with timestamps

7. Polish motion, micro-typography, and the heatmap last

Ask me for the three API keys when you need them. Confirm the Supabase project setup before any live scraping. Build the design and empty state first, then the data layer. Make it beautiful before it works.

How to version this for your own company

The prompt is structured so adapting it is a find-and-replace job, not a rewrite. Four sections need to change.

The subject is the obvious one. Replace every reference to “Clay” or “Clay (clay.com)” or “Clay Narrative OS” with your company name and URL. The naming convention I use is [Company] Narrative OS, but you can call it whatever you want.

The competitive set is the second swap. The prompt lists eight competitors specific to the GTM data category. Replace them with the seven or eight competitors that actually matter in your category. Keep the list to seven or eight, because fewer makes the positioning map look empty and more makes it unreadable. Order matters too. Put your two or three most important head-to-head competitors first, because those drive the comparison cards on the Competitive Landscape screen.

The data sources are the third swap. The Reddit subreddit list is GTM-tilted right now. If you’re in a different category, replace those with the subreddits where your buyers actually hang out. Same goes for podcasts and newsletters. If you sell to engineers, the relevant properties are The Changelog and Software Engineering Daily, not Lenny’s or 20VC. Pick the seven or eight your buyers actually consume.

The visual identity is the fourth swap. I used electric chartreuse for the Clay OS because I didn’t want it to look like Clay’s brand. If you’re building one of these for your own company instead of as outside analysis, you might want it to feel on-brand. Swap the accent color, the typography stack, or both. Keep the dark canvas though, because it reads as serious and analytical, and it makes the heatmap pop.

Once those four swaps are done, paste it into Lovable as the first message. The first version will be 80% of the way there. You’ll iterate from there with two or three follow-up prompts, mostly to fix things you only notice after the data actually scrapes.

The poster, who goes by westernarian, disarmed the easy rebuttal first. They are not a luddite. They build workflows, like systems, and have shipped their share of automations. The worry was sharper than “I don’t understand the tools.” It was this: “Marketing is becoming a ROI center and im not sure thats even marketing anymore.” Underneath it, quieter, the line that earned the upvotes: “Some of it should probably stay messy. Some of it should probably stay human.”

They’re right about what to be afraid of but wrong about what it means. The distance between those two is the whole debate, and the industry is about to get this exact question wrong in his exact way.

The room split in an hour

Scroll the thread and you can watch marketing argue with itself in real time.

One camp came to bury the old job. “The future of marketing is filled with engineers who are building and managing teams of agents,” wrote BigPersia, who figured the creatives “will get pushed out in the short term if they can’t adapt.” A commenter posting as three_s-works was honest about the incentive: “As a marketer that came up through engineering, I’m for it, selfishly.” The mood is simple. The train is leaving.

The other camp came to a funeral. The single most upvoted comment in the entire thread was not bullish. It came from a marketer posting as Prettylittlelioness, watching two former clients get taken over by operators who treat marketing as a machine. Her word for the campaigns that resulted: “bloodless.” Her diagnosis of the era: “we overcorrected from being vibes led to turning into a math class.” A twenty-year creative director, posting as Top-Establishment918, said it shorter. “Now all I do is prompt all day. Feels lazy.” And the line that got the OP to reply “Great line!” came from UnoMaconheiro: “we didnt make marketing smarter we just made it easier to make spreadsheets about it.”

Both camps are loud. Both have a point. Both are answering the wrong question.

The reframe a stranger got right

The question everyone is fighting about is binary. Is marketing becoming engineering, yes or no, pick a team.

Dozens of comments deep, a poster called Nexio_10 quietly fixed it and almost nobody noticed. “I don’t think marketing is becoming engineering. I think the execution layer is becoming engineering while the strategy layer becomes even more important.” Then the line that should have closed the thread: “The tools are getting commoditized. Good judgment isn’t.”

That is the answer. The execution layer of marketing is becoming engineering. That is a different sentence with a different conclusion bolted to it.

The work is splitting into two layers. The bottom layer is execution. Building the pipeline, cleaning the data, running the agent ecosystem, shipping the dashboard, wiring the attribution, winning the citation. That layer is being engineered, fast, and it is not going back. The top layer is judgment. Knowing what to build, what the work should say, which bet is worth taking, which output is sharp and which is filler. That layer is not being engineered. It is becoming the only scarce thing in the building.

When the bottom layer commoditizes, the top layer does not lose value. It absorbs all of it. The bulls think the engineer eats the creative. The mourners think the creative is already dead. They are watching the same event, the floor dropping out from under execution, and drawing opposite conclusions, when the real conclusion is that a point of view just became the most valuable asset a marketer can hold.

Why this happened now, and why it is not reversible

The reason execution turned into engineering is not that a vendor wished it into being. It is that the channels marketers leaned on for a decade compressed at the same moment, and the layer that replaced them is machine-readable in a way the old web never was.

Answer engines do not reward “good content.” ChatGPT, Perplexity, Claude, and Google’s AI Overviews extract entities, weigh source authority, and match structured knowledge against a query before a human ever sees a result. Winning a citation in that environment is an engineering problem and a judgment problem at the same time. You need the structured, retrievable substance and a point of view worth citing. One without the other loses.

This is the highest-leverage thing a marketing engineer builds, and it is brand new. It did not exist as a discipline three years ago. At Webflow my team built first-party systems to own this layer in the CMS category and watched answer share cross 60 percent with a swing of more than 300 incremental AI citations. That is not a content calendar. That is not “a marketer who learned SQL.” It is a new category of work, and you cannot optimize a citation you cannot see, which is the entire reason a measurement layer like Profound exists.

What the role actually is

A marketing engineer owns output, not pipes. They identify the problem, build the thing, ship it, measure it, kill it or scale it, alone, end to end, then decide what it should have said in the first place.

A few weeks back, in the playbook for hiring this role, I used one example to make the “alone, end to end” part concrete. At Webflow I wanted to go deeper in the freelancer community. Between days stacked with calls, I built a handful of agents that scraped the freelancer and web-dev subreddits, surfaced real-time pain, shaped a narrative and an offer around it, activated across channels, measured, and refined. One person running a cross-functional acquisition program in days, not quarters. No PM, no brief, no ticket sitting in someone else’s backlog. Fitting, given where this piece started, that the raw material was a stack of subreddits, the same place this whole debate is now playing out.

That last move, deciding what the work should say, is the job. A marketing ops manager keeps the systems clean so campaigns can run. Necessary, valuable, not this. A skeptic in the thread, b2b_framework_guy, made the cheap-version case well: “most of the people calling themselves marketing engineers are just marketers who learned sql. its not that deep.” For a lot of people wearing the badge, he is right. That describes the floor, not the ceiling. Learning SQL gets you into ops. Knowing which of a hundred possible builds will move the number, and which will rot in three months without a human watching it, is the part you cannot learn in a weekend. That part is the role.

Here is the ceiling, written by someone who has never read a word of this. This week the Director, Marketing Strategy & Ops at Figma posted a req for a Marketing Engineer. The mandate: make the marketing org disproportionately faster with AI. Find the most valuable problems hiding inside manual work. Build agents and workflows that ship. Delete work that no longer needs a human. The line that gives it away: the person he wants gets annoyed at a repetitive process because they can already picture the system that should replace it. That is not “learned SQL.” That is the role, written by a company that does not sell the tool, in language I never handed them.

Three questions I keep getting asked

Since I published that playbook, I have had somewhere north of fifty messages about it, from founders, from CMOs, and from people already doing this job inside companies. The questions were not the part that stayed with me. The notes that stayed with me came from the practitioners, each writing a version of the same sentence: that is what I do, and I finally have a name for it. That is how you know a role is real. Skeptics argue about a title. The people living it exhale, because someone finally described their actual week.

I have been calling this shift the Great Convergence. The technical marketers are being pulled toward creativity. The creative marketers are being pulled toward systems. The two halves the org chart kept in separate rooms are collapsing into one person, because the best operators stopped honoring that wall years ago. The marketing engineer is the name for the person standing in the middle of it. Profound put that name on the role, and they put it on correctly, which almost never happens in a category that ships a new title every quarter. They saw the loop running inside their sharpest customers before the rest of the market had a word for it, which is why they are the ones who ended up naming it.

The OP’s fears live inside the questions, though, so here are the three sharpest, anonymized, answered straight.

“Isn’t this just a vendor’s invented title? Profound named it because they want you to buy Profound.”

A founder asked me this, skeptical. He had the OP’s best argument, which is genuinely good. westernarian described the playbook exactly: “Invent the title, write the manifesto, get a few high signal people to wear it as a badge, sell the tool the title basically forces you to adopt.”

He is right about the mechanism. I will not pretend otherwise, and you should distrust anyone who does. He is wrong about the conclusion. A go-to-market move and a real shift in the work are not mutually exclusive. The vendors are selling the shift because the shift is happening. When Profound’s team presented the role at SEOweek, the framing, relayed by a commenter who was in the room, was not “fire your creatives.” It was that the marketing engineer takes direction from the marketing leader and the creative call stays human, while “teams are definitely going to be smaller, with a focus on high performing teams.” That is not hype. That is your org chart in eighteen months. The cynicism about the label is fair. Letting it talk you out of seeing the thing the label points at is how you lose two years.

One req is an anecdote. Here is the market. Look at the titles and you would think these are different jobs. Read the reqs and they are one job. Figma calls it Marketing Engineer. Ramp calls it a Vibe Growth Marketing Manager. Cloudflare files it under Marketing Engineering. The title is still settling. The role already showed up. And the demand shows up before the reqs even post. Pull Google Trends yourself. “What is a marketing engineer” and “marketing engineer jobs” are both breakout terms in the last month.

That is Google’s own data, not a vendor’s slide. A vendor can name a title. A vendor cannot make companies with no stake in the tool write the req, or make strangers start searching for the job by name.

Let me say plainly where I land because you should always know where the writer is standing. I am all the way in on this role. Not because backing it is the fashionable move this quarter, but because I have already built this way myself, and because the people operating this way now are not theorizing, they are shipping, and they are starting to find each other. Last week Profound hosted the first-ever Marketing Engineering hackathon. It ran five times oversubscribed, packed with people who read the role description and recognized their own week in it, then showed up to build in public because somebody had finally made a room for the work they had been doing alone, which is more than any other hackathon can say right now. That is not a title hunting for adherents. It is adherents who finally got a title. The label is a go-to-market move. The work underneath it is the realest thing happening in marketing right now. Call the role a fiction if you want. The waitlist disagrees. The burden is on you to explain the people already living it, and I have yet to hear a version of that argument that survives ten minutes with one of them.

“I’m a creative marketer. I can’t code, and I don’t want to. Is my career over?”

This is the question under the entire thread. It is what “feels lazy” meant. It is what “how many of us are even going to survive this transition” meant. It deserves a real answer.

No, and it is closer to the reverse. The scarce input is now the judgment that decides what to build, and that judgment is creative. Knowing which agent moves the number is taste. Knowing what the work should say so a stranger who has never heard of your company stops scrolling is narrative instinct. None of it comes from the stack. The career that is ending is not the creative’s. It is the creative’s who refuses to touch the tools at all, and the builder’s who can ship anything and decide nothing. The first becomes slow. The second becomes an expensive intern who ships a hundred things no one uses. The job is both halves in one head, and the creative half has to lead. If you have taste and you learn enough of the tools to be dangerous, you are not getting washed. You are the person the role was invented for.

“If everything has to prove a return, doesn’t the bold work die in the planning meeting?”

This is the OP’s strongest point and I will not wave it off. He named the failure mode precisely: “the weird bold stuff dies in the planning phase because nobody can prove in advance that it’ll work.”

That death is real, and it is a management failure, not a property of the role. A commenter named buttonMashr99 wrote the fix without dressing it up: keep early exploration messy and close to the customer, then systematize only what shows repeatable traction. You do not run the bold bet through an attribution model before it exists. You protect a lane where work is allowed to be unmeasured, you let the idea live long enough to throw a signal, and then you bring the engineering in to scale what worked. Teams that demand proof before the experiment had that problem in 2015 with a spreadsheet. The tools just let them do it faster. The role does not kill the bold work. A leader with no nerve does, and now has better software to do it with.

The tell hiding in the thread

Here is the part that should end the argument, sitting in the comments where no one assembled it.

The thread is about whether marketing is becoming a machine that scales the average. The thread is also full of comments that were obviously written by AI, getting downvoted on sight, by a crowd that smelled them instantly.

One commenter posted a long, fluent, structurally flawless reply. The top response was not a rebuttal. It was “I LOVE HOW obviously written by AI that comment is.” Another reader nailed the fingerprint: “the ‘it’s not just x, it’s y’ sentences.” The poster, caught, laughed it off: “Nah nah my mate Claude wrote it.” Further down, no mercy: “Use your own words and formulations.. hate this ai shit.”

A commenter named Valuable-Cap-3357 had already explained why, a hundred comments before it happened. The default output of these tools, he wrote, “isn’t bad, it’s average,” and the engineering layer “doesn’t fix that; it just scales the average.” The thread then proved his thesis on itself, in public, in real time. The average got posted. The humans flagged it and moved on.

Now the part nobody in the thread wanted to say.

A share of the grief in that thread is not about losing creativity. It is about losing the place that the absence of creativity used to hide. For twenty years, execution volume was cover. You could fill a week with campaign ops, channel management, reporting, and QA, and never once be required to have a point of view, because the busywork read as value. Automate the busywork and the cover is gone. What is left on the table is the single question the machine cannot answer for you: do you have something to say. The crowd in that thread answered it instantly for every AI comment that didn’t. The machine did not kill the point of view. It revealed who never had one.

That is also the good news, if you have one. Taste was always the moat. It just used to be optional. Now it is the whole job.

The ruling

Give the OP his warning, because it is real. Build systems for the sake of systems, optimize for the dashboard instead of the customer, run every bold idea through attribution before it can breathe, and you get exactly the bloodless marketing he fears. That outcome is avoidable. It is a choice, not a destiny, and treating it as destiny is how good people talk themselves into sitting this one out.

The bulls had the timeline right. This is coming, it is not optional, and the teams that move first run smaller, ship more, and open a lead that does not close cheaply. By 2027 this is a standard role. By 2028 it is a team. The companies hiring the first one now will have the second and third in seat before everyone else writes the req.

But the binary both camps fought over was the wrong fight, and the stranger dozens of comments deep had it right. Marketing is not becoming engineering. The execution layer is becoming engineering, and that is the best thing to happen to creative marketers in years, including the ones currently mourning. When the machine absorbs the average, judgment becomes the scarcest and most defensible asset in the function. The marketing engineer is the person who runs that trade on purpose. Hired for the tools, you get the bloodless machine. Hired for the taste, you get the opposite: the operator who hands every repeatable, measurable task to the machines so every human hour left goes to the work no model can do, which is the exact work the OP is fighting to protect. The engineering does not cost you the creativity. It buys the creativity its time back, then scales whatever you brought to begin with.

The part the mourners need straight: the marketers getting washed out are not the ones who refused to become engineers. They are the ones who spent a career mistaking motion for a point of view, and just lost the place that hid it.

So if you run a marketing team, stop debating the title and make the hire. Pay on the senior IC band, because the people worth hiring are choosing between you and a senior engineering offer, not a marketing one. Point them at the layer where your buyers now ask their questions, the answer engines, and hand them the one input the job runs on: a current read on what those engines say about you and your competitors. You cannot win a citation you cannot see. The teams already ahead are watching that share in Profound and shipping against the gaps every week, which is the whole loop the role exists to run.

Have something to say. Then build the machine that says it everywhere your buyers are looking, all at once. In that order, never the reverse. That is the whole job now. Done right, human marketing does not end here. It gets the most room it has had in a decade, finally carried by a machine big enough to keep up with it.

On May 7, ChatGPT started hyperlinking brand names straight to company homepages. Plain bold text became a clickable link. Referral traffic to monitored brands jumped roughly 60% overnight and held.

Most people read that as a traffic story. Based on the calendar, I’m reading it as an ad-tech story.

What actually happened

Start with the size of it, because the size is what makes this real instead of anecdotal.

In Profound’s monitored set, daily OpenAI referrals roughly doubled starting May 7 and stayed there. Homepage share of those referrals went from around 3.5% to around 24% in a week. Brand front doors went from a rounding error to one in four referral clicks.

This is not one dataset talking to itself. Similarweb’s clickstream panel measured total ChatGPT referrals up about 158% week over week, with homepage traffic up 355%. Qwairy studied more than 140,000 responses and found inline brand links jumped from 0.4% of answers to 6.2% in a single day. Three independent vantage points. One event.

Josh Blyskal and the Profound team caught it in the wild first (props). One of the most important observations in AI search this year.

Real, attributable brand clicks where there used to be almost none. If that were the whole story, it would be a good one.

It is not the whole story.

Now look at the calendar

May 5: OpenAI opened its self-serve Ads Manager. CPC bidding. A conversions API. No minimum spend.

May 7: brand hyperlinks rolled out.

Two days. You do not need a leaked roadmap to read that sequence. A relevance-weighted CPC auction needs one thing above all else: a clean record of what people click. The branded link update is how OpenAI started collecting it, at scale, across every brand and every query at once.

Every clickable mention now throws off a signal. Which brand got clicked. On which question. In which context. At what rate against the other brands in the same answer.

That is the raw material of an ad ranking system.

Why the clicks matter more than the traffic

Google’s ad machine was never built on impressions. It was built on learning which results earn clicks.

CTR is not a reporting metric there. It is the input that decides what gets shown, where, and at what price. Impressions were the warm up. Clicks were the unlock.

OpenAI is running the same play in compressed time, and it is not hiding it. The Ads Manager that went live on May 5 runs a relevance-weighted second-price auction. That is the published mechanism. It means a tighter, more relevant ad on a smaller bid beats a lazy ad with a bigger budget. Relevance gets weighted. To weight relevance, you have to know what people actually click. The branded link update is the meter that reads it.

So the two events are one event. The traffic win is real. It is also the byproduct. The product is the click data itself.

Who won, who sat out, and why

The category split makes sense the moment you stop counting traffic and start reading intent. In Profound’s data, B2B SaaS referrals jumped more than 200%. Fintech rose around 60%. E-commerce stayed roughly flat.

ChatGPT is minting clicks in the categories where people ask for a company by name. Best tool for. Alternatives to. Who should I use for. Purchases with a transactional path route through the shopping surface instead, so retail sits the link auction out for now.

The brand auction is getting built first. If yours is a category where buyers ask ChatGPT for a name, you are already in the training set whether you planned to be or not.

Three moves while the window is open

The free-traffic window is open right now. Treat it like inventory you can earn before you have to rent it.

Make ChatGPT a named channel in your reporting. Add chatgpt.com and openai.com as referral sources today. Google made this easier on May 13 by adding a native AI Assistant channel to GA4 that classifies ChatGPT, Gemini, and Claude traffic with no custom filters. One caveat. A large share of AI visits arrive from mobile apps that strip the referrer and land in your direct bucket, so the reported number undercounts the real one. Tag what you can. Assume there is more.

Treat your homepage like a cold landing page. One in four AI clicks now lands on your front door from someone who knows nothing but your name. They arrive with the one sentence ChatGPT wrote about you and about five seconds of patience. If they cannot tell what you do and who it is for in that window, you earned the click and handed it right back.

Win share of answer while the clicks are still earned. This is the Answer Ownership move. Every click you earn organically today is a data point in the auction that prices your ads tomorrow. The brands that own the answer now set the floor everyone else has to outbid later. The ones that wait will pay to buy back visibility they could have had for free.

The part that should make you uncomfortable

OpenAI pulled in over $100 million from a six-week pilot before any of this went self-serve. The stated target is $2.5 billion this year and $100 billion by 2030.

Those numbers do not come from showing ads. They come from pricing them well. And pricing them well requires exactly the click data the May 7 update just switched on.

You are not the customer of that system yet. Right now you are the free traffic. Every click you earn today becomes the case study OpenAI uses to price your ads tomorrow.

The window where AI mentions are earned, attributable, and free does not stay open. Own the answer while it is still organic.

Great work to Josh Blyskal and the Profound team. This is the most important shift in the category today.

This is a real step, and I want to say that plainly before I get into the parts everyone is going to skim past. We have wanted first-party AI visibility data since AI Overviews started eating the top of the page. Now a slice of it exists, inside the tool we already trust for organic, and attributed to Google itself.

Then you read the help documentation, and the report quietly tells you what Google is willing to measure and what it is not. The second list is longer, and a lot more interesting.

Start with one sentence

Skip the launch bullets. The line that matters is in the help doc, in the definition of an impression. Google counts an impression as how often “links to your site were shown” inside a generative AI feature on Search.

Read that twice. The unit is a link shown, not your content used. That distinction is the entire AEO game, and Google just drew a hard line straight through the middle of it.

AI Overviews and AI Mode do two different things with your pages. Sometimes they surface a link, a citation chip a user can click. Often they pull a sentence, a stat, a definition off your page to ground the answer and never surface a link at all. The first is citation. The second is influence. AEO has always been about both, and you can argue the second matters more, because being the source the model trusts is more durable than being one of six links in a carousel.

This report sees the first and is blind to the second. When your content shapes an answer without earning a visible link, your impression count does not move. So the number in front of you is not “how much am I showing up in AI,” it is “how often did Google decide to link me.” Those are very different questions, and treating them as one is the first mistake people will make with this data.

One tell that Google knows the difference: its companion blocking control (more on that below) lets a site opt out of being used “as links or for grounding purposes.” Google separates the two when it suits them. The report only reports one of them.

The pros spotted both problems within a day

Watch who said what under Google’s announcement, because the split is the real signal. The “finally, thank you” replies landed fast. So did sharper reads from people who do this for a living, and they converged on the same two complaints.

The first is granularity. The report blends AI Overviews and AI Mode into one impressions bucket. Giorgio Taverniti, who wrote the book on liquid search, did not soften it: aggregating AI Overviews and AI Mode, and shipping nothing on grounding queries, is the kind of choice you make when you have drifted away from the people working in the field. Rebekah Logan made the operator’s version of the same point. Citation behavior in AI Overviews versus AI Mode can differ wildly, so one blended number hides the thing you most want to know, which surface is citing you and which is not. Simone De Palma called the aggregated sub-menu “data engineering 101” and noted that Bing at least ships query-level data from its engine.

The second is the grounding gap, the same one sitting inside the impression definition. Jayme Welch put it cleanly: this is a measure of visibility, not understanding, and it tells you nothing about how often AI features used your content without a citation. Radu Stoian and Yongjoon Yang both asked for query fan-out, what Bing calls grounding queries. That request is going to define the next year of this conversation, and Google shipped without it on purpose.

Notice the divide. The loudest praise was excitement that the report exists at all. The most specific reactions came from the people who pressure-test AI visibility for a living, and they found the same two holes I did, inside a day. Excitement that a thing exists is not evidence the thing is good.

The missing column is not an oversight

There are no clicks. No click-through rate, no average position, no query data. Just impressions, sliced by page, country, device (Search only), and date, down to hourly granularity, with data that appears to begin around May 18.

Barry Schwartz asked Google directly about clicks and got the line you would expect: they are working with site owners on what is helpful and will add metrics over time. Maybe. But I would not hold your breath for clicks, and not because instrumenting them is hard.

A clicks column would quantify the one thing Google has the least incentive to quantify: how much traffic the AI answer keeps for itself. The whole economic logic of AI Overviews is to resolve the query on the page so the user never needs to leave. A per-page, exportable click number sitting in everyone’s Search Console would put a hard figure on that cannibalization. “Additional metrics over time” is a real roadmap. Clicks are the last room in the house they unlock.

So treat the impressions number as a denominator, not an answer. It can show you the shape of your AI visibility and how it moves. It cannot tell you whether AI search sent you a single visitor. For that you still need your server logs and your analytics, and you still need to do the matching yourself.

Why the UK got it first (not for the reason you think)

The rollout is a small subset of UK site owners, reportedly limited to .co.uk properties at first, ahead of a global expansion with no date attached. The instinct is to read that as a routine phased launch. It is not.

The UK went first because the Competition and Markets Authority is forcing the issue. The CMA’s remedies require Google to give publishers genuine control over how their content feeds AI, including the ability to opt out of having it used to fine-tune models, and Google has roughly nine months to roll that out across the UK. The legally mandated piece is the controls. The report is not itself required by the CMA, but it shipped in the same market on the same day, which is not a coincidence. When a regulator makes you hand publishers an opt-out, you want to be able to point to a reporting product launched alongside it and call the whole thing a publisher win.

That reframes the timeline for the rest of us. The pace of access is being set by antitrust pressure in the UK and the EU, not by Google’s eagerness to hand operators better data. If you are in the US waiting for this, you are waiting on regulators in another jurisdiction, not on a product roadmap you can lobby.

Read the rollout cynically and you land somewhere uncomfortable. This looks timed to coincide with the CMA controls and scoped to do just enough to keep regulators satisfied. And notice the detail that should bother you most: the data starts in May 2026, with no history before it. So you cannot line up a decline in your own clicks against the rise of AI Overviews, even if you wanted to. Convenient.

The sleeper launch is the toggle, not the report

Shipped the same day, and arguably more consequential: a control that lets a site opt out of appearing in AI Overviews, AI Mode, and generative features in Discover, both as links and as grounding. Opt out and you get no impressions and no traffic from those surfaces. Google says it will not use the choice as a ranking signal in core Search, so in theory you can leave AI without leaving Search. For the test cohort it takes effect June 17.

In an earlier poll, about a third of SEOs said they would block Google’s AI features. I think almost none of them should, and I suspect almost none of them will once the toggle is real and the thing they would be zeroing out is their own impression count. The honest use of this control is narrow: publishers whose entire business is the click and who have decided AI exposure is pure leakage. For nearly anyone in B2B or considered purchases, AI surfaces are now part of how a buyer builds a shortlist before they ever search your brand. Opting out to protect a click you were probably going to lose anyway is a bad trade. It is still good that the lever exists, because consent should not require a robots.txt hack.

What to actually do with it on Monday

A few concrete moves, whether you have access now or are planning for when you do.

Build the page-level citation inventory. The Pages view is the most useful tab here. It tells you exactly which URLs Google is willing to link inside an AI answer, which is your current answer-worthy set in Google’s eyes. Put it next to the pages you assume are your strongest answer assets. The gap between those two lists is your roadmap, and closing it is a production problem more than an analysis one. This is where a content engine like AirOps earns its place, because turning a list of under-cited topics into answer-shaped pages at real volume is the work, and doing it by hand does not scale to the surface area AI search now covers.

Use impressions as answer-share input, not a traffic proxy. Track the trend and the page mix, watch the country and device splits (AI behavior diverges on both), and kill the reflex to convert impressions into sessions. They are not sessions, and a chart that implies they are will get you in trouble in a board meeting. Plenty of operators in that LinkedIn thread were already drafting the client line, “your content showed up 9,000 times in AI answers this week,” and that is a fair story to tell as long as you are honest that it is a visibility story and not a value one. The moment it gets dressed up as traffic, you have lied to a client with Google’s logo on the slide.

Triangulate, do not switch. This does not replace a cross-engine AI visibility platform like Profound, and anyone telling you GSC makes one redundant has not understood either tool. They are not measuring the same thing. Profound tracks your share of voice and citations across the engines that actually carry the conversations, ChatGPT, Perplexity, Gemini in its own app, Copilot, while GSC reports Google’s own count of links displayed on Google’s own surfaces. Those numbers will not line up, and they are not supposed to. One is a cross-engine market-share lens, the other is a single-vendor, single-metric ground truth. Read them together. GSC becomes the first-party Google reference point you anchor to, and the platform stays the only thing giving you the rest of the map, which is most of it, because Google is one engine among several and AI search is not happening only inside Google.

Keep an eye on what Bing already shows. Bing’s AI performance report has been global for a while and exposes more signal than Google’s, including citations and grounding queries. No clicks there either, but the contrast is the point: Bing surfaces the grounding-level data Google is choosing to withhold. If you operate at any scale, treat Bing’s view as a useful second instrument, not because its volume matters, but because it sees the half of the picture Google won’t show you.

The measurement gap is half-closed

Here is the state of play. We went from no first-party AI data to a real, Google-attributed view of where our links land in AI answers. That is progress and I am glad to have it.

But the half that is still missing, clicks and queries and grounding without a link, is exactly the half that would settle the argument everyone is actually having: is AI search a traffic apocalypse or a new front door. Impressions tell you that you are in the room. They do not tell you whether anyone walked through the door, what they asked to get there, or how often your words ended up in the answer with your name stripped off.

We got a better altimeter this week. We still have no airspeed indicator. Plan accordingly, and read the fine print before you put any of it in a deck.

One is from recent Google’s generative-AI guidance. It puts llms.txt on the list of things you can stop fussing over, next to a reminder that you do not need special files or markup to appear in AI search. The other is from Chrome’s Lighthouse documentation, published within days of the first. It calls llms.txt an emerging convention for LLMs and agents and notes that without it, agents may spend more time crawling a site to work out its structure.

So one team tells you the file does nothing, and another team ships an audit that checks whether you have it. Same logo, same month. Read only the headlines and it looks like a company arguing with itself.

But…the two statements describe two different jobs. The conversation online went sideways because we keep folding both jobs into one flat word, “AI,” and then act surprised when the advice points in two directions.

Here is the distinction that settles it.

Discovery and functionality are not the same job

When put the question to John Mueller (Google) directly on Bluesky, his answer was the most useful thing said on the topic all month, and I would read the whole thread before forming a take.

The short version: the llms.txt files sitting on Google’s own developer properties are not there for search. Mueller split the question into discovery and functionality. Discovery is getting found by a global search engine. Functionality is what happens after the find, when a person or an agent is already on your page and trying to finish something. He compared it to a call to action. You do not add a CTA to rank. You add it because once someone arrives, you want them to convert. Both matter to whoever owns the site’s outcomes. They are simply different problems that call for different tools.

llms.txt lives on the functionality side. It was never a discovery lever, which is exactly why a search team can tell you to ignore it for rankings while a browser team finds it mildly useful for agents mid-task. Both statements are true because they are answering different questions.

Mueller went further, and this is the part most of the hot takes skipped. The place llms.txt actually pulls weight today is developer documentation read by AI coding tools. Handing a coding assistant a simplified, low-token version of a reference page can make it faster and more accurate. He was careful to frame it as a stopgap, since those tools read HTML perfectly well on their own. For anything that is not developer docs, he was blunt: it does not make much sense yet, agentic traffic is still a trickle (his advice was to go check your own logs), and a Markdown copy of a shoe’s spec sheet is not going to sell more shoes. His closing line is the one I keep coming back to. Prioritize needs before dreams.

What the broader data says

This is where the marketing internet and the measurable reality stop agreeing.

SE Ranking analyzed roughly 300,000 domains and found no relationship between having an llms.txt file and how often a domain showed up in AI answers. When they removed the file from their model entirely, the model got more accurate, not less. On the consumption side, one log study tracking AI crawlers across ninety days found that out of more than half a billion bot visits, only a few hundred touched llms.txt at all. Adoption sits somewhere around ten percent of sites and climbing, which gives you the real shape of this thing. A lot of people are creating the file, and almost nothing is reading it.

That gap, high creation and near-zero consumption, is the whole story. We are writing a file for an audience that has not shown up.

What I found when I ran it

I do not like arguing about this from the sidelines and I’ve tested this nearly two dozen times in the last 6 months.

Across the sites and pages where I ran before-and-after measurement, I saw no movement I could honestly attribute to the file. No lift in AI citations, no change in how answer engines pulled from the pages, nothing that separated the test set from the control beyond ordinary noise.

I want to be precise about what that does and does not mean. It does not mean the file is harmful. It is cheap to publish and it will not hurt you. It means that if you are shipping llms.txt expecting to appear more often in AI Overviews, ChatGPT, or Perplexity, the expectation is the problem, not your implementation. I wish it were that easy…

Where it actually earns its place

There is a clean rule hiding in all of this.

If you publish developer documentation, ship llms.txt. Coding agents genuinely use it, it is inexpensive to maintain, and the token savings are real. This is the one case where the file does a job nobody else is doing.

If you do not publish developer docs, treat it as optional. Worth knowing that the Lighthouse audit marks the file Not Applicable when it is missing rather than failing you, because providing it is still optional. An audit checkbox is not the same as a result.

The argument worth having instead

The reason the llms.txt fight wears on me is that it is pulling attention away from the part of that same Lighthouse release that actually matters.

The llms.txt check is the least important item in Chrome’s new agentic browsing category. The heavier signals in that category decide whether an agent can read and operate your site at all: a clean accessibility tree, layout that does not shift under an agent’s feet, semantic HTML, and WebMCP, the emerging standard that lets a site expose its functions to an agent directly instead of forcing the agent to guess from a screenshot. WebMCP is heading into a public origin trial in Chrome 149. That is the work that will separate sites an agent can use from sites that merely exist near it.

So when the agentic web does arrive in volume, and the logs say it has not yet, the sites that win will not be the ones that wrote the best text file. They will be the ones an agent can actually navigate and act on.

Discovery is one job. Functionality is another. Spend your scarce hours on the one that is real today, and build the structural pieces that will still matter when the rest catches up.

Needs before dreams.

About StackedGTM

StackedGTM is a media and intelligence platform for go-to-market in the AI era, written by Josh Grant. It’s read by founders, CMOs, and the growth and marketing operators at companies like Anthropic, OpenAI, Stripe, Rippling, Cursor, Webflow, and hundreds more. No BS, no fluff, just deep insights and how-to frameworks on what’s happening in AI GTM.

The newsletter is supported by Profound, the platform serious brands use to measure and act on how they show up across AI search, from tracking citations to running agents against the AEO workflow. That support keeps it independent and free to read. The editorial calls are mine, including the skeptical ones above, and any piece paid for directly is labeled at the top. This one is not.

If you want an operator’s read on where GTM is heading, subscribe.

“How are we actually doing in AI search compared to our competitors?”

Most arguments about AEO measurement get framed as a data problem but they’re really not. They are a market structure problem, and until this week the channel was missing the one piece of infrastructure every other legitimate marketing channel has.

Consider what makes a performance channel legit inside an enterprise. Not volume. Not even attribution, which most channels have only partially solved. The thing that matters is price discovery, a mechanism by which the market tells you what your performance is worth relative to everyone else trying to do the same thing.

AEO will never have a literal price the way paid does. That is not the point. Price discovery in market structure terms is about comparative valuation, not dollar amounts.

SEO has it. The entire channel is built on it. You cannot rank in position three without two URLs sitting above you, and Google’s results page is a daily, public, brutally honest auction of relative quality. Position is comparative by definition. There is no such thing as a good ranking in a vacuum.

Paid search has it. Auction data, CPC benchmarks, impression share, quality scores. You know what a click is worth because the market sets the price every time you bid.

Brand has it (even if imperfectly). Share of voice, unaided recall, brand tracking studies. Signals that are noisy but real. A marketing leader knows roughly where the company sits.

Even email, the oldest channel in the stack, has open and click rate benchmarks granular enough to be useful.

AEO has had none of this. For nearly two years the channel has run on absolute counts. I have sat in rooms where one site’s monthly citation count was treated as a triumph, and rooms where another site’s count, many times larger, was treated as a disappointment. In neither case did anyone actually know which read was correct. This is not because the people working in the channel are unsophisticated. It is because the data to answer the question correctly did not exist outside any one platform’s walls.

What looked like a measurement problem was actually a structural one. You cannot have a legitimate channel without comparative valuation. You can have activity, you can have spend, you can have dashboards that look the part. But until participants can see where their performance sits in a real distribution, the channel is running on faith, and budgets allocated on faith get cut first when the cycle turns. I am already watching that happen, unfortunately.

What benchmarking infrastructure in AEO actually looks like

This week Profound shipped Benchmarking in Agent Analytics, and it is the first credible answer to this problem the category has produced. They built the missing layer, the one that lets the channel calibrate itself against itself.

The mechanics are straightforward. Profound compares your AI citation performance against more than 100,000 pages tracked across the Profound Network, filterable by industry and company size, refreshed weekly. I have been a Profound customer long enough to remember when a cross-network view like this was technically impossible. That it is now table stakes tells you how fast this category is moving. Every page lands in one of four tiers, Poor, Fair, Good, or Great, based on where it falls in the percentile distribution. You see your site’s overall tier at a glance, and you can click into any page to see exactly where it sits in the network.

That is the description. Here is what it actually does.

It turns “we got cited 32,000 times” into “we are in the 73rd percentile for our industry and company size, with seventeen pages in the bottom quartile dragging the site average down.” Those two sentences are not the same. Not in category, not in usefulness, not in what they let you do on Monday morning.

The page-level view is the part I did not expect to matter most but I think it does. Site-level benchmarks are useful for executive conversations. Page-level benchmarks are what let content teams act. When every cited page on your site is ranked against peers, the bottom-tier pages stop being a guess about where to focus. They become a worklist.

There is a quiet design choice worth flagging. Pages need at least five AI citations to be included, and any tier segment with fewer than twenty sites is suppressed. The team understood that benchmarks at small sample sizes are worse than no benchmarks, because they give false precision. The thresholds are conservative enough that what you see can be trusted.

The part most people will get wrong

The first-order effect of this shift is obvious. Marketing leaders can finally answer the board question with a percentile instead of a screenshot. That is real and it matters, but it is the least interesting consequence.

Here are three things I expect over the next twelve to eighteen months that most teams have not priced in yet.

Budgets will get defensible. A percentile is something a CFO can argue with. A citation count is not. When AEO investment can be defended against a distribution (”we are in the 40th percentile, here is what it costs to move to the 70th”), the channel graduates from experimental line item to forecastable spend. That is the transition every emerging channel has to make, and most stall there for years. AEO might compress that timeline considerably. This is timely given I’m already companies who invested early in AEO start to look back and see if the return was worth it with skepticism on the investment.

Enterprise content teams will shrink, not grow. This is the prediction I am most confident in and the one most teams will resist. Most content orgs have been hiring against a “more content” thesis for the AEO era. The data does not support that thesis once you can see the distribution.

A fintech I advise pulled their AI citation data by page. Their top 14 pages were driving 61% of their AI citations. The bottom 180 pages were driving 9%. I want to say that out loud one more time, because I do not think most people have internalized what a Pareto distribution looks like when it shows up in their own content org. Fourteen pages. Sixty one percent. One hundred and eighty pages. Nine percent.

They did not have benchmarking when they built that long tail, so they had been investing in it on instinct for nearly 18 months, assuming volume would eventually compound. The distribution said the opposite. Kill half the bottom tier, take the saved budget, and triple down on the fourteen pages already doing the work. Most content orgs are sitting on a version of this same distribution and do not know it yet.

Once page-level percentiles exist, the math is unavoidable. The shrinking is what everyone will fixate on. It is the least interesting part. The real shift is in what the job becomes. The skill that compounds in the AEO era is not the ability to produce more content. It is the ability to architect workflows that account for performance across every discovery channel at once. That is the Marketing Engineer, the role I wrote about recently. The companies that see this first will rebuild the content org around a few people who think in systems instead of output. The companies that don’t will keep hiring against a volume thesis the data has already killed. I have watched this exact pattern run twice in SEO over the last decade. The people who read it early built careers on it. The people who read it late are still writing the brief they wrote in 2019.

The information asymmetry between participants and non-participants will widen fast. Benchmarks compound. The more sites in the network, the sharper every comparison gets, and the harder it becomes for anyone outside the network to credibly claim they know their position. Six months from now, the gap between teams who can answer “where do we rank” with a percentile and teams who can only answer with a screenshot will be the difference between teams that get budget and teams that lose it.

What this means for the category

The category is too young for any one platform to have won anything yet. The next eighteen months will be a real fight, and right now Profound is out in front of it.

The company that ships the benchmarking layer first usually holds a structural advantage in the period that follows, because comparative valuation is itself a network effect. Every additional site in the Profound Network sharpens every benchmark in it. Every sharpened benchmark makes the platform more valuable to be measured by. Every increment of value makes the next customer easier to win. It is not a moat that closes quickly. It is one that compounds, and the compounding starts now. Props to Profound for shaping this and finding a way to make the data they’re collecting valuable to the entire industry.

We have been calling AEO a channel for 18 months. Some of us have been calling it that slightly longer, and feeling slightly stupid about it every time the data part of the conversation came up. A channel without price discovery is a behavior. A channel with price discovery is an operating discipline.

Eli is the author of the book Product-Led SEO and for the last few years has worked as an SEO strategic consultant for some of the largest brands on the internet like LinkedIn, Tinder, Coinbase, Gusto, G2, and many others. He writes a weekly newsletter on the future of SEO and AEO at ProductLedSEO.com, and he advocates for putting the user first in any organic strategy, whether it’s designed for traditional search or new LLMs.

Eli sent me a line last week I haven’t been able to stop thinking about:

“For years I didn’t believe small and local businesses should have websites at all. They didn’t get any traffic. Now they feed the LLMs.”

Read it twice. That’s the entire shift in two sentences.

For a decade, the pages most B2B content teams built were optimized for one thing: aggregate organic traffic. Pages that didn’t drive sessions got deleted. Pages too narrow to rank for a head term never got written. The unranked, the specific, the weird. They got pruned out of every content portfolio I’ve ever audited.

Some of these pages LLMs cite…and cite well.

This isn’t a vibe. AirOps spent the last several months running fan-out analysis across tens of thousands of real ChatGPT responses. They decompose prompts into the sub-queries the model actually retrieves against, then score which pages get cited and which get walked past. It’s the deepest empirical dataset we have on any answer engine. The findings appear to hold directionally across Perplexity, Claude search, and Google AI Overviews based on what teams in the space are seeing but the specifics vary by system and the rest of this piece is grounded in the ChatGPT data unless noted.

The picture is unkind to almost every editorial instinct the SEO industry has spent fifteen years building.

The thesis in one sentence:

Ranking still matters. Everything you did to rank doesn’t.

The mechanism: page becomes passage

Google ranks URLs. Answer engines cite passages. That two-word swap is the whole shift and most of the AEO advice you’ve read is downstream of getting it right.

When ChatGPT answers a question, the model doesn’t fetch your page. It fetches a passage. The pattern across retrieval-augmented systems is broadly the same: pages get chunked into passage windows of a few hundred tokens, each chunk gets scored against the query (typically through some combination of embedding similarity and lexical match), and the top chunks get pulled into the model’s context. The exact pipeline inside ChatGPT, Perplexity, and AI Overviews isn’t fully public and the systems differ in important ways. The directional principle holds across all of them: the unit of value is the passage, not the URL.

Your page’s domain authority gets you indexed. Your page’s ranking gets you retrieved. AirOps found that the first returned result for a fan-out query gets cited 58.4% of the time versus 14.2% for the tenth result, so SEO is still a precondition. Once a chunk enters the retrieval pool, it’s on its own.

Authority becomes local. A single page can be cited for one sub-topic and invisible for the other eleven on the same URL. Page-level signals like internal linking, topical depth, length, and comprehensive coverage don’t transfer cleanly down to the chunk. Every word on the page that isn’t the answer becomes a cost. Each paragraph of adjacent context dilutes the chunk’s relevance to the query that retrieved it.

It’s probably worth naming this.

The Retrieval Tax (working name. If you've got something cooler, I'm listening…reply and tell me). Every word on a page that isn’t the answer to the question being retrieved is a tax on the answer’s relevance. Ultimate guides pay the highest retrieval tax in content marketing. Focused answer pages pay almost none.

The AirOps fan-out work measures the tax in citations.

Before the three findings: 95% of the surface is invisible to your keyword tool

One precondition fact. Nothing in the rest of this piece makes sense without it.

The fan-out queries ChatGPT generates when it builds an answer are largely invisible to traditional keyword tools. In the AirOps dataset analyzed by ALM Corp, 95% of fan-out queries had zero monthly search volume in conventional keyword tools. Ahrefs, Semrush, Google Keyword Planner. None of them can see these queries.

The surface of your category is bigger than your keyword tool can see and the invisible part is where citation is decided. If your content strategy is downstream of a keyword tool, you are optimizing for 5% of the actual retrieval surface, and not the 5% that matters most for AEO.

Everything below follows from this.

Finding 1: Domain authority is inversely correlated with citation

Inversely correlated, not uncorrelated. The numbers aren’t subtle.

In the AirOps fan-out dataset, pages that get cited consistently have an average DA of 53. Pages that never get cited have an average DA of 56. The backlink gap is sharper: always-cited pages have around 1.1M backlinks on average; never-cited pages have around 3.2M. A 3x inverse gap. At every level of query match, the lowest DA quartile in the dataset performs as well or better than the highest.

The site-type breakdown is even more telling. The five highest-DA categories in the dataset are YouTube (DA 100), Wikipedia (95), major news (94), Reddit (92), and health publishers (90). Effectively identical authority profiles. Their citation rates range from 2.4% to 59.2%. Twenty-fold difference at essentially identical DA. The signal is somewhere else.

LLMs don’t penalize high-DA pages. The mechanism is more boring than that. The editorial behaviors that maximize DA (comprehensiveness, hedging, generalism, optimizing for head terms) are the same behaviors that maximize the retrieval tax. High DA selects for content that pays the most retrieval tax. The correlation isn’t punitive. It falls out of the mechanism.

This is the finding that breaks the link-building model of enterprise SEO. Links still matter for ranking. They still matter for getting crawled, indexed, and retrieved. The link-building budget that won you DA is no longer the budget that wins you citation, and the reallocation question is genuinely uncomfortable for any team whose marketing org chart has been organized around DA for the last decade.

Eli’s small-business framing is the same point on a different timescale. The local plumber has a DA of 12. He’s not in the link-building game. He’s also written the single most specific page on the internet about a P-trap, because it’s the only thing he was qualified to write about. The model picks his page over Wikipedia’s, not despite his DA but in part because of what high DA correlates with at the page level.

Finding 2: Ultimate guides bury the answer

A 4,000-word ultimate guide is an SEO masterpiece. For passage retrieval, it is a disaster.

Here’s why. The retrieval system chunks the guide into passage windows. The user’s question is narrow. The chunk containing your answer also contains hundreds of words about tangentially related topics, so its relevance score against the specific fan-out query that retrieved it gets diluted by the surrounding noise. A competing page that runs 800 words on one question chunks into a single window whose content sits much closer to the query. The model picks it.

AirOps shows this empirically. When primary query relevance is high, focused pages around 800 words outperform comprehensive guides at 5,000+. SparkToro covered the same finding under the right headline: the death of the ultimate guide. That framing is correct. Not “the difficulty of the ultimate guide.” Not “the new constraints on the ultimate guide.” The death of it.

Most enterprise content portfolios have spent the last five years consolidating narrow pages into hub guides because hubs ranked. Atomization, the opposite move, is what wins for citation. If you’ve spent the last two years consolidating, you’ve spent the last two years building the wrong asset for what’s coming next.

That’s not a comfortable sentence. It’s the sentence the data forces.

Finding 3: 26 to 50 percent subtopic coverage beats 100 percent

This one gives you a planning heuristic, which makes it the most operationally useful finding in the AirOps work.

For any seed query, the fan-out process expands into a set of sub-questions the model uses to assemble its answer. You can score any candidate page on how much of that sub-question set it addresses and how strong its primary query match is. When primary match is strong, citation rate peaks at 26 to 50 percent sub-topic coverage, then falls off above it. Pages that try to cover everything get cited less than pages that own a defined slice.

A page that owns three sub-questions definitively gets cited three times. A page that touches twelve sub-questions superficially gets cited zero.

This retires the keyword map as a content planning artifact. In its place: a sub-question map. Enumerate the questions in your category. Pick the 26 to 50 percent slice where you have practitioner authority, proprietary data, or a differentiated point of view. Build one page per sub-question. Abandon the rest.

The pages you don’t write are as strategic as the ones you do. Probably more.

What Eli sees in client work

1) An ecommerce page that never received a lot of search traffic because it was on a highly competitive search term, but is now seeing outsized clicks because it is featured in LLMs.

2) Commoditized product review content that no longer receives many clicks despite high rankings in search, but it leads to brand mentions in LLMs that likely, but can’t be proven, drives brand traffic.

3) On a personal level, when prospective clients reach out and say they found him on an LLM, he always asks for the prompt, and typically, the source citation that led to an LLM mention is on a page that might never have seemed like a good source. Examples include podcast show notes pages, bios from many years ago at conferences, or media mentions.

4) A client whose primary product was classified listings rearchitected their AEO strategy to have their local classified pages be mentioned as a source for users to find. These pages never really ranked in organic search, but now they are far more relevant because they are mid-funnel for LLM users.

5) Companies that have specifically doubled down on LLM-only content, with the expectation that they were going to get cited, didn’t see the results they wanted because they didn’t think through their whole user journey.

The playbook, asymmetric on purpose

The to-do list isn’t subtle. It’s also not symmetric. One of these moves matters more than the rest.

The big one: atomize. Audit your top 25 pages by historical SEO performance. Identify every page that contains more than one answerable question. Most will contain five to fifteen. For each answer that earns its own page, spin it out to a dedicated URL whose title is the question. Keep the original as a hub if it earns its keep on rankings, but the answers themselves need to live alone, with their own chunks and their own retrieval surface. Atomization isn’t free. It reshuffles internal linking, redistributes authority across more URLs, and creates cannibalization risk if the new pages aren’t differentiated enough. For priority topics where citation share is the actual goal, the gains outweigh the costs. For your weak-performing long tail, leave the guide alone. This is the move that takes a quarter and pays for the next two years. Nothing else on this list matters as much.

Specialize. Pick the 26 to 50 percent of your category’s sub-questions you can own deeply. Abandon the rest.

The Deletion Audit. This is the inversion of every content audit you’ve ever run. Pull the list of pages your team has flagged for sunset: low traffic, narrow topic, weird angle, no internal links, dead in Google. Filter for the ones that are still factually current and well-written. Then ask one question of each: is this the best answer to a specific question on the internet? The ones where the answer is yes are not sunsets. They are your AEO portfolio, hiding in plain sight because the SEO audit framework you inherited can’t see them. Most teams will find five to twenty pages they were about to delete that are quietly the best assets in their portfolio. Stop deleting them. Start linking to them.

Title-Query Convergence. The cleanest unilateral move on the list. The ALM Corp analysis of AirOps’ data found pages with 50%+ title-to-query word overlap get cited at 20.1%. Pages below 10% overlap get cited at 9.3%. A 2.2x lift driven entirely by what’s in your title tag. The actionable version: on narrow answer pages, your title should be the question, not a clever framing of the question. “How do I revoke an API key” beats “The Complete Guide to API Key Management” every time on a single-question page. Hub pages and category pages need a different titling approach because they still have to serve broader keyword rankings, so this is a tactic for the atoms, not for everything. Most teams haven’t made the move on their atoms because clever titling is what content marketers were trained to do. Untrain it where it costs you citations.

Measure citation, not rank. Pick a citation tracking tool. Pick a category. Run weekly. If you’re not measuring share of cited sources across ChatGPT, Perplexity, Claude, Gemini, and Google AI Overviews, you are flying blind on the part of the funnel that will be load-bearing by Q4.

One honest caveat before the prediction

Retrieval algorithms move fast. The AirOps findings reflect how ChatGPT was building answers when the data was collected. Six months from now the specifics will shift. The optimal coverage band may move. The DA correlation may compress or invert further. The exact title-overlap thresholds will drift. The numbers are not laws.

The direction is. The shift from page to passage, from comprehensive to specific, from generalist to specialist, from keyword map to sub-question map. Every retrieval system that matters is moving toward more of all of these, not less. Anyone betting against atomization, specificity, or measurable citation share is betting against where every answer engine is heading. The numbers will move. The direction won’t.

What I’d put money on

By the end of 2026, the ultimate guide stops being the default unit of B2B content (slightly sad here as a fan/reader/writer of long-form content). The hub-and-spoke model doesn’t disappear but it loses its position as the answer to every brief. The platforms that sold teams on hub-and-spoke are already pivoting. The risk isn’t with them. The risk is with the thousand B2B content shops that built their playbooks on top of those platforms and haven’t pivoted yet. They will either rebuild around answer atoms or they will lose meaningful share in the AEO surface of their categories.

The model rewards specificity. The model penalizes comprehensiveness. The model is the distribution system now.

Eli’s plumber didn’t know any of this. He just wrote the most specific page on the internet about a P-trap because that’s the only thing he was qualified to write about. The model found him.

The question isn’t whether the plumber was right. The question is whether your team can deliberately reproduce, at scale, across an enterprise content portfolio, in the next two quarters, what he did by accident.

Josh Grant and Eli Schwartz

Josh Grant is the founder of StackedGTM.AI and writes the Weekly Operator Brief. Eli Schwartz is the author of Product-Led SEO. Subscribe to his newsletter to stay on the cutting edge of SEO & AEO productledseo.com.

Data in this piece is drawn from AirOps’ fan-out research (The Fan-Out Effect, The Long Tail), ALM Corp’s analysis of the AirOps dataset, and SparkToro’s coverage. The retrieval mechanism descriptions reflect the standard pattern across retrieval-augmented systems and are not specific assertions about any one platform’s pipeline.

This is one of the longest piece I’ve ever written. I usually believe brevity is the soul of wit. This one I went deep on because the topic earned it.

The model in my head was Sean Ellis. Hacking Growth changed how I thought about my career. I had the chance to write something with a few months back and that experience reset my bar for what a flagship piece should be.

Mid-April to today. Steal the prompts. Steal the frameworks. Build on top of them.

Read time: ~30 minutes. Save it. Share it. Come back to it.

Now let’s go.

Two years ago, the game was clear.

Own the blue links. Own the category keywords. Displace your competitors in paid and organic. If you could do that, you got the traffic, you built trust on your website, you ran a funnel with predictable data at every stage. Hard. But legible. You could see it. You could manage it.

That game is over. Not evolving. Not shifting. Over.

Discovery, trust, comparison, the entire early buyer journey, has moved into a single conversational window. Your buyer opens ChatGPT. Types something like “what’s the best demand gen platform for a Series B SaaS company.” Gets three names back in eight seconds. Closes the tab.

Your website never loaded. Your funnel never started. Your sales team never got the ping.

There is no analytics event for this. Sometimes you catch a referral from ChatGPT or Perplexity when someone clicks through. But the shortlist moment, when your brand is named, evaluated, and either recommended or skipped, happens before the click. Before the session. Before you ever know a buyer was looking.

The thing recommending vendors is not a smarter search engine. It is something different. It browses. It evaluates. It cross-references multiple sources before it answers. It hands a shortlist to a human buyer who mostly trusts it.

It is, in every practical sense, the first salesperson in every B2B deal happening right now.

You did not hire it. You cannot train it. You cannot fire it.

And it is already talking to your buyers.

I have been writing about AEO since before most people agreed on what to call it. I published The Definitive 2026 Guide to AEO when people were still arguing whether zero-click was real. The best thing we can do right now is build in the wild, share what we find, and push the industry forward together.

This is The Shortlist. Let’s go.

The Buyer You Have Never Met

94% of B2B buying groups rank their preferred vendors before they ever talk to a sales rep. 77% of the time, they buy from that day one favorite. Not the best demo. Not the smoothest negotiation. The vendor they preferred before your sales team picked up the phone.

That is from 6sense’s 2025 Buyer Experience Report. Nearly 4,000 buyers. Not a small sample. Not an outlier.

The deal is decided before your team enters the room.

Now add this. 94% of those buyers used large language models during the buying process. Nearly two thirds used tools like ChatGPT and Perplexity as much as or more than traditional search. 45% said AI was their primary research method for identifying suppliers. Not secondary. Not a double-check. Primary.

Buyers form their day one shortlist using AI. That shortlist predicts the winner 77% of the time. Your team has zero visibility into any of it.

It gets sharper. AI platforms do not return ten options and let buyers browse. According to BrightEdge and Amsive research across millions of AI responses, the average AI platform cites 3 to 4 brands per response. The top 20 domains capture 66% of all AI citations.

That concentration is brutal. In traditional search, ranking fifteenth still gets traffic. You can improve incrementally. In AI-mediated research, the math is binary. You are cited or you are not. There is no page two of an AI answer.

George Bonaci, VP of Growth at Ramp, put it bluntly when I interviewed him for StackedGTM.AI:

“In traditional search, position two still gets clicks. In AI answers, there’s often only one recommendation. The citation layer is a power law, and we’re in the land-grab phase right now. The alpha is now.”

The downstream impact is not small. Early data from Averi.ai suggests AI-referred traffic converts 4.4 to 5.6x the rate of organic search. I saw this firsthand at Webflow. AI-referred visitors converted 6x higher than non-brand organic. Buyers who arrive from AI citation are not browsing. They are deciding. They show up already knowing your category, your positioning, and roughly where you stand against your competitors.

The AI did the work.

The direction of travel is not subtle. Gartner projects 90% of B2B buying will be intermediated by AI agents by 2028, with $15 trillion in B2B spend flowing through those exchanges. Timeline will be messier than a clean number. Direction is not in question.

The buyer has changed. The research process has changed. Your funnel is not where deals are won or lost anymore. It is downstream of a decision the AI already made.

The question is whether you are on the list.

How the Shortlist Gets Built

80% of the URLs being cited by AI agents right now do not rank in Google’s top 100.

Not page two. Not page five. Not indexed at all in traditional search. The content building your buyer’s shortlist is almost entirely invisible to your SEO dashboard. These are two separate games. Most GTM teams are only playing one.

Here is what actually happens when a buyer asks ChatGPT, Perplexity, or Gemini to recommend vendors.

The AI is not crawling your website in real time. It pulls from two sources. First, parametric memory: everything baked into the model during training. Second, retrieval augmented generation (RAG): real-time pulls from external sources the model trusts at the moment of the query.

RAG-driven citations carry significantly more weight than anything from training memory.

The practical implication: what other people say about you, in real time, in places AI trusts, matters more than what your own website says about you.

82% of links cited by AI come from earned media. Over 95% from non-paid coverage. Muck Rack’s Generative Pulse study, over one million AI responses.

Your homepage is not building your shortlist position. Other people’s content about you is.

Recency tightens the screw. More than half of all AI citations come from sources published in the last 12 months. The highest citation rate hits within seven days of publication. A brand that goes quiet for a quarter does not just lose momentum. It actively loses ground as newer content about competitors fills the retrieval layer.

Consistency is structural. Not optional.

Now the part most GTM teams miss completely.

ChatGPT, Perplexity, and Gemini are not the same system. They have fundamentally different citation models. Optimizing for one while ignoring the others means you are structurally invisible to a significant chunk of your buyers.

Yext analyzed over 6.8 million citations across all three. SEMAI analyzed 25,000 URLs over 60 days. The data is consistent. The differences are stark.

Here is the platform breakdown in one place.

A few notes on the table that matter operationally.

ChatGPT is the platform your buyers used this morning. It is also the only platform that meaningfully cites LinkedIn posts. A mid-size B2B company publishing “47% of our 200-respondent survey preferred X” beats a high-authority site saying “many businesses prefer X.” Specificity beats domain authority.

I want to be honest about something. Six months ago, more than 90% of our AI referral traffic at Webflow came from ChatGPT. My instinct was to optimize for ChatGPT and let the rest follow. The volume gap felt rational. That instinct made sense then. It does not make sense now. Enterprise adoption of Claude is accelerating fast. Gemini’s referral traffic grew 388% year over year. Enterprise buyers especially are living inside Claude and Copilot, not ChatGPT. The one your buyer uses at work and the one they use at home are increasingly different.

You need presence across all of them.

Gemini grows fastest and rewards owned-domain structure. If your website is not built for machine extractability, you are invisible on it.

Perplexity is the most underestimated. It is the only platform actively citing comparison pages and solution-specific content at scale. It is also the most citation-transparent: every claim links to a source. Your citations need to be airtight. The teams winning Perplexity have a real Reddit presence, comparison content, and niche publication coverage. The teams losing Perplexity have none of the three.

Before you read another word of this guide, do this.

I built a tool that runs your brand against ChatGPT, Perplexity, Gemini, and Reddit in real time. The Zero-Click Funnel Mapper shows every buyer question in your category, every AI answer, every competitor mention, and exactly where you are invisible. 90 seconds. Most brands score under 30.

That number is not a vanity metric. It is a structural diagnosis of your shortlist position right now.

Run it here: Zero-Click Funnel Mapper.

Only 11% of domains are cited by both ChatGPT and Gemini. The overlap is smaller than almost anyone expects. Winning on one platform guarantees nothing on another.

There is a deeper problem most teams have not yet named. The vast majority of AI conversations happening about your category never surface in any tool you currently use. They happen inside ChatGPT, Claude, Perplexity, and Gemini sessions that produce no clickthrough, no referral, no analytics event. Profound calls these dark queries and surfaces them through Conversation Explorer, a panel of 400M+ real anonymized user prompts refreshed weekly, with intent, sentiment, and demographic breakdowns. The volume of dark queries in B2B categories typically dwarfs the volume of measurable clicks by 10x or more.

One more signal that reframes everything. Brand search volume has a 0.334 correlation with AI visibility, the strongest single predictor identified in recent research. Backlinks show a weak or neutral relationship. Models favor brands people already search for directly. The more people look you up, the more the model treats you as a default authority.

Brand investment is now AI visibility investment. The two are the same thing.

Knowing where you appear, where you do not, and how you are described when you do, that is the starting point for everything that follows.

Most teams cannot see it at all.

That is the real problem.

Social Is Not a Channel. It Is Your Retrieval Infrastructure.

48% of AI search citations come from community platforms.

Not from your website. Not from your blog. From Reddit threads, YouTube tutorials, and LinkedIn articles written by people who have nothing to do with your marketing team.

85% of brand mentions in AI answers originate from third-party pages, not owned domains. Independent analysis of over 5.5 million LLM responses. Your homepage, your product pages, your carefully crafted brand narrative, they are the minority voice in how AI systems understand and represent your company.

The majority voice is your community. Or your competitor’s community, if yours does not exist.

The brands that built genuine communities years ago accidentally built citation infrastructure. Webflow, Notion, Figma, and Linear all benefit from years of community content they never planned as AI training data. Now that conversation determines their AI shortlist position.

The brands on the other side are traditional enterprise software companies. Sales-led. Content gated. No Reddit presence. No YouTube ecosystem. No community to speak of. Starting from zero on the layer that matters most. The gap is widening every month.

This is why the push for community marketing is not a trend. It is a structural response to how AI retrieval works.

Now the data your GTM team needs.

Reddit is the single most cited domain across LLM responses at a 40.1% citation frequency. It beats Wikipedia, YouTube, and every major news outlet. Analysis of 150,000 citations across 5,000 keywords. Google paid $60 million per year to license Reddit’s data for AI training. That number tells you exactly how much Reddit content is worth as a retrieval signal.

Reddit is not uniform. 88% of Reddit citations come from category-level queries. When a buyer asks “what is the best demand gen platform,” Reddit is where the AI turns first. When they ask about a specific brand, one third of citations check features, one third ask how to use something, one quarter seek factual detail. Reddit is shaping your category positioning and your product perception simultaneously, in conversations you are probably not part of.

YouTube has overtaken Reddit as the most cited social platform overall. 16% of LLM answers versus Reddit’s 10%. YouTube is no longer a traffic channel. It is a citation engine. The transcripts, chapter markers, and descriptions create exactly the kind of extractable text AI agents pull into answers about how products work and which option is best.

LinkedIn shows up consistently across every platform studied. Top social source for Copilot, DeepSeek, and Meta AI. The format that gets cited is articles, not posts. A LinkedIn post disappears in 48 hours. A LinkedIn article with a clear argument, specific data, and a named author becomes a retrievable asset that compounds.

Run a Reddit audit this week. Do not do it manually. Use AI to do the heavy lifting.

Open Gumloop. Drop in their Reddit Scraping node. Zero setup. Point it at your three most relevant subreddits, pull the top 50 posts and comments from each, and feed the output directly into Claude with this prompt:

“You are a forensic competitive intelligence analyst building a B2B citation strategy from raw Reddit data. I am giving you the top 50 posts and comments from [subreddit name], [subreddit name], and [subreddit name]. For every vendor mentioned in [your category], extract: (1) frequency of mention, (2) the exact phrases buyers use to describe them, (3) sentiment (positive, negative, mixed) with the specific objection or praise driving it, (4) which buyer pain points trigger each mention, (5) which vendors are recommended together and which are positioned as alternatives. Then identify the five highest-value content gaps: specific buyer questions where no vendor is clearly winning the answer. For each gap give me the exact question phrasing, the format that would win it (comparison table, how-to, listicle, deep guide), the first paragraph of a genuinely useful answer, and the subreddit and thread to seed the conversation. Mirror the actual buyer language. Do not sanitize it. Return as a structured report by vendor with a separate gap section.”

What comes back is a real-time map of the citation content AI agents are using to build your buyer’s shortlist right now. Which brands own the conversation. How they are described. What language buyers use that you are probably not using in your own content. Where the gaps are that nobody is filling.

Run it monthly. Lighter version: paste five Reddit threads directly into Claude and run the same prompt. Twenty minutes. More signal than most tool dashboards.

What to do with this section.

Identify the three subreddits your buyers spend time in. For B2B SaaS, typically r/sales, r/marketing, r/entrepreneur, plus category-specific communities. Build genuine, consistent presence. The 95/5 rule applies. 95% value, 5% brand. Authentic participation over time is the only thing that works. Fake community presence gets called out and actively damages your AI citation position when negative sentiment surfaces.

Search “best [your category] platform” on YouTube. If your brand is not appearing in those videos or producing comparable content, you are invisible on the fastest-growing citation platform. Start one video series this quarter. Not a product demo. A genuine educational series that answers the questions your buyers are actually asking.

Convert your three strongest LinkedIn posts from the last six months into full LinkedIn articles. Add data. Add a clear argument. Publish under your name. Posts drive engagement. Articles drive citations.

Audit your G2 profile today. G2 profiles with strong reviews, current information, and clear category positioning are pulled directly into AI answers as third-party validation. Stale or mispositioned profiles actively pull you off the shortlist.

The brands building community now are not just building audience. They are building retrieval infrastructure that will determine their AI shortlist position for the next three years.

The window is still open. It will not stay open forever.

What AI Agents Actually Want to Cite

Google asks: what is the best page for this query?

AI agents ask something different. They ask: what is the safest thing I can repeat without being wrong?

That distinction changes everything about how you write.

Google rewards depth, authority, and backlinks. AI agents reward clarity, extractability, and verifiability. A page that ranks number one on Google can be invisible in AI citation. A page that ranks outside the top 100 can be cited repeatedly because it answers one specific question with absolute precision.

This is the content architecture problem most GTM teams have not solved. They are writing for humans and for Google. They are not writing for the thing now doing the first round of vendor evaluation on behalf of their buyers.

44.2% of all LLM citations come from the first 30% of a piece of content. The intro. The opening. Not the conclusion. Not the middle. The beginning. AI agents scan for the answer before deciding whether to cite the source at all. If your opening is context-setting, background, or a slow build to the point, the agent has already moved on to your competitor’s page.

Every section of your content needs to open by stating the answer, not teasing it.

ChatGPT only cites 15% of the pages it retrieves. 85% of sources retrieved during a search are never cited. Your content can be found and still lose. Being indexed is not enough. Being structured correctly is what gets you from the retrieved pile into the cited answer.

The formats that get cited, based on analysis of 2,000+ cited pages.

Content with comparison tables achieves 2.8x higher citations than text-only equivalents. Adding statistics to content improves AI visibility by 41%. Princeton and Georgia Tech’s GEO study. The single most effective optimization technique they tested. Pages structured into 120 to 180 word sections earn 70% more citations than pages with very short or very long sections.

None of this is random. AI agents are not looking for the most insightful content. They are looking for the most extractable content. Content they can pull a specific passage from, attribute to a source, and repeat with confidence. If your content is written in flowing prose that requires reading the whole piece to understand, the agent cannot extract it cleanly. It moves on.

One more signal most teams overlook. Adding a visible “Last Updated” date to the top of a guide increased citation rate from 42% to 61% in one study. A 45% lift from a timestamp. Not from rewriting content. From signaling recency. Content updated within the past three months is twice as likely to be cited as older pages. AI agents weight freshness as a trust signal. Your best content from 18 months ago is losing ground every week you leave it untouched.

Before/after that makes this concrete.

Content that does not get cited:

“At our company, we believe demand generation is a critical component of any successful go-to-market strategy. In this guide, we will explore the various aspects of demand generation and how teams can think about building programs that drive results...”

Content that gets cited:

“Demand generation for B2B SaaS differs from lead generation in one critical way: lead gen captures existing demand while demand gen creates it. According to Forrester 2025, 89% of B2B buyers complete more than half their evaluation before contacting a vendor. That means demand gen must influence buyers before they know they need you.”

The second version opens with a direct answer, uses a specific data point with a named source, and can be extracted as a standalone passage without losing meaning. The AI can cite it confidently. The first version cannot be safely cited without including the whole paragraph, which agents rarely do.

Run this on your content right now. Paste the opening three paragraphs of your best performing page into Claude with this prompt:

“You are an AI agent doing vendor research for a B2B buyer. Read this content and answer three questions. (1) Can you extract a single self-contained passage that directly answers a specific buyer question without surrounding context? (2) If a buyer asked you to recommend vendors in this category, would you cite this content? Why or why not? (3) What is the single biggest structural change that would make this content more citation-worthy? Be specific to the actual text. Do not give general advice.”

What comes back is your content audit. The answers will be uncomfortable. That is the point.

What to do.

Audit your ten most important pages this week. Paste the openings into Claude with the prompt above. Rewrite every opening that fails the test. This single change will move your citation rate faster than any other optimization.

Add a comparison table to every piece of content that compares options, vendors, approaches, or outcomes. Tables: 2.8x higher citation rates. Not optional.

Add specific statistics with named sources. Not vague claims. Not “many companies report.” Specific numbers, specific sources, specific years. The 41% visibility boost from adding statistics is the single most effective optimization in the Princeton GEO study. You already have data. Start attributing it.

Add a visible “Last Updated” date to every cornerstone piece. Today. Set a calendar reminder to update each piece with at least one new data point every quarter. The 45% citation lift from a timestamp is the highest ROI, lowest effort optimization in this entire guide.

Build one comparison page for your category this month. “X vs Y vs Z: Complete 2026 Comparison.” Pricing, features, use cases, honest differentiators. The format Perplexity trusts most for bottom-of-funnel queries. The content your buyers are searching for at the exact moment they are building their shortlist. If you do not own it, your competitor will.

The brands getting cited consistently are not producing better ideas. They are producing more extractable ideas. Same insight. Different structure. Answer first. Data second. Source it. Update it. Make it easy for the agent to repeat without being wrong.

It will reward you for it.

You Cannot Manage What You Cannot Measure

Ramp 7x’d their AI visibility in weeks. Became the fifth most visible fintech brand globally.

Ramp was a community-oriented, content-driven brand with the raw material already in place. What they did not have was a system that told them where it was working, where it was not, and how to fix the gaps in real time.

That system is Profound.

Here is what ‘systematic’ looked like in George Bonaci’s own words. When I interviewed him for StackedGTM.AI in March 2026, he described the approach directly:

“We went from sporadic AI citations to dominating answers for queries we care about. How? We reverse-engineered what makes an AI cite you. It’s not keyword density. It’s not backlinks. It’s structured proof. Named customers. Specific problems. Quantified outcomes. Implementation mechanics. When a finance leader asks an AI ‘who should I trust to manage $50M in spend,’ the AI is looking for receipts.”

That is the play. The receipts. Profound is what makes the receipts findable, fixable, and shippable at speed. The Opportunities panel surfaced the specific category prompt clusters where Ramp was not appearing and which competitors were filling the gap. It surfaced the specific journalists, subreddits, and publications where Ramp’s competitors were getting cited and Ramp was not. Profound Agents generated the briefs and first drafts for the gap content using the citation patterns of pages that were already winning those exact prompts. Ramp’s team reviewed, refined for voice, shipped, and monitored what moved.

That feedback loop, running consistently for several weeks, is how a brand that was already strong became the fifth most cited fintech in AI answers globally. The reason this case study matters is not the 7x number. It is the speed. Visibility is the easy part. Acting on it before your competitors is the whole game.

I watched the same pattern at Webflow. We went from less than 2% CMS category share to owning roughly 60% of AI answers tracked in the CMS category. The infrastructure was identical to what Ramp ran. Identify the gaps with continuous monitoring. Ship the proof content into them. Watch what moved. Double down on what worked. Cut what did not. Same loop, different category, same result. Two case studies, both running the same play.

Now the bad news for everyone not yet running this loop.

Open your analytics dashboard right now.

You can see sessions. MQL volume. Organic traffic by channel. Cost per lead, pipeline by source, conversion rate by stage. Your dashboard is full of numbers and most of them are telling a story increasingly disconnected from what is actually happening to your pipeline.

Here is what your dashboard cannot show you.

It cannot show you that an AI agent researched your category this morning on behalf of a buyer at your top target account. It cannot show you that the agent named three competitors and not you. It cannot show you that the buyer formed a preference before they ever visited a website. It cannot show you that by the time that buyer eventually shows up in your funnel, if they show up at all, the decision is already 80% made and you are not the front runner.

That conversation happened. It left no trace. It is happening hundreds of times a day across your category.

78% of marketing teams have zero AI visibility tracking. No citation monitoring. No share of voice measurement. No way to know whether they are winning or losing the shortlist before sales gets involved. They are managing a growth motion increasingly decided upstream of everything they can see.

AI-referred traffic grew 527% year over year between January and May 2025. Most analytics platforms still misattribute most of it as direct traffic. You are almost certainly undercounting it significantly. The traffic you are missing converts at 14.2% on average versus Google organic’s 2.8%. The highest intent buyers in your funnel are arriving through a channel you cannot see clearly.

Not a minor measurement gap. A structural blindspot in how most GTM teams understand their own pipeline.

I wrote about the measurement foundation in How to Measure AEO. The Visibility, Comprehension, Conversion loop is the core framework. Visibility tells you if you are being seen. Comprehension tells you if you are being understood correctly. Conversion tells you if it is driving revenue. That loop is the right starting point and I would read it alongside this guide.

What I want to add here is a layer specific to the shortlist problem. Measuring AEO in general is different from measuring your shortlist position specifically. General AEO measurement asks whether AI surfaces your content. Shortlist measurement asks whether AI recommends your brand when a buyer is actively evaluating vendors. Related but not the same question.

I call the framework Answer Capture Rate. ACR.

ACR measures whether you are on the shortlist and how strongly you are positioned on it. It breaks into three dimensions.

Discoverability ACR. Are you being cited at all when agents research your category? When a buyer asks “what are the best demand gen platforms for a Series B SaaS company,” does your brand appear? In how many of those responses?

Most teams who run this audit for the first time find they are appearing in fewer than 20% of category-level queries. Often less than 10%. That is your starting point. Not a ranking. A binary presence or absence in the conversation building your buyer’s shortlist.

Accuracy ACR. When you are cited, is what the AI says accurate and aligned with your current positioning? This is the dimension almost nobody checks and the one that quietly kills pipeline quality.

I have seen companies where the AI was consistently describing them as a mid-market tool when they had repositioned upmarket 18 months earlier. Every buyer the AI sent them arrived with the wrong expectation. Qualification rates dropped. Sales cycles lengthened. Nobody could explain why.

The AI was recommending an old version of the company that no longer existed.

Check what the AI says about you. Today. You may not like what you find.

Depth ACR. When the AI recommends you, does it have enough to say? Does it describe your positioning clearly, cite specific capabilities, and make a confident recommendation? Or does it hedge or bury you in a list with no differentiation?

Depth signals whether the AI has enough source material to treat you as a trusted answer or a peripheral mention. Brands earning both citations and mentions are 40% more likely to resurface consistently across multiple AI responses than brands earning mentions alone.

Low ACR:

“You might also consider [your brand], which offers similar functionality to the options above.“

High ACR:

“[Your brand] comes up consistently for B2B SaaS teams focused on pipeline quality over volume. They are frequently cited alongside specific use cases for intent-based targeting and mid-market SQL conversion. Multiple independent sources rank them first for this buyer profile. They have a strong presence in community discussions and third-party reviews that corroborate the recommendation.”

The first version puts you on the list. The second makes you the recommendation. The difference is almost entirely determined by whether you have built the content, community, and citation infrastructure covered in the previous sections.

ACR ties the whole guide together. The platform breakdown is your Discoverability ACR problem. The community infrastructure is your Accuracy ACR solution. The content architecture is your Depth ACR lever. Measurement without the underlying work is just a dashboard showing you how invisible you are. The work without measurement is effort without a feedback loop.

You need both.

What to do.

Run your ACR baseline as an automated audit, not a manual one. The fastest path depends on which sprint path you are running.

On Profound, the ACR baseline is one Agent run. The Citation Gap Analysis template handles every dimension below across every tracked engine, with prompt volume data attached to every gap, in minutes rather than hours. You will keep using this template for ad-hoc audits long after the initial baseline.

On the DIY stack, you can approximate the diagnostic through Claude with Perplexity MCP. Five-minute setup, instructions in Day 1 of the sprint. The output is directional, not ground truth, for the reasons covered in Day 1. Run this prompt:

“Run a complete ACR audit for [your brand] in the [your category] category. Across ChatGPT, Perplexity, and Gemini, execute these three queries three separate times each over the next 48 hours to account for response variability: (1) What are the top three [your category] platforms for a [your ICP] company? (2) Compare [your brand] vs [competitor one] vs [competitor two]. (3) Tell me about [your brand]. What do they do and who is it for? For every response, score me on three dimensions: Discoverability (am I cited at all, in what position, alongside which competitors), Accuracy (is the description of my company correct and current), and Depth (does the AI have enough to make a confident recommendation or am I a hedge mention). Then synthesize: which of the three ACR dimensions is my biggest gap, which platform is my weakest, and which competitor is taking the citation position I should own. Return as a structured report with an executive summary, score by dimension, platform-by-platform breakdown, and three highest-leverage actions ranked by impact.”

What comes back is your ACR baseline. Two hours of work compressed into one autonomous run. More about your actual market position than most quarterly business reviews.

Tag AI referral traffic separately in GA4 today. Custom channel group for ChatGPT, Perplexity, Claude, Gemini, and Copilot referrals. You need to see this traffic clearly, not buried in direct. At Webflow, AI-referred visitors converted 6x higher than non-brand organic. That number makes the case at the executive level faster than any framework presentation.

Watch branded search in Google Search Console as a lagging indicator. When AI agents recommend you and buyers do not click through immediately, many return later via branded search. Rising branded search with flat non-brand organic is often AI driving upstream awareness that converts downstream.

Build a prompt library of 20 to 30 category-level and competitor queries that reflect how your buyers actually research. Run the full library every two weeks via the same MCP setup. Consistency matters more than frequency. You cannot spot trends from a single data point.

That gets you the diagnostic. What it does not get you is the operating system.

The reason Profound is the standard is not that it monitors citations. Plenty of tools do that, and Claude with MCP can do the diagnostic version yourself. The reason is that Profound is built as an agent layer, not a dashboard. Five million citations processed daily through Answer Engine Insights. Dark query data through Conversation Explorer, a panel of 400M+ real anonymized user prompts that never produce a click and never appear in any GA4 report. These are the conversations actually shaping your category. Prompt Volumes data attached to every topic, so you know whether a citation gap is worth $500 in monthly demand or $50,000. Continuous competitor displacement tracking, not on-demand audits. The Opportunities panel that does not just tell you you are losing. It surfaces the specific journalist actively covering your space, the specific subreddit thread where you should appear, the specific content gap with measurable prompt volume behind it.

And then Profound Agents generate the fix.

That is the difference. Manual diagnostics tell you where you stand at a moment in time. Claude with MCP automates the diagnostic. Profound runs the diagnostic continuously, attaches it to dark query volume you cannot see manually, and ships the content that closes the gaps. Most AEO tools surface a problem and hand you a report. Profound surfaces the problem, generates the AEO-optimized brief and first draft trained on citation patterns for your specific category, and routes it for your approval. The intelligence loop and the execution loop run inside the same platform.

That is what makes it the operating system for shortlist strategy, not just a visibility tool.

The teams building measurement infrastructure now will have compounding data advantages that are very hard to overcome later. Every month of clean citation data is a month of pattern recognition your competitors do not have.

Most teams will read this section and add it to the list of things they mean to do.

The ones who actually build the measurement habit in the next 30 days will be operating with fundamentally better information than everyone else in their category.

In a world where the shortlist is being built before your sales team gets involved, better information is not a nice-to-have.

It is the whole game.

Your 7-Day Shortlist Sprint

By the end of this sprint you will have four autonomous Agents running in the background of your business permanently. They monitor your category. They track your citation position. They generate fix content when you drop off the shortlist. They deliver intelligence to your Slack before you sit down at your desk Monday morning.

Real talk on the time commitment. The full sprint runs roughly 12 hours on Profound. The DIY approximation runs 18 to 24 hours, plus ongoing maintenance, plus a permanent gap in data quality that does not close no matter how much time you spend.

Two paths run through this guide. The Profound path is the system. The DIY path is what you can approximate when you cannot get on Profound yet, with the honest caveat that you are working from a fundamentally different and weaker dataset. Not the same outputs slower. Different outputs, structurally weaker.

I will be specific about why throughout. Pick your path and start Monday.

Do the days in sequence. Each one builds on the last.

Day 1. The Intelligence Layer.

Time: 1 to 3 hours depending on path. Output: a forensic competitive intelligence brief plus your automated ACR baseline.

Most teams spend weeks building competitive intelligence. An Agent does it in one session.

On Profound.

Open the Citation Gap Analysis Agent template. Enter your category and your top three competitors. Hit run.

What comes back is everything a senior competitive analyst would produce in a week. Citation share by competitor across ChatGPT, Perplexity, Gemini, Claude, Copilot, Grok, AI Overviews, and AI Mode. The prompt clusters where your competitors are cited and you are not. Prompt volume data behind every gap, pulled from Conversation Explorer, Profound’s panel of 400M+ real anonymized user prompts refreshed weekly. Demographic breakdowns: which roles are asking which questions, in which geographies, with what intent. Every URL the engines are citing for each competitor, named and linked.

This is the workflow that took Ramp from sporadic citations to 7x AI visibility in weeks. It is the same workflow that took Webflow from 2% CMS category share to roughly 60% of AI answers in the category. It is not a manual process. It is not theoretically a manual process.

For your ACR baseline, point the same Agent at four query types. Category recommendations. Brand description. Head-to-head comparisons against your top two competitors. Market structure. Save the run. That is your before state. You will compare against it on Day 7.

Then schedule the Agent to re-run weekly. Profound diffs every subsequent run against the baseline automatically and posts the delta to your Slack.

That is Day 1 on Profound. One Agent. Minutes, not hours.

On the DIY stack.

The closest substitute is Claude Desktop with Perplexity MCP and a few hours of prompt engineering. Shape of the work: query Perplexity through Claude, run multiple searches per competitor, ask Claude to synthesize a brief, then manually run ACR queries by hand across each AI platform and compile the output yourself.

You will get a usable brief in about three hours. You should also know exactly what you are not getting.

You are not getting Conversation Explorer. There is no public-web equivalent. The 400M+ prompts behind your category, the ones that never produce a click and never surface in any tool you have access to, are not retrievable through any combination of Claude and Perplexity. You will see what is cited. You will not see what is being asked inside the actual AI engines, which is the data that decides your shortlist position.

You are not getting ground truth. Perplexity searches the public web. Profound’s Answer Engine Insights captures actual AI engine responses from a real-user panel. The DIY brief tells you what Perplexity thinks of your category. The Profound brief tells you what every major AI engine is saying when a real buyer asks. These are different datasets, not different views of the same dataset.

You are not getting continuous tracking. Your DIY baseline is a snapshot. Without a scheduler tied to actual citation data, every subsequent comparison is also a snapshot. You will detect changes by re-running the work, not by being told what moved.

This is not a gap that closes with more time. It is a gap in the underlying data layer that the DIY path runs on.

Save your Day 1 outputs from whichever path you ran. Do not touch them again until Day 7.

Day 2. The Competitive Deconstruction and Batch Rewrite.

Time: 3 to 4 hours. Output: ten pages rewritten for citation readiness, five comparison tables, every rewrite scored before it goes live.

Knowing you are not on the shortlist is not enough. You need the exact mechanism putting your competitors there.

Pull the cited pages.

From your Day 1 brief, identify the three competitors appearing most frequently. You need five cited pages from each.

On Profound, this is one click. The Competitors view in Answer Engine Insights returns citation share by prompt cluster with the exact URLs each engine is citing for each competitor. You get the actual pages the AI is recommending right now, not the pages you assume are doing the work.

On the DIY stack, you search for them manually. Run the head-of-category prompts across ChatGPT and Perplexity, copy the cited URLs as they appear, deduplicate, pick the top five per competitor. Plan for 45 minutes of clicking. Plan also for the data being noisy: you are seeing what two engines surface for a handful of prompts at one moment in time, not the citation landscape across every engine continuously.

Either way, you end with fifteen pages.

Reverse-engineer the citation formula.

Feed all fifteen pages into Claude. Ask for a forensic structural analysis: the exact opening sentence patterns, the data-to-prose ratio per 100 words, the section length guidance, the comparison table structure, the “last updated” approach, the schema signals. Tell Claude to return a replication blueprint specific enough that a writer could execute it tomorrow morning without asking questions.

What you get is a citation formula built from your actual competitive set. Not theoretical. Theirs.

Apply it to your ten most important pages.

Pull the opening three paragraphs of your ten highest-leverage pages. Paste them into one Claude session. Ask for each opening to be scored on three criteria. Opens with a direct answer. Contains a specific data point with a named source. Can be extracted as a self-contained passage without losing meaning. Then have Claude rewrite the opening sixty words of each page to pass all three criteria using the blueprint, preserving brand voice, ruthlessly optimizing for AI extractability.

Ten pages. One session. Implement the rewrites today.

Add comparison tables to your five most important pages.

Same Claude session. Ask for a comparison table comparing your approach to the two most common alternatives. Dimensions should be the outcomes B2B buyers in your category care about, not specs. The table should stand alone as a screenshot a buyer could use to evaluate. Returned as clean HTML you paste into your CMS.

Five comparison tables. 2.8x citation rates.

QA before you ship.

If you are on Profound, run every rewrite through Content Optimization before publishing. The AEO Content Score is a machine-learning metric built from millions of top-cited pages across AI engines. It tells you whether a draft is structurally optimized for citation before it goes live. Content Optimization accepts URL, file upload, or pasted text, so unpublished drafts work the same way as live pages.

This score does not exist anywhere else. The training corpus is the millions of pages AI engines are actually citing across the open web, captured continuously. You cannot reproduce it with a Claude prompt because Claude does not have access to that corpus. You can use Claude to apply general AEO heuristics. That is a different and weaker quality gate.

If you are not on Profound, the QA gate is your own judgment. Ship anyway. Iterate next sprint.

Publish everything before end of day.

Day 3. Agent Two. Your Autonomous Community Intelligence System.

Time: 1 to 3 hours depending on path. Output: a permanent community intelligence Agent dropping reports into Slack every Monday at 6am.

48% of AI citations come from community platforms. You are building the infrastructure to listen to them automatically.

On Profound.

Open a new Agent. Add four nodes.

Node 1, Web Scraping. Point it at your three target subreddits, top 100 posts and comments each. Profound’s scraping node handles auth, rate limits, and structure. No external tool, no separate API key.

Node 2, Prompt LLM. Paste in the analysis prompt below. Pick any of the 16 reasoning models the platform supports.

Node 3, Slack. Output routes to your category-intelligence channel.

Node 4, Schedule. Every Monday at 6am.

One Agent. Profound’s nodes handle the whole job. The Reddit data is connected to your visibility tracking, so when a thread starts getting cited by AI engines, the same workspace tells you. The community layer and the citation layer are wired together.

The prompt for Node 2:

“Analyze these Reddit discussions as a competitive intelligence analyst building a citation strategy for a B2B vendor in [your category]. For every competitor mentioned extract: (1) frequency of mention, (2) the exact language buyers use when recommending them, (3) sentiment (positive, negative, mixed) with the specific objection or praise driving it, (4) the pain points that trigger each mention, (5) the objections raised. Then identify the five highest-value content opportunities: specific questions where no vendor is clearly winning the answer and where genuinely useful content would earn upvotes and become a citation source for AI agents. For each opportunity give me: the exact question phrasing, the ideal content format, the first paragraph of a genuinely useful answer, the specific subreddit and thread to seed it in, and the buyer language I should use that mirrors how they actually talk. Write the answer paragraph in operator voice. Not consultant voice. Return as a structured report by vendor with a separate opportunities section at the bottom and a one-line executive summary at the top.”

Every Monday before you wake up, the Agent scrapes your communities, processes the data, posts the report to Slack. You never manually check Reddit again.

On the DIY stack.

Shape of the work: Gumloop handles the Reddit scrape, Claude API processes the data, Slack node delivers the message. You wire them together in Gumloop’s interface and schedule the workflow.

Three external tools. Three sets of credentials. Three failure points when any one of them changes their API. Plan for two hours of setup and a permanent maintenance tax.

The deeper problem is structural. Your Reddit intelligence is now isolated from your citation tracking. When a Reddit thread starts getting cited by AI engines, you have no signal that connects the two. The community insight is sitting in one tool, the citation data is sitting somewhere else, and the correlation between them lives in your head if it lives anywhere.

Either path: the entity consistency audit.

This stays in Claude regardless. One-time setup, not a recurring workflow. Feed Claude the actual text of how your brand is described across five surfaces: website homepage, G2 profile, LinkedIn company page, most recent press release, most-cited blog post.

“Analyze these five descriptions of [your brand] for: (1) consistency of category language, (2) consistency of ICP description, (3) consistency of key differentiators, (4) consistency of use case framing, (5) consistency of positioning. Identify every point of inconsistency. For each inconsistency explain specifically what citation damage it causes: how does an AI agent’s understanding of our brand get confused or diluted by this gap. Then write a single canonical brand description of 75 words optimized for AI entity clarity. Give me the exact text to use on each surface to make them fully consistent. Do not give me general guidance. Give me the specific words. The description should open with the answer to ‘who is this for’ before describing what the company does.”

Propagate the canonical description everywhere today. G2, LinkedIn, homepage meta, press kit. One of the fastest Accuracy ACR improvements available. The AI cannot describe you accurately if you describe yourself differently on every surface it checks.

Day 4. Profound Closes Your Gaps.

Time: 3 to 4 hours including pitch drafting. Output: a comparison page live in your CMS, three earned media pitches sent, your first round of Profound Agents content shipped.

Today you go from intelligence to published content without writing the first draft yourself.

Open the Opportunities panel. Three named gaps are waiting from the past week of dark queries through Conversation Explorer. Not generic suggestions. Specific, scoped, prioritized opportunities with prompt volume data attached.

The pattern looks like this. A category-level prompt cluster where you appear in zero of twelve tracked AI responses, with measurable monthly prompt volume behind it. A specific journalist at a trade publication who has cited two of your competitors in the past 30 days but never you, named, with the articles linked. A Reddit thread with 47 upvotes asking “has anyone used [your category] for [specific use case]” where the top three responses recommend competitors and never mention you, surfaced because Profound is correlating its community scraping with its AI citation tracking.

Click Run on Profound Agents for the first gap.

Profound pulls the citation patterns from competitors winning that exact prompt cluster. It generates a brief that includes the opening sixty words, the data points needed with source attribution, the section structure, the comparison table dimensions, and the schema requirements. It then generates a full draft following the brief, built on your brand kit and tone guidelines.

The content is trained on the citation patterns winning your category specifically. Not generic AEO advice. The actual cited URLs in your space, in real time. This is the differentiator most teams miss when they think they can replicate Profound with Claude. Claude can write to a brief you give it. It cannot write to a brief built from the citation patterns of your actual category, because Claude does not have access to those patterns.

You review. You refine the voice. The CMS publish node (WordPress, Sanity, Contentful, or Framer) pushes the draft to your CMS without you leaving the Agent. No copy-paste. No third tab. No separate deployment step.

That entire workflow, from gap surfaced to draft generated to ready for review to published, takes about 30 minutes. The first time you do it, it feels like watching a junior content marketer who happens to know everything about AI citation patterns work in real time. By the third gap, it feels like infrastructure.

The first thing you build today is your comparison page. “[Your Brand] vs [Competitor One] vs [Competitor Two]: Complete 2026 Comparison.” Summary table. Buyer profile fit for each option. Honest trade-offs. Answer-first. Schema-ready. Profound Agents builds it. You review. It goes live.

While Profound builds, identify your three highest-value earned media opportunities. The Opportunities panel has surfaced journalists by name with citation history attached. The pitch drafting runs in the same Agent. Output lands in your Slack with the email pre-written and the publication details attached. You review and send.

Three pitches out today. 82% of AI citations come from earned media. One quality placement does more for your shortlist position than 20 posts on your own domain.

A note for readers on the DIY stack. Today is the day the gap shows up. You can detect that competitors are taking citation positions, roughly. You cannot generate the content that recovers those positions at the same quality, because your content generation has no access to the citation patterns winning your category. You will write the comparison page yourself. You will write the pitches yourself. You will identify the journalists yourself, without a panel telling you which ones are actively citing your competitors right now. Plan for a full day. Plan also for the output to be a meaningful step below what Profound generates in 30 minutes, not because Claude is weak, but because the input data is different. Claude with general AEO guidance produces general AEO content. Profound Agents produce content patterned on what is actually winning your category this week.

Day 5. Write. Your Voice. Your Intelligence.

Time: 1 to 2 hours. No agent work today. Output: one LinkedIn article published under your name.

You have spent four days watching agents work. The Profound brief gave you competitive intelligence nobody on your team had before, because it surfaced what AI engines are actually citing rather than what the public web says they might cite. The community agent showed you exactly what language your buyers use. The Opportunities panel showed you where you are invisible and why.

Now use all of it to write something only you can write.

Pick the single most surprising insight from this week. The one that changed how you think about your category. The one that, if your readers understood it, would change how they operate tomorrow.

Write a LinkedIn article around it. 600 to 800 words. Open with your most counterintuitive claim. The kind a reader stops scrolling for. Support it with three specific data points from your Day 1 brief. Make one of them something most people in your space have not seen yet. Close with one specific action your reader can take this week.

Do not use Claude to write this. Use your Day 1 brief to find the data. Use your Day 3 community analysis to check you are using the language your audience actually uses. The argument, the structure, the voice. Those are yours.

This is the content that builds your personal citation authority. Profound Agents generate structured content at scale. They cannot generate the genuine operator perspective that makes people trust you specifically. The agents handle everything extractable and structural. This is the one thing that requires being you.

Publish it today. The most important piece of content in this entire sprint.

Day 6. The Autonomous Monitoring Stack.

Time: half to full day depending on path. Output: two more agents running permanently. The closed-loop content recovery system. The weekly ACR briefing.

Today you build the infrastructure that makes everything permanent. After today you are not running a shortlist strategy. You are supervising an autonomous system that runs one.

On Profound.

Both agents run inside the platform. No external orchestration. Block half a day.

Agent Three. Citation recovery. Four nodes.

Node 1, Trigger. Native Profound alert when visibility drops more than 10% on any tracked prompt cluster. Built into the platform on continuous citation capture. You are notified within hours of the drop, not weeks.

Node 2, Prompt LLM. System prompt:

“You are a citation recovery strategist. Visibility on [cluster name] dropped significantly this week. Diagnose: (1) why this likely happened, (2) which competitor probably filled the gap, (3) what specific content fix would recover the position. Return a two-paragraph diagnosis followed by a content brief: title, opening 60 words, three required data points with named sources, target word count, citation format requirements.”

Node 3, Profound Agents content generation. The brief from Node 2 flows directly in. Output is a full draft built on your brand kit, tone guidelines, and the citation patterns winning your specific category in real time.

Node 4, Slack with native approval step. The draft lands in your channel with a one-click approve button. On approval, the CMS publish node fires (WordPress, Sanity, Contentful, or Framer, whichever you are on). The post goes live.

Gap detected. Diagnosis written. Fix generated. Approved. Published. Your only contribution was one click.

Agent Four. Weekly ACR briefing.

Take the Citation Gap Analysis Agent you built on Day 1 and schedule it to re-run every Monday at 7am. Add a Conditional node: if any metric moves more than 10% versus last week, flag it. Add a Slack node that posts the diff to your channel.

Same Agent you built on Day 1. Now it runs forever and tells you what moved.

On the DIY stack.

You can build something with this shape. You should know what it actually does before you commit a day to building it.

Make.com orchestrates the loop. Your AEO monitoring tool fires a webhook on visibility drop. Make.com catches it, routes to Claude for diagnosis, routes Claude’s output to a content generation step, sends the draft to Slack with an approval button, pushes to your CMS on approval.

Four problems with this loop, in order of severity.

Your trigger is wrong. You have no native citation drop alert on the DIY stack. You have scheduled scans of public proxies. By the time a “drop” surfaces, your competitor has been winning that prompt for days or weeks. Profound’s alert fires within hours of the actual capture. Yours fires when your scheduled scan happens to catch it.

Your diagnosis is generic. Claude is reasoning from prompts you wrote, not from category-specific citation pattern data. It will produce a plausible-sounding diagnosis. It will not be informed by what is actually being cited in your category this week, because Claude does not have access to that data.

Your content is generic. Claude is generating from general AEO guidance on the open internet. Profound Agents are generating from the actual cited URLs in your category, refreshed continuously. The outputs read differently to AI engines because they are structurally different.

Your maintenance is permanent. Block a full day for the initial build. Plan for breakage every time any of the four tools updates their API. The Profound version is one Agent with no integration layer to break.

For Agent Four on the DIY path, the Claude API runs your prompt library on a Make.com schedule. The DIY recovery loop is firing late on partial signals, diagnosing without category context, generating from generic guidance, then waiting for the next scheduled scan to find out if anything changed. It is real work. It is also work running on materially weaker inputs than the Profound version, every single time it executes.

Either path: set up your GA4 AI traffic channel today.

Custom channel group for ChatGPT, Perplexity, Claude, Gemini, and Copilot referrals. Tag separately from organic. AI-referred traffic converts at 14.2% versus Google organic’s 2.8%. You need this number every week. In six months it will be the most important number in your performance review.

Day 7. Review, Measure, Sprint 2.

Time: 2 to 3 hours. Output: Sprint 2 brief built on actual before-and-after data from your category.

The agents have been running for a week. Today you see what they built.

On Profound, the comparison is automatic. The Citation Gap Analysis Agent has been re-running every day with results saved. Open the Day 7 run and compare against the Day 1 baseline. Profound’s diff view surfaces every change in citation position, every movement on every tracked prompt, every competitor displacement. You read the diff, not the raw data.

Then run this prompt inside a Profound LLM node, with the Day 1 and Day 7 reports passed in as context:

“I ran my full ACR audit on Day 1 and Day 7 of a seven-day shortlist sprint. Analyze the complete trajectory: which dimensions of my ACR improved and by how much, which stayed flat, which declined. What do the patterns tell me about which specific actions had the highest citation impact? Which platform showed the most movement and why? Then give me my Sprint 2 brief: the five highest-leverage actions for the next 30 days, ranked by expected ACR impact, with specific reasoning for each recommendation based on what the data shows actually moved this week. Make this a concrete plan I can hand to my team Monday morning. No frameworks. No general advice. Specific actions with owners and outputs.”

What comes back is a Sprint 2 brief built from your actual category data. Not a framework. A specific action plan from an agent that watched your sprint happen.

There is a compounding effect worth naming here. Every week the Citation Gap Analysis Agent runs adds another data point to your category’s citation history inside Profound. Sprint 2’s diff is against Sprint 1’s baseline. Sprint 4’s diff has a month of trend data behind it. By month six, you have continuous citation data nobody else in your category has. Decisions get better the longer the system runs, because the input data compounds. This is a moat that gets stronger with time. You cannot bootstrap into it after the fact.

On the DIY stack, the same comparison takes longer and produces a thinner result. You manually run every prompt in your library across every platform a second time, copy the outputs into Claude, ask Claude to compare against your Day 1 baseline, synthesize the brief. Plan for two hours of clicking before you get to the analysis. Plan also for the diff being a comparison between two snapshots of two Perplexity-based proxies, not a comparison between two captures of actual AI engine behavior. The Sprint 2 brief you get is built on the same data layer as the Sprint 1 brief: useful, approximate, and not improving over time the way the Profound version is.

What is running autonomously after Day 7.

The shape depends on which path you built.

On Profound, four agents run on real citation data. Citation Gap Analysis re-running weekly against actual AI engine captures with a diff to Slack. Community Intelligence scraping subreddits and correlating with your citation tracking, posting to Slack at 6am Monday. Citation Recovery firing on real drops detected within hours, generating content from category-winning citation patterns, routing for approval, publishing to your CMS. Weekly ACR Briefing posting Monday morning summaries from a continuously updating dataset. All four use native Profound nodes. No external orchestration layer. The system improves every week because the citation history compounds.

On the DIY stack, four agents run on public-web approximations. A Perplexity Space updating every Monday from indexed search results. A Gumloop Reddit workflow processing community data in isolation from your visibility tracking. A Make.com automation triggering on scheduled scans of proxies for AI citations. A Claude API monitoring agent running your prompt library Monday at 7am on the same proxy data. The agents do real work. They are also producing a structurally weaker output every time they run, because the data layer they act on is not what AI engines are actually doing.

The DIY system runs. It does not improve. It cannot, because it has no access to the data layer that makes improvement possible.

Most teams will read this guide and add it to the list of things they mean to do.

The ones who actually build the system in the next 30 days will be operating with fundamentally better information than everyone else in their category.

In a world where the shortlist is being built before your sales team gets involved, better information is not a nice-to-have.

It is the whole game.

What Monday Morning Looks Like After Day 7.

6:00am. Your community intelligence Agent drops the weekly Reddit report into Slack. Community sentiment, vendor mentions, content opportunities, buyer language. Correlated with your citation tracking. All processed by an LLM, all surfaced in plain English.

7:00am. Your ACR briefing Agent posts the weekly shortlist summary, comparing this week’s actual AI engine citations against last week’s. What moved. What did not. What to do about it.

7:15am. Profound checks for any visibility drops from the past week. If your brand dropped on any tracked prompt cluster, Citation Recovery has already diagnosed the cause and generated the fix content using the citation patterns winning your category right now. Waiting for one-click approval in your Slack.

8:00am. You sit down. You did not run a single search. You did not manually check Reddit. You did not audit your citation position. You did not generate any content. Four agents did all of it while you slept, running on real AI engine data, working from a citation history that gets richer every week.

You review. You approve. You decide what comes next.

That is what running a shortlist strategy looks like in 2026.

Your competitors are still doing it manually.

Start Monday.

FAQ

What is Answer Capture Rate (ACR)?

Answer Capture Rate measures whether and how strongly an AI agent recommends your brand when a buyer is actively evaluating vendors. It breaks into three dimensions: Discoverability (do you appear at all in category-level recommendations), Accuracy (is what the AI says about you correct and aligned with your current positioning), and Depth (does the AI have enough source material to make a confident recommendation versus a peripheral mention). ACR is more specific than general AI visibility because it isolates buyer-intent moments rather than broad awareness moments.

Which AI platform should I prioritize first?

Optimize for the platform your buyers actually use. For most B2B audiences in 2026, that means starting with ChatGPT, where 68% of B2B researchers have weekly usage. Then layer in Perplexity for bottom-of-funnel comparison queries, then Gemini for technical buyers and enterprise procurement. Enterprise buyers increasingly research inside Claude and Copilot. The wrong move is picking one and ignoring the others. Only 11% of domains are cited by both ChatGPT and Gemini. Coverage matters more than depth on a single platform.

How long does it take to meaningfully move ACR?

First citation movement typically appears within 2 to 4 weeks of consistent execution. Meaningful Discoverability gains take 60 to 90 days. Sustained Depth and Accuracy gains take 6 months. The variable that determines speed is not budget. It is consistency of community presence, content publishing, and earned media. Brands with existing community strength move faster. Ramp moved 7x in weeks because they had the raw material in place. Brands starting from zero on community take longer regardless of how much content they ship.

Do I need a tool like Profound, or can I do this manually?

You can do it manually. I did for a bit. The DIY stack in this guide works.

The honest accounting is that what takes four tools and 18 to 24 hours of setup outside Profound takes one tool and a fraction of the time inside it. And three capabilities have no real DIY substitute. Conversation Explorer surfaces 400M+ real anonymized prompts, the dark queries that never produce a click. Answer Engine Insights tracks competitor displacement continuously, not at quarter-end when pipeline has already softened. Profound Agents generate content trained on the citation patterns winning your specific category, not generic AEO advice.

Manual diagnostics are a starting point, not a strategy. The teams winning the shortlist are running Profound as the operating system underneath it.

The Shortlist

Go back to where this started.

A buyer at a company you have been trying to reach opens ChatGPT. Types a question. “What is the best demand gen platform for a Series B SaaS company.” Waits eight seconds. Three names come back. They read them. They close the tab.

Your website never loaded. Your sales team never got the ping. Your funnel never started.

That moment happened somewhere in your category today. It will happen again tomorrow. And the day after.

You came to this guide not knowing how the list gets built. You are leaving it knowing exactly which sources get trusted, what content gets cited, and why some brands show up every time while others do not exist in that conversation at all.

The brands on that shortlist did not set out to win AI discovery. They built communities before anyone called it retrieval infrastructure. They structured their content before anyone called it answer-first formatting. They earned press coverage and showed up on Reddit and published LinkedIn articles because that is how they built trust with humans. It turns out that is exactly how you build trust with the agents now making recommendations on behalf of those humans.

They were not playing a different game. They were playing the same game earlier.

That is the only real variable left. Not budget. Not team size. Not technical sophistication. The brands winning the shortlist right now started doing the right things before it was obvious those things mattered.

I built this play at Webflow. I have watched the same pattern across the companies I advise. The pattern is always the same. The brands that treat this seriously early get an advantage that is genuinely hard to close later.

The buyer who opened ChatGPT this morning in your category got three names back.

The only question that matters from here is whether tomorrow they get yours.

StackedGTM.AI is built for operators running real GTM motions in an AI-first market. No recycled frameworks. No consultant speak. Real research, real data, real operator POV on what it takes to win. Subscribe at StackedGTM.AI.

Google’s Search Central team quietly published a new document on May 15. It’s called Optimizing your website for generative AI features on Google Search.

Most of the coverage zeroed in on one line. From Google’s perspective, AEO and GEO are still SEO.

That line is true. It’s also not the interesting part.

The interesting part is at the end of the doc, in the section nobody is quoting.

I’ll get there. First, what Google actually said…

What’s in the doc

The guide is focused and short. It covers five things:

1. How generative AI search actually works inside Google

2. Foundational SEO practices that still apply

3. Local business and ecommerce details

4. A “mythbusting” list of tactics you can ignore

5. Initial guidance on AI agents accessing your site

The headline framing is that AI search runs on the same systems as regular Search. Retrieval-augmented generation (RAG) pulls from the existing index. Query fan-out generates related queries to find supporting content. The ranking signals are the same.

If you’ve been working in this space, none of that is news. The novelty is that it’s now in official Google documentation. The mechanics that AEO consultants have been talking about for the last 18-24 months are confirmed by the source.

The mythbusting section is the operator gift

The most useful part of the doc is the list of things Google tells you to ignore.

• llms.txt files and AI-specific markup

• Chunking content into small pieces for AI

• Rewriting pages specifically for AI systems

• Chasing inauthentic mentions across the web

• Overinvesting in structured data for AI purposes

If you’ve been pitched any of these as required work for AEO, this doc is your refund document.

I’ll say what most won’t. There’s an industry of agencies and consultants who built AEO service lines around exactly these tactics. The economics of selling a separate AI optimization retainer depend on AI optimization being meaningfully different from SEO. Google just confirmed it isn’t, not from their perspective, and not for their surfaces.

The principles haven’t changed. Create unique, non-commodity content. Make it crawlable. Use clear structure. Don’t manipulate. These are SEO fundamentals. They are AEO fundamentals too. They were never different.

What did change is the bar

Saying AEO and SEO are the same discipline is not the same as saying nothing changed.

Commodity content used to rank. It doesn’t get cited.

A “10 tips for first-time homebuyers” post performed fine in 2022. It doesn’t show up in an AI Overview in 2026. The model has a corpus of those posts. It synthesizes one. Nobody gets the citation.

What gets cited is the post titled something like “Why we waived the inspection and saved money: a look inside the sewer line.” That’s not my example. It’s directly from Google’s doc. First-hand experience. Specific stakes. A perspective the model can’t generate from common knowledge.

The principles are the same. The bar is higher.

If your content operation hasn’t adjusted for that, no AEO tactics will save you. Not chunking, not schema, not llms.txt. The model reads the substance.

The section nobody is reading

Now the part that matters.

Near the end of the doc, in a section called “Explore agentic experiences,” Google describes something most operators are not paying attention to.

AI agents are starting to access websites the way browsers do. They analyze screenshots. They inspect the DOM. They interpret the accessibility tree. They take actions, not just read content.

Google references the Universal Commerce Protocol (UCP), an emerging standard for letting Search agents do more than retrieve. The doc points readers to the web.dev guide to agent-friendly website best practices.

This is a phase transition, not an extension.

For the last fifteen years, optimization meant “will my content rank and convert when a human reads it?” That work isn’t going anywhere. Most pages still need to do exactly that. But a growing share of traffic is going to be agents acting on behalf of humans. The optimization question for those agents is different.

It’s “can this agent complete the user’s job here?”

That’s a question about interface, not content. About task completion, not engagement. About a machine reader, not a human one.

A few things it changes in practical terms.

Form fields need to be machine-parseable. Not just labeled, but structured so an agent can map intent to action.

Product pages need clear, extractable specs. Not just compelling copy.

Pricing pages need explicit, accessibility-tree-readable structure. Not just visual hierarchy.

Booking flows need to work without JavaScript-heavy patterns that browser agents trip on.

None of this is exotic. It’s standard accessibility work, plus an awareness layer about what agents need to act.

But here’s the operator point. Nobody is doing this yet. There are no UCP service lines from agencies. There are no “agent optimization” frameworks circulating on LinkedIn. There are no benchmarks for agent task completion on the average enterprise site.

The space is empty and that’s the gap.

What to do now

Three things.

First, read the Google doc yourself. It’s short and clearly written. Don’t take anyone’s summary as the full thing, including this one.

Second, audit your content production against the non-commodity bar. If your last six posts could have been written by a model with no context about your business, they aren’t going to get cited. Fix that before you touch anything else. The model already knows what everyone else knows. Publish what only you know.

Third, start thinking about your site as a place where agents act, not just where humans read. Walk through your highest-intent pages and ask: if an agent had to complete the buyer’s job here, could it? If the answer is no, that’s your roadmap.

The takeaway

The doc Google published is the most useful thing they have put out on this topic.

The “AEO is SEO” line is the bait. The mythbusting list is the gift. The agent section is the signal.

Most of the industry will spend this week arguing about the bait.

Spend it on the signal.

Profound launched Prompt Research Reports last week. It is the most important release the AEO category has shipped this year and the implications will take the rest of the conversation months to absorb.

The LinkedIn vanity on AEO is (very) loud and shallow. The teams I work with are still getting the fundamentals wrong. The problem Profound just solved is the one I have been writing about, auditing, and watching operators ignore for the last 18 months. Every AEO program I have audited shares a single hidden failure mode. I have yet to find one that does not have it.

Here is what is actually going on.

Most AEO is built on fiction

Open any AEO platform. Same architecture every time. A list of prompts, a score against each one, a dashboard claiming to tell you how visible your brand is in AI Search.

The dashboards work. The math is correct.

The prompts are wrong.

Pull the tracking list out of any AEO program in production right now and it came from one of three places: SEO keywords, sales intuition, or a quick scrape of competitor messaging. None of those inputs reflect what buyers actually type into ChatGPT, Claude, Gemini, or Perplexity. Which means every visibility score in the industry right now is being calculated against prompts real users often do not actually ask.

This is the AEO equivalent of measuring conversion rate on traffic that had no purchase intent. You can produce a number. The number means nothing.

The three failure modes of current prompt selection

SEO-derived prompt lists are intent-mismatched. Search keywords and AI prompts diverge on length, specificity, and conversational structure. “Best CRM for B2B” is a search query. “I’m running a 12-person sales team selling to mid-market manufacturers and we just hit Series A, what CRM should I evaluate first” is a prompt. The first one shows up in your keyword tool. The second one is what your buyer actually typed. Tracking the first tells you nothing about whether you show up for the second.

Intuition-derived prompt lists carry sales bias. When the marketing team asks the sales team what buyers ask, they get a list of objection-handling questions. Those questions exist late in the funnel, after a buyer is already evaluating you. The 95% of the buyer journey that happens before sales sees the lead is invisible. You end up tracking the conversations you wish were happening, not the ones that are.

Competitor-derived prompt lists are a lagging indicator. Reverse-engineering your prompt set from what competitors appear to be optimizing for assumes they figured it out. They did not. They are guessing too. You are now copying their guesses and calling it strategy.

Every AEO program I have audited in the last six months has at least two of these three failure modes baked into its tracking list…and honestly, most have all three.

Why the math breaks

Pick any AEO metric. Brand visibility, citation rate, share of voice in AI answers. They all share the same structure: a percentage of prompts where your brand shows up.

The percentage depends on which prompts you measured against.

If the prompt list is wrong, the score measures something that does not exist. You can post a 70% visibility score on a prompt set that represents 5% of real conversations. You can post 20% on a prompt set that represents 80% of real conversations. The first team thinks they are winning. The second team thinks they are losing. Both are flying blind because neither one knows what the actual conversation surface looks like.

The pattern I keep seeing: most tracking lists capture maybe a quarter of real conversation volume in the category, often less. The rest of the buyer conversation is happening without you, and your dashboard has no way to tell you it exists.

This is the upstream problem nobody is solving. Every AEO conversation right now is about content optimization, citation engineering, or schema. All of that work compounds on top of prompt selection. Get the inputs wrong and the entire program is theater.

What real prompt selection looks like

The methodology has four stages. Anyone running an AEO program at scale needs to be doing this, whether they buy a tool or build it themselves.

Stage one: retrieve real prompts. Not keywords. Not internal hypotheses. Actual user conversations captured from AI platforms over a recent window, semantically searched against your category and brand inputs. The volume matters. You need a corpus large enough to surface the long tail, not just the obvious head terms.

Stage two: filter and rank. Real prompt data is noisy. Duplicates, near-duplicates, off-topic drift, multilingual variants. The filtering pass matters as much as the retrieval pass. A clean corpus of 5,000 verified prompts is more useful than a dirty corpus of 500,000.

Stage three: cluster into topics. This is where a generic solution would fall short. Ask a generic LLM to cluster a thousand prompts about your category and you get one giant bucket labeled with your category name. Useful clustering requires models built to find distinctions inside a topic, not similarity across one. Each cluster needs to map to a distinct thing buyers are trying to do.

Worth flagging: how you cluster is a strategic decision, not a technical one. Slicing prompts by use case versus by buyer concern versus by journey stage produces completely different competitive surfaces. Accept the default clustering your tool produces and you have outsourced your category positioning to a generic algorithm. The teams who treat the keywords, topics, and specific descriptions they feed the tool as positioning work are the ones who get to choose how the category gets framed before the dashboard is ever built.

Stage four: select canonical prompts. Within each cluster, you do not need to track every variant. You need the prompt that best represents the cluster’s center of mass. One canonical prompt per cluster, ranked by how much of the underlying conversation volume it covers. That coverage score is the metric that matters now. It tells you how much of the real conversation surface your tracking list represents.

The output of this process is not a longer prompt list…it is a smaller, sharper one. The pattern I keep seeing: the right configuration ends up 30-50% smaller than what the team was tracking before, with coverage several times higher.

This is where the standard playbook gets it backwards. Adding more prompts to your tracking list does not make your AEO program smarter. It makes it dumber. Every low-coverage prompt you add dilutes your aggregate numbers, hides your real gaps under noise, and creates the illusion of completeness. Your dashboard looks more thorough and tells you less. The discipline is subtraction, not addition. There is still room for the prompts you want to monitor for brand intelligence reasons, including your product against named competitors, your specific business questions, or the conversations you want to know about even if they are not high-volume yet. Those belong on a separate tracking layer, not folded into your aggregate visibility score. Mixing them in is how the score becomes meaningless.

How to run this in practice

Run this as a quarterly cadence, not a one-time audit.

Quarter one: build the baseline. Run the methodology against your category and produce your initial canonical prompt set. Document coverage by cluster.

Quarter two: measure drift. AI conversation patterns shift faster than search keywords. New prompts emerge as products ship and buyers learn how to talk to LLMs. Re-run the retrieval and look for clusters that grew, shrank, or appeared.

Quarter three: tie to content investment. The intent breakdown of your prompt set tells you where to invest. Heavy informational skew means you need foundational education content. Heavy commercial skew means you need comparison content. Heavy transactional skew means you need decision-stage proof assets. The prompt set is the brief.

Quarter four: prioritize the gaps. Now that the denominator is real, your visibility score becomes a number you can actually move. Rank your highest-coverage clusters by where your brand shows up least. Those are the highest-leverage gaps in the category.

This is the operating cadence. None of the programs I have audited are running it end-to-end.

What Profound actually shipped

This is the methodology Profound just shipped in production. Prompt Research Reports run the four-stage workflow above against a proprietary corpus of over 1.5 billion real user prompts captured from AI platforms. Retrieval, ranking, clustering, canonical prompt selection. The output is your category’s prompt configuration with coverage scores and intent breakdown. You see which topics are covered, which are missing, and how your buyers split between research, evaluation, and purchase.

This is the only implementation of this methodology I have seen ship at scale. The reason that matters is not the product. It is the data underneath it.

You cannot do this work without a corpus of real prompts at volume. That corpus is not something you build in a quarter or buy off a shelf. Profound has been capturing real AI prompt data longer than the rest of the market has been measuring it. They built the dataset first, then shipped the operator-facing product on top of it. That is the right sequence and almost nobody else is in a position to copy it. And the data is only half the moat. Within-topic clustering at this scale is a genuinely hard mathematical problem in its own right. A competitor who got the corpus tomorrow would still need to ship the math, and the math is the part that takes time to get right.

What I am most impressed by is the speed. The AEO category is barely 18 months old. The infrastructure problems they are solving here are not trivial. Capturing real prompt data at volume. Building clustering models that find within-topic distinctions where general-purpose models fail. Surfacing all of it in a configuration UI operators can act on without a data science team. Shipping this now, while the category is still arguing about whether AEO is even real, is the difference between leading the category and reacting to it.

This pushes the category forward. More importantly, it ends the era of operators running AEO on intuition and calling it strategy.

The press covered the news…almost no one covered what actually shipped.

Folks have been asking me variations of the same question this month: should we be paying for ChatGPT placements yet? I keep giving different answers, because the variable that matters isn’t whether the ad product works. It’s how visible the brand already is organically.

What OpenAI rolled out on May 5 was the full infrastructure for commerce inside ChatGPT, built quietly over the last 12 months and now ready to run…and it made organic visibility into the most important driver of paid economics on the most important new channel in B2B.

If you only look at the ad product, you miss what’s happening to the rest of the surface.

The launch in one list

Here’s what went live on May 5:

→ Self-serve Ads Manager (beta, US)

→ CPC bidding, $3-5 max bid recommended

→ Pixel-based measurement and Conversions API

→ Programmatic Advertiser API

→ Agency partners: Dentsu, Omnicom, Publicis, WPP

→ Tech partners: Adobe, Criteo, Kargo, Pacvue, StackAdapt → $50K minimum eliminated

→ Live in US, Canada, AU, NZ; expanding to UK, Mexico, Japan, Brazil, South Korea

→ Run by Asad Awan (monetization) and Dave Dugan (ex-Meta, ad sales)

This is the core Google and Meta ad infrastructure rebuilt for a conversational surface in 90 days. Three months between the Feb 9 pilot launch and the May 5 self-serve opening.

That speed only happens when the underlying systems have already matured. Shout to Alex Halliday and the AirOps team for shipping same-day support for ChatGPT Ads measurement and attribution. AEO platforms don’t move at that pace if they don’t believe this is now infrastructure rather than experiment.

The leadership matters too. Asad Awan owns monetization. Dave Dugan, ex-Meta, owns ad sales. Above them, Fidji Simo runs OpenAI’s Applications business. She’s the executive Sam Altman hired specifically to turn ChatGPT into a commercial product. None of these people were brought in to test whether ads work. They were brought in to scale a business.

OpenAI is targeting $2.5B in ad revenue for 2026 and $100B by 2030. They crossed $100M annualized in the first six weeks of the pilot. Less than 20% of eligible users are currently seeing ads, which means inventory is about to expand massively as the auction matures and the self-serve flywheel spins up.

This is not a side experiment. Ads are now the third revenue line at OpenAI, alongside subscriptions and enterprise. It’s the newest one, and it has the steepest growth curve of the three.

What the data is actually saying

Most of the coverage of ChatGPT ads has been built around the wrong numbers.

The story that dominated last month was Adthena’s report that one of their clients saw a 0.91% click-through rate on ChatGPT ads, roughly seven times below the 6.4% benchmark on Google Search. That number got cited in every “ChatGPT ads aren’t working” piece for three weeks straight.

Then Similarweb published their benchmark last week. The aggregate CTR for ChatGPT ads is 0.68%. Top quartile is 1.0%. Best brands are hitting 1.57%. Peak is 5.4%.

For context: display ads sit at 0.35%. Podcast ads run 0.5-1%. LinkedIn Ads, which premium B2B advertisers happily pay $40+ CPMs for, average around 0.5-2% depending on objective.

ChatGPT is already outperforming display in CTR. Before the auction has any real maturity. Before the relevance model has been trained on billions of impressions. Before any best-practice creative or targeting frameworks exist.

To be fair, the display comparison isn’t perfectly clean. Display runs cold across the open web, often with no context match. ChatGPT ads run inside high-intent conversations where the user is already in research mode. The numbers aren’t apples to apples. But even allowing for the context gap, ChatGPT is clearing a benchmark most people assumed it would fail at this stage.

The “users are in task-completion mode so CTRs will stay low” thesis isn’t wrong. It’s wrong at the top end of the distribution. Brands that get the placement right are already hitting numbers most assumed would take years.

Conversion data matters more than CTR for performance marketers. Criteo reported that LLM-referred users convert at roughly 1.5x other referral channels. Conversion rates on ChatGPT ads run between 1-4% on average. It’s early, the measurement is improving but still aggregated, and the ceiling is much higher than the headline criticism suggests. Brands going early are getting cheap impressions in front of users with deeper intent than any other surface.

That’s the paid story. The organic story is more interesting.

The shift no one is naming

AirOps published research last week that’s the most important AEO finding of 2026 so far. Over a 16-week window from December through March, they tracked 170 million AI answers across roughly 3,000 brands. They captured every citation URL, every brand mention, every source.

Between mid-January and early March, average citations per answer on brand queries dropped 41%, from 4.95 to 2.96. By late March, citation counts had largely recovered, back to about 90% of the December baseline.

If you stopped there, you’d call it a temporary disruption from a model update and move on. That’s what most teams did.

But citation counts don’t tell the whole story. The composition changed during the dip, and it has stayed changed.

→ Product domains went from 55% of brand-query citations to 63% at the trough, and have held around 62%

→ Educational content dropped from 14% to under 10%

→ Review platforms (G2, Capterra, TrustRadius) climbed from 5% to about 7%

The model is going direct to source. When someone asks about a product, ChatGPT is more likely to cite that product’s own pages (pricing, comparison, documentation) than third-party content about it.

That alone is a meaningful shift for content teams who spent the last decade investing in educational top-of-funnel.

But the AirOps data showed something even more important:

Brand mentions per answer went up. Citation links went down.

The model is talking about brands more frequently in its answers while attaching fewer citation links to those mentions. Awareness is rising. Click-through is compressing.

If you only measure share of citation, you’ll miss the awareness gain. If you only measure brand mention count, you’ll miss the click collapse. Both signals are moving in opposite directions on the same surface.

That’s not a model-update artifact. That’s the new layer.

Profound’s data confirms it from another angle. Wikipedia alone accounts for 7.8% of all ChatGPT citations. The top three domains (Wikipedia, Reddit, TechRadar) control 22% of all citation share. ChatGPT referral traffic to brand sites has dropped 52% since July 2024. Reddit citations have grown 87% in the same window.

The citation pool is consolidating at the top. The click-through layer is thinning underneath. And the brands that win citations are increasingly the ones with structural decision-stage authority, not the ones with the biggest blog libraries.

What I saw firsthand

I lived a smaller version of this shift inside the Webflow growth team.

When AI chatbot referrals first started showing up in our analytics, the volume was tiny. A rounding error. The kind of channel you’d flag in a monthly review and move on from.

Two things changed quickly. First, the volume grew faster than any other channel we were tracking. AI referrals went from a rounding error to a real percentage of signups in months, not years. Last public number from Webflow: about 10% of total signups now come from AI chatbots. Some peer companies in B2B and developer tools are seeing similar or higher.

Second, and this is the part that mattered more, the conversion behavior of those users was different. They arrived deeper in the funnel than any other channel. They’d already compared us to alternatives inside the chat. They’d already gotten an opinion from the model about whether we were the right fit. The website was confirmation, not consideration.

That changed what content needed to do. Top-of-funnel education stopped earning its keep, because the model was synthesizing that content itself before the user ever clicked through. Comparison pages, product pages, pricing pages, the docs, the integration index, every decision-stage surface started doing more work than it ever had.

What I’m watching now is the same dynamic playing out faster, on a bigger surface, with paid mechanics on top. The brands that built decision-stage authority over the last 18 months are about to find out the auction was designed around them. The ones who didn’t are about to find out it wasn’t.

The window that explains the timing

Halliday published a stat on LinkedIn this week that almost no one has connected to the broader picture.

Between April 7 and 14, AirOps tracked ChatGPT serving roughly 2,813 sponsored cards per 100,000 searches. About 3% of queries returning a sponsored card.

After April 15: 47 per 100,000.

A 98% collapse, overnight. Held flat for three weeks since.

Halliday’s read was measured: OpenAI was testing behavior at scale, then pulled back to study the data before shifting to production monetization. That’s defensible.

I read it differently.

OpenAI didn’t lose its nerve on April 15. OpenAI calibrated the trust budget before opening the auction to self-serve.

To understand why, you have to understand the structural problem OpenAI is solving. They have two competing pressures inside the same interface.

On one side, an organic answer experience that has to remain trustworthy. ChatGPT works because people believe the answer isn’t bought. The moment that trust erodes, the entire product collapses. No amount of ad revenue replaces a broken trust contract.

On the other side, a monetization layer that has to generate enough revenue to fund the free tier, the compute, the model training, and the IPO narrative. OpenAI burned $8B in cash in 2025. Ads are the only realistic way to keep the free tier alive at 900M+ weekly users.

These two pressures share one finite resource: user trust.

Every decision OpenAI has made about the ads product is consistent with managing trust as a budget across both sides. The structural separation between ad-serving systems and the answer model. The clear “Sponsored” labeling. The age gates. The category restrictions on sensitive topics like health and politics. The privacy posture. The deliberate throttle on sponsored card frequency.

That April 15 collapse was OpenAI saying: we cannot let the auction run at 3% of queries while we open it up to thousands of new advertisers. The relevance bar has to tighten, the inventory has to be controlled, the trust hit has to be measured before we let volume scale.

Which means when self-serve opened on May 5, the auction was already pre-tuned for trust preservation, not impression maximization.

The framework

Ads are the wrong frame for what’s happening.

What’s happening is four ranking decisions converging into one system:

1. Retrieval: which content gets pulled into the answer

2. Citation: which content gets linked in the response

3. Action: which Apps get surfaced for the user to take next steps

4. Monetization: which ads appear alongside

OpenAI has shipped the infrastructure for all four in the last 18 months. The Apps SDK. The shopping research feature. The Responses API. The Conversions API. Self-serve ads.

These are not separate launches. They are one converging system with one finite input: user trust.

That makes the auction inside ChatGPT structurally different from Google’s or Meta’s.

Google’s auction prices keyword intent. Meta’s auction prices audience attention. ChatGPT’s auction has to price relevance inside a trust-constrained answer surface, where any contamination of the organic experience destroys the value of the paid one.

In a trust-constrained system, paid pricing follows organic authority. Brands the model already trusts to mention will clear the relevance bar cheaply. Brands it doesn’t trust can pay, but get gated by a quality system designed to protect the answer surface from low-relevance placement.

The mental model flips

For twenty years, the mental model for marketers has been:

→ Organic visibility is free. You earn it through content, links, and trust signals.

→ Paid placement is the premium. You buy it when you can’t earn it organically.

Inside ChatGPT, that model inverts.

→ Organic visibility is the BID FLOOR. The price you pay to enter the auction at all.

→ Paid placement is the premium on top of that floor. The less organic authority you have, the more you pay per click.

This is the part nobody has named yet. It’s the exact dynamic Google’s Quality Score has produced in paid search for a decade. Brands with strong relevance signals pay 3-5x less per click than brands with weak ones. Same auction, different effective CPCs based on the underlying quality bar.

ChatGPT’s auction is a Quality Score system on a conversational surface, gated by an even stricter trust function because the placement sits adjacent to a trusted answer.

If you spent the last 18 months investing in Answer Engine Optimization, earning citation share on your category queries, building decision-stage authority, structuring content for retrieval, you’ve been building the foundation that determines your paid economics on this channel.

If you skipped AEO and assumed you’d buy your way into ChatGPT placements when the time came: the bill is coming due in the ad auction.

What to do before the wave hits

Three moves matter right now.

First, measure your Answer Capture Rate. Not just whether your brand gets mentioned. Whether it gets cited. Whether it gets recommended. Whether it gets surfaced as the answer to the highest-intent prompts in your category. Most teams are measuring share of mention. The right metric is share of decision.

Second, audit your decision-stage authority across the surfaces that feed the model. Product pages. Comparison pages. G2, Capterra, TrustRadius profiles. Reddit threads where your category gets discussed. The pages cited in AI Mode and ChatGPT Search for “best [your category]” prompts. If you’re not in those, you’re outside the pool the auction is going to price from.

Third, plan for the inversion. The paid budget you set aside for ChatGPT ads should be a function of your organic visibility, not a substitute for it. Brands with thin AEO foundations should expect to pay 2-3x more for the same placement than brands with strong ones. Build the foundation or factor the premium into your forecasts.

This is what Answer Ownership was built for. Answer Capture Rate is how you measure it.

Search monetized attention.

AI monetizes trusted resolution.

In 12 months, the brands with high organic citation share will be paying 2-3x less for placement in the same conversations. The ones who skipped AEO are about to learn that the auction has been priced against them for the last 12 months. They just haven’t seen the invoice yet.

That’s the call I’m staking. Disagree if you see it differently. I’m going deep on this over the next few weeks.

Last month, an advisory call. A founder pulled up his AEO dashboard. Comparison pages shipped. Case studies formatted for AI extraction. FAQ schema deployed across the site. Six months of work, executed cleanly.

I asked one question. Which buying questions are you actually winning citations for right now?

He did not have an answer. Nobody on the team did. They had been producing AEO output for half a year with no feedback loop telling them whether any of it was landing.

That call is the most common pattern I see in advisory work. Teams who have correctly identified that AEO matters. Teams executing real tactics. Teams completely flying blind on whether the tactics are landing.

The teams pulling away right now are not doing more AEO. They are running closed-loop AEO. Same tactics. Different operating layer. The difference is whether the work has feedback, measurement, propagation, and governance running continuously around it, or whether the work is being shipped into a void and called a strategy (which happens more than I’d like to admit).

Distribution without monitoring is content production with no feedback. Distribution without consistency is fragmentation at scale. Distribution without reporting is investment without measurement. Distribution without brand governance is voice drift at velocity.

AI systems absorb new narratives inside weeks. None of those gaps are recoverable after the fact. By the time you feel the loss in pipeline, the citations driving it have been live for months.

Closed-loop AEO is the only version of this work that compounds. The five agents below are what running the loop looks like in practice. This is how I build it with the companies I advise.

The five agents

Each one has a specific job, specific inputs, specific outputs. When one is missing, the loop opens.

1. Monitoring Agent

Takes in: ChatGPT, Perplexity, Gemini, Claude. Reddit threads and buying conversations. G2, Capterra, review platforms. Third-party comparison pages.

Produces: Narrative shift alerts within days. Competitor citation gain briefs. A prioritized response queue.

One current engagement is a Series B data infrastructure company. The team believed they owned the head buying question in their category because they had ranked first in Google for it for two years. We deployed Profound monitoring across the category, and inside the first week the actual citation map surfaced.

ChatGPT was pulling its answer from a GitHub issue thread. A former engineering customer had documented, in detail, why they had migrated to a competitor. The issue had been resolved over a year earlier. The thread was archived. To the team it felt like ancient history.

The model treated it as authoritative. Structure, technical specificity, a clear evaluation conclusion. That was enough.

You cannot make a GitHub thread disappear. The fix was a structured response covering the same evaluation criteria, published on surfaces AI systems weight more heavily. We also updated the team’s own comparison pages so the buying question got answered coherently across the category. Citation share started moving inside three weeks. Not from the new content alone. From the new content with the rest of the loop catching up around it.

The lesson is structural. Profound’s research found only 11% of domains cited by ChatGPT also appear in Perplexity. Watching one interface is not watching the category. Watching weekly is not watching the rate of change. And the surfaces AI systems actually weight are often surfaces your team has never thought to monitor.

2. Consistency Agent

Takes in: Core positioning. Website, docs, product pages. G2 and review responses. LinkedIn and blog content.

Produces: Opening third of every page synced. Fragmentation closed before AI averages it out. Every surface updated when messaging shifts.

44.2% of LLM citations come from the first 30% of text. The opening third of every page is the citation target zone. When I run a positioning audit for a new advisory client, this is almost always where the largest gap is.

A recent audit, Series A fintech. The website described the product as serving three categories. The documentation grouped the same functionality into five. The G2 listing used a sixth taxonomy entirely. An AI synthesizing the brand across those surfaces could not tell whether the company shipped three products, five, or six, and which problems each one solved. The buyer received a blurry composite that did not match what any single team had written.

Here is the part that surprises operators when I name it. The consistency agent is not a content tool. It is an organizational coherence tool. The reason positioning fragments across surfaces is that no single team owns the coherence question. Marketing owns the website. Product owns the docs. Customer marketing owns G2. Each is locally consistent. The composite is incoherent. The agent does not fix that. It surfaces it. The fix is operator work. The agent makes it impossible to keep ignoring.

3. Reporting Agent

Takes in: Citation share by buying question cluster. Competitor citation share movements. Week-over-week answer share data.

Produces: Weekly citation share report for leadership. Buying question ownership map. Competitor gains flagged before pipeline feels them.

Reporting is the agent everyone agrees they need and almost no one builds. The reason is that tracking citation share movement week over week feels closer to financial controllership than to marketing work. It rewards a different mindset. Adversarial reading. Pattern recognition across noisy data. The discipline to act on small movements before they become large ones. Most marketing teams are not staffed or wired for that.

The founder I opened with had no measurement layer because no one on his team had built one. They were not doing AEO wrong. They were doing AEO without a scoreboard.

When I work with a team I push reporting into the loop early, before we expand distribution. In a category where citation share moves in weeks, a quarterly snapshot is not a lagging indicator. It is a different market entirely. Every budget decision made against stale data is an expensive guess.

4. Distribution Agent

Takes in: One foundational content piece. Core positioning. Target buying question clusters.

Produces: Comparison pages built for AI citation. Case studies formatted for AI extraction. Reddit answers in buying question threads. LinkedIn threads structured for indexing. FAQ schema for direct answer surfacing.

This is the agent most teams are already running. It is also the only one most teams are running.

At Webflow, the distribution work my team executed produced +331 AI citations across our top buying questions from one specific intervention. Structured FAQ and schema designed for AI extraction. Documented in case studies, reproducible in any team’s environment. That number was not the result of more content. It was the result of foundational content being formatted for the citation map AI systems actually pull from.

80% of URLs cited by LLMs do not rank in Google’s top 100 for the original query. The citation map is wider than the link graph. Most teams are still building for the link graph and wondering why the answers form without them.

5. Brand Standards Agent

Takes in: Voice and tone guidelines. Legal and compliance requirements. Approval workflow rules.

Produces: Brand-compliant output before content ships. Consistent positioning at velocity. A quality floor that holds at scale.

As distribution velocity increases, the brand floor cracks. Tone drifts. Legal language gets approximated. Technical claims that required precise wording become vague approximations that do not survive synthesis.

The non-obvious thing about brand drift at velocity is the direction it drifts. It does not drift random. It drifts neutral. Every approximation pulls the language one click toward what generic AI-generated content sounds like. Specific claims become directional ones. Sharp positioning becomes “leading provider.” The differentiation that took three years to articulate sands down to industry-standard phrasing one shipped piece at a time.

Brand guidelines living in a PDF nobody reads do not hold against this gravity. After-the-fact review either creates a bottleneck or gets bypassed. The brand standards agent moves the guardrail into the output layer, before content ships.

Its job is not to enforce a tone document. Its job is to hold the line against the specific gravity of generic.

What open-loop AEO actually costs

Most teams running “AEO” are running Distribution alone and calling it a strategy. The tactic is sound. The problem is what is missing around it.

Three things happen in a team running open-loop AEO.

The first is that competitor narrative shifts get absorbed by the model before the team notices. By the time the loss surfaces in pipeline, the citations driving it have been live for months. Damage control on positions never known to be lost.

The second is that the team’s own positioning fragments across surfaces faster than they can track. Every shipped piece adds another approximation. The model averages. The buyer gets the average. The team produces more content, the average gets blurrier, and the citation share quietly moves to whichever competitor’s positioning is coherent across surfaces.

The third is the most expensive and the least named. ROI for AEO investment is invisible without the reporting layer. AI search drives a buyer who arrives post-synthesis, shortlist already forming, and the team often credits direct or organic for the resulting deal. The work that is actually compounding gets defunded by the team’s own measurement gap. Budget moves away from the highest-leverage motion in the stack because no one built the instrumentation to see it.

Open-loop AEO has a diagnostic. If you cannot answer three questions in under sixty seconds, you are running it. Which buying questions are you winning citations for this week. Which competitor is gaining citation share fastest right now. What shipped this week with positioning your sales team has not signed off on. If any of those answers is “I would have to find out,” the loop is open at that point. That is the agent to deploy.

Where I start with a new engagement

The deployment path is not all-or-nothing. The first move is diagnostic.

If the team has no idea which buying questions they are winning across their top 20, the gap is Monitoring and Reporting. Deploy those before doing anything else. Every subsequent investment is calibrated to data that does not exist yet. Continuous monitoring is what I deploy first here, because the gap closes in days, not quarters.

If they can name the questions they own but their messaging across surfaces is fragmented, the gap is Consistency. Close it before producing more content. Volume on top of fragmentation accelerates the averaging problem.

If foundational content is strong and monitoring is in place but downstream surface area is thin, the gap is Distribution. Build for the citation map.

If they are shipping fast and the brand floor is starting to crack, push Brand Standards into the output layer. Not into a PDF.

Two operator opinions on sequence that I will name because they are not standard advice.

First, I do not deploy Distribution until Reporting has been running for at least two weeks. Teams who write new content before they can see the citation map optimize against the wrong questions. They produce a comparison page for the question they assume matters and miss the question that is actually moving against them in the answers. Two weeks of reporting changes the brief.

Second, I deploy Brand Standards last, not first. Most consultants put governance first because it feels like the foundation. It is not. You need to see what is actually shipping at velocity before you can govern it intelligently. Brand standards built before the system runs become the same dead PDF nobody reads. Built after two months of real output, they are operational.

The single agent whose absence is currently costing the most is the agent to deploy this week. Not all five at once. The one whose gap is the most expensive.

What closed-loop looks like running

When the loop is closed, the team stops finding out about competitor narrative shifts in deal debriefs. They catch the citation gain inside a week and respond inside another. Positioning across surfaces stays coherent because consistency is structural, not aspirational. Citation share shows up in the leadership report alongside pipeline because it is the leading indicator pipeline is now lagging. Distribution scales without burning out the content team because the agent is doing the format-specific rewrites. The brand floor holds because governance is in the output layer, not the review process.

This is the configuration the teams pulling away are running. The infrastructure to do it at scale exists. Over 1,000 enterprises now run on Profound, including 10% of the Fortune 500. That is not a popularity signal. It is a confirmation that the manual operation most teams are still running is the operation those teams have already replaced.

The teams still running open-loop AEO will not feel the gap for another two quarters. By then the citation share has already moved. The deal debrief will explain why.

The loop is the motion. Everything else is content production.

StackedGTM.AI covers AI-native go-to-market strategy for B2B operators. No frameworks for frameworks’ sake. No theory without proof. If this changed how you think about how the work has to actually run, subscribe.

If you want to see the Answer Ownership Agent Stack running in practice, start with Profound. Real infrastructure for a problem most teams are still solving manually. It is what I deploy first when monitoring is the gap.

The title is new. The person is not. Every high-performing marketing team already has one, hiding inside other titles, doing the work without a name for it.

Subscribe now

Here is one in the wild. At Webflow, I wanted to deepen acquisition in the freelancer community. Between days stacked with calls, I built a handful of agents that scraped freelancer and web dev subreddits, surfaced real-time pain points, shaped a narrative, shaped an offer, activated across channels, measured, refined. An executive with a toolbox, running an end-to-end cross-functional acquisition program in days, not quarters. Not a team. One person with the right tools and the range to use them. By the time I left Webflow, more of my team was operating this way than wasn’t.

The role is builder and artist in the same seat. The builder half writes the agent, picks the model, ships the dashboard, retires the vendor contract. The artist half decides what is worth building, what the narrative needs to say, and whether the output is any good. Neither half works alone. A marketing engineer who can only build becomes a backlog. One who can only imagine becomes a PM. The job is both, and the people who do it well are rarer than the title makes it sound.

This matters now because the functional split inside marketing is breaking down. Technical and creative. Strategist and operator. Analyst and storyteller. The lines are blurring because the best people stopped honoring them. They started shipping work that made the specialists look slow, and the org charts are catching up.

Early-stage companies have run this way forever out of necessity. The difference in 2026 is it is moving upmarket fast. The orgs winning already have this person inside them. The ones that don’t are feeling the gap.

In 2027, this is a standard role. In 2028, it is a team. The companies hiring the first one right now are the ones who will have the second and third already in seat by the time everyone else writes their first req.

Profound named the role. Nobody has written the definitive playbook for hiring one. This is that piece. The role, the req, the comp, and the first 90 days. For the VPs and marketing leaders making the hire. And the founders signing the offer.

Why the old archetypes don’t cover this

The growth marketer you hired in 2022 was a channel operator. Paid, lifecycle, SEO. Ran campaigns against a plan.

The marketing ops hire you made in 2023 was a systems operator. Shipping in Marketo, CRM hygiene, attribution, lead routing. Kept the pipes clean so the campaigns could run.

Both roles are still valuable. Neither one owns the loop.

The marketing engineer closes the loop alone. Identifies the problem. Builds the thing. Ships it. Measures it. Kills it or scales it. What used to be a cross-functional project with a PM, an engineer, an analyst, and a marketer is now one person’s week.

The teams that figure this out first run with a third of the headcount and ship four times the work. That is not a productivity gain. That is a different operating model.

That’s the math. That’s why you’re hiring.

What they actually do

The job is not “AI for marketing.” That is the vendor pitch. The work is more specific and harder to fake.

They deploy agents as production systems. Not Zaps. Not prototypes. Real systems with branching logic, model calls, data enrichment, human review, and measurable outputs. Research agents that pull competitor signal every morning. Enrichment agents that keep the CRM clean without a human touching it. Outbound agents that write like a human because a human wrote the pattern once. The marketing engineer owns reliability, unit cost, and output quality. When an agent breaks at 11pm on a Sunday, they are the one fixing it.

They build internal tools that retire vendor contracts. A lead scoring tool that beats the one you are about to renew. A content brief generator that pulls from your research library. A competitive intel dashboard that updates itself nightly. A first-party attribution view that reflects how your business actually works. Things that used to be a six-month engineering ask. They ship in days.

They own the measurement layer. They do not wait for analytics. They pull from the warehouse, the CRM, the product, and the model layer, and they build the view the team actually uses. They are the person who tells you, unprompted, that your attribution is lying and here is the query that proves it.

They work across every marketing function. PMM, content, demand gen, brand, paid, PR, lifecycle, localization. The agents and tools they build deploy wherever the leverage is highest that week. A launch analysis for PMM on Monday. A localization pipeline on Wednesday. A press monitoring agent on Friday. The breadth is the job.

They think in architecture, not tasks. The best ones see a single workflow and recognize the shape of the hundred others that run on the same structure. They build the first one right so the next ninety-nine compose instead of compound into debt. This is the cognitive attribute that separates a great marketing engineer from a fast one. It is also the hardest thing to assess in an interview.

They invent capabilities that did not exist before. The first six months are about making the team faster at work they already do. The next six are about asking what was impossible before agents and shipping the first version. Real-time brand sentiment monitoring across thousands of AI conversations. Competitive displacement narratives that deploy within hours of a competitor move. Answer engine optimization systems that win citations across ChatGPT, Perplexity, Claude, and Google AI Overviews. The marketing engineer is the person who sees the new category of work and ships the first version while everyone else is still scoping the RFP.

They make everyone else faster. A content lead ships more, faster, better. A PMM runs a launch analysis in a morning instead of a week. A demand gen manager gets the dashboard on Monday instead of never. The leverage shows up in other people’s output, which is why a good one is worth three hires.

They are measured like marketers, not like engineers. Pipeline. Reach. Conversion. Velocity. What they build has to move those numbers. If it does not, it should not have been built.

What they do not do: own a channel or manage the agency. Pull them into that work and you scoped the role wrong.

The real bar is creative judgment

Here is the part every hiring manager is about to get wrong.

The technology is not the hard part. The tools are getting easier every month. A smart person can learn Cursor, Lovable, n8n, and Gumloop in a weekend. They can ship a working agent by the end of the week. The floor is lower than it has ever been, and it is dropping fast.

The ceiling is not the technology. The ceiling is judgment.

Knowing what agent to build is the job. Anyone can deploy one. Knowing which one will move the number, which one is a distraction, and which one looks useful but will rot in three months without a human watching it. That is the part you cannot learn in a weekend. That is the part that separates the marketing engineer who compounds from the one who ships a hundred tools nobody uses.

Creativity is not a soft skill in this role. It is the skill. Taste tells you what not to build. Imagination tells you what has not been built yet. Narrative instinct tells you how the output will land with a customer who has never heard of your company. Product sense tells you when a workflow is ready and when it is still a demo. None of that comes from the stack. All of it comes from the person.

The tooling is the paintbrush. The marketing engineer is the artist. A beginner with a great brush still paints a beginner’s painting. Give a great painter a cheap brush and you still get a painting worth hanging. The tools compound talent. They do not replace it. The companies that miss this hire for the tools and wonder why the output feels hollow.

This is why the role is rare. Plenty of marketers are creative. Plenty of operators can build. The overlap is small. A marketing engineer who can ship but cannot decide what to ship becomes a very expensive intern. One who can imagine but cannot build ends up filing tickets with engineering like every other PMM. You need both halves in the same seat, and you need the creative half to lead.

Where they sit

Most teams get this wrong on day one, and the role never recovers.

Report them to the CMO/VP of Marketing. Not a chief of staff. Not the head of ops. Not a dotted line into engineering. The person who owns the GTM number. The role only works when the top of marketing is personally invested in what gets shipped and personally embarrassed when nothing does. Three levels down, the first time a campaign goes sideways, this hire gets pulled into the fire drill and never comes back. I have watched this happen twice. Both times the role was declared a failure within a year. Both times the failure was the reporting line, not the hire.

Keep them as a team of one for the first six months. Not inside marketing ops. Not inside analytics. Not matrixed into demand gen. A direct line to the VP and a lateral mandate across the org. Their job is to make everyone else faster, and they cannot do that from inside someone else’s backlog. The moment this role is reporting into a functional leader with a number to hit, the work bends toward that leader’s quarter and the rest of the team stops getting the leverage.

They own what they build. They influence everything else. A marketing engineer who “owns demand gen” becomes a demand gen manager with extra steps. A marketing engineer who builds the tools demand gen uses becomes a force multiplier across every channel at once. The second version compounds. The first one does not. The distinction sounds subtle in the org chart conversation. It is not subtle in year two, when the first version is managing one channel and the second version has made four teams twice as fast.

Close to engineering, not reporting to engineering. A standing line to a friendly engineer for the hard stuff. Infra, data pipelines, anything that touches production systems engineering depends on. Not on the eng team. They move at marketing speed, which is faster than eng speed. That is a feature, not a bug you need to fix by moving them under a staff engineer.

One more thing that matters more than it should. The VP of Marketing/CMO needs to be the one who fights for the comp band, writes the req, runs the interview loop, and defends the role in the first operating review where someone questions it. Delegating any of that to a recruiter or a chief of staff is how the hire arrives under-leveled, under-paid, and reporting to the wrong person on day one. The top of marketing has to own this hire the same way the CTO owns the first staff engineer. Anything less and the role gets treated like a nice-to-have, which is how it ends up acting like one.

What to pay them

Base of $180,000 to $220,000, plus equity on the senior IC band. Higher in San Francisco or New York, where you are competing directly with senior product engineering and senior PM comp.

If finance pushes back on the band, three arguments.

You are not competing with marketers. You are competing with senior software engineers and senior product managers. The strongest candidates have those offers in hand, often multiple. Anchor the role to marketing comp and you lose the top quartile of the funnel before the first interview. Anchor it to senior IC comp in adjacent functions and you get to choose from the real pool. Every company I have seen try to hire this role at marketing band rates has ended up either reposting the req six months later or settling for the candidate who could not get the senior engineering offer. Neither outcome is cheap.

The ROI math is straightforward. A competent marketing engineer retires or renegotiates vendor contracts in the first six months as a byproduct of the work, not as a goal. In most mid-market marketing stacks, that delta alone covers a meaningful share of the fully loaded cost of the role in year one, before counting any output gain across the rest of the team. Ask your finance partner to model the range against your current martech spend. The conversation gets shorter.

This hire compounds. The value in year two is larger than year one because the tools, workflows, and measurement systems they built are still running and still producing leverage. You are not paying this person to do work. You are paying them to build systems that make future work cheaper. That is a structurally different argument than a typical headcount case. Finance partners find it credible when it is made correctly, and they find it unconvincing when it is made by someone who has not done the modeling. Do the modeling before the conversation.

A note on equity. Compensate this role on the senior IC equity band, not the marketing band. The two are often different at companies of the same size and stage, and the gap is wider than most comp teams realize. If your equity framework treats marketing as a lower-equity function by default, the offer will underperform in the market against the engineering and product offers these candidates are comparing it to. Flag this to the comp team before you write the first offer, not after the first candidate declines.

One more thing. Do not cheap out on the first one. The first marketing engineer you hire sets the internal comp anchor for every one that follows. Underpay the first, and the second is harder to hire, because the band on the job ladder is already set too low. The cost of fixing that later is higher than the cost of paying the first one correctly.

The Job Description (steal this)

Drop this into Greenhouse. Edit the company-specific lines. Ship it.

Marketing Engineer

Reports to: VP, Marketing/CMO

Level: Senior IC

Location: Remote, United States

Compensation: $180,000 to $220,000 base, plus equity on the senior IC band

About the role

You will be the first marketing engineer on this team. You will report to the VP of Marketing/CMO and work directly alongside content, demand generation, and product marketing. Your mandate is simple and hard. Make the entire marketing function measurably faster, more accurate, and more inventive by building the agents, tools, and measurement infrastructure the team runs on.

This is a builder role inside a marketing organization. It is also a creative role. You will spend your days writing prompts, designing systems, and shipping production software with modern AI tools. You will also spend them in narrative meetings, on customer calls, and in positioning debates where you argue for what the work should say. Both halves are the job. Candidates who want to do only one will not succeed here.

You will be held to marketing outcomes, not infrastructure metrics. Pipeline, reach, conversion, velocity, share of voice across the answer engines your buyers now default to (tracked in Profound). The systems you build are the means. The numbers are the end. The creative judgment to know which systems are worth building is the reason we are hiring you and not a junior engineer with a prompt library.

What you will do

Deploy agents as production systems. Real systems with branching logic, model calls, data enrichment, human review, and measurable outputs. Research agents that pull competitor signal every morning. Enrichment agents that keep the CRM clean without a human touching it. Outbound agents that write like a human because a human wrote the pattern once. You own reliability, unit cost, and output quality. When something breaks in production at an inconvenient hour, you are the one who fixes it. This is not a prototyping role.

Build internal tools that retire vendor contracts. An enrichment and scoring system that beats the platform we are about to renew. A content operations workflow that turns one customer interview into a week of publishable assets in under a day. A competitive intelligence tool that surfaces signal from public sources every morning. A first-party attribution view that reflects how our business actually works. An answer engine optimization system built on Profound that wins citations across ChatGPT, Perplexity, Claude, and Google AI Overviews. You choose the stack. The team depends on the output.

Own the marketing measurement layer. Integrate data from the warehouse, the CRM, the product, and the model layer into a system the team actually uses. Build the views the VP opens in every operating review. Surface the metrics that predict revenue. Retire the metrics that do not. When the attribution is lying, you are the person who tells us and brings the query that proves it.

Invent capabilities that did not exist before. The first six months are about making the team faster at work they already do. The next six are about asking what was impossible before agents and shipping the first version. Real-time brand visibility monitoring across thousands of AI conversations using Profound. Competitive displacement narratives that deploy within hours of a competitor move. New categories of work nobody on this team has named yet. The range to see the new category is as important as the skill to build it.

Make the rest of marketing faster through direct partnership. Embed with content, demand generation, and product marketing. Find where each function is blocked by manual work or missing data, and build the specific thing that unblocks them. Your performance will be measured in part by the output velocity of the people around you. If the content lead is not shipping more, faster, better because of what you built, the work is not landing.

Make rigorous build-versus-buy decisions. Build when building is the right answer. Buy when buying is the right answer. The skill we are hiring for is the judgment to distinguish between them, and the taste to know that a working tool nobody uses is worse than no tool at all. A great marketing engineer kills more ideas than they ship. We expect the same from you.

Bring creative judgment to every build. The creative half of this role is as load-bearing as the technical half. You decide which agents are worth building and which are distractions. You shape the voice and point of view of the outputs your systems produce. You read a brief, a landing page, a launch plan, and you know when the idea is sharp and when it is slop. You argue for positioning in the room. You kill work that looks useful but will rot without a human watching it. The tools are the paintbrush. The taste is the job.

What success looks like

At 90 days. You have shipped at least one internal tool the team uses weekly. You have mapped our marketing data infrastructure end to end. You have a written point of view on the three highest-leverage things to build next and the two things we should kill.

At six months. You have replaced or retired at least one underperforming vendor. You have put at least two production agents or workflows into daily use. You have built a measurement system the VP of Marketing references in every operating review. One person on another team can name a specific thing you built that made their week faster.

At twelve months. The marketing team ships materially more output per person than it did before you joined. The rest of the company can name specific things you built and specific ways the work got better because of them. You have a defensible point of view on whether and when to hire the second marketing engineer, and the beginnings of a plan for what that team looks like in year two.

What we are looking for

Creative judgment about what to build. This is the first and most important attribute. You consistently identify which problems are worth solving and which are distractions. You build systems people actually use, not systems that demonstrate technical capability. You can look at a workflow and see the shape of the hundred others that run on the same structure. The tools are the paintbrush. You are the artist. We are hiring the artist.

Demonstrated experience shipping production software with AI tools. At least one substantial project that other people depended on to do their work. Built inside a company, inside a founding team, or independently. We will evaluate the work directly. Show us the thing, not the resume.

Fluency with modern AI tools and workflow systems. You build with the current generation of AI-native tools rather than from scratch. Working proficiency in at least two of Lovable, Replit, Cursor, v0, Bolt, or equivalent. Working proficiency in at least one modern workflow or agent platform such as n8n, Gumloop, Relay, or Zapier with AI actions. Direct hands-on experience with at least two frontier LLM APIs, including evaluating model outputs against each other for real tasks. Working knowledge of Clay or a comparable enrichment tool. Hands-on experience with Profound. You have used it to monitor share of voice across answer engines, identify citation gaps, and ship the work that closes them.

Sound judgment about when to apply AI. You have deployed language models in production and have informed opinions about model selection, prompt design, evaluation, cost management, and failure modes. You know when a model is the right tool and when a simpler approach will outperform it.

Narrative and product instinct. You can tell when an output is sharp and when it is slop. You can read a landing page and know what is off. You can hear a customer problem and see the agent that solves it. This is the creative range the role depends on, and it is the reason we are not hiring a junior engineer.

Strong written communication. You will explain technical work to non-technical stakeholders, on an ongoing basis, in writing. Clarity, concision, and narrative structure are required. If you cannot write, you cannot do this job.

Operating speed consistent with a marketing function. Marketing runs in cycles of days, not sprints. You are comfortable shipping working software in short timeframes, iterating against real feedback, and accepting that some work will be revised or discarded. If your instinct is to spec for two weeks before you build, this is the wrong role.

Compensation and structure

Base salary $180,000 to $220,000, calibrated to depth and scope of demonstrated experience. Equity on the senior IC band, meaningful at this stage of the company. Remote within the United States.

The clean JD formatted for Greenhouse is downloadable here. Steal it, edit the company-specific lines, and ship it.

90-day scorecard

If you cannot tell whether the hire is working by day 90, you scoped the role wrong.

Days 1 to 30. Land.

Mapped the marketing stack end to end. Knows every system, where the data lives, and which connections are brittle. Can draw it on a whiteboard from memory.

Shipped one small thing the team uses. A script, a dashboard, an internal tool. The artifact does not matter. The evidence that they can ship inside this company does.

Built a working relationship with one counterpart in every adjacent function. Engineering, data, PMM, content, demand generation. Each of those people can tell you what the new hire is working on this week.

Written point of view on the three biggest time sinks on the team. Documented. Shared with the VP. Prioritized. The two they plan to kill go in the same doc.

Days 31 to 60. Build.

Shipped at least one production workflow that replaces a manual process. Measurable time saved, quantified in writing. “We got four hours a week back on the content QA loop,” not “the team feels faster.”

Built at least one measurement view that did not exist before. The VP of Marketing opens it in the weekly operating review, unprompted.

Killed, renegotiated, or consolidated at least one vendor contract. Savings documented and returned to the budget or redeployed. The finance partner knows the number.

Public backlog in place. Prioritized and versioned. Anyone on the team can see what is coming, what is in flight, and what was explicitly deprioritized and why.

Days 61 to 90. Compound.

Shipped something that made another marketer measurably faster. Named person, named workflow, quantified time saved. “Sarah on content used to spend six hours a week on competitive research. Now she spends forty minutes.”

Two or more production workflows running with real reliability. Logged, monitored, and debuggable by someone other than the marketing engineer in an emergency. The bus factor is not one.

Presented at a marketing all-hands or operating review. The team understands what was built, why it matters, and what is next. If nobody on the team can explain the role in their own words after this presentation, the role is not landing.

Formed a point of view on the second marketing engineer hire. They are thinking about the shape of the function, not just their own backlog. This is the earliest signal of a senior IC who will eventually lead one.

The bar

Two questions at day 90, asked honestly.

Did the marketing team ship materially more than it would have without this hire?

Is the rest of marketing actively asking for more of what this person does?

If both answers are yes, the hire is working. Invest. Expand scope. Start the case for the second one.

If the answer to either is no, the scorecard above will tell you where the breakdown is. Two failure modes to watch for specifically.

They shipped nothing. The role requires someone who ships under ambiguity. If 90 days produced no working artifact, the candidate does not have that disposition, regardless of how they interviewed. This is not coachable on the timeframe the role operates on.

They shipped a lot but nothing the team uses. The role requires taste about what to build. If 90 days produced ten tools and none of them are in daily use by anyone other than the builder, the candidate is building for themselves, not for the team. This is the creative judgment failure mode from earlier in this piece, arriving exactly where we said it would.

Either failure mode resolved at day 90 is less expensive than the same failure mode resolved at day 180. The cost of not having the conversation at 90 is three more months of budget, three more months of the team not getting leverage, and a role that now has a reputation problem inside the company. Have the conversation. On time.

How to know you hired wrong

Four signals. Any one of them is enough to start the conversation at day 60, not day 90. Waiting until 90 is how you end up in month six explaining to your CEO why the role is not working and why you did not see it coming.

They are waiting for specs. A marketing engineer who needs a PRD for every project is a marketing ops manager with different tools. The role requires going from “this is slow” to a shipped solution without a PM in the middle. If at day 45 they are still asking what to build rather than proposing what to build, the disposition is wrong. This is not coachable in the timeframe the role operates on. You can teach a tool. You cannot teach the instinct to ship without permission.

They are building the wrong size of thing. At day 45 they are six weeks into a platform rebuild rather than shipping small things the team uses. The instinct is inverted. The job is a compounding sequence of small wins, not a single big reveal. The correct pattern in the first 90 days is five small tools in daily use, not one large tool still in development. If you see the inverse, the builder is optimizing for their own portfolio, not for the team.

Nobody on the team can tell you what they are working on. Ask the content lead. Ask the demand gen owner. Ask the PMM. If all three shrug, the role is not landing. A marketing engineer whose work is invisible to the people they are supposed to make faster is working in the wrong direction, regardless of what they are building. The correction is fast and specific. Embed them with one function for two weeks and measure whether adoption changes. If it does not, the fit is wrong and two more weeks will not change that.

They are performing AI instead of using it. Every conversation is the newest model, the latest agent framework, the workflow tool someone posted about on LinkedIn that morning. Nothing has shipped. You hired a hobbyist. The best ones are boring about the technology and precise about the output. A useful diagnostic: ask what they shipped in the last two weeks and what it is producing for the team. If the answer is a demo instead of a deployed system, you have your signal.

A note on the conversation itself

Having this conversation at day 60 is the correct move in every case, even when you are not sure. A senior IC who is landing well will not be destabilized by honest feedback at day 60. A senior IC who is not landing well needs the feedback to have any chance of recovering. The only case where day 60 feedback is wrong is if you are avoiding the conversation because you are uncertain, which is the exact case where avoiding it causes the most damage.

If after day 60 feedback and a clear recovery plan the signals persist at day 90, the answer is not more time. It is a clean separation, handled well, and a restart of the search with sharper filters. The cost of a wrong hire in this role is higher than in most, because the whole team is depending on velocity that is not materializing. Every week you spend waiting is a week the rest of marketing is not getting the leverage the role was supposed to produce. That cost is cumulative. Act accordingly.

The line

The first marketing engineer you hire will shape the next five.

They will set the bar for who gets hired after them. They will set the expectation for what this role can produce. They will decide, through what they ship and what they refuse to ship, whether the rest of your org treats this as a real discipline or a vanity title the marketing leader added to look modern.

Get the first one right and the function compounds. Every tool they build makes the next hire more productive. Every workflow they deploy lowers the marginal cost of the next campaign. Every measurement view they ship sharpens the judgment of the people around them. Two years in, you are not running the same marketing function with AI stapled on. You are running a different function. The competitors trying to copy it in 2028 will discover that the lead was structural, not tactical, which is the kind of lead that does not close without spending two to three times the comp to pull senior people out of the companies that moved first.

Get the first one wrong and the opposite happens. The tools do not get built. The vendor contracts do not get killed. The team does not get faster. You spend the credibility of the role itself, which makes the second hire harder than the first one should have been, because the story inside your company is now that this role does not work.

This is why the req matters more than the sourcing pass. Why the scorecard matters more than the interview loop. Why defending the comp band matters more than closing the candidate. The cost of getting this hire wrong compounds in the same direction as the value of getting it right, and both curves are steep.

You now have the playbook. Scope the role. Steal the req. Run the scorecard. Defend the comp.

Then go find the person.

About StackedGTM.AI

StackedGTM.ai shapes how modern GTM categories are understood, evaluated, and bought. Playbooks, frameworks, and operator intelligence for the CMOs, VPs, and founders navigating the AI shift.

Written by someone who has run the motion, for the operators running it now. No hype. No cosplay. No fluff.

In 2025, across the buying questions that matter most to someone evaluating a CMS platform, Webflow ranked first in AI-generated answers. WordPress ranked second.

Webflow has 1.3% market share.

When my SEO and AEO team started deploying Profound to track and manage which brands owned the answers across our category, the result stopped me cold. We had spent years building presence inside the web design and dev community, inside the AI-native conversation, inside the modern web discourse. Those signals carry enormous weight with the models synthesizing answers for buyers evaluating platforms. WordPress had dominant volume. We had built relevance in the right places. In the environment that now shapes buying decisions, those are not equivalent advantages.

That inversion is the whole game.

The old moat was built from what you had accumulated: backlinks, brand awareness, content volume. These compounded over years into barriers new entrants could not cross. The new moat is built from what you can consistently maintain: answer presence across the right question clusters, coherent positioning across every surface AI systems index, citation surface area built in the formats models actually pull from.

These also compound over time. But they compound in favor of whoever executes most consistently, not whoever started earliest or spent the most.

A team with the right operational infrastructure can displace a competitor with ten times the content budget, if that competitor is still running the old motion.

Most teams understand this. Almost none can execute it at the pace the environment requires. This piece is about that gap.

Why understanding the strategy is not the same as having one

There is a person on your team, usually whoever owns SEO or content, who manually runs your top buying questions through ChatGPT, Perplexity, and Gemini every few weeks. Who screenshots what comes back. Pastes it into a spreadsheet. Tries to spot patterns, writes a summary, and brings it to a meeting that happens once a month.

By that point the data is three weeks old.

Meanwhile, the answer your competitor is getting cited for has been live for six months. The Reddit thread shaping your category narrative has been indexed for a year. The G2 reviews drifting away from your positioning have been accumulating since last quarter. A comparison page on a third-party site is feeding a version of your differentiation you never approved.

You are doing the work. You are always behind it.

This is the execution collapse nobody names clearly. Not a strategy problem. Not a vision problem. A structural mismatch between the pace at which AI-search environments move and the pace at which manual content operations can respond.

In traditional search, strategy and execution were separable. You wrote the playbook, handed it to a team, and measured performance against it over quarters. In AI search, they are the same thing. Your Answer Ownership strategy is, in practice, whatever your team can consistently execute at the frequency the environment demands.

A team that cannot monitor across five AI interfaces and twelve third-party platforms every week does not have a monitoring strategy. They have a monitoring aspiration. A team that cannot propagate a positioning update across every content surface within days of a messaging shift does not have a consistency strategy. They have a wishlist.

The execution layer is not beneath the strategy. It is the strategy made real, or not made real, depending on whether your team can keep up.

Marketing budgets flatlined at 7.7% of company revenue in 2025. 59% of CMOs report insufficient budget to execute their strategy. The gap is not money. It is operational infrastructure. The teams widening the distance have built systems that monitor, update, synthesize, and distribute at a pace a manual team cannot match. The teams falling behind have not.

Why the urgency is not where most teams are treating it

The share of zero-click searches grew from 56% to 69% in a single year. When AI Overviews appear, organic CTR falls from 1.76% to 0.61%. The top organic result is no longer a traffic guarantee. It is a citation candidate.

The standard response is anxiety about traffic. The more important story is what the traffic arriving from AI search is actually worth.

Ahrefs found that AI search visitors generated 12.1% of signups while accounting for only 0.5% of all traffic. That is a 23x conversion premium over traditional organic. NerdWallet surfaced the same pattern on two consecutive earnings calls: less traffic, more revenue. When their CEO told Morgan Stanley analysts that LLM referral conversion rates were “much higher and growing rapidly,” he was not describing a new channel. He was describing a buyer who arrives post-synthesis, already informed, shortlist already forming.

These buyers are not at the beginning of research. They are at the moment of evaluation. Every surface they encounter needs to be built for that moment. Every surface that is stale, inconsistent, or absent is a gap a competitor fills.

Most teams are measuring a signal, organic traffic, that is structurally declining, while the metric that actually predicts pipeline health goes completely unmeasured.

The metric that replaces traffic

I call it Answer Capture Rate.

Your Answer Capture Rate is the percentage of your highest-revenue buying questions where your brand appears accurately and favorably in the synthesized answer, across the AI interfaces your buyers actually use. Not impressions. Not rankings. Not traffic. The share of the specific answers that form the shortlist a buyer brings to their first sales conversation.

ACR is the metric that replaces organic traffic as the primary indicator of AI search health, because traffic is no longer the mechanism by which most high-intent buyers find you. The mechanism is the answer. If your brand does not appear in the answer, the buyer’s shortlist forms without you, before a single page on your site is ever visited.

Most teams have no idea what their ACR is. They are optimizing for a signal that is structurally declining while the signal that actually predicts pipeline health goes unmeasured. A practical starting point: track 20 to 50 core buying questions across ChatGPT and Perplexity weekly. That is an operational problem, not a measurement one.

The five components below map exactly how to build ACR and maintain it at the pace the environment requires.

The Answer Ownership System: Five Agents, One Operating Layer

1. Monitoring: Continuous signal across every surface

Answer ownership is not a state you achieve. It is a position you maintain under continuous competitive pressure, across platforms that operate completely independently of each other.

Research from Profound found that only 11% of domains cited by ChatGPT also appear in Perplexity. These are not variations of the same system. They are fundamentally different recommendation engines with different citation behaviors, different source preferences, different update cadences. Monitoring one tells you almost nothing about the others.

Before automated monitoring was in place, narrative shifts surfaced through sales calls. By the time a deal debrief revealed that a buyer had seen a competitor’s framing, the content driving that framing had been live for months. Damage control on positions never known to be lost.

Once a monitoring Agent was watching the category continuously across AI interfaces, Reddit, LinkedIn, and review platforms, a competitor’s comparison page gaining citation share was caught within days of it being indexed. A response was live in a week. The gap between those two timelines is where deals are won or lost.

Response time compresses from months to days. In an environment where AI systems can absorb and reflect a new narrative in weeks, that compression is not an operational detail. It is the difference between owning the answer and chasing it.

Profound’s monitoring Agent runs this watch continuously, not on a schedule, across every AI interface, Reddit, LinkedIn, and review platforms simultaneously. When a competitor gains citation share, you know within days. The sales call that used to be how you found out about a narrative shift becomes a confirmation instead of a discovery.

2. Consistency: One source of truth across every surface

When an AI system builds an answer about your product, it pulls simultaneously from your website, your G2 reviews, your documentation, your blog, your YouTube descriptions, and your LinkedIn content. 44.2% of all LLM citations come from the first 30% of text. The opening third of every page is the citation target zone. If that opening says something slightly different from the opening on your comparison page, the model reflects that fragmentation back to the buyer.

Consider what this looks like inside most organizations. Your sales team uses “AI-native.” Marketing writes “AI-powered.” Documentation says “machine learning-enabled.” Three teams. Three reasonable approximations of the same claim. An AI synthesizing your brand across those surfaces does not pick the clearest version. It averages them. The buyer receives a blurry composite that none of your three teams intended to describe, and that blurry composite becomes the foundation of a buying decision.

I spent six weeks with one company doing nothing except closing consistency gaps. No new content. No new claims. Just taking what they already knew to be true about themselves and making it say the same thing across every surface their buyers encountered. Three months later, their brand was appearing in AI answers where it had been absent. The product had not changed. The coherence had.

That kind of maintenance, done manually, never fully happens. There is always something more urgent. The surface that should have been updated eighteen months ago is still running old messaging. The fragmentation accumulates quietly, and the model averages it into something none of your teams recognize as their positioning.

The consistency Agent treats your core positioning as a single source of truth. When messaging shifts, every downstream expression updates with it: website, documentation, product pages, review responses. The fragmentation that produces blurry AI answers gets closed before it compounds into something unrecognizable.

3. Reporting: Current data for decisions that cannot wait

Only 42% of marketing teams are actively monitoring AI search visibility at all. Most of those are doing it manually, which means they are tracking what happened, not what is happening.

In a category where citation share shifts meaningfully in weeks, a six-month-old ACR report is not a lagging indicator. It is a picture of a different market entirely.

Every content investment, every budget reallocation, every messaging decision made against stale data is calibrated to a map that has already expired.

The reporting Agent pulls ACR data on a set cadence and surfaces what moved, which competitors gained ground, and which question clusters need attention, without anyone spending hours extracting and consolidating. Leadership sees the metric that actually predicts pipeline health on a regular basis, built from current data. Competitors gaining ground in the answers that matter most surface before you feel it in pipeline, not after.

4. Distribution: Citation surface area at scale

80% of URLs cited by LLMs do not rank in Google’s top 100 for the original query. The citation map looks nothing like the old link graph. Case studies and pricing pages drive the highest AI referral traffic. How-tos and guides have cratered.

Every piece of foundational content you create has downstream expressions across Reddit, LinkedIn, YouTube, review platforms, and third-party comparison sites that represent real citation surface area. Most teams produce the foundational content and execute roughly 20% of the downstream distribution. The remaining 80% is repetitive, format-specific rewriting that never quite reaches the top of the priority list.

I worked with a Series B company in data infrastructure whose SEO metrics looked strong. Good domain authority. Solid rankings for core terms. When we audited their AI answer presence across top buying questions, they were almost invisible. Not second or third. Absent. A competitor had spent two years showing up consistently across Reddit, G2, and comparison platforms, answering the same questions clearly, in the formats AI systems actually pull from.

The uncomfortable part of that conversation was not identifying the problem. It was explaining that the competitor had done nothing technically sophisticated. They had just shown up consistently in the places that mattered. There was no shortcut. Just eighteen months of work that should have started thirty-six months earlier.

Ramp did the opposite. Using Profound, they identified that AI engines were citing automation and software comparison content, exactly what their traditional SEO had deprioritized, built two pages designed for AI pickup, and generated 300+ citations in thirty days. Their Accounts Payable solution went from 3.2% to 22.2% AI visibility in a single month. One month. Two pages. 7x from a standing start.

The distribution Agent scales that motion automatically. A single piece of foundational content gets transformed into a LinkedIn thread structured for indexing, YouTube metadata written for extraction, a Reddit contribution framed for the community where the buying question actually lives. Same positioning. Built from one source. The content calendar stays the same. The citation surface area multiplies.

5. Brand governance: Quality at velocity

As content velocity increases, brand consistency is the first thing to break. Tone drifts. Legal language gets approximated. The technical differentiation that required precise language becomes a vague claim that does not survive synthesis.

An AI system pulling from dozens of approximated surface expressions does not find the clearest version. It averages the drift. Every inconsistency is a signal the model discounts the next time it builds an answer about your category.

Brand guidelines living in a PDF nobody reads are not a guardrail in a high-velocity content operation. They are a wish. At speed, after-the-fact review either slows everything down or gets skipped. At scale, both outcomes destroy the quality floor that took years to build.

The brand Agent builds your voice, legal requirements, and tone standards directly into the output layer before content ships. The guardrail is structural, not procedural. The quality floor you spent years establishing stays intact as volume increases, without the approval cycle that either creates bottlenecks or gets bypassed entirely.

What the full system actually produces

The Webflow result I opened with was not a content sprint. It was what happens when a team gets visibility into the right signals and executes consistently against them. Profound gave us that visibility: continuous monitoring across AI interfaces, weekly reporting on which buying questions we owned and which we had already lost, a clear picture of where competitors were gaining citation share before we could feel it in pipeline. We knew where to work because the data told us. The team did the rest.

That was the motion run by a disciplined human team with the right intelligence. What is different now is that the execution layer itself is agentic. Profound Agents runs each component of the Answer Ownership System continuously, without the manual ceiling that made the motion hard to sustain at the frequency the environment requires. The strategy is the same. The infrastructure executing it has changed entirely.

The scale of adoption tells you something important. Over 1,000 enterprises now run on Profound, including 10% of the Fortune 500. Target, Walmart, Figma, Ramp, MongoDB, and Plaid among them. That is not a popularity signal. It is a confirmation that the infrastructure being replaced, manual monitoring, episodic reporting, inconsistent distribution, approximated brand standards, is exactly what most teams are still running. And those teams are losing citation share every week to the ones who replaced it, in answers their buyers have already moved on from.

Deploy First. Let Agents Do the Rest.

You already know you have exposure. Every team does. The question is whether you close it with a system that runs continuously or a manual audit that is already out of date before it lands in your inbox.

The agents are built. You do not need to hire for this. You do not need a sprint. You need to pick the component most exposed in your category right now and deploy against it.

Monitoring. Consistency. Reporting. Distribution. Brand governance. One of those is where your competitors are gaining citation share while you are reading this. The agent that covers it can be running before the end of the week.

Before Profound, we found out about narrative shifts in deal debriefs. Months after the damage was done. With Profound running, we caught a competitor gaining citation share within days. Response live in a week.

That compression is the whole game.

The companies that own their categories in three years started before the loss showed up in pipeline. Most teams are still waiting for the deal debrief.

StackedGTM.AI covers AI-native go-to-market strategy for B2B operators. No frameworks for frameworks’ sake. No theory without proof. If this piece changed how you think about how buyers find you, subscribe. There is more where this came from.

If you want to see the Answer Ownership System running in practice, start with Profound. I have been genuinely impressed with what they have built specifically around AI answer monitoring and agents. Real infrastructure for a problem most teams are still solving manually. That is rare right now.

Steal all three.

A buyer in your category opened ChatGPT this morning. Typed something like “best [your category] platform for a Series B SaaS company.” Got three names back. Closed the tab.

Your website never loaded. Your funnel never started. Your sales team never got the ping.

That moment left no analytics event. No Salesforce record. No form fill. And it happened dozens of times today across your category. The shortlist was built before you knew anyone was looking.

Most teams find out six weeks later when pipeline gets weird and nobody can explain why.

I have seen a lot of AEO content this year. Most of it tells you what to do. Optimize your schema. Get on Reddit. Publish more. That is all true. It is also completely manual in a game that moves 40 to 60 percent per month on citation volatility alone, per citation monitoring data across thousands of tracked queries. You cannot outrun that by hand.

The teams quietly pulling ahead are not doing more AEO. They are building systems that do AEO for them, continuously, while they sleep. Here are a few of them, and the exact prompts to build them.

Automation 1: The Content Refresh Pipeline

Here is the number that reframes this whole thing.

According to BrightEdge and Amsive research across millions of AI responses, ChatGPT only cites 15% of the pages it actually retrieves. The other 85% get found and skipped. Your content can be indexed, crawlable, and technically excellent and still lose every time. Being retrieved is not the same as being cited.

The reason most content loses is structural, not strategic. Analysis of LLM citation patterns shows 44.2% of all citations come from the first 30% of a piece of content. The opening, not the conclusion. If your page builds context before it answers, the agent moves on before it ever reaches your best material. Adding one named statistic improves AI visibility by 41%, according to Princeton and Georgia Tech’s 2024 GEO study. Per AEO citation research, pages updated in the last three months are cited twice as often as older ones.

Those three facts together are a workflow.

I have written about our Webflow work publicly. The AirOps case study documents the results: 5x content refresh velocity, 40% traffic uplift within days, AI-sourced signups growing from 2% to nearly 10%, AI-referred visitors converting 6x higher than non-branded organic. A separate AirOps recap put the share of voice growth from LLMs at 94% during the same period.

No new content strategy. No headcount. A pipeline that rewrote the opening of each target page to lead with the answer, injected one named data point, and pushed the update straight to the CMS. Human review as the only gate.

Here is exactly how to build it.

Pull your target pages from Google Search Console. Filter for queries with over 200 impressions and under 2% CTR. These are pages Google is already surfacing where AI is eating the click before it happens. Take the top 20 URLs and run this prompt in Claude with web search on, or drop it into an AirOps Power Agent or n8n Claude API node directly:

Visit [URL].

Score the opening 150 words on three criteria:
1. Does it lead with a direct answer (not context, not setup, the answer)
2. Does it contain a specific statistic with a named source and year
3. Can the opening be extracted without surrounding context and still make
   complete sense

Score each 1 to 10. Then rewrite the opening 100 words to score 10 on all three.

Rules:
- Keep the existing brand voice
- Do not add claims not already supported in the body of the page
- First sentence must be the answer, not a question or a scene-setter
- Statistic must include source name and year inline, not in a footnote

Return the three scores with one-sentence explanations, then the rewrite.

Wire this as a workflow. URL list from GSC in. Claude rewrite via API. Approved rewrites push to your CMS automatically. The only human touchpoint is a one-click approval. Add a visible Last Updated timestamp every time the pipeline publishes. Per AEO citation research, this single metadata change moved citation rate from 42% to 61% in controlled testing. Do it every time, on every page.

Schedule it to re-run monthly on your top 50 pages. Not because you will remember to. Because the workflow will.

AI did not rewrite the rules for content. It just raised the bar for clarity, structure, and freshness. Automated enforcement of that bar is the whole game.

Automation 2: The FAQ Plus Schema Engine

I have shared it publicly before.

Six Webflow product pages: Design, CMS, SEO, Shared Libraries, Interactions, Hosting. The workflow pulled real questions from People Also Ask, niche subreddits, and community forums simultaneously. Claude generated on-brand answers to the gaps. Those answers were structured into FAQPage JSON-LD and injected directly into each page.

The results:

331 new AI citations. 57% of all new citations on the domain that period. 149,000 additional SEO impressions. A 24% increase versus the prior period.

No hype. No AI buzzwords. Just structured answers to real questions people actually ask, delivered in a format AI engines are built to extract.

Per analysis of 2,000-plus cited pages across platforms, FAQ-heavy content with proper FAQPage schema achieves a 71% citation rate versus 58% without it. Without schema, the agent infers what your page answers. With it, you hand it a machine-readable instruction set. That 13-point gap is entirely structural and it is free to close.

The thing most teams get wrong is sourcing. Marketing teams write FAQ sections based on questions they think buyers are asking. Those are not the questions buyers type into AI engines at 11pm trying to solve a problem. The gap between those two sets of questions is where citations go to die.

Want to go deeper on question mining? I wrote the Definitive Guide to Questioning Mining here.

In Gumloop, drop in their Reddit Scraping node, zero configuration required. Point it at your two or three most relevant subreddits and pull the top 100 posts and comments. Separately, use a SERP API (SerpAPI and DataForSEO both have dedicated PAA endpoints) to pull Google’s People Also Ask boxes for your ten priority queries. Merge both outputs into Airtable, then run this:

Here is a list of questions pulled from Reddit and People Also Ask for [category].

1. Cluster by buyer intent: Awareness, Evaluation, Decision

2. Within each cluster, identify the five questions appearing most frequently
   across both sources

3. For each of those 15 questions, check our content at [URL] and flag:
   - Answered directly
   - Answered partially
   - Not answered

4. For every Partially Answered and Not Answered question, write a 60-word
   direct answer:
   - First sentence is the answer, not a lead-in
   - Include one specific data point with a named source
   - Must make complete sense without surrounding context
   - No hedging language

Return as a table: question, intent stage, coverage status, answer draft.

Run approved answers through this before touching schema:

Edit this FAQ answer for FAQPage schema deployment:

[paste answer]

Requirements:
- Under 80 words
- First sentence is the answer
- One specific data point with named source and year inline
- Self-contained (someone reading only this understands it fully)
- Reads like a knowledgeable human wrote it

Return only the edited answer. No explanation.

Then generate deployment-ready JSON-LD:

Convert the following FAQ pairs into valid FAQPage JSON-LD schema
following schema.org specifications.

[paste question and answer pairs]

Format:
- Valid JSON-LD in a <script type="application/ld+json"> tag
- Each FAQ as a Question entity with acceptedAnswer
- Full answer text, no truncation
- Ready to paste into a page head with no further editing needed

Return only the schema block.

Paste that block into your page head. If you are on a platform without custom code access, the workflow outputs a handoff file engineering can implement in ten minutes.

Schedule the full workflow every four weeks. New questions surface constantly. The automation catches them. You do not have to.

The playbook is simple: use data on the questions people are actually researching, create content that answers them clearly, and structure it so AI engines can surface it with precision. The workflow just makes that repeatable.

Automation 3: The Competitive Displacement Agent

This is the one almost nobody has built yet.

Per Yext analysis of 6.8 million citations across platforms, only 11% of domains are cited by both ChatGPT and Gemini. Per BrightEdge research, 80% of the URLs being cited right now do not rank in Google’s top 100. Citation volatility runs at 40 to 60 percent monthly, per citation monitoring data across thousands of tracked queries. By the time your quarterly review catches a drop, it has been compounding for weeks.

Manual monitoring fails at the speed this moves. You need a closed loop.

Docebo is a learning management platform in a crowded enterprise software category. They built systematic tracking of AI share of voice and automated response to competitive displacement across their content library. The results AirOps documented: a 25% share of voice lead in their category, with AI discovery driving 12.7% of high-intent leads, up 5x year over year.

Not from a content sprint. From a system.

In Profound, AirOps, or Semrush’s AI Visibility Toolkit, configure tracking for 20 to 30 priority queries, the exact questions your buyers type when evaluating your category. Run your first full pull. Save every response. That is your before-state. Everything from here is measured against it.

In Make.com, build a scenario that pulls citation data weekly via your tracking tool’s API. Set one condition: if any tracked query drops 15% or more week over week, the scenario fires. When it fires, it passes this to the Claude API:

A citation drop was detected.

Brand: [brand]
Query: [query]
Drop: [X]% week over week
Current top-cited pages: [URLs and titles]
Our current content: [URL]

1. Diagnose why competitors are being cited instead of us:
   - Does their opening answer the question more directly
   - Do they have a comparison table we are missing
   - Do they cite more recent or specific data
   - Are their sections shorter and more extractable
   - Is their schema more complete

2. Identify the single highest-leverage fix

3. Write a specific content brief:
   - What exactly changes and where on the page
   - The first sentence of the fix as a model
   - Any specific data point to add with suggested source type

Return: diagnosis in two paragraphs, brief in bullet points. Under 300 words.

That diagnosis routes to Slack. One-click approve fires a second call that drafts the full fix and pushes it to your CMS:

Using the diagnosis and brief below, draft the content fix for [URL].

Diagnosis and brief:
[paste output from above]

Current content at the relevant section:
[paste existing section]

Rules:
- Match existing brand voice exactly
- Do not introduce claims not supported on the page or in public sources
- Fixed section must open with a direct answer
- If a comparison table is recommended, build it, do not describe it
- Output ready to paste into the CMS

Return only the replacement content. No preamble.

Citation drop detected. Competitor identified. Fix drafted. Published. Under two hours. Nobody had to notice it happened.

Once a month, run the entity audit. Feed Claude your homepage, G2 profile, LinkedIn company page, and most-cited blog post:

I am giving you four descriptions of [brand] from different surfaces.

Homepage: [paste]
G2 profile: [paste]
LinkedIn company page: [paste]
Most-cited blog post intro: [paste]

Analyze for entity consistency across:
- How we describe our product category
- How we describe our ideal customer
- Our primary differentiator
- The use case we lead with

For each inconsistency:
1. Name the specific conflict
2. Explain in one sentence what citation damage it causes

Then write:
- A 75-word canonical brand description optimized for AI entity clarity
- The exact copy update for each surface to bring them into alignment

Return as: Inconsistencies, Canonical Description, Surface Updates.

Per AEO citation research, brands earning both citations and mentions are 40% more likely to resurface consistently across multiple AI responses than brands earning mentions alone. Entity drift, where your brand gets described differently across surfaces, is one of the most common and least diagnosed reasons citation rates plateau. One prompt, once a month, run automatically. It catches drift before it compounds.

The winners of AEO right now are not the best content teams. They are the best systems thinkers.

These three automations are not three separate tactics. They are one ecosystem. The refresh pipeline keeps your content citation-ready. The FAQ engine keeps your answers sourced from where buyers actually ask. The displacement agent closes the loop when competitors move. Each one compounds the other. None of them work as well in isolation.

Agents are making this job both easier and more complex at the same time. Easier because the execution layer — the research, the rewrites, the schema, the diagnosis — can now run without you. More complex because the game is no longer about publishing good content. It is about building infrastructure that responds faster than any manual team can. The brands figuring that out right now are building leads that will take competitors years to close.

The buyer who opened ChatGPT in your category this morning got three names back. Yours was either one of them or it wasn’t.

78% of marketing teams have no way of knowing which. Per Averi.ai analysis of AI referral data, the traffic coming through that channel converts at 14.2% versus Google organic’s 2.8%. The highest-intent buyers in your funnel are arriving through a channel most teams cannot see, let alone defend.

These three systems fix that. Not eventually. This week.

Build the first one. Let it run. Then build the next.

Building one of these workflows this week? Reply and tell me which one. I read every response.

Josh Grant Founder, StackedGTM.AI | Ex-VP Growth @ Webflow | Ex-Affirm

There is a version of a GTM interview where a journalist asks a practitioner to explain their job to an audience that has never done it.

This is not that.

George Bonaci is VP of Growth at Ramp. He thinks in systems, moves in first principles, and has a specific kind of clarity about where GTM is going that you only develop by actually being in it at scale.

I am Josh Grant. Most recently VP of Growth at Webflow. Before that, Affirm. I have spent the last year obsessing over what happens to growth and demand generation when AI collapses the buying journey and the funnel stops being measurable in the ways we were trained to measure it.

We are both operators. We have both built growth engines inside companies with billions of dollars of pressure on them. We have both had to make bets with incomplete data, defend positions in QBRs with imperfect attribution, and figure out what modern GTM actually means in practice rather than in a LinkedIn carousel.

This interview is what happens when two people who have actually done the job stop being polite about it.

No frameworks for beginners. No safe takes. No “it depends” without the answer that follows it.

Just two growth leaders at the frontier, trying to figure out what comes next.

In a recent post I wrote about what GTM operators are unlearning in 2026, you dropped this: “The real skill is knowing which nodes on your org chart should be humans and which should be agents.” That line stopped a lot of people mid-scroll. So let’s start there. How are you actually making that call at Ramp right now, and what does the decision framework look like in practice?

Most people hear “agents” and think “faster employees.” That’s the boring version. The interesting question isn’t “what can AI do?” It’s “what should a human never have to do again?”

When I look at any role across the 8 growth teams, I ask one question: if this role disappeared tomorrow, would anyone notice the *decisions* were missing, or just the *output*? If the answer is output, that’s an agent. If the answer is decisions, that’s a human…for now at least.

I apply the same logic to the growth org chart. We’re literally hiring for a role we call the “Agentic Operator” - and the name is intentional. It’s not “AI Marketing Manager.” It’s someone who thinks about which workflows should be autonomous systems and which require human judgment.

And when thinking through the details I have a more in depth framework. The framework has three questions. First: is the decision computable or interpretable? If you can express the decision rule in a way that’s predictably measurable - bid optimization, send-time optimization, audience expansion based on historical lookalikes - that’s an agent node. If the decision requires pattern recognition that depends on taste and intuition, that’s a human node.

Second: what’s the cost of a wrong answer? If a wrong answer wastes a small test budget, fine. If it poisons a relationship with a CFO evaluating a $2M spend management contract, that’s a human that should be on the hook.

Third - and this one most people miss: is the task load-bearing for someone’s growth as a professional? I won’t completely automate a task that is the primary way someone on my team develops judgment. Otherwise you are trading efficiency for an organizational lobotomy. You’re saving the company $80K while destroying a future Director of Growth.

Having said all that, here is what might be uncomfortable: the ratio of output to decisions is roughly 80/20. Eighty percent of what knowledge workers do is production, not decision-making. The actual decision surface in most marketing roles is shockingly thin. Most companies have just built organizations that disguise production as strategy because headcount is how old fashioned leaders measure their importance.

So at Ramp, we are deliberately working to shrink the team’s production load to near-zero and concentrating humans entirely on taste and novel strategy. Taste meaning: does this feel right for our buyer? Would a CFO trust this? Novel strategy meaning: what bet should we make that no playbook covers?

The punchline is we’re not replacing headcount with agents. We’re replacing task fragmentation with agents so the humans who remain are doing the work that makes them more dangerous next quarter.

Ramp operates in a category where the buying decision is increasingly happening before anyone talks to sales. Buyers are researching, comparing, and shortlisting inside AI before they ever fill out a form. How are you thinking about owning that answer layer, and is it showing up in your pipeline data yet?

Here’s what’s actually happening: the buyer’s journey is inverting. It used to be awareness, consideration, decision, action. Now a CFO opens ChatGPT or Claude and says “what’s the best AP automation tool for a 500-person company” and gets 2 or 3 options in eight seconds. The consideration phase moved before awareness. You’re being evaluated before you even know you’re in the room.

We treat this as an AEO problem, not anything else. We went from sporadic AI citations to dominating answers for queries we care about. How? We reverse-engineered what makes an AI cite you. It’s not keyword density. It’s not backlinks. It’s structured proof. Named customers. Specific problems. Quantified outcomes. Implementation mechanics. When a finance leader asks an AI “who should I trust to manage $50M in spend,” the AI is looking for receipts - same as that leader would.

The thing most people aren’t seeing: this creates a winner-take-most dynamic more extreme than Google’s page one. In traditional search, position two still gets clicks. In AI answers, there’s often only one recommendation. The citation layer is a power law, and we’re in the land-grab phase right now. The alpha is now.

Is it showing up in pipeline? Yes. We’ve been seeing a growing cohort of inbound where the first touchpoint is effectively invisible in our attribution system - no ad click, no webinar, no content download. They just show up ready to buy. When we talk to them, a meaningful percentage say some version of “I asked ChatGPT.” That’s the dark funnel becoming the primary funnel.

Most growth leaders are still running toward traffic, MQLs, and pipeline volume. What is the metric you are actually optimizing for in 2026 that most of your peers are not measuring yet?

Revenue per cognitive hour.

Not revenue per headcount. Not revenue per marketing dollar. Revenue per hour of genuine human *thinking* my team invests.

Here’s why this matters. When agents start handling 60, 70, 80 percent of production, your cost structure collapses in a way that breaks every existing ratio. CAC looks absurdly low but the denominator changed, not the numerator. Pipeline volume spikes but the marginal cost of a bad lead hits near-zero, so quality signals get noisier.

Revenue per cognitive hour cuts through that. It forces you to separate thinking from execution. And when you do that honestly, you realize most of your very smart team’s week isn’t thinking. It’s execution.

When you compress all the production work into agents and look at what’s left, you find out how much strategic capacity your team actually has. At Ramp, that number surprised me. We had more raw strategic horsepower on the team than I thought. It was just buried under busywork. Freeing it up requires a new agentic first architecture.

The implication is stark. If you measured this honestly at most companies, you’d find that doubling your team’s impact doesn’t require doubling headcount. It requires cutting their non-thinking work by 80% and letting them actually think.

We both came up through growth at unicorns during a specific era. Blitzscaling, paid acquisition, funnel optimization, CAC math. What is the one thing you learned in that era that you have had to actively unlearn, and what replaced it?

I spent years worshipping funnel conversion rates. Top of funnel, middle of funnel, bottom of funnel. Every QBR was a waterfall chart. Every optimization was about finding the leak and patching it. And it worked - in a world where the buyer journey was linear and measurable.

What I had to unlearn is the core assumption underneath all of that: that the buyer’s journey is a sequential process you can instrument and optimize stage by stage. That assumption is just wrong now. It makes you optimize for local maxima at each stage while missing the system-level dynamics that actually drive growth.

What replaced the funnel for me is something I think of as a field model of demand. Instead of a funnel with stages, I think about a field with gradients. Buyers exist in a field of awareness, trust, and intent that shifts constantly based on signals from everywhere - AI recommendations, peer conversations, product experience, brand perception, content, news. Your job isn’t to move people through stages. It’s to increase the overall field strength so that when someone hits a trigger moment — their current vendor screws up, their company hits a growth threshold, a new budget cycle starts — the gradient naturally pulls them toward you.

Now, I know what you’re thinking: “If I am at a traditional company, how do you explain field theory to a board that wants a waterfall chart?” but that’s the reality of the new world we are marketing in.

There are two versions of AI adoption in GTM. One is workflow automation: move faster, do more with less. The other is structural: it changes what the team looks like, what the success metrics are, how decisions get made. Which version is Ramp actually living, and what did it take to get there?

I told my team something a few months ago that was unusual to hear. I said: I actually don’t care if we miss our numbers in the short term if it sets us up for long-term success. The goal should be that we don’t even want to hire anyone going forward because it would slow us down compared to investing in agentic capabilities.

And that wasn’t just a motivational speech but rather a resource allocation statement. And it’s the difference between workflow and structural adoption.

Workflow automation is using AI to do the same work faster. Your writer drafts with Claude. Your analyst summarizes with a model. The org chart stays the same. The job descriptions stay the same. You get more throughput.

Structural adoption is when AI changes *what work exists*. Not faster copywriting, but content that generates itself at the point of need with no writer in the loop. Not faster analysis, but continuous autonomous monitoring that surfaces decisions you didn’t know to ask about.

Getting to structural adoption required one thing above all: permission to sacrifice short-term output for long-term capability. Most growth teams can’t do this because they’re measured quarterly and optimizing for agents is a multi-quarter bet. That’s why the org chart question from your first question matters so much. If your team is set up to produce, they’ll resist the shift to building systems. You have to change what the team *is* before you can change what it *does*.

You are sitting at the intersection of fintech and AI at a moment when both are moving fast. Where do you think most growth leaders are still underestimating the shift, and what are they going to wake up to in the next 12 months that they are not seeing yet?

The org chart is the bottleneck. Not the tech.

I wrote this on LinkedIn but most growth teams are still organized like it’s 2024. Writer writes. Designer designs. Ops person wires it together. PM manages the backlog. But the job of a growth team was never to launch ads, design A/B tests, or write emails. Those are tasks. The job is solving the problems that prevent the company from growing faster. Most teams spend 90% of their time on tasks and 10% on problem-solving.

AI can flip that ratio. But only if you let it. And most orgs won’t, because the tasks are what justify the headcount. This is the part no one says out loud: the biggest obstacle to AI adoption in marketing isn’t the technology. It’s the incentive structure. Leaders who’ve spent careers building empires of 30, 50, 100 people are not going to voluntarily shrink those empires, even when shrinking them would make the team more effective.

Two other things people are sleeping on:

The buying entry point is shifting from search engines to thinking engines. You can’t buy a PPC ad inside ChatGPT’s response (well not really at least). You can’t retarget someone on Claude. The entire concept of a paid channel that you can buy inventory in starts to dissolve when the primary research interface is conversational AI.

And marketing in general is splitting in two. Content for humans (stories, emotion, brand trust) and content for machines (structured data, citation-worthy facts, verifiable claims). Different strategy, different team, different measurement. Most companies are still focused on one and hoping it works for both. It won’t.

If you were building a growth function from scratch today, zero legacy stack, zero inherited playbook, first principles only, what does day one look like?

Day one, I don’t hire anyone. Genuinely how I’d start, not a provocation.

Day one is me, a terminal, and three questions. Who is the buyer, and what are they asking their AI assistant right now? Not in a personas-and-journey-maps way. In a literal, “I’m going to map the top 100 prompts a buyer in my category types into Claude and see what comes back” way.

Second: what proof do I have that this product delivers? Not messaging. Not positioning. Proof. Numbers. Customer outcomes. Verifiable claims. I’d build a proof library before I touched a content calendar.

Third: what are the five to ten decisions per week that, if made well, actually move this business? And which of those can an agent make autonomously?

Day two, I build three agents before I make a single hire. An answer engine monitor that tracks my brand’s presence across LLMs daily, identifies opportunities, and kicks off work to capture them. A competitive intel agent watching pricing pages, feature launches, messaging changes, finds our angle, and implements it. A content production agent that takes my proof library and generates content, pages, and whole inbound flows, optimized for both humans and agents.

Day three, first hire. One person. Not a traditional marketer. A systems thinker who can code. Someone whose instinct when they have an idea is to build it, not brief it. This person’s job is to build the system that does marketing.

The traditional growth playbook says hire a team, build a funnel, buy some ads, optimize the conversion rate. That playbook assumes humans are the unit of production. They’re not anymore. Agents are. Humans are the unit of strategy.

The playbook most growth leaders learned was built for a world where humans were the unit of production.

That world is gone.

What replaces it isn’t a new playbook. It’s a new question: not “how do I build a bigger team?” but “what decisions does my team actually need to make?”

George has already answered it for Ramp.

The ones who win the next three years will be the ones who stop defending the old answer and start building around the new one, right now.

The most dangerous thing in your head right now isn’t what you don’t know.

It’s what you’re sure you know that no longer applies.

Every operator I respect is going through some version of the same reckoning right now. The frameworks that got them here are quietly becoming the ceiling keeping them from what’s next. The playbooks they’ve defended in QBRs, the mental models they’ve built careers on and now, they’re stress-testing all of it.

I asked ten of them to name it out loud. Here’s what they said, and what it means.

1. Traffic is not the proxy anymore.

Kevin Indig, Growth Advisor, put it plainly: “In 2026, I’m unlearning that traffic is the best proxy for growth. As AI answers more questions before the click, visibility, trust, and pipeline matter more than pageviews.”

This is the first domino. If your north star metric is sessions or pageviews, you are optimizing for a world that is actively dissolving. AI search doesn’t send traffic…it absorbs intent and returns answers. The companies winning in this environment aren’t chasing clicks. They’re engineering the answer. Visibility in the model is the new first-page ranking, and it doesn’t show up in Google Analytics.

2. Software as the default is over.

Aakash Gupta, Founder of Product Growth, said something that should make every SaaS vendor nervous: “I’m unlearning using software and doing everything with Claude Code instead. I even run my edits through there now.”

The assumption baked into most GTM stacks is that tools are the answer. Buy the platform, configure the workflow, train the team. That assumption is cracking. When a single AI interface can replace five tools, the question stops being “which software should we use” and starts being “which software still deserves to exist in our stack.”

3. Delegation is being redesigned from the ground up.

Ethan Smith, CEO of Graphite, named something most leaders won’t admit: “I am unlearning some forms of delegation. I am able to ask AI to do so much of analysis and work that I want completed, that I can do much of my work by myself. I still delegate, but less than I did before.”

This is uncomfortable because delegation has been a leadership virtue for decades. The executive who “lets go” is celebrated. But if AI can do the analysis, draft the memo, model the scenario — the math on what requires a human changes. This isn’t about replacing people. It’s about being honest that some of what we delegated wasn’t leadership. It was just work we didn’t want to do.

4. The org chart is a design problem now.

George Bonaci, VP Growth at Ramp, reframed the entire people management conversation: “I’m unlearning ‘span of control’ as a people problem when in 2026 the real skill is knowing which nodes on your org chart should be humans and which should be agents.”

Span of control, how many people a manager can effectively oversee, has been an organizational design constraint for a century. Bonaci is saying that constraint no longer applies uniformly. Some nodes on the chart should be agents. Which ones? That’s the new design question, and most organizations haven’t started asking it.

5. The marketing team structure is ending.

Jonathan Martinez, Founder of GrowthPair, didn’t hedge: “Old structure of a marketing team. It’s coming to an end, and we’re going to see an advent of new roles/org structure. Growth marketers -> growth engineers, media buyers -> creative strategists, etc.”

The job titles we’ve hired for over the last decade were built around a specific division of labor that AI is collapsing. Growth marketers who can’t build are becoming less valuable. Media buyers who can’t think creatively are becoming redundant. The operators who will matter in two years are the ones who are already expanding into adjacent skill sets — not waiting for a job description to tell them to.

6. Attribution will never explain everything. Stop waiting.

Simon Heaton, Director of Growth Marketing at Buffer, named the belief that has quietly paralyzed more marketing teams than any other: “I built my career on data-informed growth, but I’m unlearning the belief that attribution will eventually explain everything. In today’s fragmented discovery landscape, conviction, customer closeness, and a deep understanding of your market are becoming a bigger part of the job again.”

We’ve been waiting for the attribution model that finally solves it. It isn’t coming. The customer journey is too fragmented, too nonlinear, too influenced by channels that don’t pass UTMs. What replaces perfect attribution isn’t guessing — it’s judgment. Which requires being close enough to your customer to have earned an informed opinion.

7. The tool-switching reflex is done.

Eoin Clancy, VP Growth at AirOps, captured something I’ve felt but haven’t named cleanly: “In 2026, I’m unlearning the desire to log into individual tools when there’s a job to be done. From strategy to reporting, MCPs are helping me make decisions faster, and with more depth.”

The habit of opening a specific tool for a specific task — CRM for contacts, BI tool for reporting, doc for strategy — was trained into us by a decade of SaaS. That habit is becoming a tax. The operators moving fastest right now are the ones who’ve broken it.

8. Staying a beginner is the strategy.

Pranav Piyush, CEO of Paramark, said the quietest thing on this list: “My priors about how marketing works were built in a different world. AI is changing a lot of things faster than I can track, while some fundamentals are not changing at all. The unlearning I’m focused on: staying a beginner.”

This is harder than it sounds. Expertise is identity. You get paid for what you know. Choosing to hold that knowledge loosely — to approach a domain you’ve worked in for a decade with genuine beginner’s mind — takes real intellectual courage. It’s also probably the most durable competitive advantage available right now.

9. More is not more.

Uzair Dada, CEO of Iron Horse, said what a lot of CMOs are thinking but won’t say in a board meeting: “Unlearning past marketing frameworks and best practices. Unlearning that more content and more paid media does not mean more results. Unlearning that the old funnel is still relevant. It’s simplifying what we do as marketers and focusing on Getting Discovered and Getting Chosen.”

The volume playbook — more content, more spend, more touchpoints — was always a blunt instrument. AI has made it obsolete faster than anyone expected. Getting Discovered and Getting Chosen is a cleaner frame. It forces the question: are we actually showing up where our buyers are forming opinions, and are we actually the obvious choice when they do?

10. Channel mix is the wrong question.

Everett Butler, Head of Marketing at Lindy, closed the list with the sharpest line: “Your channel mix doesn’t matter. What matters is which product moments make someone pull out their phone and text a friend.”

After nine operators dismantling the infrastructure of modern marketing, Butler lands on what actually endures. Not the channel. Not the campaign. The moment. The experience so good it creates organic word-of-mouth. That hasn’t changed. That won’t change. Everything else is up for renegotiation.

The pattern across all ten.

Nobody named a channel. Nobody pitched a tactic. Nobody said “learn this new playbook.”

Every single one of them is in the middle of demolishing something they used to believe was true — traffic metrics, org design assumptions, attribution models, delegation instincts, tool habits, volume plays.

The operators pulling ahead right now aren’t learning faster.

They’re deleting faster.

The question worth sitting with: what are you still carrying that no longer applies?

Writing this alongside and is a real pinch me moment.

In 2017, I picked up Hacking Growth. At the time, I was leading global marketing operations and digital marketing for a large fintech. I was deep in marketing automation systems. Living inside relational databases. Building global workflows. Scaling teams across regions. Automating everything I possibly could.

Campaigns were launching. Dashboards were clean. Budgets were growing.

But I was optimizing machinery.

Sean’s work changed that.

He did not describe growth as a bigger budget or a clever channel mix. He described it as a disciplined system for discovering truth. Rapid experimentation. Cross functional teams. Testing velocity as advantage. Learning faster than competitors.

Growth was not about pushing more volume through the funnel. It was about systematically uncovering what actually drives activation, retention, and expansion.

That shift rewired how I think.

I stopped seeing marketing as distribution and started seeing growth as a compounding loop. I unified product and marketing around activation metrics. I prioritized experimentation over opinion. I became obsessed with measurable learning.

Nearly one million copies of Hacking Growth have since been sold.

I am not so sure I would be typing this without that book.

It did not just influence a tactic. It altered my trajectory.

Jonathan Martinez represents the next evolution of that mindset. Over the last year, we have worked closely as he has built GrowthPair into one of the most respected agencies for hiring global marketing talent. He operates where execution meets emerging behavior. He studies how buyers interact with large language models. He tracks visibility, share of voice, and citation frequency across AI systems. He experiments relentlessly. And he has become one of the clearest voices translating AEO from theory into practical advantage.

Sean once wrote that the rules of growth were changing.

We are at another inflection point.

Search no longer just retrieves links. AI systems synthesize answers. They frame the problem. They define the options. They influence perception before a buyer ever lands on your website.

The leverage layer has moved upstream.

We wrote this blueprint together because growth is shifting again. The teams who understand this early will shape how their categories are explained. The teams who hesitate will compete for downstream traffic instead of upstream influence.

Growth changed once before.

It is changing again.

And this time, inclusion shapes demand itself.

AEO Blueprint for Startups

Sean here!

In the early 2000s, I poured millions into paid search because it gave me a predictable ROI. We were not just buying traffic. We were optimizing funnels, strengthening referral loops, and scaling paid acquisition against improving lifetime value. It was clean, attributable, and immediate. I could model it. I could control it.

SEO was different. It had more upside, but it also had real downside. It felt messy and slow. It was hard to measure. And the space was full of hucksters promising results they could not possibly deliver. I chose the channel I could instrument and optimize.

Looking back, that avoidance is one of my biggest regrets in my growth career. The most successful and valuable growth leaders I know built deep expertise in SEO during that experimental phase. They captured compounding advantage while the rest of us stayed in the comfort of paid acquisition.

AEO feels similar today. It is early. It is imperfect. It is harder to attribute than paid channels. But it may be even more important than early SEO. Search engines helped you capture intent. Large language models increasingly shape how intent is formed in the first place. If your company is included in the answers, you influence perception before a prospect ever visits your site.

That is a powerful position to hold.

I do not want to miss this wave. And you should not either. That is why I teamed up with Josh Grant and Jonathan Martinez to break down the highest leverage ways to get started now, before advantage compounds for someone else.

The AEO Diagnostic

Jonathan here!

To get started, a quick directional test that anyone can run to see how they’re ranking on LLMs is to search your phrases on ChatGPT or your favorite LLM. For GrowthPair, I may search something like:

“What are the top agencies for hiring global marketing talent?”

This is simply to get your feet wet and see where you’re at. If you have multiple phrases and are doing this daily to see where you stack up, it’ll get very time consuming.

Before diving into tools, it’s worth understanding how people actually search on LLMs. AppSamurai’s marketing manager, Metehan Yeşilyurt, studied 1,827 real ChatGPT conversations and discovered the query median length was 11 words. This contrasts with the average Google search of just 3.4 words.

This change in consumer behavior requires a mindset shift for researching the phrases you’d like to go after.

To get a bit more advanced with your analyses, I suggest using a tool like Peec, AirOps or Ahrefs which will query LLMs daily for your phrases to see where you’re ranking.

To illustrate where most companies are today: at GrowthPair, a global marketing talent startup I founded, I’d rate us a 4/10 on the AEO scale. We have the basics in place (llms.txt, FAQ sections, etc) but we still have tons of work to do on researching and optimizing further.

If you’re early in your SEO journey, temper your AEO expectations accordingly since there’s a strong correlation between ranking on Google and LLMs. While AEO introduces new tactics and metrics, it builds on the same content authority principles as traditional SEO rather than replacing them entirely.

The 80/20 AEO Playbook

Josh here!

SEO captured explicit intent. AEO shapes synthesized understanding.

Search engines helped companies win when buyers typed a clear query. They retrieved relevant sources and ranked them. Large language models go further. They do not just retrieve. They synthesize. They summarize categories, compare options, and often frame the problem before a buyer has visited a single website.

In search, you competed for ranking. In AI systems, you compete for inclusion in the explanation.

If your company is not part of that explanation layer, you do not just lose traffic. You lose framing power. And framing power compounds over time.

So what should you actually do right now?

The answer is not to chase prompt hacks or overhaul your entire marketing strategy. It is to build AEO the same way you would build any durable growth engine. Intentionally. In layers. With discipline.

I think of this as the Inclusion Stack. It has four components:

1. Question Ownership

2. Onsite Encoding

3. Offsite Consensus

4. Citation Engineering

You do not need to perfect all four immediately. But you do need to begin strengthening each one deliberately. Here is what that looks like in practice.

1. Question Ownership: Start With Question Mining

If you do nothing else this quarter, start here.

The foundation of AEO is not content production. It is question discovery. I recently wrote an entire guide on how to mine questions at scale.

AI systems reflect real human language. If you optimize for what you hope buyers are asking instead of what they are actually asking, you are building on assumptions.

Instead of brainstorming topics, extract buyer language from places where intent already exists:

Sales call transcripts
Support tickets
Demo objections
Reddit threads and community Slack groups
Product reviews
Competitor comparison pages

Cluster those questions. Prioritize them by revenue proximity, authority fit, and competitive weakness. Search volume matters less than whether you can credibly own the answer.

This defines your Answer Surface Area. It is the set of questions your company should naturally appear in when AI systems explain your category.

A focused two week sprint that surfaces and prioritizes one hundred real buyer questions will do more for your AEO roadmap than months of unstructured publishing.

Start there.

2. Onsite Encoding: Make Your Expertise Easy to Understand

Once you know which questions you should own, encode them clearly on your site. LLMs reward clarity. Ambiguity reduces inclusion.

Begin with fundamentals.

Clean crawlability.
Remove thin or duplicative pages.
Add structured data where it reinforces meaning.

Then rewrite your homepage and core product pages so anyone can answer, in one sentence:

Who is this for?
What problem does it solve?
How is it different?

If your positioning requires explanation from your sales team, it will not translate well into AI generated summaries.

Then apply FAQ enrichment to your most commercially important pages. Add real buyer questions. Answer them directly in plain language. Define terms clearly. Surface tradeoffs honestly.

At Webflow, aligning core product and category pages with real buyer phrasing improved clarity first. Visibility followed. We were not adding content for volume. We were removing friction so models could extract meaning more easily.

This is work you can complete in weeks.

3. Offsite Consensus: Authority Is Broader Than Your Domain

AEO cannot be won solely on your own website.

Large language models synthesize from across the web. Reddit threads. Review platforms. Industry publications. Partner blogs. Podcast transcripts. Analyst commentary. Community conversations.

If your expertise only lives on your domain, your influence will eventually plateau.

This is not about chasing press mentions. It is about showing up where your category is already being discussed and contributing something meaningful.

Participate in high signal community threads with substance, not promotion. Publish structured insights in outlets that shape professional opinion. Ensure your positioning is accurate and differentiated on comparison platforms. Share original ideas that partners and peers reference.

Authority in the AI era is distributed. Models recognize patterns across independent surfaces. When your perspective appears consistently, credibility strengthens.

Your website makes you legible.
Your broader presence makes you credible.

Inclusion is rarely the result of a single page. It is often the result of visible consensus forming around your expertise.

4. Citation Engineering: Structure Ideas to Be Referenced

In SEO, ranking was often enough. In AEO, citation matters.

Models favor content that is clear, structured, and distinctive.

Name your frameworks.
Define terms precisely.
Use comparisons and decision trees.
Share data, even modest internal insight.

Instead of offering general advice, articulate defined systems.

A simple test helps. If an AI system had to summarize this page in one paragraph, what would it pull?

If the answer is unclear, tighten the structure.

LLMs do not reward volume. They reward clarity and extractable insight.

5. Measure Like an Investor, Not a Traffic Analyst

This is the mindset shift that ties it together.

If you treat AEO like SEO, you will default to clicks. But clicks are downstream.

Instead, measure like an investor managing exposure across an influence portfolio.

Track visibility across your core questions.
Monitor share of voice relative to competitors.
Assess citation frequency.
Review context and sentiment.

Review monthly. Allocate effort the way an investor allocates capital. Strengthen weak clusters. Expand into adjacent territory. Consolidate thin content. Double down where inclusion increases.

You are not optimizing a page. You are increasing exposure to upstream influence. That is portfolio management.

The Compounding Advantage

Twenty years ago, the biggest growth advantage went to teams who invested in SEO before it was clean and measurable.

A similar moment exists today.

The market does not just search anymore. It asks. And the companies that consistently answer shape how the category is understood.

SEO captured demand. AEO shapes demand. Traffic is downstream. Inclusion is upstream.

If you want to act now, the path is clear.

Mine the real questions.
Encode clarity onsite.
Build credibility offsite.
Structure ideas for citation.
Measure like an investor.

Do that consistently and you will not just appear in AI generated answers. You will help define them.

Measuring Early AEO Efforts

Hey, Jonathan back to tackle metrics!

As Josh mentioned, measuring clicks is now very inefficient since consumer behavior is changing. AEO introduces several new metrics worth tracking, and the best way to understand them is to compare old versus new. SEO focuses on driving traffic via clicks (rankings, CTR), whereas AEO emphasizes influence and trust by becoming the source of truth for LLMs.

• SEO: Organic traffic, keyword rankings, backlinks.

• AEO: Brand mentions, answer position, citation source, sentiment

The most important metric is Visibility: how often you’re mentioned in LLM responses across your tracked queries.

Share of Voice (SOV) measures how often a brand is mentioned in LLM responses relative to competitors for a specific set of queries, calculated as (Your Brand Mentions ÷ Total Brand Mentions) × 100.

The last metric I’d put in my top three is citation frequency, which is how often LLMs are citing your brand. Citation frequency is particularly powerful because citations (where LLMs link to your content as a source) signal authority. When LLMs cite your site, they’re essentially validating your expertise to users.

Here’s a quick example of how I’d track all metrics for the search phrase “What are the top agencies for hiring global marketing talent?”:

Visibility: GrowthPair appeared in 37 out of 100 tracked prompts = 37% visibility

Share of voice: GrowthPair appeared 30 times, competitors appeared 70 times = 30% SOV

Citation frequency: GrowthPair was cited 8 times out of 100 tracked prompts = 8% citation rate

Again, tools like Peec, AirOps, and Ahrefs can track this across multiple LLMs daily.

Conclusion: The Compounding Advantage

Sean back to wrap things up!

Twenty years ago, I chose the channel I could measure over the one that could compound. It felt disciplined at the time. In hindsight, it was cautious.

Today, large language models and AI are changing how people make buying decisions. Prospects are not just searching for links. They are asking for synthesized answers, recommendations, and summaries. And those answers increasingly shape perception before a company ever gets the chance to pitch itself.

That creates a new layer of leverage. The brands included in those answers influence how problems are framed, which options are considered, and what “best” even means. Over time, that influence compounds.

You do not need perfect attribution to start. You do not need a dedicated team. As Josh laid out, begin by mining the real buyer questions, encode your expertise clearly onsite, build credibility offsite, and structure your ideas so they can be cited. Measure progress directionally and iterate with discipline.

In growth, the biggest advantages rarely come from doing something perfectly. They come from doing something early. AEO is one of those moments. Your compounding advantage begins when you decide to participate.

It is not prompt engineering.
It is not publishing more.
It is not another SEO tactic.

It is a moat.

A structural advantage built on one capability: understanding the real questions your market is asking and owning the answers that shape how those questions get resolved.

That skill is question mining.

And in an AI-first world, it is becoming the new market insights function.

Not as a department.

As infrastructure.

If you are responsible for how your company is explained, in messaging, in content, in sales conversations, and increasingly in AI-generated answers, this guide is for you.

For years, companies relied on research teams, surveys, positioning workshops, and quarterly insights decks. That model worked when discovery was slower and document-based.

It breaks when answers are synthesized in real time.

Today, visibility is determined less by who ranks and more by whose explanation gets reused.

AI-generated summaries now appear across a growing share of informational searches, and their footprint continues to expand. When answers are synthesized directly on the results page, discovery shifts from ranking documents to influencing explanations.

This shift is measurable. Across published industry analyses, queries that trigger AI summaries often see meaningful compression in organic click-through rates—frequently in the double digits, and in some cases 20–30%+ depending on intent, vertical, and SERP layout.

Ranking is no longer the moat.

Clarity is.

Search engines ranked documents.
Large language models assemble explanations.

When someone asks a question inside an AI interface, there is no page two. There is no “we’ll get them later.” There is one synthesized response built from the clearest available sources.

If your explanation cannot survive synthesis, it does not exist in that moment.

That is where question mining becomes infrastructure.

Done correctly, it feeds everything:

Messaging sharpens because it reflects real tension instead of invented differentiation.
Positioning strengthens because it mirrors how buyers actually compare options.
Content strategy becomes disciplined because it prioritizes decision-shaping uncertainty.
AEO improves because your explanations align with the exact questions AI systems are trying to resolve.
Sales enablement gets stronger because objections are handled before the call.
Product teams gain signal because recurring friction is visible, not anecdotal.

AEO is not the whole story.

It is the most visible proof of the shift.

AI systems make explanation quality measurable. They expose whether your thinking is clear enough to be reused. But the underlying capability is broader than AEO.

It is about building a machine that continuously captures, prioritizes, and operationalizes market uncertainty.

Most companies are not building that machine.

Most marketing teams are measuring output while losing influence.

They publish more.
They optimize keywords.
They track traffic.

Meanwhile, AI systems assemble explanations from whoever reduces uncertainty most clearly.

I have seen companies rank for thousands of keywords and still lose deals to the same three unanswered objections.

The problem was never volume.

It was ownership.

Keywords describe topics.

Questions expose uncertainty.

Uncertainty is where decisions happen.

“Headless CMS” is a topic.

“Is a headless CMS overkill if my marketing team needs to move fast?” is a decision.

Question mining is the discipline of systematically identifying the questions that determine whether someone chooses, hesitates, or walks away.

Most of those questions already exist inside your company:

In sales calls where deals stall.
In support tickets where confusion appears.
In reviews where regret surfaces.
In Reddit threads where buyers compare tools honestly.
In internal search logs where people type what they cannot find.
In AI prompts where buyers ask for synthesis instead of links.

Most teams have the signal.

Very few build the machine.

Building that machine manually is possible. It is also fragile.

Questions live across transcripts, tickets, reviews, analytics tools, AI prompts, and internal systems. Normalizing them. Clustering them. Qualifying which ones actually shape decisions. Refreshing them continuously.

That is not a spreadsheet exercise.

It is infrastructure.

Some companies build that layer internally. Others use platforms like AirOps to unify fragmented question signals, structure them into intent clusters, and operationalize them across content, messaging, and AI surfaces.

The implementation can vary.

The requirement does not.

The work is not collecting questions.

It is deciding which questions shape decisions and answering them so clearly that your explanation becomes the reference point across AI systems, search results, sales conversations, and internal alignment.

That is the moat.

Not more content.

Shared understanding at scale.

Note: Want to listen to an audio version of this guide created via NotebookLM? Check it out below.

01. The Answer Ownership System

Question mining is not a campaign.

It is operating discipline.

The goal is simple: ensure that the most important questions in your market are answered clearly, consistently, and repeatedly by your brand.

That requires a loop.

I’ve been referring to this recently as the Answer Ownership System.

The Answer Ownership System:

1. Capture real questions from live sources

2. Normalize phrasing and detect recurring uncertainty

3. Qualify which questions actually shape decisions

4. Turn those into canonical, reusable explanations

5. Distribute those explanations across every surface

6. Refresh them as language and context evolve

When this loop runs continuously, explanation becomes infrastructure.

Sales friction drops.
Positioning sharpens.
AI visibility compounds.
Customer confusion decreases.

This is not a content calendar.

It is a clarity engine.

Validation: Elite Teams Already Run This Loop

I pressure-tested the Answer Ownership System with Ethan Smith (CEO of Graphite), one of the operators I trust most in AI search and modern GTM.

He went back to the research and surfaced examples of category leaders executing each step. Different industries, same structure.

Capture: Pull real questions from live sources

Elite teams treat questions as first-party data. They extract them from sales calls, support tickets, reviews, and community threads.

Examples

• Gong turns sales conversations into a living source of objections and buyer language (Gong Labs is the externalized version of this).

• HubSpot tracks knowledge base searches, support tickets, and community questions to identify content gaps.

Impact

• Gong turned objection mining into a scalable content and narrative engine.

• HubSpot uses search analytics to surface unanswered self-serve questions, then builds content to close those gaps.

Normalize: Merge different phrasings into shared uncertainty

Most teams drown in duplicates. Elite teams collapse messy phrasing into clean, reusable intent.

Examples

• Zapier normalized intent around app-pair workflows, not “automation software.”

• Canva normalized design uncertainty into template-driven intent systems.

Impact

• Zapier scaled to 70,000+ integration pages and drives roughly 6M+ monthly organic visits.

• Canva built a template ecosystem at massive scale and drives 38M+ monthly organic visits.

Qualify: Decide which questions actually shape decisions

Not every question deserves investment. Elite teams prioritize decision-weighted uncertainty, not curiosity.

Examples

• Stripe prioritizes developer uncertainty because unclear answers lose adoption.

• Sheridan’s Big 5 (pricing, problems, comparisons, reviews, best-of) is a qualification lens built around decision-making moments.

Impact

• Stripe’s documentation functions as an adoption engine and trust moat because it resolves high-stakes uncertainty.

• Teams using Big 5-style transparency consistently reduce friction in evaluation and internal buy-in.

Answer: Create canonical explanations that can be reused

Elite teams don’t write “content.” They create canonical answers that become the reference point.

Examples

• Stripe has a canonical documentation architecture that anchors explanation.

• Ahrefs creates blog posts that naturally demo the product inside the answer (e.g., long-tail keyword research tutorials using Keywords Explorer).

Impact

• Stripe becomes the default reference in payments conversations because the explanation is consistent and reliable.

• Ahrefs key principal is the canonical answer includes the product as part of solving the problem

Distribute: Push the same answers across every surface

Elite teams don’t let answers live in one channel. They distribute explanation across every GTM surface where decisions happen.

Examples

• Zapier distributes canonical answers across integration pages, product education, and workflows.

• G2 distributes explanation via comparison and category pages.

• Canva distributes explanation through template landing pages, search surfaces, and use-case flows.

Impact

• Zapier dominates intent-based discovery because answers meet users at the exact moment of need.

• G2 owns a large share of “X vs Y” evaluation paths.

• Canva’s template system becomes a discovery engine and conversion engine simultaneously.

Refresh: Prevent explanation decay and drift

This is where most teams fail. Elite teams treat answers like infrastructure that needs maintenance.

Examples

• Ahrefs runs systematic content refresh and consolidation programs.

• Stripe uses versioning and documentation hygiene to keep explanations current.

Impact

• Ahrefs has documented traffic recoveries as high as 468% on refreshed and consolidated assets.

• Stripe retains trust because users can rely on documentation that stays current as the ecosystem shifts.

2. What a “Good Question” Actually Is

Most teams believe they are doing question mining.

They are collecting questions.

Usually the loud ones. The easy ones. The ones that show up in SEO tools.

That is not a strategy.

In an AEO-aware environment, a good question meets four criteria:

1. It reflects real decision uncertainty.

2. AI systems are likely to encounter it across prompts.

3. A clear answer would meaningfully shape how the category is explained.

4. Your brand can credibly own that explanation.

If a question does not meet those criteria, it may still be useful.

It is not leverage.

The Volume Trap

Search volume feels objective. It produces numbers and dashboards.

But in AI-driven discovery, volume is often a weak proxy for influence.

The questions that shape AI answers are frequently:

• Worded inconsistently

• Embedded in objections

• Emotional before they are logical

• Lower frequency but higher consequence

“How much does this cost?” is common.

“What ends up costing more six months in?” influences decisions.

Here is the uncomfortable truth:

The questions that matter most rarely look impressive in a dashboard. They’re inconsistent, sometimes phrased awkwardly, often buried inside a longer complaint or hesitation. Most of them are low volume. But they’re the questions that make someone pause, and that pause is what actually shapes a decision.

Search volume tells you what people are curious about. It doesn’t tell you what’s holding them back.

If you build around volume alone, you’ll generate traffic. You might even rank well. But if you build around uncertainty, you influence how decisions get made.

In an AI-driven environment, that distinction matters more than ever. AI systems don’t reward popularity. They reward explanations that reduce ambiguity.

High-volume questions help someone understand a category. Low-volume, high-consequence questions help someone choose. And choosing is where leverage lives.

The Practical Filter

Not every question deserves equal investment.

Browser questions help someone learn.

Buyer questions help someone decide.

AI systems privilege explanations that reduce ambiguity and enable choice.

Use this filter:

• Does answering this reduce uncertainty?

• Would it change how a recommendation is framed?

• Would the answer be reusable across multiple prompts?

• Can your brand credibly be cited?

If yes, prioritize it.

If not, support it…but do not anchor strategy to it.

The Core Insight

In this environment, question mining is not about curiosity.

It is about identifying the uncertainty that shapes decisions…and becoming the clearest explanation available.

Curiosity builds awareness.

Uncertainty drives influence.

The brands that own uncertainty build the moat.

3. The Question Mining System (Not a One-Off Exercise)

Most teams treat question mining like research.
They do it when traffic dips.
They do it before a big content push.
They do it when someone asks for “fresh ideas.”

Then they stop.

That’s the problem.

In an AEO world, question mining is not a project. It’s a system. If it doesn’t run continuously, it decays. Language shifts. Buyer concerns evolve. AI systems update how they frame answers. Yesterday’s “good question” quietly stops mattering.

Elite teams don’t “do” question mining.
They run it.

The Shift: From Ad Hoc Research to a Living System

Ad hoc question research looks like this:
Someone pulls Reddit threads once a quarter.
Someone skims a few sales calls.
Someone pastes notes into a doc.
Content gets created.
The doc dies.

A real question mining system looks different.

It has defined inputs, a shared backlog, clear ownership, a regular cadence, and feedback loops from performance. Most importantly, it treats questions as infrastructure, not inspiration.

If AEO is about owning answers, question mining is how you decide which answers deserve to exist in the first place.

The Full Question Mining Stack

At a minimum, a functioning system has five layers. Miss one, and things break quietly.

1. Source intake
Questions flow in from everywhere. Reddit, sales calls, support tickets, reviews, internal search, social threads. This is raw, messy, human language. That’s a feature, not a bug.

2. Normalization
The same question shows up phrased ten different ways.
“What’s the downside?”
“What breaks?”
“Is this risky long term?”
They are the same question.
If you don’t normalize, you mistake repetition for novelty.

3. Qualification (the AEO filter)
Not every question matters. You filter for decision proximity, reusability in AI answers, and whether your brand could credibly be cited. This is where judgment matters most.

4. Clustering by intent
Questions don’t live alone. They form gravity wells. You cluster by evaluation, fear, outcome, and process. Not by keywords. Not by topic.

5. Answer mapping
Every qualified cluster maps to a canonical answer, a format (page, section, inline, sales asset), and a primary owner. If a question has no answer owner, it doesn’t exist.

Where Teams Usually Fail

Most breakdowns happen in the middle.

Teams are good at collecting questions.
They are bad at deciding which ones matter.
They are terrible at maintaining momentum.

The result is a pile of “interesting questions” and very few owned answers.

A system fixes this by forcing decisions.
What are we answering next?
What are we ignoring on purpose?
What already has an answer that just needs tightening?

Human Judgment vs. Automation (The Right Split)

Automation is not here to replace thinking. It’s here to prevent blind spots.

At scale, humans struggle with volume, inconsistency, and pattern recognition across sources. This is where tools like AirOps earn their place in the stack.

Used well, automation helps teams aggregate questions across every source that matters, normalize wildly different phrasing without losing intent, surface repeated uncertainty AI systems will encounter, and cluster questions faster than any manual process ever could.

What automation should not do is decide what’s strategically important, define what a “good” question is, or own the final answer.

Humans still do that.

The best teams use automation to widen their field of vision, then apply judgment ruthlessly.

A Simple Operating Cadence (Steal This)

Weekly
New questions flow into a shared backlog.
Obvious duplicates get merged.
One or two new clusters get flagged.

Monthly
Teams review clusters through an AEO lens.
Decide what deserves a canonical answer.
Assign ownership and format.

Quarterly
Review which answers are getting reused in AI.
Update language as questions evolve.
Retire answers that no longer matter.

This is boring. That’s why it works.

The Point of the System

A question mining system doesn’t exist to generate ideas.

It exists to make sure the most important questions never get missed, the same confusion doesn’t resurface every quarter, and your brand steadily becomes the clearest explanation in the category.

In an AI-first discovery world, that’s not a content advantage.

It’s a compounding one.

4. Reddit: Where Unfiltered Buyer Truth Lives

If you want honest questions, don’t start with search tools.

Start with Reddit. This has become my favorite question mining source.

Reddit is where people go when:

• They don’t trust marketing

• They don’t want to talk to sales

• They want answers from people who have already lived with the decision

That’s why Reddit is one of the highest-signal sources for AEO-grade question mining. Not because it’s clean or structured. Because it isn’t.

Reddit doesn’t show you what people say they care about.
It shows you what they’re worried about when no one is watching.

Why Reddit Is So Powerful for AEO

From an AEO perspective, Reddit matters for three reasons:

1. LLMs actively ingest Reddit as a source of real-world explanation and sentiment

2. Questions are phrased in natural, emotional language, not SEO language

3. The same uncertainty shows up repeatedly across threads, even when phrasing changes

If AI systems are trying to explain how something actually works, Reddit is often where that explanation starts.

Step 1: Choose Subreddits by Buyer Maturity (Not Topic)

Most teams get this wrong immediately.

They search for subreddits about their product category. That’s lazy.

Instead, map subreddits to buyer stage.

Early-stage uncertainty:

• r/startups

• r/Entrepreneur

• r/marketing

• r/smallbusiness

Mid-stage evaluation:

• r/SaaS

• r/webdev

• r/ProductManagement

• r/growthmarketing

Late-stage, post-decision reality:

• r/sysadmin

• r/devops

• r/dataengineering

• r/cscareerquestions (for tooling decisions)

You’re not looking for mentions of your brand.
You’re looking for decision stress.

Step 2: Ignore Posts. Mine the Comments.

This is critical.

Post titles are optimized for attention.
Comments are optimized for truth.

The highest-value questions often appear:

• As follow-ups

• As rebuttals

• As “wish I had known this earlier” replies

• Buried three levels deep

Example:

Post title:
“Is headless CMS worth it?”

Low signal.

Comment buried in the thread:
“We went headless and marketing couldn’t ship without engineering for six months. How do teams actually avoid that?”

That comment is gold.
That’s an AEO-grade question.

Step 3: Learn to Spot High-Signal Question Patterns

Not all Reddit questions are equal. The best ones fall into a few recognizable patterns.

Rage posts
“This tool is a nightmare. Nothing works the way sales promised.”
These reveal expectation gaps AI systems will try to explain later.

Regret posts
“If I were starting over, I wouldn’t choose X.”
These generate the most reusable answers in AI comparisons.

Comparison threads
“X vs Y vs Z for a team like mine.”
These heavily influence how AI frames tradeoffs.

Quiet fear questions
“I might be missing something here, but…”
These often surface the real blocker.

Train yourself to look for emotion plus uncertainty. That’s where decisions live.

Step 4: Turn Chaos into Structured Signal

This is where most teams give up.

Reddit is noisy. Threads are long. Language is inconsistent. Doing this manually does not scale.

This is where workflow automation matters.

Tools like Gumloop make Reddit mining dramatically easier because they have native Reddit scraping nodes (these nodes are awesome, so easy to use). You can:

• Pull posts and comments from specific subreddits

• Filter by keywords, sentiment, or post type

• Pass raw text into downstream workflows automatically

From there, systems like AirOps become the backbone of the process.

Used together, teams can:

• Aggregate Reddit questions alongside sales calls and support tickets

• Normalize wildly different phrasing into shared question clusters

• Detect repeated uncertainty AI systems will encounter

• Flag questions that deserve canonical answers

Automation doesn’t replace judgment.
It makes Reddit usable at scale.

Step 5: Apply the AEO Filter Ruthlessly

Once you’ve surfaced questions, most of them still won’t matter.

Run each Reddit-derived question through this filter:

• Is this a real decision someone is trying to make?

• Would AI systems reasonably try to answer this?

• Does this shape how the category gets explained?

• Could our brand credibly be cited here?

If the answer is no, discard it.

If yes, it goes into the backlog.

This is where most teams fail. They keep everything. Elite teams curate aggressively.

A Concrete Example (What This Looks Like in Practice)

I did this firsthand at Webflow when we were trying to understand why our freelancer segment was eroding.

We didn’t start with surveys.
We didn’t start with keyword tools.
We scraped the hell out of every community where freelancers actually hang out.

Reddit threads.
Community forums.
Long comment chains.
Rants.
Regret posts.
Quiet “I might be done with this” conversations.

Not to look for brand mentions.
To look for friction.

Here’s what surfaced over and over, phrased a hundred different ways:

Raw community sentiment:
“Webflow feels insanely powerful, but it’s starting to feel like too much for solo work. Am I just bad at this, or did something change?”

Normalized question:
“Why does Webflow feel more complex for freelancers than it used to?”

Clustered intent:
Fear + evaluation

What mattered wasn’t the wording. It was the uncertainty underneath.

We used those insights to:

• Prioritize AEO answers that directly addressed freelancer concerns

• Rewrite content to explain tradeoffs more honestly

• Shape campaigns around reassurance, not features

• Inform positioning decisions across content, SEO, and growth

Those answers didn’t just live on pages.

They showed up in:

• AI-generated explanations of Webflow

• Comparisons against simpler tools

• Conversations before anyone ever talked to sales

That’s the leverage.

The Real Value of Reddit for AEO

Reddit doesn’t tell you what to write.
It tells you what people are still confused about after reading everything else.

If your answers don’t exist there, AI systems will borrow explanations from someone else who took the time to listen.

Reddit is messy.
Emotional.
Hard to mine.

That’s exactly why it works.

5. Sales Calls & Gong: Revenue-Critical Questions

If Reddit shows you raw buyer anxiety, sales calls show you where deals actually stall.

This is the highest-leverage question source most marketing teams underuse. Not because the data is not there. Because it feels uncomfortable. Sales questions expose confusion, hesitation, and mistrust in real time.

From an AEO lens, that is gold.

Sales calls are where questions stop being theoretical and start being expensive.

Why Sales Questions Matter More Than Any Other Source

Every sales question has three properties that make it uniquely powerful for AEO:

• The buyer is already qualified

• The question appears right next to a decision

• The answer directly affects revenue

If an AI system is trying to explain whether a product is worth it, sales objections are often the clearest articulation of what actually matters.

This is why sales calls should feed your AEO strategy continuously, not occasionally.

Pre-Price vs. Post-Price Questions

This Split Is Everything

One of the most important distinctions when mining sales calls is when the question appears.

Pre-price questions sound like curiosity.
They are about fit, capability, and confidence.

Examples:

• How much setup does this usually take?

• What kinds of teams struggle with this?

• Where do people underestimate the effort?

These questions determine whether a buyer will even accept the price later.

Post-price questions sound like objections.
They are about justification, risk, and internal alignment.

Examples:

• Why is this more expensive than X?

• What happens if we do not fully adopt it?

• How do teams justify this internally?

AI systems tend to mirror this structure when explaining tradeoffs. If your content only answers one side, the explanation is incomplete.

This is where a revenue platform like Gong becomes powerful. Gong allows teams to analyze themes based on deal stages as defined in their CRM. You are not just analyzing questions. You are analyzing when they surface in the buying journey.

That same segmentation logic can be applied across industry, account size, region, or customer segment. Different revenue ecosystems generate different question patterns. Mining those patterns produces more precise answers.

This matters for AEO because LLMs aim to deliver contextually relevant responses. The more clearly your site reflects the unique pain points of specific personas or segments, the more likely your brand is to appear in answers tailored to that exact user prompt.

Elite AEO teams mine both pre-price and post-price questions intentionally.

Objections Disguised as Curiosity

The most valuable sales questions rarely sound hostile.
They sound polite.

• How scalable is this?

• Is this overkill for a team like ours?

• What do companies regret not thinking about first?

These are not informational questions.
They are risk probes.

If your content answers the surface question but ignores the underlying fear, the answer will not stick. And AI systems will not reuse it.

Sales calls teach you how buyers actually phrase doubt. That language is exactly what AEO answers need to reflect.

A quick note of appreciation to Gong Labs here. Their first-party research reinforces just how often objections are disguised as curiosity. In their analysis of real sales conversations, buyers rarely present resistance directly. Instead, they surface concerns as exploratory questions tied to implementation risk, scalability, internal buy-in, or long-term uncertainty. Their work on handling objections with AI and tools like AI Theme Spotter highlights how consistently this pattern appears across industries and deal types.

The question may sound casual. The revenue impact is not.

Enterprise-Only Questions

Do Not Ignore These

Enterprise questions are easy to dismiss because they do not show up at volume.

That is a mistake.

Enterprise buyers ask questions like:

• How does this break at scale?

• What governance models actually work?

• Where does this fall down in complex organizations?

These questions heavily influence how AI frames whether a product is enterprise-ready or SMB-only.

If your brand never answers them publicly, AI systems will infer the answer anyway. Usually not in your favor.

How to Mine Sales Calls at Scale

Without Burning the Team

This does not require manual listening marathons.

With Gong, you already have:

• Transcripts

• Objection tags

• Topic frequency over time

• Stage segmentation tied to CRM definitions

Layer in workflow automation and this becomes even more powerful.

Teams now use workflow tools to:

• Pull transcripts automatically

• Extract question-shaped sentences

• Group questions by stage, deal size, or outcome

• Feed those questions into structured systems

It is worth making an important distinction here. In theory, you could paste transcripts into a generic LLM and ask it to extract themes. In practice, that is not the same as using a purpose-built AI platform trained on millions of revenue interactions. Platforms like Gong (with their native agents) are optimized specifically for sales and customer conversations. Pattern detection becomes far more precise because it is grounded in first-party revenue data, not just prompt interpretation.

From there, AirOps becomes the control plane.

Sales phrasing becomes canonical answers.
Those answers get distributed across GTM surfaces.
The system stays consistent instead of fragmenting into one-off assets.

When transcripts include rich metadata such as stage, segment, win or loss, and objection tags, the prioritization becomes even sharper. AirOps can separate curiosity from risk probes and produce a ranked backlog of revenue-blocking questions.

Automation handles the scale.
Humans decide what matters.

What This Looked Like in the Real World

I saw this clearly while advising a B2B2C healthcare AI company selling into mid-market and enterprise teams.

Deals were not dying early.
They were stalling late.

Pipeline was strong. Demos landed. Pricing was not the issue. But once buyers entered serious evaluation, momentum slowed.

So we mined sales calls. Not to coach reps. To extract questions.

One pattern surfaced constantly:

• Is this actually built for teams our size?

• How many customers like us are really successful with this?

• Are we going to outgrow this in a year?

None of these sounded confrontational. All of them signaled positioning uncertainty.

We normalized them into a single AEO-grade question:

Who is this product actually built for, and where does it break down?

That question became the spine.

We used it to:

• Create AEO content explaining ideal fit and non-fit

• Rewrite comparison pages to lead with tradeoffs

• Shape campaign messaging around clarity

• Align sales on a consistent answer

What changed was not volume.
It was understanding.

That answer started appearing:

• In AI-generated category explanations

• In third-party comparisons

• In buyer conversations before sales ever got involved

Prospects arrived better informed.
Late-stage objections dropped.
Sales cycles shortened.

That is the leverage.

Do Not Stop at Prospect Calls

Question mining should not end with new business.

Conversations with existing customers surface implementation friction, adoption challenges, and retention risks. These questions often predict churn long before cancellation.

Retention and expansion are revenue metrics.

Existing customers are also using LLMs to answer their questions. If your brand does not have a clear explanation publicly available, someone else’s framing fills that gap.

Sales call mining is not just about closing new business. It is about shaping explanation across the entire customer lifecycle.

Beyond AEO

The Organizational ROI

Independent of AEO, publishing answers based on real prospect and customer questions drives measurable ROI.

It shortens sales cycles.
It reduces repetitive objections.
It improves onboarding clarity.
It creates a feedback loop for product teams.

For product marketing, this is extremely attractive. The ROI is not theoretical. It is tied directly to revenue efficiency and customer clarity.

Question mining becomes easier to fund when it is positioned as cross-functional infrastructure, not just SEO or AI visibility work.

AEO is one outcome.
Revenue efficiency is another.

It is a many-birds-one-stone strategy.

The AEO Takeaway

Sales calls do not just tell you what to fix in the funnel.

They tell you what AI systems will struggle to explain unless you do it first.

If the same question keeps stalling deals, it deserves:

• A clear answer

• A canonical explanation

• Ownership across content, positioning, and sales

Because in AEO, revenue-blocking questions are the highest-priority questions you can mine.

6. Customer Support & Tickets: Post-Purchase Reality

If sales calls show you where deals stall, support tickets show you where expectations break.

This is post-purchase truth.

Support questions are not hypothetical. They come from people who already chose you, already paid, and are now trying to make the decision feel right.

From an AEO perspective, that makes them incredibly valuable.

Support tickets reveal the gap between what buyers thought they were buying and what they’re actually experiencing.

That gap is where churn lives.

Why Support Questions Matter So Much for AEO

Support questions have four properties that make them uniquely powerful:

1. The buyer has already committed

2. The question appears right after reality hits

3. The confusion is expensive

4. The language is painfully honest

AI systems care deeply about this kind of signal. When they explain a product, they often borrow from the same misunderstandings real users surface after purchase.

If you don’t answer these questions publicly, AI systems will infer the answers anyway. Usually from other users, forums, or competitors.

Expectation Gaps vs. Simple How-To Confusion

Not every support question is an AEO opportunity.

The key is separating how-to confusion from expectation failure.

How-to questions sound like this:

• “Where do I click to do X?”

• “How do I turn this setting on?”

• “Is there a doc for this?”

These matter for UX and docs. They are not AEO-critical.

Expectation gap questions sound different:

• “I thought this would do X automatically”

• “Why is this more manual than I expected?”

• “Do most customers run into this?”

These are positioning problems disguised as support tickets.

Those are gold.

Onboarding Questions That Quietly Predict Churn

Some questions show up early and then disappear.

Others show up early and never go away.

Pay attention to questions that:

• Appear in the first 30 days

• Show up repeatedly across customers

• Resurface right before churn or downgrade

Examples:

• “Is this the intended workflow?”

• “Am I using this wrong, or is this just how it works?”

• “What does a successful setup actually look like?”

These are not beginner questions. They are confidence questions.

If users never get clarity here, they don’t complain. They leave.

Feature Confusion vs. Positioning Failure

A simple rule:

If many customers misunderstand the same thing, it’s not a feature problem. It’s a positioning problem.

Support tickets are where that truth shows up first.

When you see questions like:

• “Why can’t this do X like Y?”

• “Is this missing, or am I missing something?”

• “Why does this feel more complex than advertised?”

That’s not a roadmap issue. That’s an explanation issue.

And explanation issues are prime AEO opportunities.

Why Support Questions Convert Insanely Well

This surprises teams.

Content built from support questions often converts better than top-of-funnel content because it:

• Meets buyers at a moment of clarity

• Preempts regret

• Builds trust through honesty

• Reduces post-purchase anxiety

From an AEO standpoint, these answers also get reused heavily.

AI systems love explanations that say:

“Here’s what this does, what it doesn’t do, and what most people misunderstand.”

That language comes straight from support.

How to Mine Support Questions at Scale

This does not require ticket-by-ticket review.

Modern workflows make this manageable.

Support systems already tag:

• Ticket topics

• Time to resolution

• Churn-adjacent conversations

With workflow automation, teams can:

• Pull ticket transcripts automatically

• Extract question-shaped language

• Group repeated confusion across accounts

From there, AirOps helps teams:

• Normalize how different users phrase the same misunderstanding

• Cluster questions by intent and lifecycle stage

• Identify which gaps deserve public AEO answers

• Track when explanations reduce repeat tickets

Support, content, and AEO stop operating in silos.

What This Looks Like in Practice

A recurring support question:
“Why do I still need to do this manually?”

Normalized AEO question:
“What does this product automate vs. require ongoing work?”

Intent cluster:
Expectation gap + outcome

That answer becomes:

• A public AEO explanation

• An onboarding asset

• A sales enablement reference

• A churn prevention lever

One answer. Multiple surfaces.

The AEO Takeaway

Support tickets are not just a cost center.

They are a live feed of unanswered questions that buyers and AI systems are both trying to resolve.

If the same confusion keeps showing up after purchase, it deserves a clear, public answer.

Because in an AEO world, the fastest way to lose trust isn’t bad marketing.

It’s unmet expectations.

7. Social (X, LinkedIn): Ambient Curiosity at Scale

Search shows you what people ask when they’re intentional.

Social shows you what people wonder about when they’re scrolling.

That difference matters.

X and LinkedIn are not where buyers go to research. They’re where confusion, half-formed opinions, and misconceptions surface in public. That makes social one of the best sources for early-stage AEO signals, if you know how to mine it without getting distracted by engagement.

Social isn’t about demand capture.
It’s about demand formation.

And AI systems watch it closely.

Why Social Matters for AEO (Even If You Hate Social)

From an AEO lens, social is valuable because:

• People ask questions they wouldn’t type into search

• Misunderstandings spread faster than corrections

• The same confusion shows up repeatedly in comment threads

• AI systems absorb the dominant explanations over time

If Reddit shows you raw buyer truth, social shows you ambient confusion at scale.

That confusion eventually turns into search queries, sales objections, and support tickets.

This is upstream signal.

Comment Threads Are Live FAQ Testing

Ignore the post. Read the comments.

The real questions rarely appear in the main post. They show up underneath it, often phrased as pushback or clarification.

Examples:

• “Wait, does this mean you can’t do X?”

• “How is this different from what we already do?”

• “This sounds nice, but what breaks in practice?”

Those are not engagement comments.
They are unanswered FAQs forming in public.

When the same question appears across multiple posts, you’ve found something AEO-grade.

Quote Tweets and Reposts Create Misconception Loops

Quote tweets and reposts are especially dangerous.

Someone paraphrases an idea slightly wrong.
Someone else reacts to that version.
The explanation drifts.
The wrong framing spreads.

Before long, AI systems start borrowing the distorted explanation because it appears more frequently than the original.

This is how brands lose narrative control.

If you see repeated quote tweets saying:
“So this basically means X is dead…”

That’s not a hot take.
That’s a misconception loop forming.

Those loops are high-priority AEO opportunities.

Founder Explanations Gone Wrong (High Signal, Low Ego)

Founder posts are another goldmine.

Not because founders are wrong.
Because explanations often assume too much context.

When a founder explains something and the comments fill with:

• “Can you explain this more simply?”

• “Who is this actually for?”

• “So does this replace X or not?”

That’s not ignorance.
That’s a signal the explanation didn’t land.

Those gaps are exactly what AI systems struggle with later.

Mining founder comment threads is one of the fastest ways to identify where industry language has outpaced understanding.

How to Extract Signal Without Chasing Virality

This is where most teams fail.

They chase likes instead of patterns.

The goal is not to find viral posts. It’s to find repeated confusion.

Here’s how to do it cleanly:

• Track recurring questions across multiple posts, not one

• Ignore engagement metrics initially

• Look for the same question phrased differently

• Focus on comments that ask “how,” “why,” or “what does this mean in practice”

One post means nothing.
Five posts saying the same thing means everything.

Making This Scalable (Without Living on X)

You do not need to manually scroll all day.

Workflow automation makes this manageable.

Teams now use tools like Gumloop to:

• Pull comments and quote tweets from defined accounts or topics

• Extract question-shaped language

• Pass that text into downstream analysis automatically

From there, AirOps helps teams:

• Normalize phrasing across posts and platforms

• Cluster repeated confusion by intent

• Flag which misconceptions deserve canonical AEO answers

• Track whether explanations improve over time

Automation collects.
Humans decide.

A Concrete Example

Repeated social comments:
“Is this just SEO with AI slapped on?”
“So do we still need content or not?”
“This feels like more work, not less.”

Normalized AEO question:
“How does AEO actually change what teams do day to day?”

Intent cluster:
Evaluation + fear

That answer becomes:

• A public explanation AI systems reuse

• A positioning clarification

• A sales enablement asset

• A filter that keeps the wrong buyers out

One ambient question. Multiple surfaces.

The AEO Takeaway

Social doesn’t tell you what people are searching for.

It tells you what they don’t fully understand yet.

If you ignore it, misconceptions spread unchecked.
If you mine it well, you shape the explanation before AI systems do.

That’s leverage at scale.

8. Reviews, G2, and “I Wish I’d Known” Questions

If sales calls show you hesitation and support tickets show you confusion, reviews show you regret.

This is post-decision clarity.

Reviews are not feedback. They’re delayed questions buyers wish they had asked earlier. And that makes them incredibly valuable for AEO, because AI systems lean heavily on post-purchase language when explaining tradeoffs.

This is where truth surfaces without filters.

Reviews Are Just Questions Asked Too Late

Most reviews aren’t statements. They’re answers to unasked questions.

Read them carefully and you’ll see the pattern:

• “Great product, but I didn’t realize how much setup was involved”

• “Works well once you learn it, but there’s a steep curve”

• “Powerful, but probably overkill for smaller teams”

Those are not opinions.
They’re unresolved questions in hindsight.

Each one maps cleanly to a buyer uncertainty that never got addressed clearly enough before purchase.

That’s an AEO opportunity.

Why Reviews Matter So Much for AEO

From an AEO perspective, reviews matter because:

• They describe tradeoffs in plain language

• They use comparison phrasing buyers actually understand

• They reveal expectation gaps, not feature gaps

• AI systems treat them as credibility-weighted input

When an AI model explains why someone might or might not choose a product, review language is often the backbone of that explanation.

If your brand doesn’t own those answers, the model will borrow them from reviewers instead.

Regret Signals and Trust Gaps

The most valuable review content isn’t praise or complaints. It’s regret.

Look for phrases like:

• “I wish I had known…”

• “In hindsight…”

• “If you’re considering this, be aware…”

• “This is great, but only if…”

These signal trust gaps.

Not deception.
Misalignment.

And misalignment is exactly what AEO content is supposed to fix.

The Comparison Language Buyers Actually Use

Comparison pages written by marketers rarely match how buyers compare tools in reality.

Reviews do.

Buyers say things like:

• “This feels more flexible, but slower”

• “Cheaper upfront, more expensive over time”

• “Better for teams, worse for solo work”

• “Powerful once set up, frustrating before that”

That language is gold.

It’s the phrasing AI systems reuse when summarizing pros and cons across tools.

If your comparison content doesn’t reflect this language, it won’t get cited.

How to Mine Reviews Systematically

This is not about reading a few five-star reviews.

You want scale and pattern recognition.

Start with platforms like G2, app marketplaces, and public review sites.

Then focus on:

• 3–4 star reviews (highest signal)

• Negative reviews that still recommend the product

• Positive reviews with caveats

Extract:

• Repeated “but” statements

• Setup and onboarding mentions

• Fit and non-fit language

• Comparison phrasing

Those are your inputs.

Making This Scalable With Automation

Manually reading reviews doesn’t scale.

Workflow automation fixes that.

Teams use tools like Gumloop to:

• Pull reviews automatically by product, category, or competitor

• Extract question-shaped or regret-based language

• Route that text into structured workflows

From there, AirOps becomes the system of record.

It helps teams:

• Normalize wildly different review phrasing

• Cluster regret signals by intent

• Map recurring gaps to AEO-worthy questions

• Track which explanations reduce negative sentiment over time

Automation handles volume.
Humans decide which gaps deserve public answers.

Turning Regret Into Preemptive Answers

Here’s what great teams do next.

They don’t hide the downsides.
They explain them better than anyone else.

Example:

Review language:
“Great tool, but I didn’t realize how much ongoing work it would require.”

Normalized AEO question:
“What does this product actually automate, and what still requires manual effort?”

Intent cluster:
Expectation gap + outcome

That answer becomes:

• A public AEO explanation

• A comparison page section

• A sales enablement asset

• A trust-building filter for the right buyers

The goal isn’t to convert everyone.

It’s to convert the right people with eyes open.

Why This Converts So Well

Content built from review-based questions converts insanely well because it:

• Mirrors real buyer language

• Acknowledges tradeoffs honestly

• Prevents regret before it happens

• Builds trust faster than polished marketing ever could

AI systems reward that honesty.

Buyers do too.

This matters beyond your own site. Third party sources drive 85 percent of brand mentions in AI generated answers. Offsite narrative is not secondary. It is a primary visibility signal.

When you answer the real questions buyers are asking, you create clearer context that other domains reference. That is how explanation spreads. And that is how visibility compounds.

The AEO Takeaway

Reviews aren’t feedback to be managed.

They’re a backlog of unanswered questions your future buyers are already asking.

If you mine them well and answer them publicly, you don’t just improve conversion.

You train AI systems to explain your product the way you would.

That’s compounding advantage.

9. Internal Search, Chat, & Zero-Result Questions

Internal search isn’t about a search box.

It’s about any place a user types a question on your site expecting you to explain something.

That might be:

• A search bar on your marketing site or docs

• A help center search

• An in-product search or command palette

• A chat tool like Drift, Qualified, or Intercom

• A demo request or contact form field

Different UI. Same signal.

From an AEO perspective, these are some of the highest-intent questions you’ll ever see.

What This Signal Actually Represents

When someone types a question on your site, they’re not exploring the category.

They’re evaluating you.

They already believe:

• You might be the right solution

• You should have an answer

• Clarification will help them decide

This is self-reported intent at the moment of friction.

Keyword tools guess.
Internal questions tell you directly.

What a “Zero-Result” Question Really Means

A zero-result question doesn’t always look like “No results found.”

It looks like:

• A search that returns irrelevant pages

• A chat question that triggers a handoff to sales

• A repeated “Can you clarify…” message

• A demo form that includes confusion in the free-text field

In every case, the meaning is the same:

A user expected an explanation.
You didn’t give one.

That gap creates doubt. And doubt doesn’t stay internal. Users take it to AI systems, Reddit, or competitors.

Why Chat Tools Often Beat Search Bars

If a site doesn’t have a search bar, chat tools are often better.

Tools like Drift, Qualified, and Intercom capture:

• Natural language questions

• Emotional subtext

• Urgency and stakes

• Repetition across users

Examples:

• “Is this overkill for a team our size?”

• “How long does setup really take?”

• “What do people usually struggle with first?”

That is internal search with context attached.

From an AEO lens, this is gold.

Navigation Gap vs. Messaging Gap (Still Critical)

Not every internal question means “write new content.”

You still need to diagnose the gap.

Navigation gap
The answer exists, but users can’t find it.
Fix UX.

Messaging gap
The answer doesn’t exist or isn’t clear.
Fix the explanation publicly.

How to tell:

• If the same question appears across chat, sales, or support, it’s messaging

• If it shows up repeatedly over time, it’s messaging

• If it only happens once, it might be navigation

Elite teams don’t overreact. They pattern-match.

How Teams Actually Capture This Data

Most teams already have this data.

They just don’t route it anywhere useful.

You can capture internal questions from:

• Site search logs

• Docs and help center search

• Chat transcripts (first question is highest signal)

• Demo request and contact form fields

• In-product prompts and failed actions

You want:

• The raw question text

• Frequency

• Where it appeared

• What happened next

That’s enough to start.

Turning This Into an AEO Backlog

Raw logs aren’t helpful by themselves.

Teams use automation to:

• Pull internal questions weekly

• Flag repeated or unresolved ones

• Deduplicate phrasing

• Surface patterns

From there, AirOps helps teams:

• Normalize internal questions with sales and support language

• Cluster questions by intent

• Identify which gaps deserve canonical AEO answers

• Track whether new explanations reduce repeat questions over time

This is how internal confusion becomes external clarity.

A Simple Example

Repeated chat question:
“Is this overkill for a small team like ours?”

Normalized AEO question:
“Who is this product best suited for, and who should not use it?”

Intent cluster:
Evaluation + fear

That answer becomes:

• A public explanation section

• A comparison anchor

• A sales alignment asset

• An AI-reusable explanation of fit

One internal question.
Multiple downstream wins.

The AEO Takeaway

You don’t need a search bar to mine internal questions.

Anywhere a user types a question expecting clarity counts.

Those questions tell you exactly where your explanation breaks down while intent is highest.

If you answer them clearly and publicly, you don’t just improve conversion.

You prevent AI systems from inventing the answer for you.

10. Clustering Questions into Answer Themes

By this point, you don’t have a question problem.

You have a too-many-questions problem.

Reddit, sales calls, support tickets, chat, reviews, internal search. They all produce valuable signal. But if every question becomes its own piece of content, you end up with sprawl. Dozens of half-answers. No clarity. No reuse.

AEO doesn’t reward volume.
It rewards coherence.

Clustering is how you get there.

Why Grouping by Topic Fails

Most teams cluster questions by topic.

Pricing.
Security.
Integrations.
Features.

That’s comfortable. It’s also wrong.

Topics describe what something is about.
Intent describes why someone is asking.

AI systems don’t care that ten questions mention “pricing.” They care whether those questions are about fear, evaluation, justification, or process.

If you cluster by topic, you create pages that talk around decisions.

If you cluster by intent, you create answers that resolve them.

Group by Intent, Not Keywords

At scale, many questions that look different are actually the same.

Examples:

• “Is this overkill for us?”

• “Are we too small for this?”

• “Is this only for enterprise teams?”

Different wording. Same intent.

That intent is fit anxiety.

From an AEO lens, those should not be three answers. They should be one clear, canonical explanation of who the product is for and who it is not for.

This is where teams usually overproduce and under-explain.

The Four Intent Buckets That Matter Most

Almost every high-value question you’ve mined can be clustered into one of four answer themes:

Evaluation
Is this right for me?

Fear
What could go wrong?

Outcome
What actually changes if this works?

Process
What does this look like in practice?

You’re not eliminating nuance.
You’re organizing it.

Each cluster should lead to a single, durable answer that can be reused everywhere.

Identifying the Canonical Answer

A canonical answer is not a page.

It’s the clearest explanation you have for a recurring uncertainty.

You know you’ve found one when:

• The same explanation satisfies multiple questions

• Sales, support, and content all point to it

• AI systems can reuse it without rewriting

The goal is not to answer every question individually.

The goal is to create a small number of answers so good they absorb dozens of questions.

That’s how AEO compounds.

What Deserves a Page vs. a Section vs. an Inline Answer

This is one of the most important judgment calls in the entire system.

Here’s a simple rule set that works.

Deserves a dedicated page when:

• The question shapes how the category is explained

• It appears across multiple sources

• It influences evaluation or comparison

• AI systems frequently need to reference it

Examples:

• Who this product is for (and not for)

• Pricing philosophy and tradeoffs

• Core architectural decisions

Deserves a section when:

• The question is important but secondary

• It supports a larger explanation

• It resolves a specific fear or objection

Examples:

• “Is this overkill?”

• “What happens if we don’t fully adopt it?”

Deserves an inline answer when:

• The question is narrow

• It removes momentary friction

• It doesn’t change the overall decision

Examples:

• Minor feature clarifications

• Setup edge cases

This discipline prevents content bloat and keeps explanations tight.

How Automation Helps Without Flattening Thinking

Clustering is where automation actually shines.

Humans are great at judgment.
They’re bad at pattern recognition across thousands of inputs.

This is where AirOps becomes foundational.

AirOps helps teams:

• Normalize different phrasings of the same question

• Detect recurring uncertainty across sources

• Surface high-signal opportunities

• Suggest intent-based clusters

• Keep clusters current as language evolves

AirOps does not replace judgment. It strengthens it.

Humans still decide:

• Which intent clusters are strategic

• Which deserve ownership

• Which to intentionally ignore

Automation accelerates insight.
Judgment creates advantage.

A Concrete Example

Raw questions:

• “Is this too complex for a small team?”

• “Do we need engineers full time?”

• “Is this only worth it at scale?”

Single intent cluster:
Evaluation + fear

Canonical answer:
“Who this product is built for, where it shines, and where it’s the wrong choice.”

That one answer now:

• Anchors a core page

• Feeds sales and onboarding

• Shapes AI explanations

• Absorbs dozens of individual questions

That’s leverage.

The AEO Takeaway

Clustering is not about organizing content.

It’s about reducing cognitive load for humans and machines.

When you cluster by intent, create canonical answers, and choose the right surface, you stop publishing content and start building an answer engine.

That’s when AEO becomes durable.

11. Turning Questions into an Answer Engine

By now, you don’t have a research problem.

You have clarity.

You know which questions matter. You’ve clustered them by intent. You’ve identified canonical answers. The mistake most teams make at this point is treating answers like content assets.

That’s not the job.

The job is to turn answers into an engine. Something that shows up everywhere buyers and AI systems need it, without rewriting the same explanation ten different ways.

An answer engine doesn’t live in one place.
It runs across the entire go-to-market surface area.

Start With the Canonical Answer (Always)

Every important question should have one primary answer.

Not five versions. Not a blog post plus a deck plus a help doc that all say slightly different things.

One clear explanation that:

• Names the tradeoffs

• Resolves the uncertainty

• Can be reused without losing meaning

Everything else is a derivative.

This is the single biggest unlock for AEO. AI systems reward consistency. Humans trust it too.

FAQ Hubs, AEO Pages, and Embedded Answers

Most teams default to FAQs. That’s fine, but only if they’re treated correctly.

FAQ hubs work when:

• Questions are clustered by intent

• Answers are opinionated, not evasive

• Each answer could stand alone in an AI response

Bad FAQs list questions.
Good FAQs resolve decisions.

For higher-impact questions, graduate them out of FAQs.

Create AEO pages when:

• The question shapes how the category is explained

• Buyers ask it repeatedly across sources

• AI systems need a stable reference

Examples:

• Who this product is for and not for

• Pricing philosophy and tradeoffs

• Core architectural decisions

Then embed answers everywhere else.

Inline answers on product pages.
Short explanations near CTAs.
Clarifying sections where confusion tends to spike.

The same answer. Different surfaces.

Comparison and Alternatives Content (Where AEO Wins Big)

Comparison content is where answer engines shine.

Most comparison pages are defensive. They list features. They avoid tradeoffs. AI systems see through that immediately.

High-performing AEO comparison content does three things:

• Explains why teams choose each option

• Names the downsides honestly

• Helps the buyer self-select

That language often comes directly from:

• Sales objections

• Review regret

• Reddit comparisons

If your canonical answers already exist, comparison content becomes assembly, not invention.

This is why teams with strong answer engines dominate AI comparisons even without ranking first.

Sales Enablement and Objection Handling

If sales is answering a question live, that answer should already exist publicly.

Every repeated objection is a signal:

• Either the answer doesn’t exist

• Or it exists but isn’t clear enough

Great teams do this:

• Identify the top 10 revenue-blocking questions

• Create canonical AEO answers for each

• Train sales to reference, not reinvent

This does two things:

• Sales stays consistent

• AI systems learn a single explanation instead of ten variations

Sales enablement and AEO are the same work. They just operate at different moments.

In-Product Education (The Most Overlooked Surface)

The best answer engines don’t stop at the website.

They show up in-product.

Think:

• Onboarding explanations

• Tooltips that explain tradeoffs, not just actions

• “Why this works this way” moments

When users understand why something behaves a certain way, support tickets drop and trust increases.

Those explanations often become the exact phrasing AI systems reuse later.

Post-purchase clarity feeds pre-purchase understanding.

Keeping the Engine Alive

An answer engine only works if it stays current.

Language shifts. Buyer expectations evolve. New questions emerge.

I truly have been enjoying AirOps lately, and getting deeper into using it to build infrastructure. AirOps isn’t just for monitoring. It’s the execution layer that turns question signals into a prioritized backlog, ships canonical answers across surfaces, and keeps those answers current as language drifts.

Think of AirOps as answer-maintenance infrastructure: it detects drift, flags which canonical answers need attention, and helps teams update once and propagate everywhere.

There is real data behind this. Across AirOps analysis, content refreshed within the last quarter is roughly three times more likely to be cited in AI generated answers than older content.

Reference: The Silent Pipeline Killer: How Stale Content Costs You AI Citations (and Customers)

AI systems do not just look for authority. They look for clarity that reflects current language. If your explanations lag behind how buyers are asking questions today, citations quietly shift elsewhere.

AirOps helps teams:

• Track which questions are rising or fading

• Refresh canonical answers as language changes

• Ensure consistency across pages, FAQs, sales assets, and product

• Prevent explanation drift over time

Humans still own the answers.

AirOps keeps the system from breaking.

A Simple Mental Model

If a question matters:

• It has one canonical answer

• That answer appears everywhere it’s needed

• AI systems can reuse it cleanly

• Humans don’t have to reinterpret it each time

That’s an answer engine.

Not content velocity.
Not SEO hacks.
Not clever formatting.

Clarity, repeated consistently.

The AEO Takeaway

Turning questions into an answer engine is how AEO compounds.

Instead of publishing more, you explain better.
Instead of chasing rankings, you shape understanding.
Instead of reacting to AI, you train it.

That’s how elite teams stop playing catch-up and start owning the narrative.

12. Operationalizing Question Mining (So It Actually Runs)

Most teams don’t fail at question mining because they lack insight.

They fail because nothing owns it.

No cadence.
No backlog.
No decision rights.
No follow-through.

The highest-signal inputs usually come from live sources that capture true user behavior: qualified chat like Intercom, demo/contact forms, on-site search logs, support tickets, sales transcripts, plus demand/behavior signals from Google Search Console and Google Analytics 4…and freshness/context from your CMS.

Question mining only works if it becomes a rhythm, not a brainstorm. Something lightweight, repeatable, and boring enough to survive real workloads.

This is where something like Page360 from AirOps becomes critical. It brings together GA4 engagement, Search Console demand, and AI search citations at the page level so prioritization stops being opinion driven and becomes an evidence-backed weekly queue.

Instead of arguing about what to update next, teams can see which canonical answers are underperforming relative to demand and act with confidence.

The Weekly Question Review Cadence

If question mining isn’t reviewed weekly, it’s already falling behind.

Not a big meeting.
Not a presentation.
A short, disciplined review.

The goal of the weekly cadence is simple:

• What new questions surfaced?

• Which ones matter?

• What are we doing about them?

A strong weekly review looks like:

• 20–30 minutes

• Same attendees

• Same structure every time

Agenda:

1. New questions added since last week

2. Repeated questions gaining momentum

3. One decision: promote, park, or ignore

No ideation.
No content planning.
Just triage.

This keeps the backlog honest and prevents everything from feeling “important.”

The Shared Question Backlog (Single Source of Truth)

Every question lives in one place.

Not Slack threads.
Not Google Docs.
Not someone’s notes.

A shared backlog includes:

• Raw question text

• Source (sales, Reddit, support, chat, etc.)

• Frequency or confidence level

• Intent cluster

• Current status (new, clustered, answered)

This backlog is not owned by content.

It’s owned by the system.

In practice, “every surface” isn’t abstract. It means your CMS (Webflow, Shopify, etc.) plus the backlog tools where real work gets managed…Notion, Airtable, Asana, Slack, etc.

The system doesn’t replace them. It feeds them.

Questions get clustered and prioritized centrally, then routed into the workflows your team already runs. Publishing happens in your CMS. Execution lives in your task systems. AirOps sits between signal and action…turning ambiguity into a clear, shippable queue.

If a question isn’t in the backlog, it doesn’t exist.
If it’s answered, it gets marked as such.
If it keeps resurfacing, that’s a signal the answer isn’t working yet.

This is how you avoid solving the same problem five times a year.

The Ownership Model (This Is Critical)

Question mining dies when everyone is “involved” and no one is accountable.

The cleanest model looks like this:

PMM owns the question quality

• What questions matter

• How they’re framed

• Whether the answer resolves the real uncertainty

Growth owns the surfaces

• Where answers live

• How they show up across site, AEO pages, comparisons

• Whether answers actually get seen

Sales owns escalation

• Which questions block deals

• Which objections keep resurfacing

• When positioning breaks down live

Support feeds signal.
Content executes.
But PMM and Growth are the spine.

This alignment is what turns AEO from “content strategy” into GTM infrastructure.

Automation as Leverage, Not Replacement

Automation is not here to decide what matters.

It’s here to make sure you don’t miss it.

At scale, questions come from everywhere:

• Sales transcripts

• Support tickets

• Chat tools

• Reviews

• Internal search

• Social threads

Manually tracking that is impossible.

This is where AirOps becomes foundational.

AirOps helps teams:

• Aggregate questions across sources automatically

• Normalize phrasing without losing intent

• Detect repeated uncertainty early

• Keep clusters fresh as language evolves

What AirOps does not do:

• Decide which questions deserve ownership

• Write positioning

• Replace judgment

Humans decide.
Automation makes it survivable.

If this still feels abstract, here is what it looks like in practice.

Eoin Clancy from AirOps recently did an awesome demo with Dave Gerhardt of Exit Five (check it out here at 21:23) that shows how teams turn fresh sales transcripts from the last 90 days into a prioritized GTM question backlog, then generate brief-ready outputs with human review.

The workflow pulls recent transcripts and metadata, extracts both explicit and implicit questions, overlays them with quantitative demand signals, and outputs a ranked list of bottom-of-funnel topics. Humans stay in control of approvals and positioning. The system handles the scale.

This is the missing bridge most teams never build. Sales language becomes structured signal. Structured signal becomes an executable backlog.

How This Actually Feels When It’s Working

When question mining is operationalized properly:

• Sales stops improvising answers

• Content feels calmer and more focused

• PMM stops reacting late

• AI explanations start sounding more like you

• Fewer “why are we still getting this question?” moments

The system absorbs chaos so people don’t have to.

A Simple Rule That Keeps It Alive

If a question:

• Shows up in more than one source

• Affects a buying or adoption decision

• Keeps resurfacing after being “answered”

It deserves attention.

No debate.
No backlog guilt.
Just action.

The AEO Takeaway

Question mining doesn’t fail because teams don’t care.

It fails because it’s treated like a task instead of a system.

When you give it a cadence, a backlog, clear ownership, and automation as leverage, it becomes self-sustaining.

That’s when AEO stops being a project and starts being a competitive advantage.

13. Where Automation and AI Multiply Impact

Up to this point, everything in this guide could be done manually.

You could read the threads.
Listen to the calls.
Review the tickets.
Scan the chats.

It would even work for a while.

Then volume hits. Language shifts. New objections appear. AI systems change how they frame answers. The system that felt manageable becomes brittle.

That’s the moment automation stops being optional.

Not to replace thinking.
To keep thinking effective at scale.

What Automation Is Actually Good At (and Humans Aren’t)

Humans are excellent at judgment.
They’re terrible at repetition.

Automation shines in four places that quietly matter for AEO.

Aggregation at Scale

Questions don’t come from one place. They come from sales calls, support tickets, chat tools, reviews, internal search, Reddit, and social threads.

Workflow automation tools like Gumloop or n8n handle this first layer. They pull transcripts, scrape communities, and route raw question data into a single stream.

They don’t decide what matters.
They make sure nothing gets dropped.

Normalization without Flattening Meaning

The same question appears phrased ten different ways:

• “Is this overkill?”

• “Are we too small?”

• “Is this only for enterprise?”

Automation groups those variations so humans can reason about intent instead of drowning in phrasing differences.

Pattern Detection Over Time

Humans notice spikes.
Automation notices drift.

Which questions are quietly increasing?
Which ones stopped appearing?
Which explanations no longer resolve uncertainty?

This matters because AI systems reuse language that persists, not language that spikes once.

Maintenance, Not One-Time Creation

The hardest part of AEO isn’t writing answers. It’s keeping them current as language evolves.

Automation flags when answers need attention. Humans decide what to do.

Where Tools like AirOps Fit in the Stack

Where some tools can help you move data, AirOps helps you manage the end-to-end lifecycle: cluster → prioritize → draft/refresh → publish/sync → measure. All with humans in control of judgment.

If Gumloop or n8n move data, AirOps is where questions turn into answers and answers turn into assets.

AirOps is not just analysis infrastructure.
It’s execution infrastructure.

Used well, AirOps helps teams:

• Normalize question language across every source

• Cluster questions by decision logic, not keywords

• Identify which questions deserve canonical answers

• Generate first-draft AEO content from approved clusters

• Refresh and rewrite answers as buyer language evolves

• Maintain consistency across site, comparisons, FAQs, and enablement

• Automate updates without explanation drift

This is a critical distinction.

Workflow tools move information.
AirOps creates and maintains the explanation layer.

Clustering → Content → Refresh (The Real Flywheel)

This is what the flywheel actually looks like:

1. Questions flow in from workflows (sales, support, chat, social)

2. AirOps clusters them by intent and decision logic

3. Humans approve which clusters matter

4. AirOps generates or updates canonical answers

5. Those answers ship across AEO pages, FAQs, comparisons, messaging, positioning strategy, lifecycle campaigns, sales assets, you name it.

6. New questions test the explanations

7. AirOps flags what needs refinement

Creation and refresh are continuous.

This is how answer engines stay alive.

Why This Matters for AEO Specifically

AI systems do not reward:

• Static pages

• Outdated phrasing

• Inconsistent explanations

They reward:

• Clear, current answers

• Consistent framing across surfaces

• Language that matches how buyers actually ask questions now

Automation makes that possible.

Not by guessing.
By reacting faster than humans can alone.

Human-in-the-Loop Is Still Non-Negotiable

The failure mode of automation is outsourcing judgment.

That’s not how elite teams work.

The winning model looks like this:

• Workflow tools aggregate and route

• AirOps clusters, drafts, refreshes, and maintains

• Humans approve priority, framing, and tone

• Automation ensures consistency and scale

AI expands your execution capacity.
Humans define truth and strategy.

What This Feels Like When It’s Working

When this layer is set up correctly:

• Content stays fresh without rewrites from scratch

• The same questions stop resurfacing

• Sales hears fewer “can you clarify…” objections

• AI explanations stay aligned with your positioning

• Teams stop arguing about what to write next

The system absorbs change instead of breaking under it.

The AEO Takeaway

Automation doesn’t replace thinking.

It protects it from scale.

Workflow tools keep the pipes flowing.
AirOps turns questions into answers and keeps them relevant.

That’s how question mining stops being a project and becomes durable advantage.

14. Question Mining → AEO → Revenue

Question mining isn’t a content exercise.

It’s a revenue system.

When teams do this well, the outcome isn’t “better blogs” or “more visibility.” It’s buyers who arrive clearer, decide faster, and trust you earlier than they would have otherwise.

That’s the throughline.

Faster Trust Formation (Before You Ever Show Up)

Trust used to form during the sales process.

Now it forms before the first interaction.

When AI systems answer questions clearly, consistently, and with the right tradeoffs, buyers show up with confidence instead of skepticism. They’ve already internalized how your product works, where it fits, and where it doesn’t.

That trust doesn’t come from persuasion.

It comes from clarity.

When your answers resolve uncertainty honestly, buyers don’t feel sold to. They feel helped. And AI systems learn to surface your explanation first because it actually reduces confusion.

Trust compounds quietly, upstream.

Higher Conversion From AI-Sourced Traffic

AI-sourced traffic behaves differently.

Lower volume.
Higher intent.
Less patience for fluff.

Question-mined AEO content converts better because it meets users at the exact point they’re stuck.

Instead of landing on a generic page, they land on:

• A clear explanation of fit

• An honest breakdown of tradeoffs

• A direct answer to the question they just asked an AI system

That alignment matters.

When the AI explanation and your on-site explanation match, conversion friction drops. The buyer doesn’t have to reconcile conflicting narratives.

They just move forward.

Reduced Sales Friction (This Is the Hidden Win)

Sales friction is rarely about price.

It’s about unresolved questions that show up too late.

When question mining feeds AEO properly:

• Buyers stop asking basic clarification questions on calls

• Objections become sharper and easier to address

• Sales stops re-explaining the same concepts over and over

The sales conversation shifts from:
“Can you explain how this works?”
to
“Let’s talk about whether this is right for us.”

That shortens cycles.
It improves close rates.
It reduces rep fatigue.

Sales friction didn’t disappear.
It moved upstream and got resolved earlier.

Compounding Content ROI (Where This Gets Dangerous)

Most content depreciates.

Question-based content compounds.

When you answer the right questions:

• The content gets reused in AI answers

• It shows up in comparisons

• It informs sales conversations

• It reduces support load

• It stays relevant longer than trend-driven posts

You’re not publishing to fill a calendar.

You’re publishing to eliminate confusion permanently.

Each canonical answer absorbs dozens of future questions. Each clarification prevents downstream friction. Each explanation trains both humans and machines how to think about your product.

That’s not linear ROI.

That’s compounding.

The Full Loop

Here’s the system, end to end:

Questions reveal uncertainty
Uncertainty shapes AI answers
AI answers influence buyers
Buyers arrive clearer
Sales friction drops
Conversion improves
Answers get reused
Trust compounds

No hacks.
No tricks.
Just better explanations, deployed consistently.

The AEO Takeaway

Question mining isn’t how you get more traffic.

It’s how you get better buyers.

Buyers who trust you sooner.
Buyers who convert faster.
Buyers who churn less because expectations were set correctly.

In an AI-first discovery world, the brands that win aren’t the loudest.

They’re the clearest.

And clarity is a revenue strategy.

15. The Future: Questions as the New SEO Primitive

For a long time, SEO was about keywords.

Find the term.
Build the page.
Optimize the rank.

That model made sense when discovery was document-first.

It doesn’t anymore.

In an AI-first world, discovery starts with a question and ends with an explanation. There is no list of links to browse. There is no second page. There is a single synthesized answer shaped by the clearest thinking the system can find.

That’s the shift.

We are moving from keywords to answer coverage.

From Keywords to Answer Coverage

Keywords describe topics.
Questions describe decisions.

AI systems don’t ask:
“Which page is most optimized for this term?”

They ask:
“Which explanation best resolves this uncertainty?”

That’s why keyword coverage alone is no longer defensible. You can rank and still be irrelevant. You can publish and still be absent from the answer.

The brands that win are the ones that systematically cover:

• The fears people don’t articulate cleanly

• The tradeoffs buyers underestimate

• The “what happens if…” questions no one wants to answer honestly

• The practical realities after the pitch is over

That’s answer coverage.

And it’s much harder to fake than keywords ever were.

Brands as Explanation Engines

The best brands in the AI era don’t feel like marketing machines.

They feel like teachers.

They explain things clearly.
They name downsides early.
They help buyers think, not just choose.

Over time, those explanations become the default language of the category. Sales reps repeat them. Buyers quote them. AI systems reuse them.

That’s how brands become explanation engines.

Not by publishing more.
By explaining better.

Why Clarity Wins the AI Era

AI systems are not impressed by cleverness.

They reward clarity.

They reuse explanations that:

• Reduce ambiguity

• Hold up across contexts

• Match how real people ask questions

• Stay consistent over time

Humans reward the same things.

Clarity builds trust faster than persuasion ever did. It shortens sales cycles. It prevents regret. It filters out the wrong buyers before they churn.

In a world where everyone can generate content, the advantage isn’t production.

It’s precision.

The Real Competitive Advantage

Question mining isn’t a tactic.

It’s how you stay aligned with how buyers actually think as discovery keeps changing.

When you run this system:

• You don’t chase traffic

• You don’t panic when algorithms shift

• You don’t rebuild your strategy every year

You listen.
You cluster.
You explain.
You refine.

And over time, the market starts repeating your language back to itself.

That’s the moat.

The Final Takeaway

Discovery has changed.

Search engines used to reward whoever ranked highest.
AI systems now reward whoever explains something most clearly.

When someone asks a question inside an AI interface, they are not browsing. They are looking for clarity. The model will synthesize the best available explanation in that moment.

If your company has not articulated that explanation clearly, it will not be part of the answer.

That is the shift.

This is not about publishing more content.
It is not about chasing every new AI feature.
It is about understanding the real questions that shape decisions and answering them so well that your thinking becomes reusable.

The teams that win will treat market insight as a living system.

Not a quarterly slide deck.
Not scattered anecdotes from sales.
Not a Slack thread that disappears in a week.

A machine.

A steady loop that captures real buyer uncertainty and feeds it into product marketing, AEO, SEO, demand gen, sales positioning, and customer experience. Over and over again.

When that loop runs consistently, things change quietly.

Sales conversations get shorter.
Messaging gets sharper.
Product friction surfaces earlier.
AI systems start reflecting your framing instead of someone else’s.

That is the moat.

Not traffic.
Not volume.
Not noise.

Shared understanding at scale.

Question mining is not a content tactic.

It is how you decide what deserves to be explained, and how you make sure your explanation shows up wherever decisions are being made.

Do that well, and you do not have to compete for attention.

You become the explanation people reuse.

Not in a panic way.
In a things I was genuinely confident about six months ago are already being unlearned way.

The pace of change in AI and marketing right now is absurd.

Frameworks that felt solid last year.
Playbooks teams scaled.
Ideas we taught with confidence.

They’re quietly breaking underneath us.

If you’re a leader actively leaning into this shift, this is probably the most energized you’ve felt in years. I feel this acutely right now. It feels creative again. Alive.

If you’re not, it probably feels like the floor won’t stop moving.

What’s disorienting isn’t one big disruption.
It’s several deep ones colliding at the same time.

OpenAI Ads Don’t Kill Performance Marketing

They Change Who Evaluates It

OpenAI ads are coming. Fast.

This doesn’t kill performance marketing.
It changes who evaluates it.

For years, ads competed in auctions. Humans decided what to click. Bidding power and creative optimization won.

Now, the model decides what to show.

That flips the order of operations.

Eligibility comes before bidding.

If the model doesn’t understand you, doesn’t trust you, doesn’t know when to surface you, you never even enter the auction.

There is no CPC problem here.
There is an invisibility problem.

Most brands won’t realize they’ve been excluded. They’ll just see performance decay and assume something downstream is broken.

Early OpenAI ads will not look like traditional performance channels. At least not at first.

My bet is that DTC brands benefit first. Shorter consideration cycles and clearer intent mean brand exposure can translate to action much faster inside an AI interface (and I too will make more impulse buys I do not need).

B2B will lag early, not because it’s less valuable, but because trust formation, attribution, and multi-stakeholder buying take longer to map inside a model-driven experience. That said, B2B being B2B, it will still jump on the spend.

Early days will feel more like paid learning than paid performance.

The real work moves upstream.
Being legible, credible, and referenceable to AI systems before dollars ever matter.

Agentic Commerce Flattens the Funnel

It Doesn’t Optimize It

Agentic commerce compresses everything.

Discovery.
Evaluation.
Decision.
Action.

Increasingly, all of it happens inside a single interaction.

Funnels don’t evolve here.
They flatten.

That breaks attribution.
It breaks lifecycle logic.
It breaks most assumptions about how conversion actually works.

When an agent answers the question and executes the action, there is no journey to optimize. There is only the moment you are chosen, or not.

This is why dashboards still look fine while teams feel like they’re losing control.

We’re measuring motion that no longer reflects how decisions are actually made.

Upstream Influence Is the Only Thing That Compounds

In AI-driven discovery, intent forms before anyone clicks.

If AI discovery isn’t top of mind, you are invisible.

Owning answers isn’t a tactic anymore.
It’s the whole game.

Onsite still matters.
Offsite matters more.

Your website is no longer the center of gravity. It’s one input among many.

Decisions are shaped across:

• forums

• communities

• reviews

• secondhand explanations

• fragmented conversations

…where AI systems assemble understanding.

Winning here means building systems that:

• mine the real questions people are asking

• recognize how those questions mutate across contexts

• ensure credible answers exist everywhere models pull from

This isn’t content marketing.
It’s decision infrastructure.

Marketing Isn’t Campaigns Anymore

It’s an Engine

The uncomfortable truth:

Marketing isn’t campaigns anymore (I’ve felt this way for awhile, but now more than ever reinforces this).

Marketing is building an engine that AI systems can understand, trust, and propagate over time.

That engine compounds quietly or decays silently, whether you’re “running something” or not.

And that brings me to the line that’s been looping in my head lately.

The Future Is Unwritten

In my usual fashion of quoting punk rock warlords,
Joe Strummer used to say:

The future is unwritten.

That wasn’t optimism.
It was a warning and a dare.

Nothing about what’s coming next is guaranteed.

Not channels.
Not roles.
Not playbooks.
Not the things that made us successful five minutes ago.

The people who win moments like this aren’t the ones protecting the past.

They’re the ones willing to tear it down while it’s still working.

That’s what this moment feels like.

Uncomfortable. Loud. Unfinished.
And full of possibility if you’re willing to step into it instead of waiting for consensus.

(Sorry for below, GenAI image models have a way to go)

My Commitment for 2026

I’m not sitting this shift out.

Just like I’ve done with AEO, I’m going to keep testing, building, breaking, and learning in the wild alongside some of the smartest minds in marketing.

Out loud.
In public.
In real time.

No polished hindsight decks.
No fake certainty.

Just honest signal from the edge of what’s changing.

Because the future isn’t something we wait for.

It’s something we write.