I’m writing from my experience as the former Chief Product Officer (CPO) at Norse Atlantic Airways, where build-or-buy decisions meant balancing technology choices with responsibility for the customer experience.

The build-or-buy discussion usually starts with technology.

Can we build it ourselves? How much will it cost? Will a vendor move faster? What happens if we need something the product does not support?

Those are useful questions. But there is another one I think deserves more attention:

Who will understand how our business works after we make the decision?

Buying software can be the right choice. Owning every line of code is rarely the goal. The responsibility for understanding the business still needs a home.

What you get when you build

Building gives you direct control over implementation. You can adapt the product to your processes and make decisions without waiting for a vendor’s roadmap.

It also gives you an ongoing responsibility. Your team owns maintenance, security, reliability, and the next change. People need to understand why the system behaves as it does, including the exceptions that accumulated along the way.

Source code helps. It does not automatically explain the commercial intent behind a rule or whether a workaround is still needed.

A system built internally can become just as difficult to understand as one bought from a vendor.

What you get when you buy

Buying gives you access to specialist technology and a team focused on improving it. That can help you deliver something useful sooner and concentrate your own effort where it matters most.

The tradeoff is distance. Part of the implementation sits outside your organization. Configuration, integrations, and vendor terminology become the language through which your team expresses its needs.

You still need to decide what the system should do. A vendor cannot resolve an ambiguity your own organization has not recognized.

If different teams have different interpretations of a customer promise, buying a platform does not settle the disagreement.

The part I would keep close

During my time as CPO at Norse Atlantic Airways, we worked with Sendbird, now delight.ai. From the airline’s side, the technology was an important part of the equation. So was the work inside our own business.

We needed to organize our knowledge and make it useful to the people responsible for the customer experience. Internal knowledge management and the work of AI agent managers mattered because someone had to understand the policies, exceptions, and desired behavior.

The provider brought capabilities. We had to bring a clear understanding of what we wanted those capabilities to achieve.

That lesson extends well beyond AI. The more capable the tools become, the more consequential it is to give them an accurate picture of the business.

Own the rules and the decisions

Owning understanding means being able to explain the behavior your business depends on.

What are you promising the customer? Which conditions apply? Where is each rule implemented? Who approved an exception? How would you recognize an outcome that differs from the intention?

Those questions cross organizational boundaries. Commercial teams may define the promise. Operations may handle exceptions. Engineering may implement the behavior. Legal or finance may impose additional conditions.

No single team can answer everything alone. Someone needs to connect those perspectives and preserve the decisions between them.

Make understanding part of the buying decision

When evaluating a platform or a proposal, I would ask:

  • Can we explain how our important business rules will be represented?
  • Can we inspect the configuration and evidence behind an outcome?
  • How will changes and exceptions be recorded?
  • Who maintains the connection between policy and implementation?
  • What knowledge stays with us if a supplier or employee leaves?

These questions also belong in an internal build decision. They help reveal work that a feature list or delivery estimate can overlook.

A successful handover should leave people able to reason about the system, not just operate its interface.

Understanding creates room to change

A business with clear ownership of its rules has a better starting point when it needs to adapt.

It can explain what should happen, investigate what does happen, and identify where a decision needs review. That supports changing vendors, introducing products, responding to incidents, and improving customer experiences.

This is part of the thinking behind Haster. We are building toward a connected view of business rules across policy, configuration, APIs, and code, with evidence people can inspect and discuss.

Whether you build, buy, or combine both, keep investing in the understanding that lets you use the technology well.

You can buy the platform. You still need to own the understanding.

Contact sales to discuss how Haster could support that understanding across your systems.