The idea in one minute
- 1Every AI tool sits on one of four levels of build: the subscription as bought, the configured subscription, the No-Code Track, and the Custom Build Track.
- 2Most of the value of the seats companies already pay for sits at Level 2, the configured subscription, and it is the level most skip.
- 3Choose the level for each tool, not once for the whole company. Who hears the answer, how many sources it depends on, and what a wrong answer costs decide it. A custom build is right when the goal requires it, or when it pays over the full lifetime cost.
01
Build or buy is the wrong first question
An elevator has four buttons. Most companies step in, see that the button for floor 1 is already lit, and reach straight for 4. Floor 1 is the AI subscription they already pay for. Floor 4 is a custom-built system. Floors 2 and 3, configuring that subscription and letting teams build their own tools, never get pressed.
Companies, and enterprises most of all, look at an AI investment as a choice between those two options. Nothing in between. The industry measures it the same way.
76%
of enterprise AI use cases were counted as bought in 2025. The survey sorts every use case into bought or built.
By the time a company asks me build or buy, it has usually already bought: seats for whole departments, used as an empty chat window. What leadership plans to build next is often something those seats could do once configured, or something a team should build itself.
The first question is not build or buy. It is which level each tool belongs on.
02
Four levels, one ladder
They differ in who does the work, what gets built, how many sources an answer depends on, who catches a wrong answer, and what kind of cost they carry.
Times to build are for one team’s first version. At Level 2 the time goes into connecting sources, access, permissions and rules. Across an enterprise, rollout depends on scope.
The dividing line
Who catches a wrong answer? At the first three levels, a person reads the answer before it is used. At Level 4, the answer often reaches a customer or changes a record first. That, and how many sources an answer depends on, separate the levels more than anything else.
Each level also depends on the one below it. No-Code tools use the connections and permissions set up at Level 2. Custom systems are easiest to adopt when employees can reach them from the Level 2 workspace they already use. Skipping a level usually means building its parts later, inside a more expensive project.
Who keeps the data from use is the question most companies ask last. It decides what one system can pass on to the next. More in Which level keeps your data? and The model isn’t your moat. The loop is.
03
Level 1: the subscription as bought
Most companies are here. Microsoft alone reported more than 30 million paid Microsoft 365 Copilot seats in its July 2026 results. Enterprise seats across the main vendors list at roughly $20 to $30 per user per month on annual plans, as of Q3 2026.
The gap between access and use · US employees
At Level 1, the assistant is an empty chat window. It knows nothing about the company unless someone pastes it in, and its value is limited by what each person knows to ask.
Level 1 pays for itself per seat almost immediately. The company only sees that return when the saved time goes somewhere.
36min
a month is all a $30 seat must save, when an hour of that person’s time costs $50.
Source: Prosperaize calculation42%
of frontline employees who use AI regularly save eight hours or more a week.
Source: BCG, 202666%
of them get limited or no guidance on what to do with that time.
Source: BCG, 2026Gave AI’s impact on their productivity the top rating · US employees
Almost three times as many give it the top rating once the use comes with a plan and a manager behind it.
Source: Gallup, July 202604
Level 2: the configured subscription
Level 2 is the same subscription, set up as a company AI workspace. It comes from four pieces of ongoing work:
- 01Connections to where company documents and records live.
- 02Permissions on who can reach what through the assistant.
- 03Onboarding that gives each role a short list of uses tied to its weekly work.
- 04Company knowledge kept current, with one owner per domain and one authoritative version of each document.
This is where most of the value of the seats sits.
Points added to the share of regular users reporting measurable impact
Only about a third of employees felt they had been trained enough.
Source: BCG, AI at Work 2026, 17 marketsTwo decisions at this level are hard to change later.
Level 2 needs an owner and a budget line, because none of it ends.
A common Level 2 use: enterprise AI search over company knowledge →05
Level 3: the No-Code Track
On the No-Code Track, business teams build specific tools themselves, on data that already exists. They do it in one of two ways: with no-code builders such as Copilot Studio or n8n, or with AI coding assistants that let someone who knows the work write a small program. Examples from different functions:
The tool costs are subscriptions for the builders or coding assistants, model usage, and metered calls into the systems a tool uses. On Copilot Studio’s pay-as-you-go rate, a prompt grounded in company data costs about 12 cents, and nothing for employees who already hold a Copilot seat.
The real cost is ownership. A tool written as code adds the obligations of software: someone who can review it, tests, and a place to run it that IT knows about.
43%
of breached organizations had security incidents involving AI tools employees use without approval, up from 20% a year earlier.
06
Level 4: the Custom Build Track
At Level 4, engineers build, test and run production systems. In the right cases, it is the AI investment with the largest return.
Requirements
- Customers hear the answer
- The AI goes into a product you sell
- The answer has to reconcile several systems that disagree
- The system writes into your records
- Your data is not allowed to go to a cloud assistant
Economics
- Seats for large groups who use the assistant only occasionally
- Metered usage at millions of prompts
- An asset competitors cannot buy
Level 4 for privacy and scale
Sometimes the custom build is the assistant itself: a private assistant on your own cloud or on-premises, with the same connections, permissions and rules as Level 2. It is worth it when the data can’t leave your environment, when you need independence from one vendor, or when tens of thousands of seats cost more than running your own.
ChatGPT Enterprise, Claude and Copilot: when to configure them and when to run your own →From my work before Prosperaize
On an e-procurement platform, the client asked for a recommender that matched suppliers to tenders. Before it could work, I had to build two systems nobody had planned: one for structured tender descriptions and one for supplier profiles. The feature was the recommender. Most of the work was the data it needed.
From our own work
Level 2 · Case study 04We gave up a three-month custom build of our own. The configured workspace that replaced it brought two-hour proposals and 15-minute onboarding.The same rule, applied to ourselves.
Custom investments start in two ways. Some grow out of a lower level, when a No-Code tool or a subscription agent outgrows it. Others start custom from day one, because the AI goes into a product, large-scale use is expected from launch, or the problem is one no subscription can reach.
Either way, the decision is made on the full lifetime cost, including maintenance. You either keep paying a vendor, build an internal team, or start with a vendor and plan the handover to your own team. If you want the capability in-house, write the handover into the vendor contract from the start.
That is why it is built only when the numbers hold, and tested before it is built.A common Level 4 use: AI product development, inside what you sell →How we prove a build first →
07
Choose per tool, not per company
Choose the level for each tool, not once for the company. Most companies end up with tools on all four levels at the same time. Five questions decide it.
Who hears the answer?
How many sources does it depend on?
What does a wrong answer cost?
Does it read or change records?
Can the data go to a cloud assistant?
Two more signals help between Levels 2 and 3. If the same role asks the same structured question many times a week, it is a candidate for a No-Code tool. If the answer depends on structured data rather than documents, it usually needs one.
The same use case can sit on any level. Usually one fits best, and the answers above decide which.
One use case, four levels
Filled: where it usually sits. Dashed: where it sometimes does. Each use case links to its page.
08
Does it pay at that level?
One test, every level
The decision a tool improves, times how often that decision is made, has to be worth more than what the tool costs plus what its wrong answers cost.
What the tool costs depends on the level:
Say an account manager’s renewal brief saves one lost renewal a year. The No-Code tool behind it costs a few subscriptions and usage fees, plus a few days of someone’s time to build. It passes easily.
How much analysis to do before investing, and how much testing before relying on the result, also depends on the level:
09
Every level needs an owner
Each tool needs a named owner and a place on one company-wide list: what it does, which decision it supports, which data it uses, who uses it, and when it was last checked. The list is also where you notice a tool that has started to need a higher level.
Before a tool is built, get three people into one room:
Agree on what gets built, what data it needs, how complex it is, which level it belongs on, and how to get the most performance for the cost and the risk.
10
Is this for you?
This is for leaders deciding where to put the next AI budget: which tools to configure, which to let teams build, and which to fund as a custom system.
If the AI budget exists because the board asked for one, start by listing the decisions you want to improve. The levels only help once there is a decision to place.