SaaS sells on year-one cost. The vendor walks in with a per-seat number, multiplies it by your headcount, and the procurement team writes the check. Custom buyers think differently. They look at the same five-year window and compare what they actually pay, what they actually own at the end, and what the switching cost looks like when the vendor changes the deal in year three.
The five-year TCO math is where the conversation gets honest. Year one almost always favors SaaS. Year five almost always does not. Below is what the curves actually look like for a 50-person firm running a typical operations workflow.
What SaaS Actually Costs Over 5 Years
SaaS pricing has six recurring layers. Most procurement decks model the first one and ignore the rest.
Layer 1: Base subscription. The list price the salesperson quotes. For a mid-market operations or compliance SaaS, this typically runs $50 to $250 per seat per month. For 50 seats at $150 average, that is $90,000 per year before any add-ons.
Layer 2: Seat add-ons. Year one you bought 50 seats. Year two you added 8. Year three the vendor introduced a "Pro" tier that locks the AI features behind a higher per-seat price. By year three you are paying 40% more per seat than you started with.
Layer 3: Integration tax. SaaS does not connect itself to QuickBooks, your CRM, your ERP, or your document store. You either hire a partner at $200 per hour or you accept manual reconciliation. Either way, plan on $25,000 to $60,000 in year one for integration work, and another $20,000 to $40,000 in year three when something breaks or the vendor deprecates an API.
Layer 4: Customization overruns. Every SaaS has a customization wall. The schema fits 80% of your business. The other 20% is a billable services engagement. Most firms underestimate this by half.
Layer 5: AI assistant add-on. The vendor launches an AI feature at $30 to $50 per seat per month on top of the base subscription. Either you skip it and watch competitors get the productivity boost, or you pay it.
Layer 6: The mid-contract uplift and the eventual migration. Year three the contract renews with a 15 to 25% price uplift. Year five you decide the platform is no longer the right fit, and the migration to the next vendor costs $50,000 to $150,000 in services plus six months of organizational drag.
Add it up over five years for a 50-seat deployment and the total lands somewhere between $850,000 and $1.4 million. The number SaaS vendors quote at the kickoff meeting is the tip of that.
What Custom Actually Costs Over 5 Years
Custom is structured differently. The shape of the curve is front-loaded, then flat, then declining as the platform matures. Here is what the five-year model looks like for a Heed build at a comparable firm.
Setup fee (one-time). A working pilot with one or two core workflows lands between $25,000 and $60,000 depending on complexity. This is the equivalent of the SaaS integration tax, but it includes the application itself.
Monthly platform and seat fee (predictable). Hosting on Cloudflare, Anthropic and OpenAI API usage, Cloudflare Zero Trust seats, monitoring, and ongoing maintenance. For 50 seats this typically runs $4,000 to $8,000 per month, or roughly $60,000 to $96,000 per year. Importantly, the per-seat number does not climb 20% per year because there is no vendor with a quarterly earnings call.
Add-on builds as needs evolve. When the firm wants a new module, dashboard, or workflow, we scope and build it. Typical add-ons run $5,000 to $25,000 each. Most clients add two or three per year in the first two years, then taper.
Decreasing engineering load as the platform matures. By year three, most clients are spending less on net-new development than they did in year one. The platform is doing what it needs to do. Maintenance is a small line item.
The Math at Year 5
Add the custom curve up and a 50-seat firm typically lands between $400,000 and $650,000 over five years, including setup, platform fees, and a healthy add-on budget. That is roughly half what the SaaS path costs. See the full breakdown on the operations platform page.
The crossover point is usually somewhere between month 18 and month 28. After that, every additional month favors the custom path more strongly. By year five, the gap is six figures.
And the comparison gets sharper when you factor in what you own at the end. With SaaS, you own nothing. The data is portable in theory, the workflows are not, and the next vendor will charge you to rebuild them. With custom, you own the application, the data model, the prompts, the connectors, and the deployment infrastructure. If you ever want to take it in-house, you can.
Where SaaS Still Wins
We are not in the business of pretending custom always beats SaaS. That would be dishonest. SaaS wins in three specific situations.
First, deeply standardized markets where the SaaS schema actually fits. Payroll for a small US-only company with W-2 employees? Buy Gusto. Project management for a 5-person agency that does standard creative work? Buy Asana. The schema overhead is zero, the integration tax is small, and the build cost would never pay back.
Second, when you genuinely do not know what you need yet. SaaS is a forcing function. It tells you how the industry tends to model the problem. For a firm that is still figuring out its operations, that is a useful constraint.
Third, when the workflow is going to change so rapidly that any custom build would be obsolete in 18 months. Rare, but it happens.
Where Custom Wins
Custom wins anywhere the off-the-shelf schema does not fit, or where AI workflows trained on the firm's own data are a competitive advantage. That covers more SMB and mid-market situations than the SaaS industry would like to admit.
California's largest hillside structural engineering firm, with 50+ employees, was 85% migrated to Salesforce when they realized the schema would never fit how they actually run projects. They walked away and we built them a custom platform for less than they had already spent on the migration. Read the full story in the structural engineering case study.
An Encino-based estate and family law firm serving high net worth families is in the middle of a custom employee dashboard build that integrates Lawcus, RingCentral, Microsoft 365, and multiple AI providers. There is no SaaS that does what they need at any price. The full picture is in the law firm dashboard case study.
The Bottom Line
Year-one TCO is a marketing number. Five-year TCO is a procurement number. If you are running the right model, custom AI builds win on cost, on ownership, and on competitive differentiation more often than the SaaS industry would have you believe. The question is not whether custom is cheaper. The question is whether you have a procurement team disciplined enough to run the five-year math.