Claude

Claude's audience skews towards people making considered decisions — developers choosing tools, professionals researching services, teams comparing options. Fewer questions, higher stakes per question.

Documentation is the lever

If you sell software or a technical service, your documentation is doing more distribution work than your marketing pages. Assistants asked to compare tools reach for whatever is clearest, and clarity here is a mechanical property: does the content exist in the HTML, is it structured, does it answer the question directly.

A docs site that renders only after JavaScript is invisible to this, no matter how good the writing is.

MCP is the interesting part

Anthropic published Model Context Protocol↗(opens in a new tab), now supported well beyond Anthropic. It is the clearest existing route from being described to being used — an assistant that can query your live data rather than repeating a cached description of it.

That is the use you pillar, and almost nobody has done it. Which is exactly why it is worth doing.

Being realistic

For a local plumber, Claude is not where the customers are. For a B2B software company, an accountancy practice or a specialist consultancy, it is disproportionately likely to be involved in a decision that matters.

On accuracy. Retrieval architectures change without announcement, and none of these companies publish full details. This page states what is documented, flags what is inferred, and avoids claiming internals nobody outside the company can verify. Spotted something out of date? Tell us.