The Procurement Question You Are Failing
How documentation surfaces in security questionnaires, RFPs and enterprise evaluations, and what an empty help centre signals to a buyer who has never met you.
Somewhere around question sixty of a vendor security questionnaire, between data residency and incident response, there is a line asking for a link to your user documentation. It is not weighted heavily. Nobody scores it out of ten. It sits there looking like an administrative formality, and the person filling in the form pastes whatever URL exists and moves on to the questions that feel like they matter.
That link gets clicked. What happens in the eight seconds afterwards is worth more than most of the answers above it.
What the link is actually testing
The buyer is not evaluating your documentation. They are using it as a proxy for things they cannot test directly in a procurement cycle.
Whether you have processes or just people. A help centre that is current implies somebody owns keeping it current, which implies a company with operational habits rather than heroics. Whether the product is stable enough to describe. Thin documentation reads as a product still changing shape, which for a five-year contract is a risk. Whether their own team will be able to self-serve, or whether every question routes through a support queue and, eventually, through the champion who bought you.
That last one is the sharpest. The person evaluating you will be responsible internally for the rollout. They are imagining two hundred colleagues asking them questions, and your help centre is their evidence about how many of those questions they can deflect.
None of this is written down in the evaluation criteria. All of it is happening.
The asymmetry that makes this expensive
Good documentation rarely wins a deal on its own. Absent documentation loses them, and it loses them silently, which is what makes the maths so bad.
You will not receive an email saying "we went elsewhere because your help centre had eleven articles". You will be told the timing was wrong, or the budget moved, or they went with an incumbent. The documentation objection is not the kind of thing procurement teams say out loud, partly because it sounds petty and partly because it operates as a confidence input rather than a stated requirement.
So the cost never appears in your CRM. It appears as a slightly lower close rate in a segment you cannot isolate, which is indistinguishable from noise until it has been running for a year.
What "good enough for procurement" actually means
The bar is lower than the one in your head, and it is different in kind.
It is not comprehensiveness. Nobody reads a help centre exhaustively during an evaluation. It is evidence of maintenance - a recent date, terminology matching the product they just saw demonstrated, screenshots showing the interface they were shown rather than one two redesigns ago. A thirty-article help centre that is obviously current beats a two-hundred-article one full of 2023 screenshots, and the second one is worse than having nothing because it demonstrates a company that started and stopped.
Three things carry disproportionate weight in this specific context. A page on security and data handling, because it is the first thing they look for and its absence is loud. A page on roles and permissions, because they are thinking about a rollout to teams. And any evidence of a changelog or release notes, because it proves the product is alive.
This is a hygiene factor, not a differentiator
I am describing a pattern in how buyers behave, not a measured effect, and I want to be careful about the difference. I cannot show you a controlled test where the same deal was run twice with different help centres.
It also does not apply evenly. Selling a £40-a-month tool to individual developers, none of this matters much - your documentation is a product surface and a support cost, not a procurement artefact, and you should optimise it for the former. The dynamics above start mattering somewhere around the point where a legal review enters the sales cycle, and they matter more the further up you go.
And documentation is nowhere near the top of the list of things that lose enterprise deals. Security posture, references, integrations and price all rank above it. This is a hygiene factor. The argument is not that it wins - it is that it is unusually cheap to fix relative to how it fails.
Before your next evaluation
Open your help centre in a private window and read it as someone who has seen one demo. Check the newest date on the page.
If that date is older than your last release, fix that before you answer question sixty again.
About the Author
Simon Moxon has been building SaaS companies since 2009. He's scaled teams to 20+ people, hit £2m ARR, and learned most of the lessons the hard way. Now he's building SupportPages.io - help docs that write themselves when you ship code. He writes about what's changed in SaaS and what hasn't.