3 min read

Build vs. Buy Doesn’t End at the Vendor Demo

Buying a decision engine saved us from building the engine. It did not define the product around it: channel contracts, access, regulatory rules, support, or the legacy sunset.

Build vs BuyVendor ManagementPlatform StrategyProduct Operations

Build vs. Buy Doesn’t End at the Vendor Demo

Build vs. buy is often framed as a comparison: Can a vendor deliver the capability faster or cheaper than our team?

That is only the first decision.

On a multi-channel decisioning flow, we chose a vendor-delivered engine and configured it into production. The choice avoided building the engine itself. It did not answer how two very different channels would use it, how twelve downstream systems would interpret its decisions, or how the old platform would be retired safely.

The vendor supplies a component, not the whole product

The flow served a national e-commerce partner with a two-minute decision promise as well as direct channels. Applications arrived with different data formats and security models, then passed through twelve downstream systems.

The vendor supplied a skeleton engine. The team still needed product decisions about strategies, access, channel contracts, data types, errors, and operations. No single document mapped the partners, contracts, and data flows.

Those gaps are easy to miss in a demo. A demo proves that a component can perform a task under controlled conditions. It does not prove that the end-to-end product can meet its service promise, handle exceptions, or be operated after launch.

Write down the boundaries

We wrote the API architecture around the engine: upstream partner requirements, downstream contracts, security, data-type expectations, and error handling. That made the boundaries between the vendor capability and our product responsibilities explicit.

The regulatory requirements also needed to live in the right place. We enforced a province-conditional rule at the channel boundary so it was handled consistently. Consent and retention needed their own records and clocks. Proactive and reactive limit increases were treated as different products rather than a single flow with ambiguous behavior.

These are not implementation details to leave until launch. They affect what users see, what data is stored, and how the product behaves when rules differ by channel or context.

Define operations before the first incident

A vendor integration becomes a product the moment a customer or partner depends on it. That means the team needs a Day-2 model before go-live:

  • Who can access the system, and under what conditions?
  • Who owns support at each severity level?
  • What happens when a vendor or downstream dependency is unavailable?
  • How are errors surfaced to users and operators?
  • What evidence is required before switching traffic?
  • What conditions pause a rollout or trigger rollback?

We held the partner’s 120-second SLA as non-negotiable and cut scope across two sprints to protect it. Before cutover, we defined comparison criteria and ran the new and legacy flows in shadow so the team could compare behavior before committing to the switch.

Plan the exit while choosing the entry

The replacement engine could not simply be launched and left beside the legacy system forever. The old platform had to keep running until the new flow met the agreed criteria. We planned the sunset as part of the product delivery, not as cleanup after launch.

The replacement served more than one million customers, held the partner SLA, and retired the legacy engine with zero cutover incidents. Three regulatory changes shipped on the live flow with zero compliance exceptions in the post-launch audit.

The lesson is not that buying is always better. It is that the make-or-buy choice only settles who supplies a capability. Product ownership still covers the contracts, policies, exceptions, support model, and eventual exit.

In your next vendor evaluation, ask not only, “Can this vendor do the job?” Ask, “What product work remains around the capability—and who owns it after the contract is signed?”