Buyers don't shortlist anymore. They ask AI.
When someone asks ChatGPT for "the best tool for X," an answer comes back with three names on it. If yours isn't one of them, you lost a deal you never knew existed. Viz tells you where you stand, who's beating you, which assistants send you trials, and hands the agents that fetch your pricing page the tools to ask for a demo.
The funnel moved, and your analytics didn't.
Invisible evaluations
AI assistants compare you to competitors in private conversations. No search console impression, no landing-page visit - the shortlist forms before anyone touches your site.
Your docs feed the models
GPTBot and ClaudeBot crawl your documentation, changelog, and blog. Those pages shape what AI says about your product - and your JavaScript analytics can't see any of it.
Unattributed signups
Trials that start from a ChatGPT or Perplexity recommendation land as "direct" in your dashboards. The channel that's growing fastest is the one you can't measure.
See the whole AI funnel. Then go win it.
Track your buyer prompts
Monitor the "best X for Y" questions your market asks across Gemini, Claude, GPT, and Perplexity - mention rate, citations, sentiment, and share of voice against the competitors you pick. AI visibility →
Publish what the shortlist demands
The AI Content Pipeline turns your crawl and visibility evidence into reviewed comparison and answer pages, delivered into Posts → Drafts. You approve and publish; every piece is tracked until it earns crawls, citations, and signups. AI Content Pipeline →
Credit the trials AI sends you
Every registration, trial and demo request is credited to the assistant that sent the visitor - ChatGPT, Perplexity, Gemini and ten more - captured from WordPress registration and your forms plugin on the server, on every plan. No GA4 required; connect it for session depth. And the agent that already fetches your pricing page gets tools: describe_business and contact_business on every page (WebMCP), plus /ai-contact/, to request a demo for the person it works for. AI Conversions →
See who reads your docs
Server-level analytics shows which AI crawlers hit your content and how often - the leading indicator that models are learning who you are. Analytics →
Documentation is your new sales channel - and it sells to machines.
When a buyer asks an AI assistant to compare tools, the assistant doesn't browse your homepage the way a human would. Its answer is assembled from what models learned during training and what retrieval bots fetch at question time - and both lean heavily on documentation, changelogs, comparison pages, and technical blog posts. The content your marketing site treats as an afterthought is often exactly what the machines weigh most.
That changes what "SEO" means for a SaaS company. Classic search optimization competed for position on a page of ten links; AI answers typically name two or three products, and everyone else might as well not exist. Getting into that shortlist is a function of being crawled, being understood, and being cited - three things you can only manage if you can see them happening.
The practical loop looks like this: watch which of your pages AI crawlers actually read (the crawl is the leading indicator), track whether AI engines mention and cite you for your buyers' questions (the outcome), and attribute the trials that AI referrals send you (the payoff). Each step is measurable, and each one tells you where the next content investment should go.
Common questions, straight answers.
How do I know if AI models even know my product exists?
Two signals. First, crawl data: if GPTBot, ClaudeBot, and friends are fetching your docs and marketing pages, your content is entering the pipeline models learn from. Second, answer tracking: run the questions your buyers ask against the major engines and see whether your brand comes back. Viz gives you both, side by side.
Should a SaaS company block AI crawlers?
Usually not the retrieval and search bots - being absent from AI answers is a real commercial cost when buyers ask assistants for recommendations. Training crawlers are a genuine judgment call, but for most SaaS businesses, being known by the models is worth more than the content is.
Why do AI-referred trials show up as direct traffic?
Many AI surfaces open links without a referrer header, or from apps where no referrer exists. Some, like chatgpt.com, do pass a referrer that GA4 lumps under generic referral traffic. Viz captures that referral at the server, credits the trial or sign-up that follows to the assistant, and, if you connect GA4, pulls the matching sessions into the same view so the channel stops hiding inside "direct." Treat the count as a floor; read the rate.
What about AI agents that request a demo on someone's behalf?
Early, but coming. What is already routine is an assistant fetching your pricing page for a buyer and leaving with nothing it can act on. Viz shows what those agents came to do, grades whether your site can even answer their questions (pricing is the usual gap), and hands them tools: every page registers describe_business and contact_business for the agent in a buyer's browser (WebMCP), and /ai-contact/ is the plain, machine-readable form for agents arriving from outside a browser. Either way the demo or quote request lands in your inbox as a lead, credited to the agent, and never leaves your site.
Can I see which competitor content wins the citations I lose?
Yes. AI visibility tracking records which sources AI engines cite for your tracked prompts - including when the citation goes to a competitor's comparison page or a review site instead of you. That list is effectively your AI-era content roadmap.
Our docs are public anyway - what does measuring the crawl actually change?
It changes what you write next. Public-by-default is a distribution choice; measurement tells you whether it is paying off. If retrieval bots hammer your integration guides but never touch your comparison pages, you have learned where AI thinks your authority ends - and that the content shaping buyer-facing answers is not the content you assumed. That is a concrete basis for reprioritizing your content roadmap.