Build vs buy for AI capabilities
Vendors ship impressive assistants. Building in-house feels like control. Both fail when nobody maps the capability to competitive advantage and exit options. The loud argument about model brands is usually the least important decision on the table.
Architecture leadership should reframe the conversation around capabilities, contracts, and absorbable change—the same way we should for any major package or platform choice.
Decide on capability, not logo
Buy commodity: generic summarization, coding assist, standard OCR, common speech-to-text. Build or deeply configure where underwriting logic, claims nuance, pricing edge, or customer data advantage lives.
Insist on exportable evaluation data, portable orchestration where possible, and clear data-use terms. Soft lock-in starts as convenience: prompts trapped in a vendor UI, fine-tunes you cannot leave, retrieval corpora you cannot re-index elsewhere without a project.
Price the whole system
Include integration, monitoring, change management, evaluation operations, and model churn. A cheap API with expensive human cleanup is not cheap. A packaged copilot that cannot meet residency or audit needs is not “faster”—it is a dead end after legal review.
Also price organizational fit. A brilliant platform that your operating model cannot staff will rot. Buy decisions are change decisions.
Hybrid is normal
Many estates land on a hybrid: commodity models via a controlled gateway, proprietary workflows and rules in-house, vendor vertical solutions for bounded domains with strong exit clauses. That is fine if the seams are designed.
Design the seams explicitly: where identity lives, where prompts are stored, how evaluation runs, how PII is handled, how a capability can move later with bounded cost.
Questions that cut through hype
- What business capability does this serve, and who owns it?
- What evidence will we accept that it works in our cases?
- What happens on vendor failure or price shock?
- What data leaves, and under what terms?
- What must our people still do on day two of production?
If a proposal cannot answer those questions, it is not ready for architecture approval—regardless of how good the keynote looked.
Recommendation posture
Default to buy for undifferentiated assistance, default to control for decisioning near money and risk, and always keep an exit narrative. That posture is boring on purpose. Boring is how you still have options when the market’s favourite model changes names again next year.
How this plays out in delivery
In practice, the difference between a slide and an operable change is whether teams can point to owners, controls, and evidence under pressure. That pressure arrives as an incident, an audit question, a vendor outage, or a steering committee that wants to scale a demo. If those answers are improvisations, the feature was never production-ready—regardless of how polished the interface looked in a pilot.
Delivery leaders should therefore reserve explicit capacity for the boring work: contracts, runbooks, evaluation packs, fallback paths, and decision records. Boring work is what makes ambitious AI and platform change survivable. Skipping it to protect a velocity chart is how organizations repurchase the same programme every three years under a new name.
Questions worth asking in design review
Who owns the outcome after launch? What fails first when the dependency is slow or wrong? Which data classes are in motion, and under which policy? What would make us pause or roll back within an hour? What evidence will we examine weekly to know quality is holding?
If a proposal cannot answer those questions without hand-waving, keep the scope in a controlled experiment. Experiments are useful. Unowned production traffic is not an experiment—it is a risk acceptance you forgot to record.
Working habits that keep quality compounding
Write short decision records when you cross a boundary. Keep a living list of invariants for each critical capability. Review with a checklist that targets blast radius rather than style. Instrument silent failure modes, not only HTTP errors. Revisit model, prompt, and vendor changes with the same seriousness as database migrations.
None of these habits require a new framework brand. They require leadership attention and a refusal to confuse demos with operable systems. Teams that practice them can adopt assistants, agents, and new platforms without losing the enterprise plot.
A note on language and accountability
Replace slogans with operational nouns: capability, owner, control, fallback, evidence, exit. Language shapes governance. Teams that speak only in broad transformation slogans struggle to assign accountability. Teams that speak in capabilities can fund, staff, measure, and stop work when the evidence says stop.
Hold that vocabulary in architecture forums and programme boards. Over time it becomes the shared spine that lets software development absorb AI tools without fragmenting into disconnected experiments.
Closing
The through-line is simple: treat AI-related change as architecture and operations work, not as magic. Make ownership explicit, put uncertainty where blast radius is acceptable, measure what can silently fail, and refuse to scale what you cannot run. That discipline is how software organizations get durable value from new techniques instead of a temporary theatre of progress.
How this plays out in delivery
In practice, the difference between a slide and an operable change is whether teams can point to owners, controls, and evidence under pressure. That pressure arrives as an incident, an audit question, a vendor outage, or a steering committee that wants to scale a demo. If those answers are improvisations, the feature was never production-ready—regardless of how polished the interface looked in a pilot.
Delivery leaders should therefore reserve explicit capacity for the boring work: contracts, runbooks, evaluation packs, fallback paths, and decision records. Boring work is what makes ambitious AI and platform change survivable. Skipping it to protect a velocity chart is how organizations repurchase the same programme every three years under a new name.
Questions worth asking in design review
Who owns the outcome after launch? What fails first when the dependency is slow or wrong? Which data classes are in motion, and under which policy? What would make us pause or roll back within an hour? What evidence will we examine weekly to know quality is holding?
If a proposal cannot answer those questions without hand-waving, keep the scope in a controlled experiment. Experiments are useful. Unowned production traffic is not an experiment—it is a risk acceptance you forgot to record.
Working habits that keep quality compounding
Write short decision records when you cross a boundary. Keep a living list of invariants for each critical capability. Review with a checklist that targets blast radius rather than style. Instrument silent failure modes, not only HTTP errors. Revisit model, prompt, and vendor changes with the same seriousness as database migrations.
None of these habits require a new framework brand. They require leadership attention and a refusal to confuse demos with operable systems. Teams that practice them can adopt assistants, agents, and new platforms without losing the enterprise plot.
A note on language and accountability
Replace slogans with operational nouns: capability, owner, control, fallback, evidence, exit. Language shapes governance. Teams that speak only in broad transformation slogans struggle to assign accountability. Teams that speak in capabilities can fund, staff, measure, and stop work when the evidence says stop.
Hold that vocabulary in architecture forums and programme boards. Over time it becomes the shared spine that lets software development absorb AI tools without fragmenting into disconnected experiments.
Closing
The through-line is simple: treat AI-related change as architecture and operations work, not as magic. Make ownership explicit, put uncertainty where blast radius is acceptable, measure what can silently fail, and refuse to scale what you cannot run. That discipline is how software organizations get durable value from new techniques instead of a temporary theatre of progress.
A scoring sheet you can reuse
Score differentiating value, data sensitivity, residency fit, auditability, integration cost, exit cost, time-to-value, and organizational readiness. Weight by your context: a bank may weight auditability higher than a non-regulated SaaS firm. Make the weights explicit so debates are about evidence, not about whose favourite vendor presented last.
Require two realistic options plus a do-nothing baseline. Single-option “decisions” are purchases looking for approval.
Contract clauses that matter
Data use and training rights, subprocessors, residency, retention, uptime, support for audit, export of your prompts and evaluation assets, price change terms, and exit assistance. Have legal and architecture review together. Either alone will miss half the risk.
For vertical solutions, demand clarity on where your business rules live and how you retrieve them if you leave. If the answer is “you don’t,” price that lock-in into the deal—or walk.
Organizational buy vs technical buy
Sometimes the package is fine and the organization is not ready: no owners, no data products, no operating model for exceptions. In that case, buying early creates shelfware. Sequence readiness work before or with the purchase.
Architecture should be willing to say “not yet” without saying “never.” A timed re-evaluation with clear readiness criteria is a professional outcome, not a failure to innovate.
Putting it into the operating rhythm
None of this sticks if it appears only in a one-off workshop. Put the checkpoints into existing forums: design authority, risk intake, sprint reviews, and operations reviews. Assign named owners. Review the same metrics until the behaviour becomes muscle memory. Tools change. Operating rhythm is how architecture survives tool change.
When you expand scope—new channel, new market, new model provider—re-run the same questions rather than assuming last quarter’s controls still fit. Scope expansion is where quiet regressions hide. A short re-certification beats a long incident report.
What good looks like after six months
You can name owners for each AI-touched capability. You can show evaluation trends and cost trends. You can pause a feature without heroics. Engineers can explain the boundaries without opening a chat history. Sponsors hear outcome language and evidence, not only model brand names. That is the standard. Aim for it deliberately.
Field notes from programmes that stuck
The programmes that keep their gains share a few unglamorous traits. They name a single accountable owner for each capability touched by AI or platform change. They keep a thin evidence pack current: what the feature does, which data it uses, how quality is measured, and how to pause it. They review cost and quality on a fixed weekly or biweekly cadence instead of waiting for a quarterly surprise.
They also refuse to expand scope while basic controls are missing. That refusal feels slow in the week it happens and fast in the year it saves. Sponsors accept it more readily when you offer a dated path: we can widen to segment B when override rates stay under threshold and fallback drills pass. Conditional speed is still speed—just adult speed.
Common failure modes to watch for
Eternal pilots that serve real customers without on-call. Prompt edits in production with no version history. Retrieval corpora that mix clearance levels. Success metrics that count messages sent instead of outcomes achieved. Architecture reviews that only admire diagrams after contracts are signed. Cleanup work that is always scheduled after this critical launch.
Each failure mode is preventable with a small control. The danger is not that teams cannot invent controls. The danger is that delivery pressure makes skipping them look rational until the incident report is written.
A ninety-day improvement plan
Days 1 to 30: inventory AI-touched journeys, owners, and gaps in logging, evaluation, and fallback. Publish the list without blame. Days 31 to 60: close the top three blast-radius gaps; stand up a short design-authority slot for new use cases; put cost alerts in place. Days 61 to 90: run one controlled promotion from pilot to production using a written exit report; kill or contain at least one unmanaged experiment.
At day ninety, present evidence trends rather than tool logos. Leaders can fund what they can see. Visibility is a prerequisite for sustained investment in quality.
How this article should change Monday morning
Pick one capability you touch. Write the owner, the invariant that must not break, the fallback if the AI dependency fails, and the metric you will check next week. Share it with the people who can correct you. Then make one concrete backlog item that turns a gap into a control.
Long articles do not improve estates. Changed operating habits do. Use this piece as a mirror, not as literature. If nothing in your plan of record moves after reading it, the reading did not count.