AI didn’t kill boilerplates. It moved the value to the last 10% — and the boilerplate maintainer’s 40-interview audit shows exactly where.

On r/SaaS the maintainer of an open-source SaaS boilerplate (u/hottown) posted a counter-intuitive result. The boilerplate just crossed 14k GitHub stars — an unusual milestone for a project whose category is supposed to be killed by AI-generated code. So the maintainer ran 40 user interviews to find out who was actually using it and why. The findings name the structure that the dominant narrative misses: “half the people I talked to had never deployed a full-stack app before. They were a mixed bag of career devs, PMs, woodworkers, devOps engineers, audio engineers. Even though AI got them 90%, the last 10% was killer — stripe webhooks, auth edge cases, background jobs.”

That 90/10 split is the entire insight. The conventional wisdom said AI would commoditize software construction. What it actually did was commoditize the first 90% — the file scaffolds, the CRUD endpoints, the form components, the routine business logic. That 90% used to be where boilerplates earned their value. Now AI matches them in minutes. But the last 10% — the production-grade infrastructure that decides whether an app survives a single real user — turns out to be exactly the part AI handles worst. Auth edge cases require knowing the threat model. Stripe webhooks require knowing the failure modes and idempotency requirements. Background jobs require knowing retry semantics and dead-letter queues. None of that decomposes well into prompts because none of that is a fresh-write problem; it’s a invariant-preservation problem, and AI is built for fresh writes.

Four commenters in the thread confirmed the pattern from completely different angles. u/Beautiful-Set-9065: “AI lowers the start building barrier, but production-grade structure is still hard. Messy 90% prototypes need to turn into something shippable and maintainable.” u/Ok_Train3151 (in a 919-character comment) said it from observing non-dev friends: “AI got them a decent CRUD app in a weekend, but the moment they needed auth flows, webhooks, retries, idempotency, logging — everything fell apart.” u/Enough_Big4191: “AI gets people to something that runs, but not something that holds up. That last 10% is where systems break — auth, payments, async jobs — and that’s exactly what boilerplates encode.” And u/VisualPerfect1165 pulled out the second-order economics: “The more new builders AI unlocks, the more valuable proven foundations become.” That last line is the missing piece — AI doesn’t just preserve boilerplate value, it amplifies it, because the population of people who can vibe-code something to 90% is now 10x larger, but the population that can solve the last-10% problem stayed roughly constant.

For an indie maker positioning a product, the strategic implication is concrete. If your product solves a first-90% problem (UI components, CRUD admin, basic form flows), you’re competing with what AI generates for free and a dozen vibe-coded competitors who will undercut you on price. If your product solves a last-10% problem (auth hardening, webhook reliability, observability for non-experts, payment edge cases, multi-tenant complexity), you’re in the part of the market that’s growing both in demand (more 90%-finished apps need the last 10%) and in pricing power (fewer competitors can credibly do it). The boilerplate’s 14k stars are not a vote against AI; they’re a vote for the part of the work that AI can’t trivially absorb. The clearest move for an indie is to find your own last-10% — the part of your domain where AI gets builders into trouble — and become the person who gets them out.