The Question Everyone Asks Wrong
"Should we build or buy?"
It is the most common question operations leaders ask when they hit the limits of their current systems. And it is the wrong question, because it assumes there are two options. There are actually four. And choosing the wrong one costs more than most executives realize, not in dollars alone, but in time, morale, and competitive position.
After advising on 30+ build-vs-buy decisions across industries from financial services to luxury retail to government, we have found that the framing itself is what leads companies astray. The right question is not "build or buy." The right question is: "Where does our operational advantage come from, and does this decision protect or erode it?"
Most organizations only consider the first two. The companies that make the best technology decisions consider all four.
The Hidden Cost of "Buy"
SaaS products are designed for the median customer. They solve the 70-80% of workflows that are common across an industry. The remaining 20-30%, the part that is unique to your organization, is where your competitive advantage lives. And it is exactly the part that off-the-shelf software cannot touch.
This creates what we call the Adaptation Gap: the distance between what the software does and what your operation actually needs.
The 25% gap is where your team builds workarounds, and where your Workaround Tax accumulates.
The Adaptation Gap matters because the uncovered 25% is not the unimportant 25%. It is usually the most important 25%, the edge cases, the exceptions, the nuances that separate competent operations from exceptional ones. It is the part that, if handled correctly, becomes a competitive moat.
When a financial services firm buys a standard compliance workflow tool, it covers the routine filings and standard checks. But their actual competitive advantage might be in how they handle complex multi-jurisdictional cases, which the tool cannot model. So they build workarounds. And those workarounds become the most fragile, most critical part of their operation.
The Hidden Cost of "Build"
If buying creates an Adaptation Gap, building creates a different risk: the Maintenance Trap.
Custom software is not a one-time cost. It is a commitment. It requires ongoing maintenance, updates, security patches, and evolution as your business changes. The build cost is typically 30-40% of the total five-year cost of ownership. The rest is maintenance.
Illustrative 5-year TCO for a mid-market operations system (100-300 employees). SaaS assumes $4K/mo license + $180K workaround labor. In-house assumes 2 FTE developers. Compose assumes SaaS base + custom integration layer with managed handoff.
This is where most in-house builds fail. Not because the initial system was bad, but because the organization did not plan for the ongoing cost of maintaining it. The developer who built it leaves. The documentation was never written. Two years later, nobody understands the codebase, and the "custom system" has become its own form of technical debt.
The Decision Framework
We use a five-factor framework when advising organizations on build-vs-buy decisions. Each factor is scored 1-5, and the total determines the recommended path.
How different is your process from industry standard? If your workflow is 90% standard, buy. If the critical 30% is unique to you, build or compose.
Does this process directly create competitive advantage? Payroll processing rarely differentiates a company. Client onboarding often does. Build where it matters. Buy where it does not.
How fast does this process evolve? If your requirements shift quarterly, a rigid SaaS product will fall behind. If they are stable, the predictability of a subscription is an asset.
What data flows through this system? In regulated industries (healthcare, legal, financial services), data residency, audit trails, and access control requirements often eliminate SaaS options entirely. If your compliance team cannot approve a third-party vendor, the "buy" option does not exist.
Do you have the team to maintain what you build? If not, you have three options: hire (expensive, slow), partner with a firm that builds and hands off (our model), or buy and accept the Adaptation Gap.
The Scoring Guide
Your workflows are standard, the data is not sensitive, and this process is not a differentiator. Buy the best SaaS product in the category and move on. Spend your energy elsewhere.
The foundation is standard but the critical layer is unique. Buy the base, build the differentiated parts. This is where most mid-market operations teams should land.
Your workflows are highly unique, competitively significant, involve sensitive data, and change frequently. No off-the-shelf product will work. Build it right, or it will be built with workarounds anyway.
When "Wait" Is the Right Answer
There is a fourth option that operations leaders almost never consider: doing nothing, deliberately.
The AI landscape is evolving so rapidly that a system built today may be obsolete in 18 months, not because it stops working, but because dramatically better approaches become available. We have seen companies spend $500K on rule-based automation in 2023 that could now be replaced with an AI system at a fraction of the cost and ten times the capability.
"Wait" does not mean "do nothing forever." It means:
- Document the current process thoroughly so you can build faster when you do move
- Run a pilot on the highest-value workflow to test assumptions
- Set a trigger - a specific condition (cost threshold, error rate, headcount) that forces the decision
- Monitor the market quarterly for new tools that close the Adaptation Gap
The cost of waiting is the continued Workaround Tax. The cost of choosing wrong is the Workaround Tax plus the switching cost. In some cases, patience is the highest-ROI decision.
A Decision in Practice
An automotive company we worked with was evaluating options for their vehicle configuration and inventory management system. They had been using a combination of Salesforce, three spreadsheets, and a custom Access database built by someone who left the company two years prior.
Running the framework:
Score of 16: Compose. High uniqueness and competitive significance pushed toward build. Low internal capacity pulled toward buy. The answer was in the middle: use Salesforce as the CRM foundation, but build a custom configuration and inventory layer on top that handled their specific vehicle programs, pricing logic, and dealer coordination.
The custom layer took 8 weeks to build. It replaced the three spreadsheets and the orphaned Access database. Product, marketing, and operations were aligned on a single system for the first time. And because the foundation was SaaS, they did not need to hire a developer to maintain it. The custom layer was designed for handoff.
- There are four options, not two. Buy, Build, Compose, or Wait. Most organizations only consider the first two.
- SaaS covers 75% of the average workflow. The remaining 25% is usually where your competitive advantage lives.
- The build cost is 30-40% of TCO. The other 60-70% is maintenance. Plan for it or it becomes technical debt.
- Compose is the right answer for most mid-market teams. Buy the commodity foundation, build the differentiated layer.
- Use the five-factor framework. Score your decision on uniqueness, competitive significance, rate of change, data sensitivity, and internal capacity.