PATH / 01DECISION
Buy
The capability is standard, stable, broadly shared, well served by the market, and does not encode how the company wins.
Build vs. Buy Enterprise AI · A CIO–CFO Decision Framework
The build-versus-buy decision is no longer binary.
AI has changed the cost of creating software, but it has not eliminated the responsibilities of owning it. Buy commodity capabilities. Build the operating advantage. Compose the two around the workflow.
FIELDRUNTIME / BUILD VS. BUY
EXECUTIVE POSITION
The decision is no longer simply whether to rent software or recreate an application. It is which capabilities to buy, which workflow intelligence to own, and how to combine them into the smallest system that improves a measurable business outcome.
01
WHAT CHANGED
The old renewal question had two answers.
Price the workflow—not just the application.
Traditional software economics favored renting because building required a large team and a long implementation. AI-assisted engineering changes that boundary. The right unit of comparison is now one end-to-end workflow and the complete system required to operate it safely.
01
Old question
Renew the current product or replace it with another product?
02
New question
Which capabilities should we buy, configure, compose, build, or retire?
03
Wrong comparison
Annual license price versus the cost of producing a convincing prototype.
04
Right comparison
Three-year cost, measurable value, control, adaptability, reversibility, and ownership of operating intelligence.
02
FIVE DECISION PATHS
Choose at the workflow level.
Buy, configure, compose, build—or retire.
An enterprise may use all five paths across its portfolio. The goal is not maximum ownership. It is intentional ownership.
PATH / 02DECISION
Configure
A commercial system fits the core job and limited configuration can accommodate the organization without creating a fragile exception layer.
PATH / 03COMMON DEFAULT
Compose
Existing systems should remain systems of record, but the workflow, context, decisions, and coordination across them are distinctive.
PATH / 04DECISION
Build
The workflow contains proprietary judgment, fast-changing rules, unique economics, or learning that should remain an enterprise-owned asset.
PATH / 05DECISION
Retire
The software mainly preserves obsolete steps, duplicated records, manual reconciliation, or work that should disappear in the redesigned operation.
03
DECISION MATRIX
Start with operating reality, not a platform preference.
Match the path to the nature of the work.
| Workflow condition | Path | Why | Evidence required |
|---|---|---|---|
| 01Standard + stable | Buy | The market can spread development, compliance, and maintenance across many customers. | The workflow can adopt the product’s standard process without material workarounds or loss of advantage. |
| 02Standard core + bounded variation | Configure | The product solves the durable core and the variation is limited, visible, and maintainable. | Configuration stays inside supported extension points and survives upgrades without specialist rescue. |
| 03Commodity records + distinctive coordination | Compose | CRM, ERP, ticketing, or data platforms can remain while an enterprise-owned workflow layer carries the work across them. | Interfaces, state, authority, evidence, failure ownership, and replacement boundaries are explicit. |
| 04Proprietary judgment + continuous change | Build | The workflow is a source of operating advantage and improves through company-specific exceptions, corrections, and outcomes. | The organization can own the product, evaluation, security, support, and controlled learning responsibilities. |
| 05Duplicated or obsolete work | Retire | Recreating an unnecessary process—through SaaS or custom software—preserves cost instead of removing it. | The redesigned workflow can eliminate the step without losing a necessary control, record, decision, or customer outcome. |
04
BUYER EVIDENCE
Architecture and economics must clear the decision together.
The CIO and CFO are answering different halves of the same question.
- Can the architecture preserve authoritative state across systems?
- Are identity, permissions, evidence, recovery, and support ownership explicit?
- Can models, tools, and vendors be replaced without rebuilding the operating knowledge?
- Does the organization have the product and engineering capacity to own what it builds?
- What is the three-year fully loaded cost—not merely the license or initial build?
- Which measurable mechanism creates capacity, revenue, margin, cash, or risk reduction?
- What assumptions can finance challenge, and what operating evidence will verify them?
- What flexibility, bargaining power, and future option value does ownership create?
05
THREE-YEAR ECONOMICS
Neither the license nor the initial build is the full cost.
Compare fully loaded ownership paths.
Use the same time horizon, operating volume, risk assumptions, and business baseline for every option. Keep modeled value separate from observed value.
Cost of buying
- Licenses and usage
- Implementation and services
- Integration and customization
- Workarounds and duplicate work
- Renewal exposure and switching cost
Cost of building
- Workflow discovery and product design
- Engineering and integration
- Data, evaluations, and controls
- Production operation and support
- Maintenance, change, and recovery
Cost of composing
- Underlying platforms and systems
- Workflow runtime and interfaces
- Ownership across vendor boundaries
- End-to-end observability and testing
- Migration and replacement flexibility
Implementation + platform + integration + operation + review + change + expected failure cost.
Capacity + cycle time + throughput + revenue or margin + cash + risk reduction, adjusted by adoption and confidence.
Value minus TCO, considered alongside control, reversibility, bargaining power, learning, and strategic option value.
06
WHAT TO OWN
Models and tools are replaceable. Operating intelligence compounds.
Own what makes the workflow distinct.
Even when the enterprise buys most of the technical stack, these intelligence artifacts should remain portable, inspectable, and controlled by the organization.
Workflow graph
How work moves, branches, stops, recovers, and reaches verified completion.
Context + state
The authoritative knowledge, live operating condition, history, and permissions surrounding the work.
Evaluations
Representative tasks, edge cases, failure thresholds, evidence checks, and regression tests.
Authority model
What software, AI, and people may read, propose, execute, approve, escalate, and change.
Outcome memory
Exceptions, corrections, decisions, actions, and downstream results that make the next run better.
07
WORKED EXAMPLE
A pricing exception should not require replacing the CRM.
Buy the records. Build the decision workflow.
Keep the CRM and ERP as reliable systems of record. Build the distinctive layer that assembles deal context, checks policy and margin, coordinates approvals, preserves evidence, and learns which exceptions produce good downstream outcomes.
BUY
Systems of record
Accounts, opportunities, contracts, products, price books, orders, invoices, and financial records.
BUILD
Workflow operating system
State, context assembly, policy, exception routing, evidence, approvals, outcome verification, and learning.
AI
Interpret + propose
Understand the request, retrieve precedent, diagnose the exception, explain tradeoffs, and prepare the decision.
PEOPLE
Exercise authority
Own the customer relationship, accept material margin or policy risk, decide novel exceptions, and govern change.
EXECUTIVE CHECKLIST
Before the renewal, platform purchase, or custom build.
Require evidence for six questions.
- 01Is the workflow genuinely differentiating?
Name the judgment, coordination, customer promise, economics, or operating knowledge that competitors cannot obtain from the same product.
- 02What is the cost of fitting the business to the software?
Include workarounds, duplicate entry, handoffs, reconciliation, exceptions, delayed decisions, and lost operating visibility.
- 03What must remain enterprise-owned?
Separate replaceable infrastructure from context, procedures, evaluations, authority, evidence, and learning that should survive any vendor.
- 04Can the organization operate what it builds?
Assign production ownership, security, evaluation, support, incident response, change approval, and budget before approving the build.
- 05Is the decision reversible?
Define modular boundaries, export paths, interfaces, rollback, replacement cost, and the smallest first commitment.
- 06What evidence will settle the decision?
Run a bounded workflow test with real tasks and a finance-approved baseline before making a platform-wide commitment.
08
EXECUTIVE QUESTIONS
Before committing architecture and capital.
Build vs. Buy Enterprise AI FAQ
Is building enterprise AI now cheaper than buying software?
Sometimes, for a bounded and consequential workflow. AI-assisted engineering can reduce implementation effort, but production cost still includes discovery, integration, data, evaluation, security, human review, support, maintenance, and recovery. Compare fully loaded three-year economics, not a prototype build against a SaaS list price.
When should an enterprise buy AI software?
Buy when the capability is standard, stable, not strategically differentiating, well served by the market, and can be adopted without material workarounds, lock-in, or loss of control over critical operating knowledge.
When should an enterprise build an AI workflow?
Build when the workflow contains proprietary judgment, unique coordination, changing rules, material economics, or outcome-linked learning that creates advantage—and when the organization is prepared to own production operation and governance.
What does compose mean in a build-versus-buy decision?
Compose means retaining commercial systems for commodity capabilities or records while building an enterprise-owned workflow layer across them. That layer preserves state, applies context, coordinates tools, defines authority, verifies outcomes, and learns from real work.
Should AI agents replace existing SaaS platforms?
Not by default. Many enterprises should initially keep reliable systems of record and use agents inside a governed workflow operating system that crosses them. Individual applications can be replaced later when evidence shows that doing so improves economics, control, or adaptability.
How should a CFO compare build and buy costs?
Include implementation, licenses, infrastructure, integration, data, evaluations, human review, exceptions, controls, support, change, failure exposure, switching cost, and the value of strategic flexibility. Keep modeled benefits separate from observed results.
Who should own the build-versus-buy decision?
The decision should be shared. The workflow owner establishes the business outcome, the CIO owns architecture and operability, the CFO challenges economics and value evidence, security and risk leaders set controls, and operators validate how the work actually behaves.
Facing a software renewal or AI platform decision?
Map the workflow before signing the contract.
Bring one workflow, the current operating cost, and the decision in front of you. We will map what to buy, configure, compose, build, or retire—and define the evidence needed for a defensible CIO–CFO decision.