This Week: June 2 - 8
The Hot Topic 
How do you price APIs?
- One approach: offer request-based plans like 50k, 100k, or 1M requests/month.
- Another view: billing for actual usage is tedious and complicates invoicing.
- Simpler tiers based on usage bands make pricing easier to manage.
- But too much precision can create friction - for both finance and customers.
Full convo here
LinkedIn Crossover 
- From Rob: Pricing projects should be a benevolent dictatorship
- From Kyle Poyar: The most disruptive AI pricing models
- From Todd Gardner: Three things to know about usage-based pricing models
Events 
Upcoming Webinar: June 26, 2025 - 4:00 PM CET / 7:00 AM PDT / 10:00 AM EDT
Annual vs Monthly vs Multiyear
- • Effect on sales, risk, cashflow & renewal operations
- • Which time period is best for me?
- • Should you offer options for multiple periods?
- • Discounts on annual and Multi-year contracts
From the Good-Better-Best Newsletter 
How I’d Run a Pricing Project from Scratch
Pricing projects have a funny way of finding people that never asked for them.
If you’re working in product, product marketing, or bizops at an early-stage SaaS company, there’s a chance you’ve experienced this scenario:
Leadership decides pricing needs attention, but with no dedicated pricing function (or budget for a consultant) the project lands in your lap.
The challenge with pricing projects is that they combine two things that, together, are a recipe for chaos:
1. Urgency: You need to make decisions quickly.
2. Ambiguity: The path forward is murky.
This uncertainty can be paralyzing, especially when you’re already juggling other responsibilities. Complicating matters, pricing advice is rarely one-size-fits-all.
Help Our Community Grow! 
Share the benefits you’ve discovered with colleagues and friends who might find value here.
One simple share could connect someone with exactly the resources, insights, and connections they’ve been searching for.