The Economic Times reports that AI is reshaping how enterprises categorize software spend, with per-seat subscriptions giving way to consumption, outcome, and token-based contracts. The accounting consequence will land as hard as the engineering one: enterprise AI dollars are migrating from the software line into payroll and operations budgets.

For product managers, this reclassification reshapes who holds the budget, how sales quotas are written, and where renewal risk lives.

What changes when a seat becomes a token?

A $50-per-month seat routes through a marketing or operations director. A $200,000 annual inference contract routes through the CFO's office, with procurement and security review attached. The buyer's identity, the discount ladder, and the renewal cycle all change with the line item.

When AI spend lands in the labor budget instead of software, finance teams treat it as a productivity investment rather than an IT purchase. That single reclassification shifts:

• Approval cycle: software budgets lock once a year; labor budgets flex with hiring and attrition.
• Buyer profile: a line-of-business owner can sign a $5,000 SaaS contract; a $500,000 inference deal needs CFO review.
• Renewal motion: fixed contract renewals on a calendar; consumption bills are reviewed monthly against usage.

How does this reshape the SaaS playbook?

Three questions product managers can put on the next planning document:

1. Whose budget will this product actually pull from in year one: the CIO, a line-of-business owner, or HR and operations?
2. Does our pricing model scale gracefully when usage doubles in a quarter, or does procurement push back?
3. Can we bill monthly on metered usage, or are we locked to annual commitments customers are starting to reject?

The Economic Times framing of "labor budgets" signals where financial reporting is heading before the pricing pages catch up.

What stops working in a consumption model?

Several SaaS conventions break when AI products price per inference, token, or task:

• Sales quotas tied to seats. Reps need new units. Tokens sold, outcomes delivered, or product-qualified leads replace seat counts.
• Customer success built on adoption. Underuse is no longer the retention risk; overuse is. A customer who burns through budget in two weeks will churn before the CSM notices.
• Discounting. Discounting a metered plan costs the vendor in cash, not in deferred revenue. A sales leader who cuts a 20% deal to hit number can blow through the quarterly forecast in a week.

What to redesign next quarter

Teams still on seat-based pricing for products with variable marginal cost have a narrow window. Finance, customer success, and sales ops need to move together:

• Replace ARR-per-rep with a consumption-based quota, even if the list price stays per-seat.
• Build usage anomaly alerts into the customer success platform before renewal season.
• Train procurement-facing sellers on outcome language; line-of-business sellers no longer close these deals.

The shift to labor budgets is a signal, not a verdict. Companies that read it early can re-price without re-platforming. Companies that ignore it will learn the hard way when a customer CFO cancels an "HR tool" the IT department never approved.