Before
CMS platform
One doc set, no branches, and search that needed exact module names
After
Docs as code, a branch per release, and AI search that understands questions
Scrut Automation is a GRC and compliance automation platform. It helps teams get audit-ready for SOC 2, ISO 27001, GDPR, HIPAA and more, then stay compliant all year.
Its help center, developer docs and release notes are run by Vaishnavi Jai, Scrut's first technical writer. More than 500 pages, read by customers, support, sales and the AI agents they all use.
The challenge
Release docs had nowhere to wait
The CMS held one doc set with no branches. Release changes were drafted in another tool and merged by hand just before launch.
"We felt like we had outgrown a CMS-based approach."
Customers couldn't find answers that already existed
Search only matched exact module names and couldn't point to the right section. Customers asked support for pages that were already published.
The solution
Scrut chose Documentation.AI because it covered every requirement:
| Scrut needed | Documentation.AI gave it |
|---|---|
| Docs as code | A Git branch per release, reviewed before launch |
| Long docs that scan | Cards, accordions and tabs |
| AI native by default | llms.txt and AI search visibility built in |
| Search that understands questions | AI search grounded in the docs, pointing to the right section |
"We liked that they didn't nickel-and-dime us for every feature. The plans included all the major features."
The move, step by step
| Step | What happened |
|---|---|
| Proof of concept | 30 to 45 days testing Documentation.AI against Scrut's requirements |
| Handover | Scrut sent links to its live docs |
| Migration | 500+ docs moved with URLs and formatting intact, every page checked, JWT login set up for private docs |
| Go-live | Under a week end to end, with one day of Scrut's time to verify |
“Our customers don't even have to remember our module names. They just ask questions in their own words, and the help center points them to the right doc. If a doc is available in the help center, our support team is 100% confident the customer can find it.”
Vaishnavi Jai, Senior Technical Writer, Scrut AutomationThe results
60-70% fewer "where is this doc?" tickets
AI search now takes customers straight to the section that answers them. This is the support team's early read, before a full analysis, and integration questions are down significantly too.

Release docs in 1-2 days, down from a week
A major release touches 40 to 50 docs. Writing now starts with a prompt, and an audit skill run through the Authoring MCP server maps each product requirements document to every doc it affects.
"I just prompt the AI, and it makes the changes. I review it and then publish the branch."
Live docs in every teammate's AI tool
Manual doc exports are gone. Teammates connect the Reader MCP server once, and their AI tools read the current docs.
Working with the team
Vaishnavi's verdict on the partnership, from migration to support:
"I'm 100% satisfied with Documentation.AI. Any question we raise, we get an immediate response, and if it needs more time, they give us an exact timeline."
Outgrown your CMS?
Plan your move the way Scrut did
Our team maps your URLs, formatting and private pages, then moves the docs for you.