a real scope creep
docs tools like gitbook and mintlify are genuinely good at one thing, ie making docs look nice and letting you write them in a git-based workflow but they don't answer customers, and nothing in them knows when your product actually changes. you still have to notice your docs are late and fix them yourself.
helpdesk tools like zendesk and help scout are good at the other things, shared inbox, replying to customers. but the "docs" part of them is basically an afterthought. a static help center sitting next to the actual support tool, nobody's watching it.
my actual starting point was way narrower than that . i didnt plan out to build a support tool. the original idea was just turning merged github prs into docs updates automatically, so docs never go stale.
before building further on that i ran a proper audit on how much of it was even automatable, some of you saw those first numbers here, roughly 38% of customer-facing prs had enough in the diff alone to draft from. ran it again on double the data a few days later and the split held, but the debt itself got worse, not better, undocumented rate crept up, and the delay for the ones that do get docs versus the ones that never do just kept spreading apart, a fast lane and a graveyard, basically nothing in between. that's where the automatic docs drafting pipeline came from. draft gets generated off the pr diff same day, a human approves before anything publishes, and that's specifically aimed at closing the gap before a pr falls into the graveyard side of that split.
then i started making the widget better, more useful for customers to actually interact with. it already connected with zendesk, help scout, and intercom, so it could pull in real context from those. i added email and live chat on top of that. somewhere in doing that the whole thing turned into something else. DocsKoala is now a docs generating platform plus an ai widget that answers customers and cites the actual doc it pulled the answer from, and, if you want it to be, a customer support tool too, all packaged into one thing instead of three separate ones.
what it does today,
docs live on a real hosted help center, and they update themselves. every merged github PR gets classified automatically, if it's something a customer would notice, it drafts the doc update, visual updates included. nothing goes live without a human approving it first.
an ai widget answers customers straight from those docs, citing the source article every time.
connects with zendesk, help scout, and intercom, plus email, slack, linear and live chat and a mcp , now, so it can sit on top of what you're already using or run the whole thing itself.
one thing led to another, now it's a complete customer support pipeline for your busioness, a combination of "docs tool + helpdesk tool + the manual syncing between them" into a single product so you dont have to do anything anymore
you can try it for yourself at docskoala.com
What I found interesting is that the product didn't expand because you kept adding categories.
It expanded because every solved bottleneck exposed the next dependency. That creates a product that feels discovered rather than assembled.