I'm pricing my first cold email clients per booked meeting instead of a retainer. $250 for each meeting that actually happens, plus a one-time setup fee. No-shows are free. The hard part has been defining the unit. Rules I've written so far: - A meeting counts unless the client flags it within 48 hours (it didn't happen, or it was the wrong person). - For one deal where sales take 2 or 3 calls, only the first meeting with each company counts. The client handles the calls after that. It's the same problem you all talk about with credits. I do the counting, so how does the client trust the bill? If you've priced on outcomes: what did you count, and what did customers end up arguing about?

PricingSaaS has officially joined Willingness to Pay 🎉 I wanted to share this here because this community has become such an important part of what we’re building. The short version of the story: Back in 2024, I cold-DMed Ulrik Lehrskov-Schmidt after reading The Pricing Roadmap. I was hoping he might sponsor PricingSaaS for a few months. Instead, he made a much bigger bet on us: sponsoring us for two years in exchange for a piece of the company. That relationship turned into monthly board meetings, a ton of trust, and eventually a conversation this summer about what would happen if we joined forces. For John and me, it was an easy decision. We now have an opportunity to build something much bigger: a single platform where SaaS and AI leaders can learn about monetization, understand what’s happening across the market, and get hands-on help putting it into practice. And this community is going to be a big part of that. We’re going to keep investing in it, bringing in great operators, consultants, and builders, and doing more live events and conversations around pricing, packaging, and AI monetization. There’s an insane amount changing in software right now, and our goal is to make this the best place to figure it out together. Thanks to everyone here who has been part of PricingSaaS so far. We're just getting started. 🚀 Rob PS. Today, we also relaunched PricingSaaS and would love your feedback. Check it out at pricingsaas.com

There's so much AI news every day that I can't tell what actually matters and what's just hype. Right now I have a little automated workflow on my MacBook that runs around 8am and pulls trending GitHub repos, Hacker News, some AI subreddits and about 26 AI lab and founder accounts on X, then ranks what's blowing up on a simple dashboard. Does anyone have a setup like this, or sources you trust to separate signal from noise?

A draft invoice can match a usage export down to the cent and still miss billable activity if an account, meter, or event category never made it into that export. For teams using usage-based pricing, what do you check the export against before invoices go out? Source-system event counts, active accounts and meters, or something else? I’m curious about what actually happens in practice, even if it’s a manual spreadsheet check.

Hey everyone, I’m Anuj from Anrotex. We’re building Venpalo, a read-only way to check whether a draft usage-based invoice matches the customer’s agreed terms and the usage behind it. I’m interested in what happens after a pricing model is designed. Negotiated rates, discounts, allowances and tiers can make sense on paper, but someone still has to make sure they show up correctly on the invoice. We’re pre-pilot, so I’m here to learn from people who’ve handled these pricing and billing changes in practice, and to contribute where I can. Glad to be here.