Your CFO sees the SaaS bill: $4,500 per month. Thirty-two tools. That's what gets flagged in budget reviews. But that number isn't your cost—it's your floor.
Most companies we talk to underestimate their software expenses by 300-400%. They're only counting subscription fees. They're missing the rest of the iceberg that actually drowns the boat.
The Math of SaaS Sprawl
A mid-market company ($50M revenue) typically runs 32-47 software tools. Our analysis of clients across manufacturing, professional services, and B2B SaaS found this breakdown:
Direct costs (what you see):
- SaaS subscriptions: $4,500/month ($54K/year)
- Integration services/platforms: $1,200/month
- Custom connectors and middleware: $800/month
Operational costs (what you don't):
- Admin time managing accounts, onboarding, access controls: 180 hours/year ($18K for mid-level staff)
- Spreadsheet workarounds for system gaps: 200 hours/year ($20K)
- Data reconciliation between systems: 160 hours/year ($16K)
- Learning curves when tools change: 120 hours/year ($12K)
Systemic costs (what kills you):
- Revenue lost to workflow delays (quote-to-cash taking 3 weeks instead of 5 days): 2-3% of pipeline
- Compliance risk from duplicated data and version control: $25K-$100K annually in audit costs
- Team friction when tools don't talk: hidden productivity loss of 8-12% for knowledge workers
Real number: $180K-$280K annually for that "affordable" $54K subscription stack.
One client found they were spending $127K per year on tools they used less than 20% of the time. Another discovered their integration platform alone cost more than the three tools it was connecting.
Why You Keep Buying More Tools
Every tool solves a real problem. Your sales team needs a CRM. Your operations team needs inventory management. Your finance team needs a better way to track expenses.
But here's what happens: you solve the problem for that department. You don't solve it for the company. The new tool creates a data silo. Your finance system can't talk to your CRM. Your project management tool doesn't sync with your time tracking. Now you need a middleware solution.
Then someone finds a "dashboard tool" that might tie it all together. Except it needs manual data refreshes three times a day.
You've now built a system that requires constant human intervention to function—the opposite of automation.
The fundamental issue: off-the-shelf software is designed for broad, generic use cases. It assumes you work a certain way. When you don't—and you almost never do—you have three choices:
- Change how you work (forcing your team into inefficient workflows)
- Build workarounds (spreadsheets, manual processes, duplicate data entry)
- Customize the tool (which often breaks during upgrades and creates technical debt)
Most companies do all three simultaneously.
The Integration Trap
Integration costs spiral silently. A typical integration project:
- Discovery and requirements: 40 hours ($4,000)
- Development and testing: 80-120 hours ($8,000-$12,000)
- Deployment and monitoring: 20 hours ($2,000)
- Ongoing maintenance: 15 hours/month ($1,800/month)
One integration might be $15K-$20K. You have 12 integrations. Do the math.
And that's for stable integrations. Every time one tool updates its API, your integration might break. Every new tool you add creates multiple new integration points. You're not building a system; you're building a house of cards that requires someone to check it daily.
When Custom Software Makes Financial Sense
Here's the inflection point: when the cost of customization is lower than the ongoing cost of the system not fitting.
If your current SaaS stack is costing you $180K annually in hidden operational costs, and custom software would cost $120K to build and $15K/year to maintain, the payback period is less than a year.
We see this consistently in:
-
Fast-growing companies (200%-500% growth): Vendor software built for 50-person companies breaks at 200 people. You either rebuild, or you customize—but customization has a ceiling too.
-
Industries with unique workflows: Manufacturing with custom processes, professional services with specific engagement models, or logistics with regional requirements. You're not "different." The vendor's software is just built for different different.
-
Operations with tight integration requirements: When data needs to move between systems with <1 hour latency and without human intervention, you don't have a SaaS problem. You have a custom integration problem, which grows until you build custom software instead.
-
Companies with proprietary processes: If your workflow is actually better than your competitors', and that better workflow is locked inside your team's heads and spreadsheets, software that doesn't fit that workflow is a constraint on growth.
Learn More About This Decision
Explore the full build vs. buy framework to understand when each option makes sense strategically, and understand the real costs of custom software if you're considering building.
The Real Decision Framework
Don't ask "build or buy?" Ask these questions:
Can you change your business process to fit the software? If yes, and it doesn't harm your competitive position, SaaS is the right call. Lower operational risk, faster time to value.
How many people does each tool affect? If it's <5 people, SaaS friction is manageable. If it's >50, integration and workflow friction compounds.
What's your integration debt? If you're building more than 3 custom integrations per year, you're maintaining a custom platform anyway.
What's the total cost of ownership at scale? Model next 3 years: subscription costs + integration costs + operational overhead. Compare to custom build + 3-year maintenance. The gap often surprises you.
Is your process actually temporary? Many companies think "this process is how we've always done it." Some processes are genuinely temporary—waiting for the market to stabilize, or a specific client contract. SaaS is right for temporary. If the process is structural to your business, you need to fit software to it, not fit your business to software.
The Path Forward
If you're drowning in SaaS sprawl, you have options:
Start by actually measuring what you're paying. Not just subscriptions—the whole iceberg. Hour by hour, add every operational cost. Most companies find they're spending 3-4x what they thought.
Then audit usage. One manufacturer found they were paying for tools accessed by fewer than 5 people total. Dead weight. Another company realized 85% of their CRM's value came from 3 features—everything else was theater.
Finally, decide: is the pain of consolidation worth the savings? Is the pain of custom software better than the pain of your current workarounds?
The answer changes as you grow. At $10M revenue, SaaS makes sense. At $100M, the math shifts. Custom starts looking attractive. At $1B, your proprietary software is your competitive advantage.
Right now, for most mid-market companies, you're overpaying for software that doesn't fit. The question isn't whether that's true—it is. The question is whether you're going to do anything about it.
Let's Analyze Your Actual Costs
Most companies discover they're spending 3-4x what they thought when they actually measure. We can help you audit your software spend and understand your real options. Book a discovery call to get clarity on whether consolidation, custom software, or a different approach makes sense for your situation.
