Which level keeps your data?

Every AI system produces data as people use it: the questions they ask, the answers they correct, what they do next. Whether that data works for you later depends on the level you build at. On a subscription much of it stays with the vendor. At Level 4 all of it is yours to analyze.

Dušan StamenkovićFounding & Managing Partner · AI Practice LeadPublished 22 October 2026 · 2 min read · Cross-industry · Levels 1–4

01

The data nobody planned for

Projects plan for the data that goes in. The more valuable data is what comes out of use.

—

Questions:what people need, in their own words, including what no system answers yet.

—

Corrections:where an expert changed an answer, and why.

—

Decisions and outcomes:what was decided with the system’s help, and what happened next.

—

Usage:who uses what, when, and where they give up.

—

Definitions:terms the business had to agree on before the system could answer.

02

What doesn’t compound

—

More of the same records. A tenth year of transactions adds less than the first.

—

Raw logs nobody owns or reads.

—

Data you aren’t allowed to use for a new purpose.

03

Level by level

LevelWho keeps the data from useWhat you can do with it
1 · SubscriptionThe vendor, under its termsRead the usage reports the vendor chooses to show
2 · ConfiguredYou keep your knowledge base; usage data is what the vendor’s admin tools exportImprove your own pages and rules from what people ask
3 · No-codePartly you: run logs and outputs of your own workflowsCount, compare and fix workflows, within what the platform exports
4 · Custom buildYou, completelyEverything in the next section

04

What Level 4 lets you do with it

—

Statistical tests:did a change make the answers better, for whom, and is the difference real?

—

Behavior and usage analysis:where people get stuck, and which features carry the value.

—

Network and graph analysis:how documents, decisions and teams connect.

—

Documents and conversations into tables,then new prediction models on top.

—

Machine learning and computer visionon operational data such as machine signals or product images.

—

Continuous improvement:each release measured against the last on the same test set.

05

Choosing the level

The level is chosen first by what the answers have to do, as in our pillar on the four levels. Who keeps the data is a second question, asked at the same time: if this system’s data could feed the next one, count it.

Sometimes that moves the decision up a level. Often it doesn’t: a subscription that pays back this year beats a build that might compound in three.

06

Before you sign or build

01

Name the data the system will produce as people use it.

02

Decide who owns it, and who acts on it.

03

Check what the contract or the platform lets you keep and export.

04

Choose the level that keeps what you need, and price it.

Practice Notes · for CTOs and tech leadsMore in Insights →

Ask which level keeps the data you need.

Schedule a call with a partnerFree until 11 December