Siloed Investments: How Zero‑Sum Thinking Let a SaaS Company Lose Revenue and Duplicate Costs
A real-world example of Zero sum bias in action
Context
A mid‑sized SaaS company (≈ $25M ARR) with regional account teams and decentralized budgets was evaluating an investment in a single, centralized customer success platform expected to improve renewals and onboarding speed. Leadership framed the decision as a choice between teams — if one region got a central tool, other regions would 'lose' budget and influence.
Situation
The product and operations leads proposed a $250k integration and training project to unify CRM, onboarding playbooks, and usage analytics across all account teams. Regional managers pushed back, insisting each team should keep its own tools and budget because shared investment would reduce their local headcount or control.
The bias in action
Decision‑makers treated the budget as a fixed pie: a gain for central operations was portrayed as a loss for regional teams. Instead of piloting the centralized platform, leadership approved small, independent tool purchases for each region and cut the central project. Managers hoarded data and resisted cross‑team processes, reinforcing the belief that resources were zero‑sum. The company overlooked that a unified platform could create efficiencies and revenue growth that would expand the pie for everyone.
Outcome
Over the next nine months the company experienced higher churn and slower new‑customer conversion than forecast. Each region bought similar point solutions (duplicate spend), integration efforts stalled, and customer success metrics fragmented — making it harder to scale best practices company‑wide.