Client stories
Evidence from documentation audits and knowledge base work — specific constraints, not generic praise.
Voices from recent work
“They traced every dead link in our service catalog before rewriting a single page. The first week after launch, support tickets about ‘where is the deploy checklist’ dropped sharply — though we still needed two more passes on the auth chapter.”
— Nattapong K., engineering manager, Bangkok product studio
“Our knowledge base had grown by accretion for five years. Content Creekbase forced ownership decisions we had postponed. The taxonomy they proposed felt strict at first, but onboarding now takes days instead of a scavenger hunt.”
— Mira S., documentation lead, regional fintech
“I appreciated that they refused to invent metrics. The audit listed twelve pages that contradicted production behavior. Fixing those mattered more than a redesigned homepage.”
— Arun P., platform lead, logistics API team
“Remote workshops worked, but Bangkok traffic meant our on-site follow-up started late. Once we were in the room, the ownership matrix finally stuck — something async chats never achieved.”
— Helen T., head of engineering enablement
Extended story: consolidating three wikis
A mid-size payments company near Asok ran developer guidance across Confluence, a GitBook mirror, and a Notion space used by support. New engineers received contradictory setup steps depending on who mentored them.
Content Creekbase ran a two-week documentation systems audit, then a knowledge base architecture workshop. The brief named a single source of truth for environment setup, archived two parallel “getting started” trees, and assigned owners per domain. Editorial retainer hours covered rewriting the first eight pages. Six weeks later, the team reported that mentor time on day-one setup questions had fallen, while deep domain questions still correctly routed to specialists — an outcome they preferred to a false promise of zero questions.