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 by @51846940, 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” racked up a 97% bookmark-to-like ratio, meaning nearly everyone who saw it saved it for later. 2 Source 2 X thread, June 2026. “Open source just killed $100K worth of software subscriptions.” 35 likes, 34 bookmarks, 1,318 impressions. 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 enterprises for their 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 2026 Build vs. Buy Report, 817 respondents. 35% of enterprises replaced at least one SaaS tool. 78% plan to build more in 2026.
So the $300K figure: is it plausible? Yes — replacing a third of a 300-person company’s software spend lines up almost exactly with Retool’s 35% replacement rate. 8 Source 8 Gartner pegs mid-market SaaS spend at roughly $2,500-$4,000 per employee per year. For a 300-person company, that’s $750K-$1.2M in annual software costs; $300K is roughly a third of the midpoint. The number checks out.
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?
The viral posts share a common trait: they show the license line item. They never show the implementation invoice.
Lynton has migrated companies this size off legacy SaaS platforms. We published the full cost model. The honest picture looks like this: implementation labor for a full-suite replacement runs $100K-$150K upfront. That’s design, data migration, integration work, and the kind of edge-case handling that doesn’t surface during a weekend prototype. 5 Source 5 Lynton TCO analysis from “The Real Cost of HubSpot.” 5-year comparison: modern stack ~$195K vs. legacy platform ~$1,025K.
Then 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 built with AI coding tools. 4 Source 4 SaaStr, 2026. 30-60 minutes daily maintenance per production app. SaaStr runs 12+ internally-built apps used 800K+ times. Replace five SaaS tools and you’re suddenly looking at 25 hours per week in upkeep. 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: roughly $195K on a modern stack versus about $1,025K on a legacy platform. 6 Source 6 See Lynton’s detailed TCO breakdown in “The Real Cost of HubSpot” for the full five-year cost model. 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 person posting the savings screenshot at Month 3 hasn’t lived through the Month 6 edge case.
The categories that bleed the most
Not all SaaS is equally ripe for replacement. The Retool data is specific about where the money is going: companies are replacing the tools where they’ve been most obviously overpaying.
Three categories lead the teardown, and they’re all places where a commodity tool was doing commodity work: 7 Source 7 Retool 2026 Build vs. Buy Report. Share of enterprises replacing each category: workflow automation 35%, internal admin dashboards 33%, BI dashboards 29%.
- Workflow automation is the most-replaced category. A $50/month tool often did work a custom-built alternative now handles in a fraction of the code.
- Internal admin dashboards are close behind — the kind of CRUD interface that AI coding tools assemble in an afternoon.
- BI dashboards round out the top three, where the SaaS premium was always hard to justify against open-source charting.
The categories that aren’t moving tell you something too. Core ERP and accounting systems sit essentially untouched. 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, not a weekend project. 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 30-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, including implementation labor, maintenance hours, and the talent you’ll need to keep it running. Start with one system, prove the model, then expand. Budget for the month-six surprise. The prototype never anticipates the edge case that costs your team a Saturday.
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.
The research is free. So is the diagnosis — 60 seconds →