The Shift from Technology to Decisions
Microsoft recently convened 250 enterprise leaders at its Copilot Summit — organizations operating at the leading edge of AI transformation. The consensus was striking: AI returns are determined by the decisions leaders make, not by the technology they buy.
Two years ago, the question was “Can AI do valuable work?” That’s been answered. The question now is: How do we lead through the transformation?
Jared Spataro, Microsoft’s CMO of AI at Work, distilled five trends from the summit that every CTO and CIO should internalize.
1. Trust in AI Is Specific, Not General
Trust isn’t broad confidence in “AI” — it’s confidence in a particular system doing a particular job.
Trevor Noah reframed this with a powerful example: Johns Hopkins cancer research built an AI focused solely on minimizing unnecessary breast cancer biopsies. One dataset. One purpose. The specificity is what made it trustworthy.
Contrast that with AI agents deployed without boundaries — like the one discovered inside Hertz’s customer service that could be prompted to write code. Without edges, there’s no basis for trust.
Three Conditions for AI Trust
- Consistent performance — the system delivers reliably within its scope
- Working understanding — users comprehend how it functions
- Accountability when wrong — consequences exist and are visible
The aviation analogy resonates: people get back on planes after crashes not because of optimism, but because of FAA reports, public accounting, and demonstrated consequences. Accountability infrastructure must exist before the failure, not after.
2. Knowledge Work Demands a Redesign
Knowledge work has been ad hoc for decades. Even structured domains (legal, finance) run on vague workflows and goals that live in people’s heads.
Microsoft learned this the hard way. Their first Copilot rollout to their own sales force fell short — not because the technology didn’t work, but because they treated it like a product launch. Adoption metrics moved, but outcomes didn’t.
The result comes from redesigning the work the tool sits inside, not from giving people access to it.
This is the manufacturing revolution applied to knowledge work: measurable steps, deliberate trade-offs between human and machine labor, and tracking outcomes instead of activities.
3. The System Matters More Than the Model
For the first wave of AI deployment, the model was the decision. Organizations asked “which model?” and treated the answer as the work.
Then reality hit: the model alone isn’t enough. What matters is the harness around it:
- The data it can access
- The context it receives
- The infrastructure it runs on
- The guardrails that contain it
AI capability is a construction project, not a procurement one. The organizations pulling ahead aren’t finding better models — they’re building more deliberately around them.
This aligns perfectly with what I see in enterprise AI platform engineering: the model is 10% of the work. The other 90% is data pipelines, observability, security, cost management, and integration architecture.
4. Tokenomics Is the New Headcount
This is the headline trend — and it fundamentally reframes AI budgeting:
The relevant comparison is the cost of a human doing the same work, not a software line item.
When AI first entered organizations, leaders evaluated it against their IT budget. Tokenomics works differently. Now every leader must answer: should a human do this, or should an agent?
That calculation spans three dimensions:
| Dimension | Human | AI Agent |
|---|---|---|
| Quality | Variable, expertise-dependent | Consistent, scope-dependent |
| Time | Hours to days | Seconds to minutes |
| Cost | $50-200/hour | Declining rapidly |
The Recalibration Gap
What a task costs today won’t be what it costs next quarter. Token prices are falling 10x per year. Budget using current prices and you’ll leave value on the table.
The allocation questions are immediate:
- Who gets tokens? (Which teams, which workflows)
- How many? (Budget per function)
- For what work? (Which tasks justify AI vs human)
Most organizations don’t have infrastructure to make these decisions well. The ones that build it now will compound their advantage.
Practical Tokenomics Framework
Task: Draft contract review summary
├── Human: Senior paralegal, 2 hours = $150
├── AI Agent: GPT-4o, ~10K tokens = $0.15
├── Quality delta: AI at 85% of human quality
├── Decision: AI drafts → Human reviews (15 min = $18.75)
└── Total: $18.90 vs $150 = 87% cost reductionScale that across 1,000 contracts/month: $131K annual savings per workflow.
5. Enterprise Software Must Earn the Right to Exist
“The era of ‘I use this kind of crappy thing because I’m forced to use it’ is kind of over.” — Jacob Andreou, Microsoft Copilot
The iPhone started this trend in 2010: people experienced exceptional consumer products and carried that standard to work. For over a decade, enterprise software dodged this comparison because IT mandated tools and employees absorbed the friction.
AI closes that gap or it fails. People now have strong reference points for great AI experiences from personal use. They bring that standard to work.
Organizations that hold AI investments to consumer-grade scrutiny will:
- Build differently (UX-first, not feature-first)
- Buy differently (prove value before scale)
- Measure differently (adoption means nothing without outcomes)
What This Means for Platform Leaders
All five trends point to the same conclusion: the technology is a constant — what varies is the quality of decisions made around it.
| Trend | Action Item |
|---|---|
| Specific trust | Define AI scope boundaries before deployment |
| Work redesign | Map workflows before applying AI to them |
| System over model | Invest in platform (data, context, infra) not just models |
| Tokenomics | Build cost attribution per team/workflow |
| Earn existence | Measure outcomes, not adoption |
None of these are technical questions. They’re organizational ones. And they require deliberate leadership — not just a Copilot license.
My Take
Having deployed AI platforms across regulated enterprises, I can confirm: the technology is table stakes. What separates successful AI transformations from expensive experiments is:
- Executive sponsorship that understands this is a work redesign, not a tool rollout
- Platform engineering that builds the system around models (observability, cost tracking, guardrails)
- Tokenomics literacy at the director level — treating compute as a workforce decision
- Clear scope — AI that does one thing well beats AI that does everything poorly
The organizations I advise that are seeing 10-50x ROI all share one trait: they redesigned the work first, then applied AI to the new design. The ones struggling did it backwards.