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.

23 contributions to PricingSaaS
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 • 1d
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 • 1d
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,
How does everyone keep up with the AI noise?
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?
1 like • 2d
Your 26 accounts are mostly launch posts, not capability. Worth splitting the dashboard in two: things that shipped and are reproducible today, and things announced. The second list barely needs daily refresh.
CRM anybody?
When do you think a CRM actually becomes worth using? I’ve found that setting one up too early can sometimes create more work than value if you’re still just trying to get deals in the door. Do you use one from the start, when you’re juggling potential leads, or wait until you have a few clients/leads to manage after closing? And which CRM do you recommend?
1 like • 10d
Scott's point covers the front end. The trigger Watch. A lead you'd forget without a reminder. Until you're losing track of who to follow up with, a sheet is enough.
0 likes • 9d
Glad it landed. The part worth keeping. Your AI worker reads the framework straight out of the server, so the scaffold is already there before it writes a line. That is what keeps a 3-week build out of turning into 3 months of setup.
1-10 of 23
Mouldi Nouri
2
9 points to level up
@mouldi-nouri-2626
🚀 https://www.skool.com/free-builder-8571

Active 38m ago
Joined Aug 5, 2026
Powered by