Welcome back to Good Better Best.
Each week, we break down real pricing, packaging, and product moves from SaaS and AI leaders and share the ideas worth stealing.
It was a big week for PricingSaaS. We have officially joined forces with Ulrik Lehrskov Schmidt and the team at Willingness to Pay! You can read the full story here.
Our mission is to build a single platform where SaaS and AI leaders can use monetization as a weapon for growth. That might mean learning through this newsletter or our podcast (check out our latest episode on Clay!), using our free data product PricingSaaS Pulse to understand the market, or working directly with the Willingness to Pay team on a transformation project.
We couldn’t be more excited for the next chapter. If you’re working on AI Monetization heading into 2027, and could use a sounding board — grab time with me here.
This week, we're digging into how to price Agents.
Everyone generally agrees that tokens aren’t the right model for application companies, and outcomes are only possible for a small sliver of the market. The question is what do you do if you’re in the middle?
I caught up with my friend Manu Mehra, who spent years at Google Cloud and now works on strategic pricing at Databricks. He recently wrote a post about agent economics, where he shared one of the most useful tools I’ve seen to navigate this challenge.
Let's get to it.
PricingSaaS Partners power the next era of SaaS pricing

This Week in Pricing, Packaging, and Product
This week we observed 275+ changes. The highlights:
OpenAI halved GPT-6.1 Sol cached input pricing to $0.10 per 1M tokens [Link]
Salesforce Agentforce renamed Agentforce 1 Editions to Max and raised included credits to 2.75M [Link]
Slack is A/B testing public Enterprise+ pricing at $45/user/month [Link]
Stripe added card cashback to Treasury and launched the $329 Reader T600 [Link]
n8n cut AI credits ~30% in a rebrand to Assistant credits [Link]
LangChain retired LCU billing, moving all usage to $1 Standard Units [Link]
Stack Overflow ended contact-form pricing with a free Starter plan and 1,000 credits/mo [Link]
Microsoft Teams added LLM choice and pre-built agents to Copilot [Link]
MongoDB launched an Atlas Infinite preview [Link]
Datadog unveiled Kafka Console pricing from $100 per broker host [Link]
ElevenLabs offered 3x credits with its v4 launch and 83% off Starter's first month [Link]
PagerDuty boosted Plus to 50 seats and dropped AI Actions quotas [Link]
UiPath split Maestro into Automate and Orchestrate offerings [Link]
Gusto dropped its Contractor Only plan and added an $85 Business Compliance add-on [Link]
beehiiv renamed plans to Free/Lite/Pro, raised Lite to $49 and cut seats [Link]
Retool removed its Enterprise offer of up to $10K/year in AI credits [Link]
Kong moved Plus to $25/month plus usage and dropped its free trial card [Link]
Brevo put ChatGPT and Claude control in its Starter plan via MCP [Link]
Vercel added the OWASP Core Ruleset firewall to Pro Plus priority projects [Link]
Fal raised GPU rates up to 33% and added a GB200 tier [Link]
Cohere cut Model Vault Embed pricing 25% with new Embed 5 Fast and Pro tiers [Link]
Exa launched $4/1K Instant Search, cutting Search's entry price from $7 [Link]
Neon doubled Free plan storage to 1 GB per project [Link]
Astronomer launched Astro Observe, billed as a % of deployment compute costs [Link]
Artlist halved AI video caps and dropped Flows and MCP from plans [Link]
7shifts cut Premium 25% to $134.99 and added a $39.99 Essentials plan [Link]
Check out more updates on PricingSaaS →
The Agent P&L Framework
Right now, almost everyone agrees that tokens are the wrong thing to charge customers for. In the last week alone I’ve read two great posts breaking down why.
The first, from a16z: "Charging per token is becoming the default for AI companies. For most AI applications, it is a mistake."
The second, from Scott Woody (CEO Metronome): "Token billing is useful infrastructure and, for almost every company, a bad customer-facing pricing model."
I agree. But "don't price per token" only tells you what not to do. For most AI companies, the harder question is what to do instead.
The way I see it, there are two ends of the market (tokens on one side, outcomes on the other), and a very wide middle, which is the hard part.
Manu has been thinking about this exact problem, and developed his Agent P&L framework to solve it. First, some context.
Tokens, Outcomes, and the Messy Middle
If you sell model access, tokens are the right meter. Model providers and inference clouds sell compute, and their customers are buying compute. a16z makes this the first rung of their pricing ladder: if you sell model access, price tokens.

The problem starts when applications carry that logic up the stack.
Scott puts it bluntly: token billing positions your product as "a commodity markup on top of an actual commodity." Every time model prices fall, that markup gets harder to defend.
At the other end is outcome-based pricing.
Fin charging per resolved conversation is the go-to example. It works when the outcome is clean, countable, and clearly caused by the product.
But that's a short list.
a16z says to price outcomes only where attribution is clean. Scott goes further: "Outcome-based pricing only works in a very limited set of circumstances," and he argues even Fin is really an output that's marketed as an outcome.
That leaves almost everyone else: the AI apps and agents that sit on top of model costs, do real work, but can't cleanly attribute a business outcome.
The pricing mechanisms for this group are pretty well covered. Credits, outputs, hybrid seats plus usage.
But as a16z points out, "a credit is a currency, not a value metric." A credit system tells you how to bill. It doesn't tell you what your price should be, or how to defend the gap between your price and your token costs.
For companies in the middle, that gap is the challenge. They need to define their value, articulate it, and justify what they charge on top of tokens.
Enter the Agent P&L.
Manu has spent nearly a decade in pricing across Thermo Fisher, Google Cloud, and Databricks. In The Rise of Agent Economics, he starts from a simple observation: Companies can tell you they're burning "millions and billions of tokens," but not whether that consumption is "really driving the business value."
His answer is to give every agent a P&L:
Cost side: infrastructure, model inference, monitoring and evals, governance and compliance.
Value side: incremental revenue, labor hours saved, cycle time reduced, errors avoided.
From there, he uses three simple formulas:
Net Agent Value = Business value created − Total agent cost
Cost per Business Outcome = Total agent cost ÷ Verified successful outcomes
Agent ROI = (Business value created − Total agent cost) ÷ Total agent cost
Manu created the framework to help companies judge the agents they run. But flip it around, and it's one of the most useful tools I've seen for pricing in the middle.
The cost side is your floor. Tokens are only one line. Infrastructure, evals, monitoring, and governance all go into delivering an agent that works. Making that full cost visible is the first step to justifying a price above tokens.
The value side is your ceiling. Revenue generated, hours saved, faster cycle times, fewer errors. That's the math your buyer is doing, and your price has to leave them with positive net agent value.
Cost per business outcome is how you talk about price. You can bill in credits and still tell a buyer what each successful result costs them. That resonates more than a credit count.
In other words, the agent P&L lets you sell on outcomes without billing on outcomes. For the wide middle, that's the sweet spot.
To ensure the value side holds up, Manu recommends watching four metrics:
Productivity. How much of the human's work does the agent take on? For example: an agent that writes 90-95% of an analyst's SQL, while the analyst checks the business logic.
Utilization. Are people still using it after launch? Manu compared it to a great-looking dashboard with light insights: people check it for a couple weeks, then never again.
Accuracy and rework. If it takes 10, 20, 30 prompts to get the right answer, users lose trust and utilization drops with it.
Risk-adjusted value. There's always some risk. The value created has to clearly outweigh it.
Number three hits especially hard for me. At PricingSaaS, we have built and tested tons of agents for all sorts of use cases. Some are amazing, some are frustrating, and accuracy and rework is the biggest variable that separates the two. If I'm wrestling with an agent for an hour to get something I could have done myself, it doesn't matter how cheap the tokens were.
Key Takeaway
Tokens work for models and infrastructure. Outcomes work for a small sliver of companies with clean attribution. Everyone in between has to define, articulate, and defend the value they add on top of token costs.
If you're in the middle, ask yourself:
What's in my agent P&L beyond tokens?
What value does my agent create, in units my buyer cares about?
Can I show customers their own cost per business outcome and agent ROI?
I think the companies that win the middle will be the ones that do this math for their customers. And when outcomes do get standardized, they'll be in the best position to move up to outcome-based pricing.
Huge thanks to Manu for the conversation. If you haven't yet, read his full post here.
Thanks for reading! If you're working on AI monetization and want to learn more about how we help, book time here.
Until next time,
Rob