"$29 a user per month" sounds cheap. It is genuinely cheap for the first ten users. It is rarely cheap for an organization at scale, and almost never the right baseline for an honest build-versus-buy comparison.
Hidden costs we keep watching companies absorb
Per-seat sprawl. A $29 seat × 80 employees × 12 months is already over $27,000 per year for one tool. Multiply by the five SaaS tools your operations team is using and the math is closer to a senior engineer's annual cost — which, applied differently, could have replaced the lot of them. And per-seat pricing has a property owners consistently underestimate: it scales with headcount, not with value. Hire twenty people next year and your software bill rises twenty-five percent even though the tools did not get better. Custom software has the opposite curve — the cost is front-loaded and the marginal user is essentially free.
Integration tax. SaaS platforms only talk to each other through paid integration layers — Zapier, Make, native marketplace connectors — and those layers usually charge per record synced or per "task" executed. That pricing punishes exactly the businesses doing well: the more orders, tickets, and invoices you process, the more you pay just to move your own data between tools you already license. We have seen integration spend exceed the underlying SaaS licenses on more than one project. Worse than the cost is the fragility: every zap and connector is a small, unmonitored dependency, and when one silently fails, the data quietly stops flowing until someone notices the reports look wrong. There are better patterns for this — connecting your CRM, billing, and fulfillment through a thin integration layer you own is often the highest-ROI project we do.
Data lock-in. The "we own your data" promise tends to mean a CSV export. Operational history — the audit trail, the relational structure, the attachments, the metadata that makes a record meaningful — usually does not come along. Test this before you need it: ask any vendor for a full export and see what actually arrives. Switching costs compound every year you stay, until they quietly become switching impossibilities. There is also a newer wrinkle: your operational history is precisely the data that future AI capabilities will feed on, and if it lives in someone else's database, you will be paying API fees or per-record charges to access your own past.
Workflow drift. Each SaaS tool comes with opinions about how the work should be done. Over time your team's actual workflow drifts to match the tool, not the other way around — a three-step approval becomes five steps because that is how the vendor modeled it, and two years in, nobody remembers which steps are your business and which are the tool's defaults. That drift has a real cost in operating efficiency that never shows up on an invoice. It is also strategically corrosive: if your workflow is a competitive advantage, running it inside the same tool your competitors subscribe to sands the advantage down to the industry average.
Where SaaS is still the right answer
Honesty cuts both ways. For commodity functions — payroll, email, accounting, document storage — SaaS is correct at almost any scale, because your way of running payroll is not a competitive advantage and the vendor's compliance burden is one you genuinely want to outsource. The same goes for any team small enough that the seat math stays trivial, or any workflow you run the same way everyone else in your industry does. The build conversation is only worth having for the systems where your process is actually yours.
When custom flips the math
Custom software stops looking expensive in three specific scenarios: when your workflow is genuinely a competitive differentiator, when your team size pushes total SaaS spend past $50,000–$100,000 a year for a single workflow area, and when you need data and AI integrations that vendors charge you per record to enable. One of these alone is usually not enough. Two or three together mean the math has probably already flipped, and every renewal is quietly widening the gap. We broke down the recurring patterns in when custom software pays for itself, and the common thread is always the same: the payback case is strongest where the off-the-shelf tool is being bent hardest.
How to run the five-year number
The honest comparison is rarely "build vs the sticker price." It is "build vs the all-in cost of running this SaaS stack for five years." The five-year side has four lines, and only the first one is on the invoice: licenses at projected headcount with the vendor's historical price increases applied; integration spend, including the internal hours spent babysitting connectors; the premium-tier upgrades you will be pushed into for API access, SSO, and reporting; and an exit-cost estimate for the day you leave. On the build side, be equally honest: a custom web application has a real upfront cost and a real maintenance line, typically a modest annual percentage of the build, and anyone who quotes you a build with zero maintenance is hiding the number rather than eliminating it.
Run both columns and the decision usually stops being ideological. Some workflows stay on SaaS forever, and should. But for the one or two systems at the core of how your business actually competes, the five-year number surprises a lot of teams — and it is exactly the analysis we walk through in a free 30-minute discovery call, with your headcount and your renewal invoices instead of hypotheticals. The worst time to run this math is at renewal, under deadline. The best time is now, while walking away is still cheap.