For over two decades I have been working toward a single measurement: how much of an organization’s own operational data the organization actually controls. The instinct began with a 2011 product codenamed Nodelib, which the technology of the day could not support. The Autonomy Score is that idea, finally built. It rates every place a client’s data lives across the conditions of true data sovereignty, and it is now a mandatory first step in every Prospus Autonomy Engineering engagement and a first-class signal inside Kaamfu, our Autonomous Operating Environment.

---

I have been working toward this measurement, in one form or another, since 2000.

Back in 2011 I was developing a product internally codenamed “Nodelib”, short for “node liberation”. The idea was straightforward in concept but impossible to build at the time: a single layer that could see across every system an organization used, summarize what was inside each one, and tell the operator how much of their own data they actually controlled in each place. The technology was not there. The data was not portable enough, the APIs were too inconsistent, and the LLMs that now make this kind of cross-system reasoning trivial were more than a decade away. Nodelib stayed a sketch.

The instinct behind it never went away. Every product I built after Nodelib carried a piece of the same thesis: that an organization’s most valuable asset is the record of its own work, and that no operator can lead an organization they cannot see. That thesis is the same one we wrote down formally on the Kaamfu data sovereignty page, where we declared that ownership of operational data is the foundation of autonomy. Earlier I hinted at the Autonomy Score in the Workstack Control guide I published in 2024. The reality: the average organization can directly access less than 20% of the data they generate.

This week I finally put a number on it. We call it the Autonomy Score, and it is now a deployed measurement inside both Prospus, our service arm, and Kaamfu, our Autonomous Operating Environment.

What the Autonomy Score measures

The Autonomy Score is a single rating, assigned to every place a client’s data lives, that captures how well the system that holds that data supports the client’s data sovereignty.

It is built on the same conditions we publish openly as the minimum for true ownership: whether the system is the primary system of record or a thin layer over someone else’s, whether access to the data is unrestricted or rationed, whether the data is stored in clear schemas or buried in vendor-shaped formats, whether the organization can leave with the full record intact or only with a flattened slice of it, and whether the data flows in real time or arrives in batches days after the decision was needed.

A high Autonomy Score means the vendor treats the data as the organization’s. You see everything, in real time, through clean interfaces, with no negotiated tiers in the way, and you can access all of it on demand. A low Autonomy Score means the vendor treats the data as their asset to ration. You see a slice, in batches, through filters they designed, with the full record behind a paywall, a support queue, or a straight refusal.

Kaamfu scores 100 by design, because data sovereignty is a foundational architectural commitment of the platform, not a feature added on top.

What it does inside an engagement

The Autonomy Score is the first deliverable in any Prospus Autonomy Engineering engagement. Before we recommend a single change, we map every place the client’s operational data lives (what we call a “Connect” in our internal language), and we score each one. The map and the scores together produce the first honest picture most leaders have ever seen of where their organization’s record actually sits and how much of it they can reach.

From there the path forward becomes obvious. The Connects with high Autonomy Scores stay where they are, because the vendor is already treating the data as the client’s. The Connects with low Autonomy Scores become the work, either by negotiating better access, by switching to a vendor with a higher score, by setting up structural workarounds like scheduled exports, or by migrating the relevant function into Kaamfu where the data sovereignty score is 100 by default.

In Kaamfu itself the Autonomy Score is being built into the Connect infrastructure directly. Every Connect a tenant configures, whether to a CRM, a fundraising platform, a chat tool, a time tracker, or anything else, will display its Autonomy Score alongside the data it brings in. The operator sees, in one view, where their data is and how much of it they actually control. This is the dashboard I sketched in 2011 and could not build. It exists now because the underlying technology finally caught up to the idea.

Why this is a mandatory feature, not a nice-to-have

Autonomization is the terminal state of friction removal across an organization, and friction begins with the data the organization cannot reach. An AI layered on top of a low-Autonomy-Score data environment will produce confident, fluent, and shallow output, because it is reasoning on the slice the vendor decided to expose rather than on the full record. The model is not the bottleneck. The data underneath is.

This is why the Autonomy Score is mandatory inside any Prospus engagement that aims at autonomization, and why it is being built into Kaamfu as a first-class signal rather than a back-office metric. You cannot automate chaos, and you cannot automate a record you do not control. Knowing the score, system by system, is the precondition for everything that follows.

If you want to know what your own Autonomy Score looks like across the systems your team uses every day, that is the assessment we now run at the start of every Prospus engagement.

…