When internal tools beat SaaS — and when they don't
Every operator hits a ceiling where generic SaaS becomes a constraint. Knowing when to build your own — and when to stay on rails — is the decision that separates operators from tool-shoppers.
The default move for a growing business is to buy more SaaS. The problem isn't that SaaS is bad — it's that at some point your workflow starts fighting the tool's opinions.
We see this most often with CRMs. A roofing GC with 30 people tries to run operations in HubSpot. HubSpot thinks in deals. Roofing thinks in jobs. The model doesn't fit, so the team ends up with custom fields, tag forests, and a spreadsheet on the side that the real work actually happens in.
The tell: you're paying for the software, but the software isn't paying for itself in clarity. Your team is spending more time configuring the tool than doing work in it.
The decision framework we use with clients has three questions.
1. Is your workflow standard, or does it have idiosyncratic operator logic? Standard = buy. Idiosyncratic = consider building. A standard sales team running a standard funnel should be on HubSpot or Salesforce. A 30-person roofing GC running dual-market dispatch with a specific margin model is idiosyncratic — and worth building for.
2. Is the tool the constraint, or is the tool the enabler? If you remove the tool tomorrow and the business runs better, it's a constraint. Cut it and build. If the business grinds to a halt without it, it's an enabler. Keep it.
3. What's the cost of coupling? If you build your own, you own the maintenance. Every integration, every edge case, every bug is yours. That's not bad — but it's a cost. You need to be confident the custom build is worth that cost over the lifetime of the business.
Our rule of thumb: if a standard SaaS tool is costing you more than one full-time headcount per year in configuration, workarounds, and workflow friction — it's cheaper to build your own.
What gets built most often: CRMs, ops dashboards, internal admin tools, job/project trackers, and approvals flows. What almost never gets built: email, calendar, payments infrastructure, and anything requiring compliance certifications you don't have.