What a Government Client Praising Your Documentation Taught Me About Commercial Value
There's a moment from my time at Griaule that I think about more than most.
We were in a contract renewal meeting with our largest client — a Federal Government agency. These meetings follow a familiar structure: review of service performance, discussion of pricing, negotiation of terms. The conversation is typically technical and commercial in equal measure.
Midway through the meeting, the client raised something we hadn't put on the agenda.
They said, unprompted, that the quality of our technical documentation had been exceptional. That their team could find what they needed, that new staff could onboard from the documentation without needing to schedule time with our engineers, that the clarity and usability of the materials reflected well on the entire engagement.
In a public sector procurement context, this is unusual. Government clients provide formal performance evaluations through official channels. Unsolicited qualitative praise in a renewal negotiation is not the norm.
What It Actually Meant
On the surface, it was a compliment. But there was a more concrete meaning underneath it.
The client was telling us, in the language of a renewal negotiation, that the documentation had reduced their cost of using our product. Their team spent less time on the phone with our support engineers. New staff could become productive faster. Edge cases that would have required escalation could be resolved through self-service.
Those are business outcomes, not documentation outcomes. The documentation was the mechanism. The value was in the reduced friction across the entire engagement.
Why Documentation Gets Undervalued
Documentation is typically categorized as a technical deliverable — something that lives in a wiki and accumulates debt at roughly the same rate as the codebase it describes.
The commercial case for documentation is rarely made explicitly, which means it rarely influences resourcing decisions. Technical writers and documentation infrastructure are among the first things cut when budgets tighten, because the cost of their absence is diffuse and delayed rather than immediate and visible.
The cost shows up later: in elevated support ticket volume, in longer client onboarding, in engineers who spend their time answering questions that documentation should have answered, in renewal conversations that are harder than they needed to be.
The Calculation Nobody Does
I've never seen a company formally calculate the support cost reduction attributable to good documentation. The attribution is genuinely difficult.
But rough estimates are possible and useful. At Griaule, our best estimate was that the documentation pipeline contributed to a 10–20% reduction in documentation-related support tickets. In an operation where support was already under significant load, that reduction had a concrete effect on team capacity.
More importantly: the government client's unsolicited praise in the renewal meeting created a dynamic where the renewal was easier — not just emotionally, but commercially. The client had evidence that the engagement was delivering value beyond the contractual minimum. That's a different negotiation than one where you're defending whether you've met the SLA.
The Practical Takeaway
If you're a PM or technical leader who needs to make the case for documentation investment, the frame that has worked for me is this:
Documentation is a support cost reduction strategy. Every page of clear, accurate documentation that answers a question a client would otherwise call support about is a unit of support capacity returned to the team.
At scale, that return is significant. The challenge is that it doesn't appear on any dashboard by default — you have to build the measurement infrastructure to see it.
But the signal exists. And sometimes, if you're lucky, a client will tell you directly in a renewal meeting.