Activity
Mon
Wed
Fri
Sun
Nov
Dec
Jan
Feb
Mar
Apr
May
Jun
Jul
Aug
Sep
Oct
What is this?
Less
More

Owned by Mouldi

Turn your idea into an AI SaaS business you own.

25 contributions to PricingSaaS
Charging per booked meeting. Thoughts?
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?
0 likes • 5h
The 48-hour silent approval is your weak point. Silence is not consent, it just means they forgot. Send the count weekly with each meeting's date and name, so the bill is a list, not an assertion.
Big news!
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
0 likes • 6h
The 2024 outreach turning into a two-year bet is the part worth copying. One question as it all merges: how pricing content stays public and how moves behind the platform?
How do you check that usage data is complete before invoicing?
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.
0 likes • 2d
A cent-level match only proves the export is internally consistent, not that the export is whole. Reconcile counts first: source events vs metered events per meter, then distinct billing accounts vs active accounts.
Hi, I’m Anuj. Working on the gap between pricing and invoicing
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.
0 likes • 2d
Same gap kills usage billing more often than design does. The failure point is the mapping between negotiated terms line items the meter produces. So check who owns rate retool before piloting. Good luck, Anuj.
0 likes • 2d
The meter is the honest party. If terms and usage disagree, trust the usage. Find where the contract says what happens when they diverge, and make that the clause you renegotiate first. Everything else follows from who holds the reconciliation right.
Office Hours: Managing AI Margins
Howdy pricing people! On October 8th we've got two special guests: Ulrik Lehrskov-Schmidt, CEO of Willingness to Pay, and Emil Eriksson, CPO of DigitalRoute. We're going to talk about AI margins, and how to stop them from slipping away as usage grows. The pairing gives both sides: - Ulrik works on strategy: credits, packaging and how to capture value. - Emil works on the technical side: how usage actually gets metered and turned into revenue. We're increasingly seeing a gap in communication between these two groups, and believe tighter collaboration is key for the next phase of AI monetization. A few things we're going to dig into: - How to set credit burn rates when your model costs keep moving - When sending work to cheaper models makes sense, and when it just makes the product worse - What your usage setup needs to track now so you can change pricing later without a rebuild Details below: Thursday, October 8th @ 11am ET Register here 👉 https://luma.com/qdlmss76 Hope to see you there! Rob
0 likes • 2d
The pricing person metering person usually discover the mismatch two quarters in, once the schema is locked. Asking what do we have to log today so we can reprice without a rebuild belongs in the first architecture conversation,
1-10 of 25
Mouldi Nouri
2
9 points to level up
@mouldi-nouri-2626
🚀 https://www.skool.com/free-builder-8571

Active 6h ago
Joined Aug 5, 2026
Powered by