A 300-person company says they cut $300K in SaaS costs. Let’s check the math.
In June 2026, someone running a 300-person company posted that they were “actively replacing SaaS solutions” and had already saved $300K in recurring license costs. 1 Source 1 X post, June 6, 2026. “As a 300 person company, we are actively replacing SAAS solutions and saving already 300k on recurring license costs.” No vendor names. No product demos. Just a dollar figure and an employee count.
The post didn’t go viral. It didn’t need to. A week later, a thread titled “Open source just killed $100K worth of software subscriptions” picked up almost as many bookmarks as likes, 34 against 35. 2 Source 2 X thread, June 2026. “Open source just killed $100K worth of software subscriptions.” 35 likes, 34 bookmarks, 1,318 impressions. That’s the engagement profile of homework, not entertainment. Another thread listing GitHub repos that replace paid developer tools pulled 84 bookmarks against 53 likes. People aren’t just reading about SaaS replacement. They’re filing it away as a to-do list.
These aren’t one-offs. Retool surveyed 817 of its customers and builders, startups through the Fortune 500, for its 2026 Build vs. Buy Report: 35% have already replaced at least one SaaS tool with custom-built software, and 78% plan to build more this year. 3 Source 3 Retool, “The Build vs. Buy Shift,” February 2026. 817 respondents. Worth noting the sample: Retool sells the build path, so treat 35% as the optimistic end of the range.
So the $300K figure: is it plausible? The average company now spends $4,830 per employee per year on SaaS, up 21.9% in a single year (Threadgold Consulting, 2025). 4 Source 4 Threadgold Consulting, “SaaS Spend Per Employee Benchmarks,” 2025. Average $4,830 per employee per year, up 21.9% year-over-year. For a 300-person company that’s roughly $1.4M in annual software spend, and even an operator running lean at half the benchmark carries $700K and change. Cutting $300K means replacing 20-40% of the portfolio. Aggressive, but nothing about it strains the published data.
The question isn’t whether it’s real. It’s what they left out of the post.
What are the hidden costs of replacing SaaS tools?
Implementation labor for a full-suite replacement runs $100K-$150K upfront, every replaced app carries a standing maintenance load once it’s live, and payback typically takes 12-18 months. That’s the half of the ledger the viral posts skip. The license line item gets the screenshot. The implementation invoice never does.
Then there’s the carrying cost. SaaStr puts a number on this that rarely shows up in the savings threads: 30-60 minutes of daily maintenance per production app at scale, though the load consolidates when one team runs the whole portfolio. SaaStr maintains its own 12 internally-built apps in about an hour a day. 5 Source 5 SaaStr, 2026. “Scaled production (thousands+ of users): 30-60 minutes daily minimum.” SaaStr runs 12+ internally-built apps, used 800K+ times, in about an hour of maintenance a day. Replace five SaaS tools and you’re looking at anywhere from five to 25 hours a week in upkeep, depending on how much of that work consolidates. At the top end, that’s half a full-time employee doing nothing but keeping your replacements running.
Year 1 of a self-built stack often costs more than Year 1 of SaaS. The savings compound from Year 2 onwards. Over five years the math is decisive, with the scope stated plainly: for a full-suite escape, counting the build, platform fees, agency retainers, and internal admin time, roughly $195K on a modern stack versus about $1,025K on the legacy platform. 6 Source 6 See Lynton’s detailed TCO breakdown in “The Real Cost of HubSpot” for the full five-year, full-suite cost model: build, platform fees, agency retainers, and internal admin time. That’s $830K saved. But the person posting the savings screenshot at Month 3 hasn’t lived through the Month 6 edge case that breaks their workflow automation at 2 AM.
The categories that bleed the most
Not all SaaS is equally ripe for replacement. The Retool data is specific about where the pressure is concentrated: companies are targeting the tools where they’ve been most obviously overpaying.
Workflow automation tops the replacement-pressure list, named by 35% of teams. Internal admin dashboards follow at 33%, with BI tools close behind at 29%. These are categories where a $50/month tool often did work that a custom-built alternative handles in a fraction of the code.
The categories that aren’t moving tell you something too. Core ERP and accounting systems don’t make the list. Nobody is claiming they vibe-coded a replacement for their general ledger. The SaaS replacement wave has real boundaries, and recognizing them is the difference between a strategic migration and a reckless one.
What mid-market companies are actually doing is a selective teardown. Rip out the commodity layer (workflow tools, admin dashboards, basic CRM) where SaaS premiums were always hard to justify. Keep the core systems where switching costs are genuinely high and failure modes are genuinely expensive.
The tweet and the vendor are both selling you something
There’s a gap in this conversation that nobody seems interested in filling. On one side, you have people posting screenshots of their savings, with every incentive to make the numbers look dramatic. On the other side, you have the SaaS vendors running retention campaigns, with every incentive to make leaving look catastrophic.
Both are selling.
The 35% of enterprises replacing SaaS tools aren’t doing it because of a tweet. They ran the numbers and allocated real budget for the build, including the people to maintain what they shipped. The companies that treated SaaS replacement as a cost-cutting exercise without accounting for ongoing operations are the ones who end up quietly resubscribing 18 months later.
This is a capital allocation decision. The savings survive the scrutiny. The timeline doesn’t survive the hype.
Where this leaves a mid-market CFO
The SaaSpocalypse narrative is playing out in the data, not just the headlines. But what a CFO at a 300-person company should actually do with this information looks different than what the social posts suggest.
The economics work over a 3-5 year window. Your savings are real, probably in the range of 20-40% of your current SaaS portfolio, concentrated in the commodity categories where you’ve been overpaying for years. The payback period is 12-18 months, not 12 days.
The move that works: pick your worst value-to-cost tool and build the replacement business case with full-cost accounting, implementation labor and the standing upkeep priced in. Start with one system and prove the model before expanding. Budget for the month-six surprise. The prototype never anticipates the edge case that costs your team a Saturday.
And run the upside math too, because the $300K isn’t the prize. It’s working capital. Redirected license spend funds the pipeline experiments your competitor can’t run, and the replacement itself sits on your books as an asset you own instead of a subscription that expires the day you stop paying.
The people posting $300K savings did the work. They just posted the exciting part and skipped the invoice. If you want to run the same math honestly, start with what your current stack is really costing you.