What an Organisation Needs to Own

Control of Commitments and the knowledge behind them must survive changes in people, suppliers and software.

An organisation needs to retain control of the Commitments made in its name and the knowledge required to carry them out.

It needs to know what was promised, why the promise was justified and who can change it. That knowledge must remain usable when people leave, a supplier changes its terms or a software product is replaced.

This is the practical meaning of custody. The organisation remains able to understand and govern its own operation across changes in the technology it uses.

The question of what to build or buy follows from that requirement.


What Ownership Is For

Boston Consulting Group’s contribution to its 2026 M&A report, How Non-AI Companies Win at AI Dealmaking, evaluates capabilities through two questions: how much they differentiate the business and how readily they can be obtained.

Its framework distinguishes four routes. Adopt capabilities that are widely available and offer little differentiation. Partner where access requires tailoring and ownership adds little value. Build where assets already under the company’s control can turn available technology into an advantage. Buy where a scarce external asset requires ownership to secure that advantage.

Here, buying means acquiring an asset or company. It is a different decision from subscribing to a software service.

The framework helped clarify my own question. Which parts of an organisation’s understanding must remain under its control, whatever arrangement it uses to obtain the technology?


Where the Business Crosses System Boundaries

Return to the pricing offer from the previous essays. The customer record may sit in a CRM. Invoices may sit in a finance system. The work required to deliver the service may be managed somewhere else.

Each system has a useful role. The Commitment crosses all three.

Someone has to preserve the connection between the offer accepted by the customer, the delivery obligation and the resulting charges. Exceptions need to remain visible where they affect another team’s work. A changed delivery date has consequences even if it is first recorded in only one system.

In many organisations, people carry these connections. They reconcile spreadsheets, explain a customer exception in a meeting and translate a decision into several incompatible records. Some of that work requires judgement. Some is repeated reconstruction of information the organisation already holds.

An AI interface can make a particular system easier to use. The organisation still needs to establish how the information inside it relates to obligations elsewhere.

That is the architectural question behind custody.


What the Organisation Must Be Able to Do

Custody has to be demonstrated through ordinary operations.

The organisation must be able to retrieve the current Commitment and the evidence on which it rests. It must know which record governs when copies disagree. It must control who can act on that record and who can revise it.

It must also be able to move the relevant knowledge when circumstances require it. A useful export preserves relationships, versions and explanations well enough for a replacement system to interpret them. A file containing disconnected rows may preserve data while losing the meaning needed to continue the work.

Access controls matter just as much as portability. The ability to retrieve organisational evidence does not give every participant a right to every record. Customer information, confidential deliberation and personal learning require their own boundaries.

These requirements can be met through hosted services, internal software or a combination. The arrangement needs to provide usable control in practice. Ownership of source code alone establishes little about whether an organisation can maintain the system or recover its history.


The Cost of Keeping Control

AI-assisted development can reduce the effort of creating software. An organisation considering an internal build still takes responsibility for operating it.

Someone must maintain permissions, repair failures and preserve records through migrations. Someone must keep the system aligned with changes in the business. Those responsibilities continue after the first useful version is delivered.

An established vendor may be the better choice where the requirements are standard and its service meets them dependably. A custom component may be justified where a distinctive operating rule is poorly served by available tools. A partnership may provide capability the organisation could not reasonably sustain alone.

The decision should include the continuing cost of ownership and a credible way to change course. Otherwise a company can reproduce the dependency it wanted to remove, this time inside software it commissioned itself.


The Same Test Applies to Reflective

These requirements also constrain what we build at Reflective Labs.

An organisation using our systems should retain authority over its Commitments and access to the reasoning and outcomes it is entitled to keep. Permissions must remain meaningful. Changes to a model or application must preserve the history on which people rely. Any promise of portability has to be tested with an actual transfer.

Those are product requirements we must demonstrate as the systems develop. Describing an organisational heart creates an obligation to make its continuity dependable.

The approach can be incremental. A company can begin with one consequential decision that crosses existing systems. It can establish the governing record, the owner and the evidence needed for that decision. It can then test whether the arrangement reduces reconstruction and makes later revision easier.

This provides a concrete basis for deciding what to keep, what to integrate and what to replace.

Custody preserves the organisation’s ability to use its experience. The final essay examines when that experience has actually become Organisational Learning.


Core thesis: An organisation retains custody when it can govern its Commitments, recover their meaning and carry its knowledge across changes in people and technology.

The idea you can't unsee: An export can preserve the records while losing the relationships that make them usable.

Vocabulary shift: "build versus buy" → "demonstrable control and continuity"

Connects to: Article 3 (When a Hundred Agents Hold a Hundred Versions of the Business), Article 5 (How an Organisation Remembers What It Learns), Article 3 of The Organizational Capability (From Workflows to Intent)

Version: 1.1 / 2026-11-07