Skip to main content
Compare // Build vs buy

Build vs buy: the question every CTO pretends to have solved.

Buying is faster until it doesn't fit. Building is perfect until you have to maintain it. Most good answers are 'buy the commodity, build the differentiator'.

Buy
Speed · vendor roadmap
Build
Fit · ownership
Extend
ERP + custom modules

VerdictBuy what everyone does the same way. Build what makes you different. Extend the middle.

It's rarely all one or the other

Framed as a binary, build vs buy produces bad decisions in both directions: teams that build their own invoicing engine, and teams that bend their unique operation around a tool that was never designed for it.

A better question is: which parts of this problem are a commodity, and which are a competitive advantage? Payroll, accounting, and email are commodities; everyone does them roughly the same way, so buy them. The workflow that makes your service faster or your pricing smarter than competitors' is where custom software earns its keep.

Between the two sits a third option that often wins: buy a platform that covers the commodity parts, like an ERP, and extend it with small custom modules for the parts that are yours.

The trade-offs

FactorBuy (SaaS)Build (custom)Extend (ERP + modules)
Time to valueFastSlowestMedium
Fit to your processYou adaptExactHigh
Ongoing costSubscriptions grow with usersMaintenance and hostingSubscription plus module care
ControlVendor roadmapFullHigh
RiskVendor lock-inDelivery and key-person riskUpgrade discipline needed
Best forCommodity processesCore differentiatorsOperations with a few unique twists

A decision framework

  1. Name the job

    Describe the outcome in business terms, like "quote complex jobs in minutes", not a feature list.

  2. Classify it

    Is this how everyone works (commodity) or how you win (differentiator)?

  3. Survey the market

    Shortlist products and check how much of the job they cover without workarounds.

  4. Price the full lifecycle

    Compare five years of subscriptions, implementation, extensions, hosting, and maintenance for each option.

  5. Decide and revisit

    Pick, then set a date to revisit. What you learn in year one often changes the answer for year three.

Five-year cost lines for each option

Cost lineBuyBuildExtend
LicensesPer seat, every yearNonePlatform subscription
Initial workConfiguration and integrationsFull design and developmentConfiguration plus modules
MaintenanceVendor's job; you retest integrationsYours: security, dependencies, fixesModule upkeep through upgrades
HostingIncludedYoursIncluded or yours
Change requestsWait for the roadmapYour backlog, your paceYour modules, platform roadmap for the rest

Costs people forget

Myth: Building is a one-time cost.

Reality: Software is a pet, not a statue. Budget for maintenance, security updates, and hosting every year.

Myth: SaaS has no hidden costs.

Reality: Integrations, per-seat growth, add-ons, and export limits add up.

Myth: We'll customize the SaaS later.

Reality: Many SaaS tools limit customization. Check before you commit.

Signs you should build

  • The workflow is a genuine competitive advantage
  • Several products were evaluated and none fit without heavy workarounds
  • You can fund maintenance, not just the first version
  • You have, or can hire, people to own it long term

Signs you should buy

  • The process works the same way at most companies
  • Time to value matters more than perfect fit
  • A mature product covers most requirements as standard
  • You don't want to run software as a capability
Never build your own login system, payment processor, or date library. Life is short.
Engineering folk wisdom

Example decisions

ScenarioRecommendationWhy
Accounting and payrollBuyRegulated, standardized, and constantly updated by vendors
A unique quoting engine for complex jobsBuild or extendIt's how you win work; off-the-shelf tools force compromises
Inventory with a few unusual rulesExtend an ERPStandard features cover most of it; small modules cover the rest
Customer portal for orders and documentsExtendERP portals cover the basics and can be customized
Internal approval workflowsBuy or extendRarely a differentiator; use what your ERP or workflow tool offers
A data product sold to customersBuildThe software is the product

The hidden costs of building

The first version of custom software is the cheapest part. After launch come security patches, dependency upgrades, hosting, monitoring, bug fixes, and the steady stream of changes the business will ask for. There's also key-person risk: if one developer understands the system, their departure becomes a business risk.

None of that means don't build. It means build deliberately, with tests, documentation, and a team that can own it, and budget for the life of the software, not just its birth.

Questions to answer before deciding

QuestionIf the answer is yes…
Do competitors do this the same way?Buy
Would doing it better win customers?Build or extend
Can a product cover most needs as standard?Buy or extend
Can you fund maintenance for years?Building is viable
Is speed to launch critical?Buy first, build later

Revisit the decision regularly

Build vs buy isn't permanent. A SaaS tool that fit at fifty employees may not at five hundred, and a custom system that was a differentiator may become a commodity as the market catches up. Revisit major decisions every year or two against the same framework, and be willing to switch when the balance changes.

The running costs people forget

Building feels cheaper at the start because the costs come later. Custom software needs a way to ship changes safely, which DORA measures through change lead time, deployment frequency, failed deployment recovery time, change fail rate, and deployment rework rateSource [1]. Someone has to own those numbers for as long as the software runs.

Running software also means operating it: monitoring, security updates, and backups that work. A long-standing government guide recommends three copies of important data on two media types with one stored offsiteSource [2]. Bought or subscribed products include much of this in the price. Put it in your build estimate honestly, and the decision usually becomes clearer.

Frequently asked questions

What about low-code platforms?
They sit between building and buying. They're fast for internal tools and simple workflows, but check pricing at scale, data ownership, and how hard it is to leave.
How do we avoid vendor lock-in when buying?
Prefer products with open APIs and full data export, keep integrations in your own layer, and document how you would migrate away.
Can we mix building and buying?
Yes, and most companies do: buy the platform, extend it for what's unique, and build standalone software only where nothing fits.
How do we estimate the cost of building?
Break the system into features, integrations, and non-functional needs like security and hosting, estimate each, and add yearly maintenance. A discovery phase makes this concrete.
What if the SaaS product we buy shuts down?
It's a real risk with smaller vendors. Check the vendor's stability, data export options, and contract terms, and keep regular exports of critical data.
Can an ERP replace several SaaS tools at once?
Often. Consolidating CRM, inventory, invoicing, and helpdesk into one ERP removes integrations and duplicate data, though some specialist tools are still worth keeping.
When is custom software clearly worth it?
When the workflow is a competitive advantage, no product fits without heavy workarounds, and you can fund ongoing maintenance.
Can we start with SaaS and build later?
Yes, and it's often smart: learn the real requirements first, then build what the product couldn't do.
How do we avoid vendor lock-in?
Check data export, API access, and contract exit terms before signing, and keep your own copy of critical data.
What's the 'extend' option?
Using a platform like Odoo for standard functions and building custom modules only for your unique workflows.
How much maintenance does custom software need?
Plan for ongoing work every year: dependency and security updates, hosting, fixes, and small changes as the business evolves.
Is low-code a middle ground?
Sometimes. Low-code tools speed up simple apps but can hit limits on complex logic, testing, and scale. Treat them as a product decision, not a shortcut.
Can you help us decide?
Yes. A short discovery engagement compares options against your requirements and budget, and the result is yours to keep.
When is building clearly better?
When the software is a real competitive difference, no product fits, and you're ready to own its delivery and operation for yearsSource [1].
What costs should a build estimate include?
Development, plus testing, deployment, monitoring, security updates, backups, and the people to run themSource [1]Source [2].

Sources

  1. [1]DORA's software delivery performance metrics (opens in a new tab)DORA, updated 5 January 2026
  2. [2]Data Backup Options (opens in a new tab)US-CERT / CISA (Ruggiero & Heckathorn), 2012