There’s a question circulating in procurement meetings and executive briefings right now. You may have fielded it yourself.
“If your team is using AI to do the work faster, why aren’t your fees going down?”
It’s a fair question.
Sometimes the answer should be yes. If the work is repetitive, low-risk, clearly specified, and easy to check, AI can reduce delivery cost, and a fair provider should redesign that workflow and share the gain through lower cost, faster turnaround, expanded scope, or an agreed combination.
But most strategic, analytics, data, and systems work isn’t a fixed task with a known answer. The visible deliverable may arrive faster. The work required to decide whether it solves the right problem, uses the right data, survives real conditions, and can be defended to the person accountable for the outcome doesn’t disappear.
AI lowers the cost of making a first draft. It doesn’t lower the cost of being accountable for the answer.
AI Saves Time. The Time Doesn’t Go Where You’d Expect.
The savings are real and measured.
Employees with access to enterprise AI tools save 40 to 60 minutes per day, according to Fortune’s reporting on Goldman Sachs data. The Federal Reserve Bank of St. Louis found AI users saved roughly 2.2 work hours per week. An MIT experiment by Noy and Zhang found that for knowledge workers, ChatGPT cut task completion time by roughly 40% while raising output quality by 18%.
These studies measure early adoption periods. Teams who’ve embedded AI deeply since then are plausibly saving more, though I haven’t seen a study confirming it at the same rigor, so treat that as expectation rather than finding.
The important question is what happens to the capacity AI creates.
Time savings don’t automatically become fewer labor hours, lower total cost, or better outcomes. Organizations may reinvest capacity in more work, broader scope, higher quality, experimentation, rework, validation, a faster pace, or demand that was previously deferred. The destination of the savings is a management decision, not an automatic outcome.
A UC Berkeley Haas study found that AI intensifies work rather than reducing it: people expanded scope, accelerated pace, and extended hours voluntarily, because AI makes starting a new task nearly frictionless. Workday’s research found that while most employees reported saving one to seven hours per week, a substantial share of those savings went straight back into rework.
Faster output can create more work to review, compare, correct, integrate, and govern. Whether that oversight is proportionate depends on the task, the consequence of error, the reliability of the inputs, and the controls around the workflow.
Faster Tasks Are Not Automatically Better Outcomes
Most AI productivity claims operate at the task level: how long it took to write a draft, summarize a document, produce a first-pass analysis, or generate code.
That’s useful evidence. It’s not the same as a better workflow or a better business outcome.
| Level | The question to ask |
|---|---|
| Task | Did AI reduce the time or improve the quality of a defined activity? |
| Workflow | Did the full process improve after review, exceptions, handoffs, rework, and maintenance were included? |
| Business outcome | Did the changed workflow improve a decision, customer outcome, revenue measure, risk profile, or sustainable capacity? |
A task can get faster while the workflow becomes harder to manage. A workflow can get faster without improving the decision it supports. “We saved time” is the beginning of the analysis, not the conclusion.
The Confidence Premium
AI makes it cheaper to produce plausible outputs. It doesn’t make those outputs trustworthy by default.
The work required to turn a plausible draft into a decision-ready result is the confidence premium:
- Validating source data, definitions, and business rules
- Checking whether the recommendation fits the organization’s real constraints
- Testing technical logic, failure states, and edge cases
- Evaluating assumptions, uncertainty, and alternative explanations where they matter
- Making privacy, security, accessibility, and governance decisions explicit
- Explaining tradeoffs so the accountable person can make the call
- Documenting the result so someone else can maintain, audit, challenge, or improve it
The confidence premium isn’t a justification for invisible busywork. It’s the work required to turn a fast first draft into something a person can responsibly act on.
The more consequential the decision, the less appropriate it is to treat first-pass speed as evidence of finished work.
When a Lower Cost Is Fair
AI can and should make some work cheaper.
That’s most likely when the scope is fixed, the output is standardized, the source material is approved or well governed, error consequences are low, and quality can be checked objectively or through defined spot checks.
Converting approved source material into a known reporting format. Producing first-pass documentation from reliable implementation metadata. Classifying well-labeled low-risk records. Drafting routine variations. Generating a standard transformation with established tests.
For work like that, lower cycle time and lower cost are the point, and the client should see the benefit.
Complex advisory work has a different value equation. Saved production time is often best reinvested in deeper validation, scenario testing, documentation, and decision support. That doesn’t mean charging for invisible activity. It means agreeing on the standard of confidence the work requires and making the work needed to reach it explicit.
Three Myths Worth Busting
“AI can handle the strategy now.”
AI is good at executing a clearly defined task. It’s poor at identifying which task is worth doing.
Strategy isn’t the absence of execution work. It’s the selection and sequencing of problems under real constraints: objectives, budgets, data availability, customer impact, organizational readiness, risk tolerance, ownership, and the opportunity cost of not doing something else. AI can help generate options. It can’t make those tradeoffs legitimate on the organization’s behalf.
Take data science work. AI can generate code, suggest modeling approaches, summarize research, or produce a first-pass analysis. It cannot decide whether your business question calls for a predictive model, a segmentation study, an incrementality test, or a simple descriptive cut.
Sometimes the smarter solution is the less complex one. A well-scoped regression model, cleanly explained and tied to a decision, creates more value than an impressive black-box model nobody trusts or knows how to operate. The right method is the one producing enough reliable evidence for the decision at hand, rather than the one producing the most impressive-looking output.
I regularly see organizations paralyzed by what I’d call the Paradox of Possibility: powerful tools, and no clear sense of which problem to solve first. A chatbot doesn’t close that gap. It gets closed by people who can translate statistical patterns into business decisions, tell correlation from causation, and navigate the dynamics that determine whether anyone adopts the result.
“More data input means better AI output.”
Not automatically. More data helps when it’s relevant, clean, connected, and understood. Otherwise you’ve handed the model a bigger junk drawer.
A model or workflow also needs context designed for the actual question: definitions, known exceptions, current business rules, source-system limitations, consent and access constraints, change history, and the boundaries of what the system may infer or do. A model can’t reliably retrieve context that was never captured, resolve a conflict the organization never settled, or recognize a critical exception nobody made visible.
“More data” and “better context” are not the same strategy.
Gartner’s February 2025 research put the mechanism plainly: it predicted organizations would abandon 60% of AI projects unsupported by AI-ready data through 2026, based on a survey of 1,203 data management leaders in which 63% either lacked appropriate data management practices for AI or didn’t know whether they had them. You’ll see higher failure rates quoted elsewhere, often from contributor posts or vendor material with no published methodology. I’d stick with the number that shows its work.
In client work, the time saved through drafting and code generation should be visible in what becomes possible next: more careful validation, more scenario coverage, better documentation, clearer tradeoffs, and stronger enablement. The goal isn’t faster deliverables for their own sake. It’s a result that can be trusted for the decision it supports.
“My analytics platform has AI built in, so why do I need a consultant?”
Embedded AI in tools like Adobe, Google, and Amplitude is built for the median use case. It can surface “conversions are down.” It can’t surface “conversions are down because the new consent banner was applied to your checkout flow.” Worse, these systems often won’t flag when they can’t answer your question, which creates real risk when decisions get made on a confident-sounding recommendation.
These systems generate or rank plausible outputs from the context available to them. That can be extremely useful. It isn’t the same as verifying that the output reflects your organization’s actual definitions, current implementation state, data lineage, or causal reality. A novice accepts the output. Someone who knows the implementation spots the flaw immediately.
So how do you help these tools give better answers? For consequential use cases, define the context the system may use, the source-of-truth references it should prefer, the output it’s allowed to produce, the evidence required for a recommendation, the conditions requiring human review, and the evaluation method that will reveal whether the workflow is improving or degrading.
Most organizations don’t have that yet. Gallup’s February 2026 survey of 23,717 US employees found half of employed US adults now use AI at work at least occasionally, with 13% using it daily, while only 41% reported that their organization has integrated AI tools at all. Individual adoption is running well ahead of organizational design.
What Changes
AI changes where expert hours go, not whether they’re needed.
| AI can accelerate | Still requires accountable judgment |
|---|---|
| First drafts of SQL, code, requirements, analysis, research summaries, and documentation | Whether the organization is solving the right problem |
| Candidate strategies, model approaches, scenarios, and workflow options | Which method fits the decision and which assumptions must hold |
| Schema mappings, transformations, and connector logic | Whether definitions, permissions, identities, and source logic are correct |
| Anomaly summaries and recommended explanations | Whether the explanation reflects actual change history and proprietary context |
| Routine formatting, classification, and production tasks | Testing, approval, exception handling, maintenance, and response when output is wrong |
The commercial question isn’t whether AI made one artifact faster. It’s whether someone still needs to be responsible for the decision the artifact supports. In consequential work, the answer is yes.
The capacity AI creates can be used in different ways: lower cost, faster turnaround, broader exploration, deeper validation, stronger documentation, more experimentation, or an agreed combination.
For complex work, the most valuable use is usually a higher standard of confidence. More scenarios considered, more assumptions tested, better evidence documented, fewer preventable surprises after launch.
Make that choice explicit. Don’t treat AI savings as a reason to hide reduced effort, or as an excuse to expand scope without agreement.
That’s how AI changes the value equation: less time producing a first draft, more deliberate investment in deciding whether the result is worth acting on.
When the Question Is About One Proposal
If a specific vendor is making the fee argument at you right now, the useful move is a second read on that proposal rather than a philosophical position on pricing.
Ongoing AI Advisory is a standing second opinion with a written entry for every question, so the reasoning is findable six months later. Monthly, month to month.
