Bundling vs. Unbundling: The Two-Cycle Theory That Explains All of Software

Tech industry veteran Jim Barksdale once argued that all software business models reduce to two moves: bundling and unbundling. History supports this — from Microsoft Office to Google Workspace, from cable TV to Netflix, and from Craigslist to its many vertical successors, the cycle has repeated consistently. AI, however, broke the pattern by arriving already fragmented, with developers typically stitching together eight or nine separate vendors — models, vector databases, orchestration layers, and more — just to ship a single application. This hidden 'unbundled tax' means engineering teams spend significant time on integration glue rather than on the core product they were hired to build. Based on historical precedent, a consolidation phase is likely inevitable, as the cost of managing seams between tools eventually drives demand for a unified bundle.