3
2 Comments

Ran the numbers before deciding how much to automate. 38% of doc work turned out to be low hanging fruit

Im working on DocsKoala. it generates docs from merged github prs. before building out more automation i wanted to actually know how much of the problem was automatable versus how much genuinely needs a human, so i ran a real audit instead of guessing.

pulled 14,891 merged prs across 220 public repos. classified each as customer facing feature, internal, bug fix, or unclear. for the 3,623 customer facing ones, checked whether the pr diff and title alone gave enough to draft a doc, and separately whether it ever got documented at all.

1,386 features, 38.3%, were automatable based on the diff alone, no extra context needed from the dev. 541 features, 14.9%, never got documented period, automatable or not.

cost estimate if a human wrote docs for just the automatable chunk manually, 20-30 min each, comes to 462-693 hours and 34.6k-52k dollars across these 220 repos.

this number is basically why DocsKoala focuses where it does. it drafts automatically for the 38% that's clear cut, and flags the rest for a human instead of pretending it can guess context that isn't in the diff. figured people building similar tools or just curious about the "how automatable is documentation actually" question would find the raw split useful.

on July 9, 2026
  1. 1

    Thats nice!!! A 38% is absolutely wild

  2. 1

    I think the most valuable part of this isn't the 38%.

    It's that you identified the boundary where automation stops being trustworthy. A lot of AI products try to maximize automation. Defining where a human should take over often creates more confidence than squeezing out a few extra percentage points.

Trending on Indie Hackers
5 days post-launch: Top 50 on Product Hunt, zero signups, and why I think that's actually fine User Avatar 118 comments The feature you're most sure about is the one you should question first User Avatar 118 comments I let 3 LLMs argue on the famous AI "Car wash: Walk or Drive" problem to prove a point. User Avatar 50 comments Built a local-first privacy extension. Looking for feedback. User Avatar 38 comments I built an AI fitness coach, then realized AI was only solving half my funnel User Avatar 36 comments I spent months chasing clients who already had a webmaster. So I built something that only finds the ones who don't. User Avatar 34 comments