惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

T
Tailwind CSS Blog
Cyber Security Advisories - MS-ISAC
Cyber Security Advisories - MS-ISAC
雷峰网
雷峰网
量子位
有赞技术团队
有赞技术团队
阮一峰的网络日志
阮一峰的网络日志
The Cloudflare Blog
博客园 - Franky
罗磊的独立博客
宝玉的分享
宝玉的分享
博客园_首页
腾讯CDC
The GitHub Blog
The GitHub Blog
D
DataBreaches.Net
IT之家
IT之家
D
Docker
Microsoft Security Blog
Microsoft Security Blog
博客园 - 司徒正美
V
V2EX
月光博客
月光博客
N
Netflix TechBlog - Medium
爱范儿
爱范儿
I
InfoQ
P
Proofpoint News Feed

informationweek

2026 tech company layoffs How Sedgwick scaled AI in legacy claims workflows InformationWeek Podcast: CTOs on using AI in regulated spaces How top CIOs are measuring the real ROI of IT automation What AI must learn from Roosevelt, conservation and 1929 Experian's chief innovation officer gleans AI gains with startup collab ETS CIO on competing with AI startups 'running with scissors' Before the next VMware: How CIOs prepare for vendor shocks The strategic alignment powering cyber-resilient organizations The AI infrastructure bottleneck is becoming a CIO problem InformationWeek Podcast: CTOs on reining in rogue AI agents Workplace equity in the age of AI Why and how to implement an AI asset rationalization strategy Why companies are shifting toward private AI models AI agents in automation: When to build, when to buy Navan CTO AI on trial: The Workday case that CIOs can The AI infrastructure boom is coming for enterprise budgets How CIOs can manage LLM costs: A practical guide What CIOs miss when buying vertical SaaS software InformationWeek Podcast: How CTOs balance AI and their teams Whirlpool, Duke Energy, Cleveland Clinic CIOs on scaling AI Where CIOs get stuck rebuilding the enterprise: What 'Rewired' reveals As AI makes projects harder to track, will CIOs need new controls? Why disaster recovery plans fail in geopolitical crises A silent erosion of enterprise AI by data poisoning Priceline CTO prioritizes engineers able to 'hold a room and a roadmap' InformationWeek Podcast: When CTOs need to restart IT projects Wayfair CTO maps agentic path across digital and brick-and-mortar commerce The AI contract gaps the Google-Pentagon deal just made visible
Why value-based pricing is inevitable
2026-03-26 · via informationweek

For most of software's history, pricing reflected how it was built and used. It was predictable, and the software was purchased as a tool. Perpetual licenses and, later, "seat-based" subscriptions were logical models for years.

With AI-enabled software continuing to accelerate its growth and usage, that way of thinking doesn't work anymore.

The move to cloud computing introduced consumption-based pricing aligned to usage. As software becomes more adaptive, autonomous and capable of driving outcomes, pricing models tied to access or activity are starting to feel outdated. Software has changed, and pricing should, too.

AI-enabled software is fundamentally different from traditional enterprise software. It can reason, take action and adapt in real time while consuming compute. That's a shift from traditional software, which delivers value through dashboards and predefined workflows.

Trying to price that new type of software using old-school static thresholds or fixed constructs is a mismatch from the start.

Related:Why build vs. buy doesn't fit modern IT systems

Moving beyond comforts of subscription pricing

Subscription pricing has stuck around because it feels safe. Organizations can budget for it, and vendors benefit from steady recurring revenue. Usage-based pricing aligns cost with consumption, especially in infrastructure and developer-focused platforms.

Metrics such as tokens, credits or compute units don't measure outcomes. They're essentially proxies for value; not value itself.

Two organizations can consume roughly the same amount of AI resources and see dramatically different business outcomes. Treating those scenarios as equivalent doesn't make sense.

In fairness, AI introduces uncertainty on both sides of the table. Vendors face variable infrastructure costs driven by inference and compute demand. Buyers struggle to forecast spending when usage fluctuates, and value shows up unevenly across teams and use cases.

Hybrid models that blend subscriptions with usage commitments or AI credits can help manage complexity and serve as an interim approach.

Hybrid models in action

Salesforce has taken a hybrid approach with Agentforce, introducing a bundled model that prices AI based on the actions it performs, like executing workflow updates or modifying records. The result combines seat-based access with consumption signals, moving away from seat counts as the only value driver.

Adobe also shows how pricing can evolve with value. While its Creative Cloud product still prices access per user, newer AI features use usage-based credits, with customers paying more as they generate more output. It's a practical hybrid model that preserves subscription stability while moving beyond seats alone.

Related:The rise of purpose-built software

Acknowledging software's more active role

Software is no longer just something you buy and deploy. As software becomes an active participant in day-to-day operations, you're essentially hiring digital teammates.

While work like resolving customer inquiries and optimizing workflows remain human-led, AI-based software is taking on real responsibility for outcomes. Pricing based purely on access starts to feel disconnected from the greater role software now plays.

Performance already drives compensation in other areas of the organization: Sales teams are paid based on results, and service providers are paid for outcomes delivered. AI makes it possible to extend that same logic to software.

Value-based pricing aligns incentives more cleanly. Vendors are rewarded for delivering measurable business impact, not for encouraging more usage. Customers pay for results that matter instead of abstract activity measures.

The operational roadblocks for value-based pricing 

If value-based pricing makes so much sense, why hasn't it been stronger out of the gate? The hesitation is less philosophical than it is operational.

Related:8 CIO recommendations for ERP implementation in 2026: Think agentic

Defining meaningful outcomes requires alignment across the business, IT and procurement. Measuring those outcomes demands the right data, analytics and agreement on how value should be attributed. Translating impact into commercial terms pushes sales, finance and legal teams into unfamiliar territory.

In fast-moving environments, speed and simplicity often win. Usage-based pricing is familiar, relatively easy to implement and quick to bring to market. In AI-driven spaces, where innovation cycles are short and expectations are high, that familiarity is appealing. The tradeoff is that it delays the inevitable.

Three steps to prepare for value-based pricing

Organizations shouldn't wait for perfect outcome-based models before preparing for them. There are practical steps that can be taken today:

  1. Start measuring outcomes. Even if contracts are still usage- or credit-based, teams can track the metrics AI solutions are meant to influence. Productivity, revenue impact, risk reduction and customer experience all provide helpful insight into how value is being created.

  1. Experiment with hybrid structures. Introducing outcome-linked elements into traditional agreements lets vendors and customers learn without taking on excessive risk. Over time, these models will build trust and transparency.

  2. Expand AI literacy beyond IT. Procurement, finance and business leaders need a shared understanding of how AI creates value, in probabilistic (not deterministic) ways. That fluency makes outcome-oriented pricing much easier to govern.

Embrace the inevitability 

The software and platforms industry will continue to test and refine pricing approaches. Some will scale, and others won't. Differences across industries and use cases will persist.

Value-based pricing is an inevitable reality as AI transforms software from a passive tool into an active contributor to business performance, leading to pricing that will increasingly reflect outcomes rather than inputs.

About the Author

Prem Ananthakrishnan

Accenture

Prem Ananthakrishnan leads the software industry segment within Accenture's software and platforms industry network.