A founder we spoke with last quarter had a spreadsheet tracking every SaaS tool her company used. The total was $287,000 per year across 41 products. She had bought almost every one of them because it was "cheaper than building it ourselves." On paper, that math had made sense each time. In aggregate, it no longer did.
We see this pattern often. Off-the-shelf software wins the first comparison — lower upfront cost, faster rollout, no engineering team needed. Then, two or three years in, the real costs show up: per-seat pricing that scales with headcount, integration work to make the tools talk to each other, workarounds for the 10% of features that don't fit your business, and the slow erosion of any competitive advantage that once came from doing things your own way.
This post is about what those hidden costs actually look like, when they matter, and how to tell whether an off-the-shelf tool is still the right call for a particular problem.
The four categories of hidden cost
When businesses evaluate a SaaS purchase, they usually compare the annual license to the cost of building an equivalent tool. That comparison misses four categories of cost that only surface later.
1. Per-seat pricing that compounds with growth
Most B2B SaaS pricing is per-seat or usage-based. That's great when you're a team of 8. It becomes painful when you're a team of 80, and painful enough to freeze hiring decisions when you're a team of 400.
A mid-market SaaS tool at $45/user/month costs $4,320/year for a team of 8. At 400 users, that same tool is $216,000/year. Nothing about the software got more valuable — you just got bigger. We've watched companies hit growth milestones and then realize their software costs grew faster than their revenue.
2. The integration tax
No SaaS tool lives alone. Your CRM talks to your billing system, which talks to your data warehouse, which feeds your BI dashboards. Every time you add a tool, you're not just paying for the tool — you're paying for the glue.
That glue is real work. In our experience, a typical mid-sized company spends 15–30% of their engineering bandwidth on integration work across SaaS tools: Zapier workflows that break when a vendor changes their API, custom iPaaS flows, webhook handlers that nobody remembers writing. The more tools you stack, the more of your team becomes an integration team by accident.
3. Workaround cost
Off-the-shelf software encodes someone else's assumptions about how your business works. For 80% of your workflow, that's fine. For the other 20%, your team builds workarounds.
Workarounds look like:
- Spreadsheets that live alongside the "real" system because the real system can't do the thing you need
- Manual double-entry between tools that should talk but don't
- Approval processes that exist only because the tool doesn't support your actual approval model
- Training docs that say "ignore the button labeled X, click the one in the sidebar instead"
None of these show up in the vendor's pricing page. All of them consume hours of your team's time every single week.
4. The commoditization cost
This is the cost nobody talks about. When you and your competitors use the same tools, you operate with the same constraints, the same reports, the same workflows. Your operational edge — the way you handle customers, price deals, manage inventory — is limited to what the tool's configuration lets you do.
For undifferentiated functions (payroll, email, accounting basics), commoditization is fine. For the things that actually make your business yours, it's a quiet tax on your moat.
A simple framework for deciding
We walk clients through a quick four-question test before they commit to either building or buying. It's not definitive, but it catches the worst decisions before they're locked in.
Question 1: Is this function core to how we make money?
Your point-of-sale system, your pricing engine, your matching algorithm — those probably are. Your payroll processing probably isn't. Core functions deserve more scrutiny because they shape your competitive position.
Question 2: How standardized is our version of this workflow?
If 95% of companies do this the same way you do, off-the-shelf wins. If your version has meaningful differences that matter to customers or operations, you'll fight the tool forever.
Question 3: What's the 5-year total cost at projected growth?
Don't compare year one. Compare year five. Per-seat pricing at 400 users is not the same decision as per-seat pricing at 40.
Question 4: What happens if the vendor changes direction?
SaaS vendors get acquired, pivot, sunset features, or raise prices 3x at renewal. How exposed are you to that risk? For a mission-critical system, vendor risk is a real line item.
When off-the-shelf clearly wins
We're not anti-SaaS. We use plenty of it ourselves. Off-the-shelf is usually the right call when:
- The function is commodity (email, calendaring, file storage, video calls)
- You're in early-stage validation and don't yet know what you actually need
- The tool has a mature ecosystem and strong API (integration tax stays low)
- Your version of the workflow matches the industry norm
- You need it running this week, not next quarter
For everything in this bucket, building custom is almost always the wrong call. You'd spend six months reinventing something that already works.
When custom starts to win
Custom software starts winning when:
- You're running the same workflow across enough seats that per-seat SaaS fees exceed the amortized cost of a build
- You've accumulated four or five workarounds around a single tool
- Your competitive advantage depends on doing something the standard tool can't do
- You're gluing 3+ SaaS tools together and the glue is becoming a second full-time system
- Vendor risk on a critical function keeps you up at night
In our experience, a well-scoped custom internal tool typically lands in the $40–80K range for an MVP and $120–250K for something enterprise-grade. That's a lot if you're replacing a $5K/year SaaS tool. It's a steal if you're replacing $180K/year in licenses plus two full-time integration engineers.
The hybrid approach we usually recommend
Most of the companies we work with don't land purely on "build everything" or "buy everything." They end up with a hybrid: off-the-shelf for commodity functions, custom for differentiated ones, and a thoughtful integration layer in between.
The integration layer is the piece most companies underinvest in. A well-designed integration layer — sometimes a lightweight internal API, sometimes a proper event bus — means you can swap SaaS tools without rewriting half your business. It's the single highest-leverage investment most growing companies aren't making.
If you're starting to feel the squeeze of per-seat fees, integration debt, or workarounds piling up around your tools, it's worth doing an honest audit. We help clients with exactly this kind of evaluation — see our software development services or get in touch if you want a second opinion before your next renewal cycle.