“Should we build or buy?” is the most consequential technology question a business faces. Choose build when you should have bought, and you waste $200,000 and 18 months reinventing a solved problem. Choose buy when you should have built, and you spend the next five years fighting a tool that does not fit your business, accumulating workarounds that cost more than custom software would have.
Neither answer is universally correct. The right decision depends on how central the software is to your competitive advantage, how well your workflows match standard solutions, and how much you are willing to pay — not just today, but over five to ten years. This guide provides a decision framework grounded in the actual trade-offs.
The Total Cost of Ownership Calculation Most Companies Skip
The build-vs-buy decision is usually framed as a cost comparison, but companies consistently miscalculate both sides.
The cost of buying is not the license fee. A $500/month SaaS tool for a 50-person team is $6,000 per year. Straightforward. But the total cost of ownership includes:
- Configuration and setup: $5,000 to $20,000 in implementation consulting or internal staff time to configure the tool for your workflows.
- Training: $2,000 to $10,000 in staff time for initial training and ongoing retraining as the tool updates its interface (which it will, on the vendor’s schedule, not yours).
- Integration: $10,000 to $50,000 to connect the tool to your existing systems. Off-the-shelf tools have APIs, but mapping their data model to yours is never as simple as the sales demo suggests.
- Workarounds: This is the big one. When the tool does 80 percent of what you need, the remaining 20 percent gets handled with spreadsheets, manual processes, and creative misuse of fields. The cost of these workarounds is invisible and cumulative — typically $20,000 to $100,000 per year in staff time for a mid-sized team.
- Vendor lock-in: If you ever want to leave, your data is in the vendor’s format, your workflows are built around the vendor’s quirks, and your team knows the vendor’s tool but not the alternative. Migration costs often equal one to two years of the original license fee.
The true five-year cost of a $500/month SaaS tool is not $30,000. It is $80,000 to $200,000 when you include the full picture.
The cost of building is not the development budget. A custom application quoted at $150,000 to build also includes:
- Ongoing maintenance: $25,000 to $50,000 per year for bug fixes, security patches, library updates, and minor enhancements.
- Hosting: $3,000 to $15,000 per year depending on scale and architecture.
- Feature additions: As the business evolves, new requirements emerge. Budget $30,000 to $60,000 per year for enhancements.
- Knowledge continuity: If the original development team leaves, a new team needs onboarding time. This risk is mitigated by good documentation and clean code but never eliminated.
The true five-year cost of a $150,000 custom build is $300,000 to $500,000 including maintenance and enhancements.
When you compare the realistic total cost of ownership, the gap between build and buy is much smaller than the initial sticker prices suggest. The decision should be driven by strategic fit, not cost alone.
The Competitive Advantage Test
The single most important question in the build-vs-buy decision: Does this software differentiate your business?
If the software supports a generic business function that works the same way in every company — payroll, expense reports, email, basic accounting, file storage — buy it. Hundreds of companies have invested billions of dollars building these tools. You cannot beat them on quality, and you should not try. Use QuickBooks for accounting. Use Gusto for payroll. Use Google Workspace for email. Redirect your engineering budget to problems that are unique to your business.
If the software is directly tied to your competitive advantage — the way you serve customers, the way you price products, the way you operate your supply chain, the way you underwrite risk — build it. Here is why:
Off-the-shelf tools impose their workflow on you. When you adopt Salesforce, you adopt Salesforce’s model of how sales works: leads become opportunities, opportunities move through stages, stages have probabilities. If your sales process genuinely works this way, great. If your sales process is fundamentally different — if you sell through partnerships rather than direct prospecting, if your deals have non-linear stages, if your pricing requires real-time calculation from external data — you will spend more time configuring and fighting Salesforce than you saved by not building.
Custom software encodes your institutional knowledge. The way your best operations manager routes orders, the heuristics your most experienced underwriter uses to assess risk, the workflow your top account manager follows to retain at-risk customers — these processes are your competitive advantage. Encoding them in software makes them repeatable, scalable, and independent of any single employee.
Custom software evolves at your pace. When market conditions change and you need to modify your pricing algorithm, add a new customer segment, or support a new product line, you can do it immediately. With off-the-shelf software, you submit a feature request and wait — or, more likely, build a workaround.
The Workflow Fit Assessment
When a business process is important but not competitively differentiating, the decision comes down to workflow fit. How closely does the off-the-shelf tool match your actual process?
We score this on a simple rubric:
90-100% fit: Buy without hesitation. The tool does what you need, the way you need it. Minor differences are trivially adaptable. Example: most companies’ expense reporting needs are nearly identical. Expensify handles them all.
70-89% fit: Buy, with caution. The tool handles the core workflow but requires significant configuration, workarounds, or process adaptation for the gaps. This is the danger zone — the 20 percent gap looks manageable during the sales demo but grows more painful over time. If you buy, budget explicitly for integration and workaround costs, and set a review date at 12 months to evaluate whether the gaps have become intolerable.
Below 70% fit: Build. The tool’s assumptions about how the process works are fundamentally different from your reality. No amount of configuration will bridge the gap. Common examples: a logistics company whose routing optimization is its core competency, a financial services firm with a proprietary risk model, a marketplace with a unique matching algorithm.
To score workflow fit, list the 20 most important things you need the software to do, weighted by frequency and business impact. Demo the off-the-shelf tool against each requirement and score it: fully supported (1.0), supported with configuration (0.8), partially supported with workarounds (0.5), not supported (0). The weighted average is your workflow fit score.
See also: Why Every Software Project Needs a Technical Writer
The Hybrid Approach: Buy the Platform, Build the Differentiation
The build-vs-buy framing is a false dichotomy. The best approach for many businesses is hybrid: buy commodity functionality and build custom extensions for the parts that differentiate you.
Example 1: E-commerce. Use Shopify for the storefront, cart, checkout, and payments (commodity). Build a custom recommendation engine that uses your proprietary customer data and merchandising rules (differentiating). Connect them via Shopify’s API.
Example 2: Healthcare. Use an off-the-shelf EHR for patient records and standard clinical workflows (commodity). Build a custom patient engagement platform that implements your organization’s care coordination model (differentiating). Integrate via HL7 FHIR.
Example 3: Professional services. Use QuickBooks for accounting and invoicing (commodity). Build a custom project management and resource allocation system that matches your firm’s unique staffing and billing model (differentiating). Sync financial data via API.
The hybrid approach gives you the best of both worlds: the reliability and feature breadth of a mature commercial product for standard functions, plus the flexibility and competitive advantage of custom software where it matters most. The cost is the integration layer, which typically runs $15,000 to $40,000 per integration point.
The Vendor Risk Assessment
When buying, evaluate the vendor as carefully as the product. Software vendors go out of business, get acquired, pivot their product direction, or increase prices dramatically. Your due diligence should include:
Financial stability. Is the vendor profitable or burning through venture capital? A VC-funded startup offering an aggressive price may double that price or shut down when funding runs out. Check for recent funding rounds, revenue growth, and profitability statements.
Data portability. Can you export all your data in a standard format? If the vendor’s API only supports limited data export, your switching cost is astronomical. Test the export functionality before committing, not after.
Contract terms. What is the minimum commitment? What happens to your data if you leave? Is there an annual price escalation clause? Many enterprise contracts include 5 to 8 percent annual price increases that compound painfully over a five-year term.
Product roadmap alignment. Where is the vendor investing? If they are pivoting toward enterprise and you are a small business, your needs will be deprioritized. If they are adding AI features at the expense of core reliability, your experience may degrade.
Customer concentration. What percentage of the vendor’s revenue comes from their largest customer? High customer concentration means the vendor’s roadmap is driven by one or two large customers, not by the broader user base’s needs.
Making the Final Decision
Use this decision tree:
- Is this function commodity (same in every business)? Buy.
- Is this function core to your competitive advantage? Build.
- Is neither clearly true? Assess workflow fit.
- Above 85% fit? Buy, with an explicit review at 12 months.
- Between 70-85% fit? Hybrid — buy the platform, build custom extensions.
- Below 70% fit? Build, with a clear scope and phased delivery plan.
- Regardless of direction, calculate five-year total cost of ownership and ensure leadership understands the full investment, not just year one.
The worst outcome is not choosing the wrong option. It is avoiding the decision entirely and ending up with a patchwork of half-adopted tools, abandoned custom projects, and spreadsheet workarounds. Make the decision explicitly, commit to it, and revisit it annually.
If you are evaluating build-vs-buy for a critical business system, reach out to The Proper Motion Company. We help businesses make clear-eyed technology investment decisions and execute on them.