The Manual Majority: why AI learns your company from your docs, not your homepage

The scene I'm in this week

Last Thursday, a $22M healthtech company outside Philadelphia. Series B, clinical workflow software, a product their customers genuinely love. The CEO and the head of product are in the room. The CEO opens his laptop before I've finished sitting down, which usually means somebody ran a test over the weekend and didn't like the answer.

He'd asked Claude a plain question, the kind a hospital operations director asks on a Tuesday. Three paragraphs came back. Two of them were his own help center, almost word for word. Good writing. Accurate, specific, actually useful. Then the last line recommended a competitor by name.

His documentation did the teaching. Somebody else got the introduction.

I asked him when he last read his own help center. Long pause. He hadn't. Neither had the head of product. It's 340 articles built over four years by support engineers and a technical writer who left in 2024, and the last person to review it as a body of work was a contractor doing a migration.

This happens in almost every room I walk into. Ask a CEO about the homepage and he can recite the hero line and tell you which word the board argued about. Ask about the docs and you get a name, two levels down, and a shrug.

Naming what's actually broken

Here's the shape of it. Your marketing site is maybe 6,000 words. Your documentation is 90,000, or 200,000, or half a million. The largest body of writing your company has ever published is a manual, and nobody ever handed that manual a story.

I call this the Manual Majority. Marketing owns the smallest surface you publish and guards every syllable of it. The other 95 percent got written page by page, at speed, by people solving a support ticket in front of them.

That's Solution-Centric Marketing with a wrench in its hand. Documentation is feature-organized by design: one page per capability, one heading per button, one procedure per screen. Written that way, the whole thing describes a toolbox. A buyer who lands in a toolbox with no idea which problem it belongs to goes and asks someone who does explain the problem, and that someone is usually the competitor whose docs open with a sentence about the buyer instead of the build.

The docs aren't the villain here. The missing story behind them is. This is just truth: your support engineers wrote in feature language because feature language was the only language anyone ever gave them.

Why is this worse in 2026 than it's ever been?

Two things moved at once, and they moved in opposite directions.

AI dropped the cost of publishing a documentation page to about zero. Doc teams that shipped 20 articles a quarter now ship 200, drafted by a model and reviewed in an afternoon. Volume went vertical while perspective stayed exactly where it was, which means the Manual Majority is growing faster than anything else you own.

At the same time, retrieval changed which page on your domain gets read. Discovered Labs found that citations to brand sites moved from 8 percent to 56 percent between 2023 and 2026, and that more than half of citations in B2B category queries now go to brand sites. The machine is coming to your own property more than it ever has. The biggest, most crawlable, most question-shaped thing sitting there is your documentation.

Think about what retrieval actually rewards. Self-contained pages. A question in the heading. A specific, checkable answer underneath. Your docs are all three of those things on every page. Your homepage is none of them. The docs win the retrieval and lose the recommendation, because getting quoted and getting recommended are two different jobs. I wrote about that gap in "The Silent Read: half of what AI knows about you never shows up on your dashboard," and documentation is where I see it happen most.

“SaaS SEO in 2026 feels less about traffic and more about being recommended. A lot of SaaS teams are no longer focusing on ranking keywords. They're asking things like: How do we get mentioned in ChatGPT, Perplexity, and AI Overviews?”

... r/SaaSSEOGEO, May 2026

That founder has the shift right, and he's still looking at the wrong surface. Everyone's optimizing the 6,000 words. The machine is reading the 200,000.

How do you tell if your documentation is working against your message?

Three tests. You can run all of them before lunch, and you don't need to hire anyone or open a project.

1. 1The Weigh-In. Get a word count for your marketing site and a word count for your documentation, and put the two numbers side by side. Most $5M-$75M B2B companies land somewhere between 15 to 1 and 40 to 1. Whatever your ratio is, that's the share of your published voice that no one on your marketing team has ever read.
2. 2The Opening Line Test. Open your five highest-traffic documentation pages and read only the first sentence of each. Count how many name a buyer or a problem. If all five open with a product name, a version number, or a verb like 'configure,' the machine has five specific, well-written pages about your company that say nothing about who you're for.
3. 3The Cold Retrieval Test. Start a fresh session in ChatGPT or Claude and ask the how-do-I question a buyer in your category would ask before they know vendors exist. Read whose material comes back, then read what the model says about the company behind it. Getting quoted and getting recommended will show up as two separate outcomes, and the gap between them is your whole problem in one screen.

Test three is the one that changes the meeting. Founders expect to be absent from the answer. Watching yourself get quoted at length and then skipped in the recommendation is a different feeling entirely, and it's the honest one.

What do I see across 100+ B2B companies?

The ratio holds almost everywhere. Across the founder-led B2B companies I've worked with in the $5M-$75M range, documentation outweighs the marketing site by 15 to 1 at the low end and 40 to 1 at the high end. Not one of those companies had a person accountable for what that body of writing says about the business.

Nine documentation homepages in ten open with the product name and a version number. Fewer than one in ten name the buyer's problem anywhere in the first screen. The pages get audited for accuracy on a schedule and never once for meaning.

Here's the part that surprises people. The single most honest voice-of-customer data in the whole company is sitting in the help center search log, and nobody reads it. Those queries are your buyers typing their actual problem in their actual words, unprompted, with no salesperson in the room. Marketing runs a research project to find that language while it accumulates untouched three clicks away.

When your own surfaces contradict each other, the engines can't resolve you into one confident thing, which is the same failure I described in "How do you build the entity authority AI engines actually trust?" Documentation is the biggest contradiction most companies own, because the marketing site sells an outcome and the docs describe a machine.

A real example

A PE-backed cybersecurity company, $31M in revenue, came to me because ChatGPT kept recommending two competitors they beat in head-to-head evaluations. Their instinct was that the homepage needed another rewrite. It was the third one in two years.

We ran the Cold Retrieval Test on ten category questions first. Their documentation got quoted in six of the ten. Their company got recommended in one. They had 410 doc articles and the top-level page said 'Platform Documentation, v4.2.' The word 'attack' appeared 900 times. The phrase 'security team' appeared four.

We built the Magnetic Messaging Framework first, then touched 14 pages: the documentation home, six category landing pages, and the seven highest-traffic articles. Each one got a two-sentence opener naming who the page is for and which problem it solves, before any instruction started. No re-architecture, no migration, no new platform. The other 396 articles stayed exactly as they were.

Eleven weeks later we re-ran the same ten questions. Quoted in seven, recommended in five. The CRO's reps started sending documentation links inside live deals, which they had never done in four years, because the pages finally made an argument instead of listing steps. And the help center search log gave them three phrases that went straight onto the homepage.

What this means for you

You don't need a documentation project. You need to stop treating the biggest thing you publish as somebody else's department. Three things worth doing this week:

1. 1Read your five highest-traffic documentation pages out loud, first sentence only. Out loud matters. You'll hear the toolbox immediately, and you'll hear which page is closest to already being right.
2. 2Write the two-sentence opener for your documentation home and your category pages. Who this is for, which problem it solves, then the instructions. That's 16 sentences of work covering the pages that carry most of your traffic and most of your retrieval.
3. 3Pull last quarter's help center search queries and read the top 50. Those are your buyers naming their problem in their own words, for free, with nobody performing. Take the three phrases that make you flinch and put them where your buyers can see them.

That work holds only if there's something upstream for the doc team to write from, which is where most of this actually breaks. Your support engineers didn't drift from the story, they never received one. The fix is a Magnetic Messaging Framework (MMF), a strategic narrative system built around four anchors: category design, villain framing, an old-way / new-way contrast, and a promised-land outcome. Villain framing is the anchor doing the heavy lifting here, because it decides which problem every page is quietly arguing against. This matters for a practical reason. Once the narrative is written down in one place, the person writing article 411 inherits the same buyer, the same problem, and the same words as the person who wrote your homepage, and your largest surface starts compounding your message instead of diluting it.

PitchKitchen builds Magnetic Messaging Frameworks for founder-led B2B companies in the $5M-$75M range. I'm Greg Rosner, founder of PitchKitchen and author of Story Craft for Disruptors, and I'd bet your docs contain a better explanation of your customer's problem than your homepage does. Go find it. Does that make sense?