
If code is cheap to generate, why not build everything? Because generating code was never the expensive part. This breakdown looks at what AI actually changed in the build vs buy software calculation, layer by layer, and where the old intuitions still hold. For the full decision guide, start with our build vs buy software reference.
What got cheaper, what did not
Cheaper:
-
Scaffolding, boilerplate and API client code
-
Test generation and migration scripts
-
Proofs of concept for CRUD-heavy tools, integrations, dashboards and workflow automation
Not cheaper:
-
Data modelling and permissions
-
Edge cases and failure handling
-
Operational ownership: patching, on-call, upgrades, audit evidence
-
Vendor pricing: per-seat costs have risen as AI add-ons and usage tiers arrived
The practical consequence is that a competent team can now validate a build option in days. That makes "prototype before you decide" a standard step instead of a luxury.
The three-test filter, technically framed
We run three ordered tests and stop at the first decisive result.
-
Differentiation: is this capability part of why customers choose you?
-
Fit: does a market product cover roughly 80 percent of the actual workflow, measured in a sandbox with a scripted scenario, with the gap outside the risky steps?
-
Control: does the data need to stay in your hands, or does the logic change weekly?
Test 3 is where regulated workloads fall out of "buy" even when the first two say yes. If control is required, the answer is build, or at minimum a self-hosted or heavily customised platform.
Layer by layer: AI capabilities
The most useful way to think about AI is as a stack, with a different default at each level.
Bottom: buy. Foundation model access via API, managed vector stores, hosted speech and vision. Building your own foundation model is rarely justified without a data advantage and capital few companies have.
Middle: genuinely open. Retrieval, prompt orchestration, evaluation and guardrails. Frameworks exist, but quality depends on your evaluation harness and your retrieval over proprietary data. This is where building tends to pay back because it encodes domain knowledge.
Top: build for differentiators. The user-facing experience and workflow integration. Buy is fine for generic copilots inside tools you already license.

The evaluation tax
A bought AI feature arrives with the vendor's accuracy claims. A built one needs:
-
Your own test sets drawn from real cases
-
Regression checks when prompts, models or retrieval change
-
Monitoring in production
Budget for it explicitly. It is the part of the build that does not shrink when code generation gets cheaper, and skipping it is how teams ship features nobody trusts. If your roadmap includes retrieval or model-backed features, our AI development services cover this layer end to end.
Why proprietary data tips the scale
Bought SaaS AI is trained on the vendor's view of the world and tuned for the average customer. A system you build can use your proprietary data, which is often the only durable edge. If your differentiation depends on what you know that others do not, that argues for build at the retrieval and workflow layer, even while you buy the model underneath.
Agentic workflows: cheap to build, hard to buy
Automations that span multiple systems are specific to how your operations connect, so there is rarely an off-the-shelf version. They are also cheaper to build than ever. These agents frequently serve as glue that makes a bought product do what the business needs without a rebuild, which is a form of hybrid.
The hybrid contract, as an engineering checklist
Buy the commodity core, build a thin differentiating layer, and keep it healthy:
-
Small, versioned integration surface
-
You own the data model for differentiating domains
-
Data export and API stability agreed at signing
-
Custom layer has an owner, roadmap and budget
Examples: bought CRM plus custom scoring and routing, bought payments plus custom ledger and reconciliation, bought support platform plus custom AI triage agent.
Cost caveats worth stating plainly
Maintenance for built systems is commonly planned at 15 to 25 percent of build cost per year. On the buy side, implementation plus integration often lands near 0.5x to 1.5x of first-year licence for mid-market tools, and AI assistants can be priced as a 20 to 40 percent uplift. These are planning heuristics from our experience, so replace them with your own numbers and compare over three to five years.
AI speed also carries a trap. Teams that treat it as a reason to skip design end up with systems that are fast to write and expensive to change. Teams that reinvest the time into design and verification get the actual benefit.
A short protocol you can run
-
Days 1-2: write the workflow, split commodity from differentiating steps, name an owner.
-
Days 3-5: shortlist two vendors, run a sandbox scenario, score fit.
-
Week 2: prototype the hardest step with AI-assisted tooling, build a five-year cost range for buy, build and hybrid, then apply the three tests and record revisit triggers.
If you want a partner for the prototype, talk to us.
Frequently Asked Questions
Does AI make custom software always cheaper to build?
No. It speeds up the first release and prototypes, but design, security, operations and maintenance remain, so lifecycle savings are smaller than first-release savings.
Should we build our own model?
Rarely. Most teams buy model access and build the retrieval, orchestration and evaluation layer around it, where domain knowledge and proprietary data create value.
Why is evaluation a separate cost?
Built AI features need your own test sets, regression checks and monitoring. That work does not shrink when code generation gets cheaper.
When is an AI agent a build candidate?
When it spans several of your systems and encodes how your operations connect. These automations are specific to you and are hard to buy off the shelf.
How do I keep a hybrid from becoming a mess?
Keep the integration surface small and versioned, own your differentiating data model, negotiate export rights up front and give the custom layer a named owner.