Where the human sits: oversight, pricing, and adoption
Author:
Logan Matson
Time for reading:
5 min read
Per-seat pricing stopped describing the value
For twenty years B2B software ran on a simple equation: growth meant more employees, more employees meant more seats, and seats meant predictable recurring revenue. Agentic AI breaks the correlation. An autonomous agent does not occupy a seat. When one person with an agent does work that used to take five, headcount stops tracking the value delivered and per-seat licensing stops capturing it.
The market moved accordingly. Pure per-seat pricing fell from 21% to 15% of the market in twelve months. Outcome-based and value-based models took the share, and the shift shows up in how deals get discussed: 73% of clients now prefer value-based or outcome-driven pricing, and 58% raise pricing in the first discovery call. Federal procurement formalized it in Q1 2026, when three of ten named consulting firms offered performance-based fees as an option to retain contracts, the first time outcome pricing appeared inside a federal consulting procurement.
What replaces the seat varies by domain. Fees get tied to measurable results: a percentage of tax savings identified, deals closed, tickets resolved. The common thread is that revenue now depends on the software working in production rather than on access being granted. That is a genuine change in incentive, and it is uncomfortable for vendors whose product demos better than it deploys.
Why adoption is a people problem before it is a technical one
Measurable outcomes require that people actually use the thing, and this is where most deployments stall. Rolling out AI is not like rolling out enterprise software, because the old playbook assumed determinism. An ERP transaction returns the same output for the same input every time. A model returns probabilistic output that shifts with retraining, data drift, and edge cases. Distrust of a system that behaves differently on Tuesday than it did on Monday is not irrational resistance. It is a correct read of the system.
There is a second layer beneath that. Because these systems replicate judgment rather than automating transactions, they land on the part of the job people built a career on. A financial analyst resisting a tool may be resisting the implied message that twelve years of accumulated judgment no longer matters. Treating that as a training gap misdiagnoses it entirely.
Frameworks that work start from the individual rather than the rollout. The Prosci AI Integration Framework has people sort their own work into three buckets, which is a small move with a large effect on how the change lands:
My work. Tasks that stay human because they depend on emotional intelligence, ethical judgment, real-time improvisation, and personal connection. Naming these first establishes what is not up for automation.
With me. Tasks where the model is a collaborator. The person sets direction and the agent helps draft, research, analyze, or generate options. Higher quality output, less cognitive load, human still driving.
For me. Routine rules-based work, such as standardized reports and data organization, that can be delegated outright to free up capacity.
The sorting matters more than the categories. When someone maps their own week, the abstract threat of replacement becomes a concrete and much smaller list of tasks they were mostly glad to hand off.
The same pattern outside the enterprise
Individual adoption has run ahead of institutional adoption. By 2025, 92% of surveyed students reported using an AI tool, up from 66% the year before, and 88% had used one for assessments, up from 53%. ChatGPT led at 66% usage. That is among the fastest adoption curves any education technology has recorded.
The measured outcomes are strong. Students using personalized AI tutoring scored 54% higher on tests, and course completion rates ran 70% better than traditional approaches. A 2025 Harvard physics study found students working with AI tutors learned more than twice as much, in less time, than those in a traditional active-learning classroom.
And confidence still lags the usage, in the same shape it does inside companies. 65% of students worry that leaning on AI makes their learning shallow and discourages critical thinking, and 56% are concerned about data privacy. Only 36% received any AI skills training from their institution. High usage with low confidence and no instruction is not a success state. It is a gap.
Deciding where the human sits
Both settings point at the same design question, which is not whether to keep a human involved but exactly where. Human-in-the-loop design means a qualified person, with adequate context and real authority to act, positioned at the points in a workflow where review changes the outcome.
Placement should be calibrated to consequence rather than applied uniformly. High-consequence actions, such as financial transactions, access changes, external communications, and infrastructure modification, warrant explicit approval before execution. Confidence-threshold escalation routes work for review when the model’s own reliability score falls below a calibrated line. Audit-only checkpoints suit high-volume low-risk operations, keeping a log without gating throughput.
Uniform oversight fails in a predictable way. Ask a person to approve everything and they approve everything, which is automation complacency wearing a governance badge. The failure modes worth designing against are that, unclear ownership when something goes wrong, and guardrails brittle enough that people route around them.
The infrastructure and the economics both now point the same direction. Outcome-based pricing means the vendor is paid when the work lands, and work lands when the people around the system trust it enough to use it and understand it well enough to catch it when it is wrong. Those are the same problem.
Per-seat pricing stopped describing the value
For twenty years B2B software ran on a simple equation: growth meant more employees, more employees meant more seats, and seats meant predictable recurring revenue. Agentic AI breaks the correlation. An autonomous agent does not occupy a seat. When one person with an agent does work that used to take five, headcount stops tracking the value delivered and per-seat licensing stops capturing it.
The market moved accordingly. Pure per-seat pricing fell from 21% to 15% of the market in twelve months. Outcome-based and value-based models took the share, and the shift shows up in how deals get discussed: 73% of clients now prefer value-based or outcome-driven pricing, and 58% raise pricing in the first discovery call. Federal procurement formalized it in Q1 2026, when three of ten named consulting firms offered performance-based fees as an option to retain contracts, the first time outcome pricing appeared inside a federal consulting procurement.
What replaces the seat varies by domain. Fees get tied to measurable results: a percentage of tax savings identified, deals closed, tickets resolved. The common thread is that revenue now depends on the software working in production rather than on access being granted. That is a genuine change in incentive, and it is uncomfortable for vendors whose product demos better than it deploys.
Why adoption is a people problem before it is a technical one
Measurable outcomes require that people actually use the thing, and this is where most deployments stall. Rolling out AI is not like rolling out enterprise software, because the old playbook assumed determinism. An ERP transaction returns the same output for the same input every time. A model returns probabilistic output that shifts with retraining, data drift, and edge cases. Distrust of a system that behaves differently on Tuesday than it did on Monday is not irrational resistance. It is a correct read of the system.
There is a second layer beneath that. Because these systems replicate judgment rather than automating transactions, they land on the part of the job people built a career on. A financial analyst resisting a tool may be resisting the implied message that twelve years of accumulated judgment no longer matters. Treating that as a training gap misdiagnoses it entirely.
Frameworks that work start from the individual rather than the rollout. The Prosci AI Integration Framework has people sort their own work into three buckets, which is a small move with a large effect on how the change lands:
My work. Tasks that stay human because they depend on emotional intelligence, ethical judgment, real-time improvisation, and personal connection. Naming these first establishes what is not up for automation.
With me. Tasks where the model is a collaborator. The person sets direction and the agent helps draft, research, analyze, or generate options. Higher quality output, less cognitive load, human still driving.
For me. Routine rules-based work, such as standardized reports and data organization, that can be delegated outright to free up capacity.
The sorting matters more than the categories. When someone maps their own week, the abstract threat of replacement becomes a concrete and much smaller list of tasks they were mostly glad to hand off.
The same pattern outside the enterprise
Individual adoption has run ahead of institutional adoption. By 2025, 92% of surveyed students reported using an AI tool, up from 66% the year before, and 88% had used one for assessments, up from 53%. ChatGPT led at 66% usage. That is among the fastest adoption curves any education technology has recorded.
The measured outcomes are strong. Students using personalized AI tutoring scored 54% higher on tests, and course completion rates ran 70% better than traditional approaches. A 2025 Harvard physics study found students working with AI tutors learned more than twice as much, in less time, than those in a traditional active-learning classroom.
And confidence still lags the usage, in the same shape it does inside companies. 65% of students worry that leaning on AI makes their learning shallow and discourages critical thinking, and 56% are concerned about data privacy. Only 36% received any AI skills training from their institution. High usage with low confidence and no instruction is not a success state. It is a gap.
Deciding where the human sits
Both settings point at the same design question, which is not whether to keep a human involved but exactly where. Human-in-the-loop design means a qualified person, with adequate context and real authority to act, positioned at the points in a workflow where review changes the outcome.
Placement should be calibrated to consequence rather than applied uniformly. High-consequence actions, such as financial transactions, access changes, external communications, and infrastructure modification, warrant explicit approval before execution. Confidence-threshold escalation routes work for review when the model’s own reliability score falls below a calibrated line. Audit-only checkpoints suit high-volume low-risk operations, keeping a log without gating throughput.
Uniform oversight fails in a predictable way. Ask a person to approve everything and they approve everything, which is automation complacency wearing a governance badge. The failure modes worth designing against are that, unclear ownership when something goes wrong, and guardrails brittle enough that people route around them.
The infrastructure and the economics both now point the same direction. Outcome-based pricing means the vendor is paid when the work lands, and work lands when the people around the system trust it enough to use it and understand it well enough to catch it when it is wrong. Those are the same problem.
