AI ROI: What Fortune 100 Procurement Leaders Are Seeing

Subscribe For Updates

Uncover negotiation leverage and unlock savings across your IT spend.

Enterprise AI spend is growing up fast, and some of the growing pains are starting to hurt.

In a recent conversation with 15 IT procurement leaders from Fortune 100 companies, NPI asked what they’re seeing as AI moves deeper into enterprise operations. The discussion covered ROI, consumption commitments, hardware costs, new commercial models and the skills procurement teams need as AI buying accelerates.

What we heard was less about where AI might be headed and more about what’s happening right now. Commitments are being burned through months earlier than expected. Discounts are disappearing when usage exceeds forecasts. Vendors can’t always explain what drives the bill. Hardware orders placed ahead of price increases are being repriced anyway.

At the same time, procurement teams are finding some approaches that work. Here are seven takeaways that stood out.

1. AI ROI is Still Pretty Fuzzy

Everyone wants to talk about AI ROI. Measuring it is a different beast. About 53% of the procurement leaders in our discussion said their organizations are tracking AI usage, while 40% are beginning to connect usage with output.

The biggest obstacle? Nobody defined the desired outcome at the beginning. When asked about their biggest ROI measurement challenge, 40% pointed to undefined outcomes, 27% lacked a baseline and 20% said they couldn’t isolate AI’s impact.

There’s also a cost problem hiding in the ROI equation. Token and consumption spend get most of the attention, but they’re only part of the bill. AI adoption can bring additional infrastructure, governance, security and control costs with it. As one procurement leader pointed out during the discussion, that adjacent spend is often missing from the ROI math.

For procurement, that puts more weight on the questions asked before the purchase:

  • What outcome are we trying to achieve?
  • What does the process cost today?
  • How will we measure improvement?
  • What other costs will this AI investment create?

If those answers don’t exist going into the deal, proving ROI later gets a lot harder.

2. The Best AI ROI Stories Are Surprisingly Small

One of the clearest ROI examples shared during the discussion didn’t involve a sweeping AI transformation.

An accountant built an agent using Claude and Copilot to replace a manual month-end accrual consolidation process. The task had taken roughly 10 hours each month. Now AI generates the output and the employee validates it, and the approach has been rolled out across the accounting team.

The math works because it’s simple. There was a defined task, a known amount of labor and a measurable change after AI was introduced.

The idea also came from an internal contest for the best AI use case, which points to something procurement leaders may want to consider. Instead of chasing an enterprise-wide answer to “What’s our AI ROI?”, look for repeatable workflows where the before-and-after comparison is obvious.

Those smaller wins can give organizations the evidence they need to make smarter decisions about where AI investment should go next.

3. A Two-Year AI commitment Could Be a Five-Month Problem

Companies are learning the hard way that overages need as much negotiation as anything else in the AI contract.

One company signed a two-year AI consumption commitment in mid-March. By August, it was gone. Once the committed volume was exhausted, the negotiated discount went with it. The company found itself back at the negotiating table, except this time the vendor knew exactly how much the customer was consuming.

Another participant described dealing with a similar issue.

This is where AI commitments can get dangerous. The discount may look attractive at signing, but if the consumption model is wrong, the customer can end up renegotiating with established usage, dependent users and very little time.

One procurement leader described another twist: after the company exceeded its commitment, the vendor treated the higher consumption level as the new baseline. There was no additional discount for the added volume because that growth was now considered expected.

The takeaway for procurement is important: negotiate the overage as carefully as the commitment.

Before signing, know what happens when consumption reaches 100%, 120% or 150% of forecast:

  • What rate applies?
  • Does the original discount survive?
  • Are there predefined growth bands?
  • What triggers a renegotiation?

With AI, the scenario you thought was an edge case can arrive surprisingly fast.

4. If Your Vendor Can’t Explain the Meter, Don’t Bet Big on the Forecast

AI pricing models are introducing a growing collection of tokens, credits, agents, hosts and consumption units. Understanding what actually generates a charge can be harder than it sounds.

One procurement leader spent more than two hours with a vendor trying to determine which agent classes carried a cost. The vendor couldn’t provide a satisfactory answer. Its own portal AI also calculated a host count roughly twice the customer’s actual engineering population.

The eventual solution was refreshingly practical: run it live for a month and see what gets billed.

That may be a useful model for other AI buyers. If the billable unit is unclear, a three-year forecast built on that unit isn’t going to become more reliable just because the spreadsheet is detailed.

Push for a pilot, measurement period or short-term arrangement that lets you observe real consumption before making a major commitment. Better usage data can be worth far more than a bigger discount against the wrong forecast.

5. Buying Hardware Early May Not Protect Price

You can’t talk about AI without talking about hardware.

One procurement leader described placing hardware orders early specifically to get ahead of announced price increases. The strategy made sense. The problem was that the orders weren’t fulfilled. The customer was eventually told the equipment would not be delivered unless the orders were repriced and resubmitted.

That raises an important question for any procurement team trying to buy ahead of hardware inflation: Does your price protection survive until fulfillment?

An early PO doesn’t necessarily protect the budget if the supplier retains the ability to reprice before delivery. With AI infrastructure demand putting pressure on parts of the hardware market, buyers need to look closely at how long quoted prices are valid, what happens when fulfillment is delayed and which contractual protections actually lock the price.

AI spend is much bigger than the AI invoice. Hardware, infrastructure and other adjacent costs belong in the conversation too.

6. Traditional Volume Discounts Are Harder to Apply

AI also creates an awkward question for procurement: what do you negotiate when volume itself is difficult to predict?

Some companies are looking beyond traditional volume discounts. In our discussion, 60% of participants said they’re exploring value-based commercial structures to address AI-driven cost increases.

Value-based models aren’t automatically better for the buyer. They require clear definitions, measurable outcomes and firm boundaries around how much value the vendor gets to capture. Procurement also needs finance and the business involved early enough to agree on those terms.

But as AI pricing becomes more consumption- and outcome-oriented, procurement teams will need more options than “buy more, get a bigger discount.”

7. Procurement Teams Are Learning AI By Doing AI

The final topic was talent, and one result stood out: roughly 85% of respondents identified AI fluency as the biggest area their teams need to develop.

One organization created a procurement AI committee staffed by employees already enthusiastic about AI. They’re building prompt libraries, demonstrating use cases and teaching their peers. Other companies have created AI champion programs, run hackathons and agent-building training, and added AI skills and tool knowledge to procurement job descriptions.

Some are going further, including AI usage in performance metrics or hiring roles specifically focused on AI tooling within procurement operations.

There’s a lesson here for procurement leaders trying to figure out how much AI training to buy. Some of the strongest examples we heard were homegrown.

Give people access to the tools. Give them real procurement problems to solve. Then create a way for the people finding useful applications to teach everyone else.

The next AI deal will benefit from what buyers are learning now

What made this conversation interesting wasn’t a big prediction about where enterprise AI is going, but the specificity of what procurement teams are encountering today.

A two-year commitment can disappear in five months. A vendor may struggle to explain the unit it wants you to commit to. Buying hardware ahead of an increase may not protect the price. And some of the easiest AI ROI to prove may come from an accountant automating 10 hours of monthly work.

These are the growing pains of a market where adoption is moving faster than many of the commercial practices around it.

For IT procurement, that makes the learning happening right now especially valuable. Test consumption assumptions before making large commitments. Negotiate what happens when the forecast is wrong. Define the outcome before trying to calculate ROI. Look beyond the AI invoice for the true cost. And give procurement teams room to experiment with the technology themselves.

Subscribe For Updates

Uncover negotiation leverage and unlock savings across your IT spend.

A Blueprint for AI Cost Control: How to Negotiate Smarter Agreements, Avoid Overspending and Accelerate ROI

Subscribe For Updates

Uncover negotiation leverage and unlock savings across your IT spend.

Join technology and sourcing experts from Crosslake and NPI for a practical look at how companies can build an end-to-end approach to AI cost control. From sourcing, price benchmarking and contract terms to FinOps, architecture and cost governance, this session will explore the decisions that determine what AI ultimately costs and how effectively it scales. Attendees will walk away with a practical blueprint for moving from AI experimentation to sustainable production without letting costs, risk or complexity get ahead of the business.

What you’ll learn:

  • How to approach AI sourcing and vendor negotiations, including pricing benchmarks, commercial models and contract terms that can materially affect long-term costs 
  • How architecture and technology decisions influence AI consumption, scalability and total cost as workloads move from experimentation into production
  • How to establish FinOps practices, cost governance and accountability to provide greater visibility and control over AI spend
  • How to connect procurement, technology, finance and governance into a practical AI cost-control framework that accelerates ROI
Subscribe For Updates

Uncover negotiation leverage and unlock savings across your IT spend.

6 Questions Every IT Procurement Leader Should Be Asking About Shadow AI

Subscribe For Updates

Uncover negotiation leverage and unlock savings across your IT spend.

For years, the conversation about Shadow IT was fairly straightforward: employees found a piece of software they wanted, signed up without going through the normal approval process, and created a visibility and governance problem for IT and procurement.

Shadow AI is making that problem much harder to spot. Today, AI doesn’t necessarily enter the enterprise through a rogue application or an unfamiliar supplier. It can arrive as a new feature from a vendor you’ve worked with for years. It can show up as an AI SKU added during a renewal, a consumption meter inside an existing cloud account, or an agent an employee builds on an approved platform. In many cases, there’s no new supplier, purchase order or sourcing event to alert procurement that something has changed. That changes what IT procurement teams need to look for and, just as importantly, how they manage AI spend.

What Is Shadow AI?

Shadow AI is the use or deployment of AI capabilities without adequate visibility, commercial oversight or governance. The important word here is capabilities. An enterprise may have approved a vendor or platform without fully understanding every AI capability being activated or created within it.

There are two primary paths. The first is vendor-driven AI, where an approved application introduces a new AI feature, pricing meter or commercial model. The second is employee-built AI, where employees use approved platforms to create agents, applications and automations of their own. The entry points are different, but both can leave procurement without a clear view of ownership, permissions, data use, pricing, monitoring and business outcomes. That’s why Shadow AI is, first and foremost, an inventory problem.

Why Traditional Procurement Controls Can Miss AI Spend

Most procurement processes are designed around recognizable commercial events. A business unit wants new software. A vendor needs to be onboarded. Someone submits a purchase request. A contract comes up for renewal.

AI increasingly bypasses those triggers. In our recent webinar, Welcome to the Era of Shadow AI: What Can Procurement Do About It?, we identified five common entry points: embedded AI within existing SaaS applications, AI SKUs and credits introduced during renewals, model and agent services consumed through cloud accounts, APIs purchased by engineering teams, and employee-built agents created on approved platforms.

The common thread is that the vendor may be visible while the AI capability is not. That creates a new challenge for procurement. You can have an approved supplier, negotiated contract and established purchasing process and still lack a complete picture of how AI is being used and what it is costing.

AI Pricing Makes the Visibility Problem More Expensive

AI also introduces a growing number of ways to charge. Depending on the supplier and product, enterprises may encounter per-user licenses, tokens, credits, actions, conversations, premium editions, add-ons and other consumption measures. Several of those meters can exist within the same supplier relationship.

Salesforce Agentforce offers a useful example. Its commercial models have included $2-per-conversation pricing, Flex Credits priced per action, and per-user licenses and add-on editions. Meanwhile, Salesforce increased pricing for some broader editions, citing additional value from AI capabilities.

For procurement teams accustomed to benchmarking seats and subscription rates, the job now includes understanding the meter itself. What generates consumption? Who can generate it? How quickly can usage grow? Where does it appear on the invoice? Can the organization forecast it? What happens when the vendor changes the commercial model? Those questions need answers before usage scales.

Procurement Has More Leverage Than It May Think

The fact that AI features are arriving through existing suppliers doesn’t mean enterprise customers have to accept every change on the vendor’s terms. A complete veto over a SaaS provider’s product roadmap is unlikely, but there are more practical protections that procurement teams are successfully negotiating.

NPI has seen enterprise customers negotiate no-training provisions for customer data, prior written consent requirements for vendor use of generative AI, and notify-and-explain provisions covering new AI features or changes. Supporting protections can include audit rights, AI price caps, exit rights and termination rights for material changes.

One particularly useful approach is requiring vendors to provide advance notice to designated customer contacts when they introduce a new AI feature, change an underlying model, alter how customer data is handled or change the associated fees. Procurement can also push for new AI capabilities to remain off and incur no fees until the customer chooses to activate them. That gives sourcing teams something they badly need in the AI market: time to evaluate a change before it becomes the new normal.

Employee-Built Agents Create Another Procurement Blind Spot

Vendor-driven AI is only half of the issue. Employees can now build apps, agents, copilots and skills in a matter of hours. These tools may read data, write to systems, send information, trigger workflows or even approve actions. An organization can approve the platform used to create an agent without ever reviewing the individual agent itself.

For procurement, the relevant question is expanding from “Which AI tools are employees using?” to “Which AI capabilities and agents can access our systems, data and business processes?” An enterprise AI agent registry can help close that gap by documenting the owner, approved data sources, permissions, security testing, usage monitoring, recertification requirements and a kill switch for each agent.

The goal shouldn’t be to count how many agents the company has deployed. A better measure is whether those agents are part of governed workflows tied to defined business outcomes, with clear decision rights and human approval where it matters. The webinar illustrates this with a procurement workflow spanning spend intelligence, sourcing, risk and contract agents, followed by a human decision gate and measurement of business outcomes.

Procurement Needs Visibility Across the Entire AI Supply Chain

There’s another reason supplier-level visibility is no longer enough: the company named on the contract may represent only one layer of the AI service. Behind that vendor can sit model providers, cloud infrastructure, data and retrieval services, orchestration layers, monitoring tools and other dependencies. Each can affect cost, data handling and commercial risk.

Procurement therefore needs to understand the full AI supply chain: vendor of record, underlying model providers, cloud infrastructure, data paths and retention, pricing meters, change-notice rights, and exit and portability provisions. If an underlying provider changes its pricing, terms or availability, the cost of an AI application can change even though your organization hasn’t signed a new agreement.

6 Questions IT Procurement Leaders Should Be Asking About Shadow AI

A useful test is surprisingly simple: If one of your vendors tripled your AI bill next quarter, would you know before the invoice arrived? If the answer isn’t an immediate yes, start with these questions:

1. How many vendors are charging us for AI? Include embedded AI, add-ons, cloud services, APIs, departmental purchases and expense channels.

2. Where is our AI spend occurring today? Break it down by vendor, business unit, deployment path and purchasing channel.

3. Which costs are consumption-based? Identify whether you’re paying by tokens, credits, actions, conversations or another measure.

4. Where are we paying for overlapping capabilities? Map what your assistants and agents actually do rather than looking only at vendor names.

5. Who owns each AI cost and business outcome? Every meaningful deployment should have both a business owner and a commercial owner.

6. Can we forecast AI spend with confidence? Build forecasts around rates, usage and adoption, and establish thresholds that trigger review when actual consumption moves outside expectations.

These questions move the AI conversation away from a generic inventory of vendors and toward the information procurement actually needs to govern spend.

What Should IT Procurement Do About Shadow AI Right Now?

Procurement shouldn’t try to solve Shadow AI alone. Finance and FinOps can help with allocation and forecasting; IT with architecture and inventory; security and privacy teams with risk controls; legal with enforceable terms; and engineering with optimization and business outcomes. Commercial governance, however, is squarely within procurement’s wheelhouse.

That means maintaining an AI inventory by vendor, capability, owner and deployment path; normalizing different pricing meters; identifying capability overlap; creating renewal triggers when AI SKUs, models, meters or terms change; negotiating stronger contractual protections; benchmarking pricing and terms; and working with FinOps to establish budgets, thresholds and anomaly alerts.

For teams wondering where to begin, NPI recommends four priorities for this quarter: build the AI inventory, instrument upcoming renewals with AI-specific questions and approval triggers, establish baseline unit economics, and begin a recurring cross-functional review of AI spend and anomalies.

The bigger change is moving away from treating Shadow AI as something you audit periodically. AI products, usage and pricing can change too quickly for a once-a-year exercise. Procurement needs an ongoing view of what is being used, what it costs, what changed and where intervention may be required.

How NPI Helps Enterprises Get Control of AI Spend

Getting visibility into Shadow AI is only part of the job. Procurement also needs a way to turn that visibility into better buying decisions, stronger agreements and ongoing cost control.

NPI helps enterprises do that in two ways. AI Agreement Optimization is designed for organizations approaching a specific AI purchase or renewal, combining consumption analysis, forecasting, pricing benchmarks, contract intelligence and negotiation support to help clients buy the right amount of AI at the right price and terms. NPI’s AI FinOps Managed Service provides ongoing analysis across an organization’s AI vendors, including consumption trends by vendor and business unit, optimization recommendations, invoice validation, renewal support and benchmarking against peer organizations.

Together, these services help procurement teams move from trying to piece together where AI spend is coming from to having the intelligence and ongoing oversight needed to manage it as it grows.

Watch: Welcome to the Era of Shadow AI

Shadow AI is already inside most enterprises, and the challenge now is finding it early enough to govern the commercial impact. In our webinar, Welcome to the Era of Shadow AI: What Can Procurement Do About It?, we dig deeper into how AI is bypassing traditional procurement controls, where hidden spend and risk are emerging, what contractual protections enterprise customers are successfully negotiating, and how procurement can build a more effective operating model for AI governance.

If you’re responsible for IT sourcing, software renewals, AI agreements or technology spend, it’s worth watching.

Subscribe For Updates

Uncover negotiation leverage and unlock savings across your IT spend.

Understanding Microsoft’s AI Commercial Model: Copilot Pricing, E7 & Azure Implications

Subscribe For Updates

Uncover negotiation leverage and unlock savings across your IT spend.

Microsoft’s approach to workplace AI is changing. What began as a per-user subscription is now a hybrid model of seats and consumption, with new implications for budgeting, governance, Azure commitments, and EA strategy. Join us as we talk about recent changes to Copilot pricing, Microsoft 365 E7 considerations, and how these changes affect Azure and MACC negotiations.

  • What’s changed with Copilot pricing and the cost implications for enterprise customers
  • AI cost blind spots with E7 and other products likely to make it into your next agreement
  • How Copilot consumption affects Azure commitments (MACC) and what procurement teams should consider before increasing commitments
  • Practical governance and negotiation strategies to control variable AI costs before they scale 
Subscribe For Updates

Uncover negotiation leverage and unlock savings across your IT spend.

Microsoft’s Copilot Has a New Cost Driver. Here’s Why It Matters.

Subscribe For Updates

Uncover negotiation leverage and unlock savings across your IT spend.

For years, buying Microsoft Copilot was relatively easy to understand. You bought licenses, assigned them to users, and knew what your monthly costs would look like.

That’s no longer the whole picture. Microsoft is introducing a new consumption-based pricing model for some of its most powerful AI capabilities. Instead of paying only for seats, organizations will also pay for the work AI performs. This change has significant implications for budgeting, governance, forecasting, and contract negotiations.

We recently published a SmartSpend Bulletin exploring these changes in detail. It breaks down how Microsoft’s new Copilot Credit model works, where organizations are likely to underestimate costs, and what procurement teams should be doing before their next Microsoft renewal. Here are a few of the biggest takeaways.

AI Is No Longer Priced Like Traditional Software

Microsoft 365 Copilot continues to be licensed on a per-user basis. Copilot Cowork is a different animal.

Copilot Cowork, Microsoft’s new agentic AI capability, requires a Microsoft 365 Copilot license, but every task it performs is billed separately using Copilot Credits. Those credits are also becoming Microsoft’s common billing mechanism for other AI services, including Copilot Studio, Dynamics 365 agents, Work IQ APIs, and Power Platform AI.  

For procurement teams, that means AI costs are becoming a blend of predictable subscription spending and variable consumption. Managing those two cost models requires a different approach than simply forecasting license counts.

Estimating AI Spend Is More Difficult Than It Looks

Microsoft groups AI work into light, medium, and heavy tasks, but those categories lack nuance.

The number of credits consumed depends on several variables, including the AI model performing the work, how much organizational context is being processed, the runtime required to complete the task, and the actions the agent performs across Microsoft applications.  

In other words, the cost of using AI isn’t determined simply by how many employees have access. It’s driven by how they use it and that’s the challenge most customers haven’t figured out yet – how to manage and forecast a highly volatile and unpredictable facet of Microsoft spend.

Consumption Can Add Up Faster Than Expected

One example in our bulletin models a 150-user Copilot deployment with what most organizations would consider moderate adoption.

Even under those assumptions, consumption adds roughly 75% on top of the monthly licensing costs. As usage increases, it’s entirely possible for AI consumption to rival or even exceed the cost of the licenses themselves.  

That’s one reason we encourage organizations to be cautious about making long-term consumption commitments before they have enough usage data to understand what “normal” actually looks like.

Microsoft’s AI Pricing Now Extends Into Azure Strategy

There’s another important consideration that many organizations haven’t connected yet: Copilot Credit spending also counts toward Microsoft’s Azure Consumption Commitment (MACC). For some organizations, that creates flexibility. For others, it creates pressure to forecast AI consumption well before there is enough historical data to support those forecasts.

The bulletin recommends treating early AI consumption estimates as planning assumptions rather than commitment targets. Actual usage data should drive long-term commitments, not optimistic adoption projections.  

Governance Can’t Wait Until After Deployment

Many organizations have established governance around AI security, privacy, and acceptable use. Commercial governance needs to become part of that conversation.

Who has access to agentic AI? What spending thresholds trigger alerts? Who owns a shared tenant-wide credit pool? How will the business determine whether higher-cost AI workflows are delivering enough value?

Those questions become much harder to answer after thousands of AI tasks are already running every day.

Read the Full SmartSpend Bulletin

This is only a snapshot of what’s covered in our latest bulletin:The New Economics of Microsoft Copilot: Managing Seats and Consumption. If you’re looking for a deeper dive, read the full version to learn:

  • A detailed explanation of how Copilot Credits work
  • The tradeoffs between pay-as-you-go and Microsoft’s P3 pre-purchase program
  • A cost model illustrating how AI consumption builds over time
  • The relationship between Copilot Credits and Azure MACC commitments
  • Negotiation strategies for Enterprise Agreements and Copilot expansions
  • Practical governance recommendations to help organizations stay ahead of variable AI costs

How NPI Can Help

As Microsoft shifts toward consumption-based AI pricing, procurement teams need more than licensing expertise. They need confidence that projected costs, commercial commitments, and governance strategies reflect how their organization will actually use AI.

NPI helps enterprise IT and procurement teams validate business cases, benchmark Copilot pricing and credit commitments against the market, right-size Azure and Copilot consumption commitments, and establish governance frameworks that keep AI spending visible, predictable, and aligned with business value from day one. If you have questions about Copilot pricing or have a Microsoft purchase or renewal on the horizon, let us know.

Subscribe For Updates

Uncover negotiation leverage and unlock savings across your IT spend.

Microsoft H2 2026: The Licensing, AI & Negotiation Changes That Matter

Subscribe For Updates

Uncover negotiation leverage and unlock savings across your IT spend.

Anyone negotiating a Microsoft agreement in H2 needs to prepare for a different kind of Microsoft negotiation. From July’s pricing changes and the elimination of traditional discount tiers to AI-driven licensing models, token-based consumption, Agent 365, and evolving Azure commitment strategies, the rules have changed. Join us for a briefing on what these changes mean for enterprise IT procurement teams and the strategies leading organizations are using to protect budgets and negotiate stronger commercial outcomes.

What You’ll Learn

  • How recent Microsoft licensing, pricing, and AI announcements work together to change Enterprise Agreement economics
  • What July’s Microsoft 365 pricing updates, Copilot’s shift toward token-based consumption, and Agent 365 mean for future software costs
  • Why traditional negotiation strategies are becoming less effective and where procurement teams can still create leverage
  • How leading enterprises are preparing for upcoming Microsoft renewals through demand modeling, benchmarking, and commercial strategy
Subscribe For Updates

Uncover negotiation leverage and unlock savings across your IT spend.

Why The Best AI Discount Right Now Isn’t on a Price Sheet

Subscribe For Updates

Uncover negotiation leverage and unlock savings across your IT spend.

The most useful AI pricing signal of 2026 isn’t in anyone’s rate card. It’s in frontier vendor competition. One frontier vendor is resetting usage quotas so often that developers built a website to track it. The other is rationing access to its flagship model week by week because it can’t serve the demand. That asymmetry, not list price, is where enterprise buyers should be looking. Why? Because it tells you exactly how much leverage you have and how long the window stays open.

When OpenAI and Anthropic filed for their IPOs, investors flagged the same underlying risk in both: the interchangeability of their products and how easily customers can move between them. That’s a risk for them. It’s a massive opportunity for enterprise buyers.

The Wall Street Journal has reported that OpenAI is weighing significant token price cuts specifically to win customers from Anthropic, in anticipation of Anthropic doing the same. You don’t get pricing behavior like that in a market with real lock-in. You get it when two vendors know the switching cost is low and are fighting to keep it that way.

Every quota reset, lifted rate limit, and preemptive price cut is a competitive concession. The question is whether a customer’s architecture and contracts let them capture any of it.

Don’t judge AI vendors only by who has the “best” model on paper. Pay attention to how they’re actually operating their business, because that has a bigger impact on what you’ll experience as a customer.

Independent intelligence indices put Anthropic’s newest flagship one point ahead of OpenAI’s best model. But the cost story paints a different picture. Recent cost-per-task analysis shows the OpenAI model completing equivalent work at roughly a third of the cost, and OpenAI is pairing that with unusually generous subscription quotas, frequent quota resets, and the temporary removal of rolling usage windows.

Anthropic, meanwhile, has publicly tied flagship availability to compute capacity, extending subscription access in one-week increments and stating it will restore standard access “as soon as capacity allows.” That’s not a criticism of either company. It’s market data. Capacity constraints on one side and aggressive generosity on the other mean the effective cost per unit of work can swing dramatically without a single line of the customer’s contract changing.

Per-token price comparisons miss the point. A model that costs more per token but resolves a task in fewer steps can be cheaper. A model that’s cheaper per token but locked behind tight quotas can be more expensive once your teams hit the ceiling and shift to premium API rates.

The unit that should drive vendor decisions is cost per task completed at acceptable quality, measured on your own workloads. That’s the number that reveals whether a two-point benchmark gap is worth a 3x cost difference. In most enterprise workflows, it isn’t.

Make substitutability real. Interchangeability only creates leverage if you can act on it. A routing layer or model gateway that lets you shift traffic between vendors, and down to cheaper tiers, turns “we could switch” from a bluff into a credible negotiating position. NPI’s deal reviews show routing to the right model, not just the cheapest one, is driving 40–85% reported bill reductions.

Don’t lock long into a price war. If frontier pricing is about to fall, a three-year commit at today’s rates is a losing trade. Favor shorter terms and negotiate repricing protection or benchmark-triggered rate reviews for anything longer.

Contract for the volatility you’re seeing. Quota policies, rate limits, and model availability are changing week to week. Push for model-change protection, granular consumption reporting, hard spend caps, and data portability so that operational changes on the vendor side don’t quietly reprice your deal.

Time renewals to competitive events. A renewal that lands while your incumbent’s rival is publicly cutting prices and lifting limits is worth more than the same renewal six months earlier. Track the competitive calendar the way vendors track your fiscal year end.

Treat access risk as part of the cost. The past few weeks have shown that frontier model availability can change on short notice, whether from capacity constraints or policy decisions. A stack with routing and open-weight fallback options isn’t just cheaper. It’s insulated from a risk most buyers haven’t priced in.

Vendors are competing hard for your workloads right now, and that competition is producing genuine concessions: lower cost per task, looser limits, and anticipated price cuts. But none of it accrues to buyers who are architecturally captive or contractually locked in. The savings go to organizations that can measure their real cost per task, move work between vendors, and negotiate with the data to prove both.

If you’d like to see what this looks like against your own AI vendor portfolio, we’re glad to walk through a live example. Contact us today.

Subscribe For Updates

Uncover negotiation leverage and unlock savings across your IT spend.

The New Economics of Microsoft Copilot: Managing Seats and Consumption

Download PDF

Download My Copy
Subscribe For Updates

Uncover negotiation leverage and unlock savings across your IT spend.

Microsoft’s workplace AI pricing has officially split in two. Microsoft 365 Copilot remains a fixed per-user subscription, while agentic capabilities like Copilot Cowork are billed separately through consumption-based Copilot Credits. For IT procurement leaders, this isn’t just another licensing change. It’s the introduction of variable AI costs alongside fixed subscriptions, requiring a new approach to budgeting, governance, and contract strategy.

Copilot Cowork, Microsoft’s agentic AI system, reached general availability in June 2026. Two commercial facts define it. First, Cowork requires a Microsoft 365 Copilot license as a prerequisite (list price of $360 per user per year). Second, and more consequentially, the subscription includes no Cowork entitlements at all. Every task Cowork performs is billed on top of the license, in proportion to the work performed.


The billing unit is the Copilot Credit. This is the same currency Microsoft already uses for Copilot Studio, and now the common meter across Copilot Cowork, Work IQ APIs, Dynamics 365 agents, and Power Platform AI workloads. Credits pool at the tenant level, and an organization’s total cost is the sum of credits consumed across all these experiences.


Meanwhile, Microsoft has stated its continued commitment to the per-user subscription. Copilot Chat, in-app Copilot experiences, and native agents such as Researcher and Analyst remain covered by the seat license with no incremental charge. But the direction of travel is clear: the highest-value agentic work sits on the consumption meter.

Microsoft offers two ways to buy Copilot Credits. Pay-as-you-go bills monthly at $0.01 per credit with no upfront commitment. Or organizations can prepay for a one-year pool of credits through the Copilot Credit Pre-Purchase Plan (P3). The catch? Any unused credits expire at the end of the term.

The P3 discount schedule is worth reading closely, because the headline discount is far steeper than what most organizations will actually qualify for:

The 20% discount tier requires a $3M annual credit commitment. But the reality is a typical enterprise pilot lands in single-digit discount territory. The practical implication: P3 is a commitment decision far more than it is a savings decision, and the expiration clause converts any over-forecast directly into waste.

Credit consumption per task is variable, driven by four cost components:

Microsoft does not publish deterministic per-task pricing. Instead, its Copilot Credits Guide (June 2026) frames consumption through illustrative scenarios: a light task such as a recurring weekly status draft runs roughly 70–200 credits; a medium task such as assembling a customer-meeting briefing from emails, calendar, CRM, and file context runs roughly 400–600 credits; and a heavy task such as analyzing six months of product usage data into a leadership-ready analysis exceeds 1,500 credits. In dollar terms at pay-as-you-go rates, that is roughly $1-$2 for light work, $4-$6 for medium work, and $15 or more for heavy work – per task.

Two properties of this model deserve emphasis. Consumption is userinitiated and effectively unbounded. Nothing in the license structure caps what an enthusiastic user can spend. And because credits also meter Work IQ API calls, Copilot Studio agents, and Dynamics 365 agents, the tenant level pool becomes a shared budget across workloads that are typically owned by different teams.

Consider an enterprise that has licensed Microsoft 365 Copilot broadly and enables Cowork for a 150-user population across sales, marketing, and management. Assume moderate adoption: each active user runs four light tasks, two medium tasks, and one heavy task every other month.

Using the midpoints of Microsoft’s illustrative ranges and pay-as-you-go pricing, the monthly picture looks like this:

Under these moderate assumptions, consumption adds roughly 75% on top of the license cost. That’s about $41,000 per year in usage against $54,000 in seats. Annualized consumption of roughly 4.1 million credits would qualify for only the 7% P3 tier, worth under $3,000 per year.

And these are planning-level assumptions built on Microsoft’s own illustrative figures. Actual consumption will vary with workflow complexity, and adoption curves for tools of this kind rarely stay flat. If usage doubles (an entirely plausible scenario), the consumption line exceeds the license line.

Copilot Credit spending also counts toward your Microsoft Azure Consumption Commitment (MACC), which can work for or against you depending on your position. If you have unused MACC capacity, Copilot Credits are a viable lever to reduce shortfall risk before renewal. But if you’re negotiating a new commitment, Microsoft now has another consumption stream to justify a larger MACC. The challenge is that Copilot Credit usage is still highly unpredictable.

Our advice is the same as with any Azure commitment. Sizing must be based on proven consumption data, not adoption forecasts. Twelve months of actual Cowork usage is evidence. Early-stage credit projections are assumptions, and they shouldn’t be treated as committed spend.

Microsoft has, to its credit, shipped meaningful FinOps controls alongside the meter. Copilot Credit usage is managed centrally through the Microsoft 365 admin center, where administrators can monitor spend, configure spend policies, set usage thresholds, and allocate credits across the organization. The existence of controls, however, is not the same as a governance posture.

Before enabling Cowork, organizations should have answers to a short list of questions:

  • Which personas get access, and against which sanctioned scenarios?
  • Who owns the approval path for expanding either? What spend thresholds and alerting are configured before the first credit is consumed?
  • Who owns the tenant-level credit pool when Cowork, Copilot Studio, and Dynamics 365 agents all draw from it across different budget lines?
  • How will task-level value be measured? A $5 medium task that saves an hour is a good trade, but someone must own that justification.

The organizing principle we recommend is the one we apply across public cloud sourcing generally: govern variable spend separately from predictable spend.

For organizations approaching an EA renewal or a Copilot expansion decision, the credit model changes the negotiation surface in several ways:

  • Resist bundling a credit commitment into the deal before usage data exists.
    Pay-as-you-go carries a modest price premium over P3, but at pilot volumes that premium is small, and it buys the option value of committing later against real telemetry. Optimize first, commit last.
  • Treat the P3 expiration clause as a risk to be negotiated or sized around.
    An over-forecast pool that expires is a 100% loss on the unused portion, which dwarfs a 5-10% tier discount.
  • If Copilot Credits are being positioned as MACC-eligible, insist that the forecast be labeled as an assumption and stress-tested.
    Recognize that Microsoft’s fiscal-year timing, ECIF-style incentives, and milestone structures remain available levers here just as they are in any Azure commitment negotiation.
  • Benchmark the credit economics themselves.
    Bundle pricing already discounts to $0.008 per credit in market, and as adoption data matures, fair market value for committed credit pools will become as benchmarkable as any other consumption construct.

The seat-plus-consumption model should not be treated as a pricing footnote. It is the template for how Microsoft intends to monetize agentic AI across its entire stack. Organizations that treat Copilot Credits as a minor add-on will discover the variable meter the hard way.

Organizations that put governance in place before deployment, model usage based on their own workforce instead of vendor assumptions, and delay commitment decisions until real consumption data exists will be best positioned to capture the productivity upside without taking unnecessary financial risk.

NPI works on the buy side only. We advise enterprise IT and procurement teams on Microsoft commercial strategy, grounded in fair market value benchmarking across thousands of enterprise transactions. On Copilot Credits specifically, clients engage us in four ways:

  • Exposure modeling and business-case validation. We help clients pressure-test Microsoft’s illustrative estimates against their own user populations and workflows, so the cost of enablement is understood before the first credit is consumed rather than discovered on the first invoice.
  • Fair market value benchmarking. We assess whether proposed Copilot license pricing, P3 credit commitments, and bundled constructs are competitive against comparable enterprise deals. Based on this analysis, we set defensible targets before you respond to a quote.​
  • Commitment sizing and MACC strategy. We help separate confirmed consumption from working assumptions, right-size credit and Azure commitments accordingly, and structure milestones, timing, and incentive levers so the commitment serves your adoption curve rather than Microsoft’s fiscal calendar.
  • Consumption governance. Formal governance frameworks for Copilot Credits are still emerging across the industry. NPI brings the perspective we’ve developed governing variable Azure spend to help clients think through ownership, spend policies, and thresholds for the tenant-level credit pool before enablement outpaces accountability.

Download PDF

Download My Copy
Subscribe For Updates

Uncover negotiation leverage and unlock savings across your IT spend.

Breaking the Single-Model Lock-In: What Microsoft Adding Claude to Copilot Teaches Us

Subscribe For Updates

Uncover negotiation leverage and unlock savings across your IT spend.

Microsoft now runs three separate AI model providers inside its own flagship product: OpenAI, Anthropic, and its own in-house MAI models. Here’s what IT procurement teams can learn from this: If the company with $135 billion riding on OpenAI still won’t build Copilot around one model, companies signing single-vendor AI contracts without model portability or exit terms are taking on more risk than Microsoft itself is willing to carry.

On July 15, 2026, Microsoft opened a new setting that lets non-federal customers in its Government Community Cloud turn on Anthropic’s Claude inside Microsoft 365 Copilot. That’s just the latest milestone in a rollout that started as an opt-in developer preview in September 2025. By January 2026, it had already become the default setting for most commercial cloud tenants, active whether or not their IT department signed off on it.

Anthropic’s Claude first showed up inside Copilot’s Researcher agent and Copilot Studio as an alternative to OpenAI’s models. By November 2025, Claude Sonnet 4.5, Haiku 4.5, and Opus 4.1 had also landed in Microsoft Foundry and inside Excel’s Agent Mode. Then came the bigger shift: Anthropic onboarded as an actual Microsoft subprocessor, with its models turned on by default for most commercial cloud tenants outside the EU, EFTA, and UK.

No AI Monogamy for Microsoft

Here’s what makes Microsoft’s moves genuinely strange. Microsoft owns 27% of OpenAI, a stake now valued at roughly $135 billion. The vendor has locked in rights to OpenAI’s models and technology through 2032 as part of a restructuring that also has OpenAI committing to an additional $250 billion in Azure spending (sources: The Motley Fool; Microsoft).

By any normal reading of vendor relationships, that’s about as close to a marriage as two companies get. Microsoft has equity, board influence, IP licensing, and a decade of integration work riding on OpenAI’s models. Except there’s nothing normal about Microsoft’s position.

Alongside the OpenAI stake and the new Anthropic integration, Microsoft has also started shipping its own in-house MAI models. This move has been explicitly framed by Microsoft’s own AI leadership as a path to independence from any single external lab (sources: CNBC; Forbes).

That means Copilot, the product Microsoft is betting its entire AI-productivity story on, now runs on three separate bets at once: OpenAI, Anthropic, and Microsoft’s own models. That should give every company with an AI vendor contract pause. The single most AI-invested company on earth is telling us, through its own product architecture, that no single model is safe to depend on exclusively.

Why This Matters for AI Procurement Contracts

If Microsoft, with money, IP, and years of integration on the line, still refuses to be locked into one model, it’s worth asking why so many enterprise buyers are still signing multi-year AI agreements built around a single vendor with no real exit terms attached.

According to a16z’s most recent survey of enterprise CIOs, 81% now run three or more model families in testing or production, up from 68% less than a year ago. Multi-model has become the default operating posture for large enterprises, not the exception. Yet a lot of procurement paper still hasn’t caught up. Contracts get negotiated around price, seat counts, and SLAs, while the question of what happens when the underlying model changes, gets deprecated, or simply falls behind gets left as an afterthought, if it’s addressed at all.

That gap matters more now than it did even a year ago, because the ground underneath these vendors keeps shifting. Menlo Ventures’ latest enterprise AI report shows OpenAI’s share of enterprise LLM spend falling from 50% in 2023 to 27% today, while Anthropic climbed from 12% to 40% and Google from 7% to 21% over the same stretch.

Here’s another way to read that: An enterprise that signed a single-vendor commitment in 2023 locked itself to what was then the clear market leader. Two years later, that leader’s share had nearly halved. Model quality, pricing, and even regulatory posture can all move faster than a typical multi-year enterprise contract.

Anthropic’s own announcement of the Foundry integration made an admission worth sitting with. Adopting a new model at a company already invested in Microsoft’s ecosystem traditionally meant navigating separate vendor contracts and billing systems, adding “weeks or months of procurement overhead.” Microsoft and Anthropic solved that friction for themselves by building the integration directly into the platform. Most enterprise buyers don’t have that luxury unless they’ve already negotiated it.

Contract Terms to Negotiate for AI Model Portability

None of this means abandoning Microsoft, OpenAI, or any single vendor relationship. It means treating model portability, the ability to swap the underlying AI model without renegotiating the entire contract, as a negotiating line item with the same weight as price and uptime.

In practice, that comes down to a short list of provisions worth pushing for in any AI sourcing agreement:

  • The right to substitute an equivalent model without repricing the entire contract or triggering a new procurement cycle.
  • Data and prompt portability at termination, including embeddings, fine-tuned artifacts, and logs, without egress fees designed to make leaving expensive.
  • Advance notice periods for model deprecation or version retirement, long enough to test and migrate before the old model disappears.
  • Pricing terms benchmarked against a basket of comparable models, not tied to a single vendor’s list price, so a competitor’s price move actually puts pressure on your incumbent.
  • Clear disclosure of where data actually flows once it leaves the primary vendor’s environment, since a “subprocessor” relationship like the one Anthropic now has with Microsoft still means data lands on infrastructure the primary contract may not fully cover.

Microsoft’s own move here is the best argument for why these terms belong in every AI contract, not just the ones involving frontier labs. The company with the deepest financial and technical entanglement with OpenAI still built an exit ramp into its own product.

Enterprise IT leaders negotiating Microsoft, OpenAI, or Anthropic agreements right now have more leverage to ask for the same thing than they probably realize. That leverage tends to show up most clearly once someone benchmarks the actual rates and terms on the table against what comparable buyers have negotiated.

Redmond isn’t proving that any one model is bad. Microsoft is proving that betting an entire operation on one vendor’s roadmap is a risk even Microsoft won’t take with its own money on the line. Your next AI contract should reflect the same math.

Subscribe For Updates

Uncover negotiation leverage and unlock savings across your IT spend.

Mastering AI Economics

Subscribe For Updates

Uncover negotiation leverage and unlock savings across your IT spend.

NPI's Mastering AI Economics webinar series helps procurement leaders understand AI cost models, strengthen vendor negotiations, and build governance strategies that scale with the business. Expert-led and experience-driven, these sessions are design specifically for large enterprise IT sourcing. 

Topics include:

► The Inference Economics Reckoning: Why Enterprise AI Costs Keep Rising as Token Prices Fall

► Who Owns AI Costs? Why Procurement Must Lead the AI FinOps Conversation

► Welcome to the Era of Shadow AI. What Can Procurement Do About It?

► And more!

Register for one or the entire series!

Other Events in the Mastering AI Economics Series

Subscribe For Updates

Uncover negotiation leverage and unlock savings across your IT spend.

Confessions of a Software Auditor

Subscribe For Updates

Uncover negotiation leverage and unlock savings across your IT spend.

What really happens behind the scenes of a software audit? In this session, a former software auditor pulls back the curtain on current vendor audit tactics including what triggers them, how targets are chosen, and the playbook auditors use to drive compliance revenue. Join us to learn how to spot early warning signs, protect your organization from unnecessary exposure, and turn the tables to maintain control during an audit. Whether you’re facing an active audit or trying to avoid one, these insider insights will sharpen your strategy.

Attendees will learn:

  • Common red flags and behaviors that make enterprises audit targets
  • The internal audit tactics vendors don’t want you to know
  • Proven strategies to stay audit-ready and negotiate from a position of strength
Subscribe For Updates

Uncover negotiation leverage and unlock savings across your IT spend.

Meet PRISM: How to Win the Renewal Before the Quote Arrives

Subscribe For Updates

Uncover negotiation leverage and unlock savings across your IT spend.

Most enterprise IT renewals are won or lost long before the vendor presents a proposal. Yet many procurement teams don’t begin preparing until the renewal conversation is already underway, after leverage has started to shift to the supplier.

Join NPI for an introduction to PRISM (Pre-quote Renewal Intelligence & Strategy Module), a new offering designed to help enterprise procurement teams shape renewal outcomes before the vendor ever writes the quote. We’ll discuss the costly mistakes organizations make during renewal preparation, why traditional approaches are becoming less effective in today’s supplier-favored market, and how PRISM provides the intelligence, stakeholder alignment, and negotiation strategy needed to enter renewals with a plan instead of a reaction.

What You’ll Learn:

  • Why the most important phase of any IT renewal occurs before the first vendor conversation and how suppliers use that window to their advantage
  • The most common renewal preparation mistakes that weaken leverage, create internal misalignment, and lead to unfavorable outcomes
  • Why NPI created PRISM and how it helps procurement teams uncover vendor vulnerabilities, align stakeholders, and build negotiation leverage before a quote is issued
  • The six components of PRISM and how they work together to produce flatter opening quotes, stronger negotiating positions, and more favorable renewal outcomes

Subscribe For Updates

Uncover negotiation leverage and unlock savings across your IT spend.