Free help-center audit
Your help center drifted from your product. I'll show you where, for free.
Send me your help center. Within 3 working days you get a written audit: what's wrong, outdated or missing, with evidence for every finding, and a fixed price to fix it if you want me to.
- Report in 3 working days
- No obligation
- 5 audits a week
The problem
Docs drift. Nobody owns keeping them true.
Every release widens the gap a little. Nobody notices until a customer does.
The product ships faster than the docs
A renamed button, a new setting, a retired API. Each one leaves a page that's quietly wrong.
Support answers the same questions
When the help center doesn't answer, or answers wrongly, the question becomes a ticket.
Buyers' engineers read your docs first
They judge the product by its documentation before anyone books a demo.
AI assistants now read them too
Chatbots and AI connectors answer from your help center. A stale page becomes a confident wrong answer, at scale.
How it works
From request to a help center that matches your product
-
Request
Fill in the form below. It takes about two minutes.
-
Audit
I read your help center against your product, API reference and website. With a free trial or free tier, I test the steps in the real app.
-
Report and fix plan
Within 3 working days: every finding with evidence, and a fixed price to fix them all. Yours to keep, whatever you decide.
-
Fix and keep current
If you go ahead, I fix the gaps within a month, then keep your docs in step with every release.
What the audit checks
A full read of your help center, not a sales teaser
I don't promise a number of findings. If your help center is in good shape, the report says so.
- Steps that don't work when followed, or no longer match the interface
- Features, settings and limits your product has that no article explains
- Pages that contradict your API reference, your website or each other
- Outdated screenshots, names and menu paths
- Broken links, anchors and downloads
- Anything I couldn't verify, flagged as a question for your team instead of guessed
Pricing
Start free. Pay only for the fix you choose.
The audit sets the scope, so the price of the fix is fixed before you commit.
Help-center audit
Free
- Written report within 3 working days
- Evidence for every finding
- A fixed-price fix plan
- The report is yours, and stays private
Limited to 5 audits a week.
Help-center fix
From $1,000
- Every gap in your report fixed
- Delivered within one month
- A runbook to keep the pages in step with releases
- Updates for product changes for one month after delivery
The exact price comes with your audit, based on what it finds.
Keep it current
$500 / month
- Your docs match your product, release after release
- Changes live within 2 working days of a release, the same day with preview access
- Release notes included
- Up to 10 page changes a month; bigger months quoted first
For help centers I've fixed.
Pay 6 months upfront and save 15%: $2,550 instead of $3,000.
Guarantees
Two promises I can keep, because I control them
Live with the release
Pages I maintain are updated the same day a change goes live when I can see it before release, and within 2 working days otherwise.
Condition: you tell me about releases, through release notes, a change log or a message.
Wrong until it's right
If a page I delivered is wrong, I revise it until it's correct. No limit on accuracy fixes.
Covers the pages and scope we agreed.
Proof of work
See how I audit before you send anything
EULER help center: 13 gaps, and a sample page for each
An unrequested review of a B2B SaaS help center, read against its website, API reference and AI connector reference. Each sample flags what I couldn't verify.
See the review ↗DDCE-100 Plus checker guide
The guide for an engineering web app I built. It opens with what a result does and doesn't prove, and has a "Check:" line after every step.
Open the guide ↗Who you'd work with
An engineer who writes the docs, and builds the workflow that keeps them true
I'm Bach Widy. I spent ten years as a field engineer in lightning protection, earthing and SCADA protection, writing method statements, survey reports and guides for people who had to act on them. Now I write documentation for software teams.
- Research first: your product, your API reference, the docs you already have
- Short yes/no questions for your engineers, not long meetings
- What I can't verify is flagged, never guessed
- Every link and step I publish is tested
Questions
Before you send your help center
Do you need access to our product?
No. I can audit from your public help center and website. If you have a free trial or free tier, I sign up myself and test the steps in the real app, which makes the audit deeper.
Will you publish our audit?
No. Your report is private. I'd only use it as a sample with your written permission.
What if you don't find much?
Then the report says so, and that's useful to know too. The audit is free either way.
How is the fix priced?
From the audit. You see every finding before I quote, so the price is fixed and the scope can't grow by surprise. Fixes start at $1,000.
Do you use AI?
Yes, for research and checking, the way I'd use any tool. The facts come from your product, your docs and your engineers, and I review every line before it ships.
Where are you, and how do we work together?
I'm in Jakarta (UTC+7) and work asynchronously: email, comments and a shared task board. A short weekly call is fine if you want one.
Free audit
Request your free audit
You'll get a reply by email right away, and the report within 3 working days.