When should a company reverse a buy or build decision?

A company should reverse a buy or build decision when evidence about the work, costs or operating capacity makes another arrangement preferable, and it can support the change. A higher bill, a new vendor feature or a struggling internal tool can justify a review. The decision to switch needs a credible alternative and a plan for the work already in progress.

Reconsidering a choice does not require proving that the original team was wrong. The market, the task and the people available to maintain it may have changed. An internal connection may also have been intended as a temporary bridge from the start.

The buy, build or combine guide explains the initial choice. Here, the question is how to change an existing AI-assisted workflow without overlooking the cost and responsibility of getting from one arrangement to the next.

Identify what has changed enough to warrant a review

Start with the reason for reconsideration and the evidence behind it. “Our build is expensive” needs more explanation. Which continuing work costs more than expected, and what could change it?

Useful triggers include:

• A material capability gap. The service cannot complete an important part of the intended task at an acceptable standard.
• A changed operating commitment. Demand, support requirements or the availability of maintainers differs from the arrangement originally approved.
• A credible alternative. A supplier or internal team can now demonstrate a requirement that previously justified the current choice.
• A commercial decision approaching. Renewal, a planned replacement or a known dependency change creates a point at which the next commitment must be examined.

These findings lead to different investigations. A recurring integration failure might need a repair. A missing maintainer raises a capacity question. A new product deserves testing against the actual task before it earns a replacement budget.

The UK government’s Sourcing Playbook describes reassessing delivery models as quality, technology and strategic conditions change. It addresses public-service sourcing, rather than establishing rules for a private company’s AI purchase. Its useful discipline is to reconsider the delivery arrangement in light of current conditions, including the possibility of combining components.

A planned temporary build illustrates the point. In an August 2026 X post, Kevin Goldsmith reported building custom connections for vendors that lacked official ones, then switching when the official versions became available. He described the internal work as a bridge. That is a firsthand account without a documented cost or quality comparison; it shows why taking an intended exit need not mean the earlier build failed.

Compare the choices from today onward

Past effort belongs in the history of the decision. It cannot be recovered by continuing to fund an arrangement that no longer fits. Equally, an existing asset can still be useful even though its creation cost is already spent.

The distinction appears in HM Treasury’s Green Book 2026 guidance on sunk costs. It excludes costs already incurred and unchangeable from forward appraisal, while retaining the opportunity cost of using resources already paid for. This is government appraisal guidance, not a private-company accounting policy. It helps separate irrecoverable expenditure from the continuing value of code, records, knowledge and staff capacity.

Suppose a commercial photography agency with 180 employees built an AI assistant to prepare internal shoot briefs. It reads a booking form, the client’s shot list (the photographs requested) and location access notes. Jamie Lee, a producer, checks the shoot date, requested images and unresolved access details before using the brief.

Alex Morgan, the operations manager, is now considering a brief-drafting feature in the agency’s booking system. The comparison starts with the work both arrangements must deliver. It should include keeping the custom assistant, repairing a specific weakness and replacing its drafting component.

Use the same task scope and operating period for the alternatives. Include temporary overlap, record transfer, staff learning and acceptance work, alongside what will continue after the switch. Keep uncertain estimates visible. The internal-software cost guide explains how to turn continuing responsibilities into work that can be estimated.

A remaining contractual payment needs separate attention. Establish what can change, which obligations remain and what a termination or replacement would require with the responsible commercial and finance owners. Calling all existing spend “sunk” does not establish that the company can stop paying or that a new commitment is affordable.

A March 2026 Reddit account captures that overlap. A Reddit user described bringing needed project-management functions into their own application and having their engineering lead build reporting, while the existing product contract still ran until year-end. The employer and economics are unverified, and the account does not establish a completed exit. Its practical detail is that replacement work and an existing obligation can coexist.

Decide which part really needs to change

For Alex, replacing the drafting component does not require discarding the booking system, producer checks or useful test cases. The agency may retain mappings between booking fields and brief requirements while changing who supplies the draft.

The proposal needs to establish whether the booking-system feature can use the permitted records, preserve their meaning and save the result against the correct shoot. A fluent summary that loses a missing access confirmation fails an important requirement. A feature demonstration using complete records would not examine that case.

Buying can still leave custom connections and business-content maintenance. Building can still depend on purchased services. Describe the changed responsibilities rather than treating “buy” and “build” as indivisible packages.

In an October 2026 LinkedIn post, Matthew New, a partner at software consultancy Uptech Studio, reported switching time-tracking products and using AI with the new product’s API to build the reports the firm needed. His account keeps purchased core functions alongside custom reporting. It is a commercially interested practitioner’s self-report, without a verified savings comparison or stated company size. The useful question is which part of the arrangement needs to be replaced and which work remains yours.

Ask the proposed operating owner to demonstrate an ordinary correction as well as a clean draft. For the agency, that could be a revised shot list attached to an existing booking. Jamie should be able to identify the applicable version, check the changed brief and explain what remains unresolved. The test should use permitted material and the intended access arrangement.

If the replacement merely moves unresolved work to a different employee, include that work in the comparison. If it satisfies the task with a support arrangement the company can sustain, the custom drafting component may no longer justify continued development.

Carry unfinished work through the switch

Acceptance of the replacement and transfer of existing work are separate obligations. Alex needs to know what happens to a brief Jamie already accepted, a brief waiting for a location access confirmation and a new booking arriving after the change.

For an unfinished brief, copying its text is insufficient. The receiving process must retain the booking relationship, source version, unresolved question and responsible person. Moving it must not silently turn “awaiting access confirmation” into “ready for the shoot.”

The Sourcing Playbook’s transition guidance connects the outgoing exit plan with the incoming service and warns about the staff burden of operating the current arrangement while preparing its replacement. Apply that planning question to the people carrying your work. A small component change can still require coordination between the producer, technical owner and supplier.

Before moving live work, have those owners establish:

1. What transfers and what stays available. Include necessary source records, decisions and history, with appropriate access and retention.
2. How pending work is reconciled. Identify missing, duplicate or uncertain bookings and keep someone responsible for each unresolved case.
3. Which route receives new work. Make the change point explicit so two systems do not independently create apparently authoritative briefs.
4. How work continues if the change fails. Keep an approved alternative and explain how people distinguish accepted, pending and uncertain results.

A fallback cannot undo an incorrect brief that someone has already acted on. Use the service-continuity guide’s work reconciliation checks for that separate recovery task.

Authorize a bounded replacement

The review should end with the next commitment the evidence supports. That might be a comparison, a repair, a limited replacement or a decision to retain the current arrangement. Avoid turning a request to investigate into permission to migrate everything.

For Alex, a useful proposal could read as follows.

Before accepting the switch, identify who authorizes the changed use, who operates it and which findings would restrict or stop it. Set review points around the next meaningful commitment or known change. There is no universal number of months after which a sourcing choice becomes wrong.

Afterward, inspect whether the intended work is actually complete: new briefs use the approved route, pending bookings have owners, necessary history remains accessible and the retired component no longer takes new requests. Confirm remaining supplier and internal obligations separately. A lower bill or a disabled application alone cannot establish that the transfer succeeded.

Keep the record with the wider tools and workflows decisions. It should explain what changed, what evidence justified the new arrangement and what responsibility the company accepted. That gives the next owner a reasoned starting point when conditions change again.

Questions about reversing a buy or build decision

Should past development spending stop us buying a replacement?

Past spending that cannot be changed should not determine the next choice. Existing code, mappings, test cases and knowledge may still have useful value, however. Compare the future work and consequences of retaining, repairing or replacing the arrangement, including the transition. Use the forward comparison to distinguish historical expenditure from resources and obligations that still matter.

Do rising maintenance costs mean we should buy instead?

Rising maintenance costs justify investigating the cause and alternatives. A bounded repair may be better than replacement, and a purchased service may still require configuration, checking and custom integration. Compare the same completed task and continuing operating commitments before deciding. The component review helps identify what would actually leave the internal team’s workload.

Should we switch when the current contract renews?

A renewal date creates a decision point, not proof that a replacement is ready. Start early enough to examine the applicable terms, compare alternatives and establish a supported transfer. If necessary evidence is missing, have the responsible owners decide what arrangement can lawfully and practically continue. Do not assume a new subscription or an expiring date supplies the missing acceptance evidence.

Can we reverse only part of a buy or build choice?

Yes. A company can replace a custom drafting component while retaining its source system, checking process and useful connections. Specify the boundary and test the join, including an important exception. Buying that component does not remove responsibility for the parts retained internally. The photography-agency example shows why the booking relationship matters alongside the generated text.

How do we know the replacement is complete?

Check the work, records and obligations as well as the new service. Existing accepted work must remain understandable, pending items must retain owners and unresolved questions, and new requests must follow the approved route. Confirm that retired components cannot keep accepting work and that remaining commercial or retention duties are handled. Use the transfer checks before calling a successful demonstration a completed replacement.