Metered Billing Math Breaks Down at Scale
109 posts across 31 communities in the last 30 days; 27% from r/SaaS.
“The problem is you are conflating deployment with maintenance. The initial setup fee covers one time, not the rest of the customer's life. You need to decouple that fee from a recurring retainer for those specific 3%. The fix is a managed infrastructure fee for the self hosted…”
“Hi, I’m coming up against the same issue. Would love to know your solution if possible. Thanks [re: UK open banking API pricing is insane, anyone else stuck on this?]”
“I get why they charge per contract but it sucks when one post blows up and your bills goes up too. id rather pay based on how many messages or automations I actually use. Some people also use cloud phones for scheduling tasks across accounts so it really depends on what kind of…”
SaaS businesses face significant challenges managing billing, ranging from choosing the right billing cycle and platform to accurately tracking and interpreting MRR and dealing with failed payments. The complexity increases with usage-based models, contracts, discounts, and scaling from manual processes to automated systems.
SOURCES (60)
“When you move metered billing to a new system, the invoice total can look right while the usage underneath is wrong. Two checks I'd run first. Replay versus conflict. Say usage event evt_1042 arrives twice with the same customer and the same quantity. That's a…”
“the hubspot pricing jump is real, we got burned by that too. look into Micro if you want crm + email + tasks without paying per seat fees that eat your mrr alive [re: is hubspot crm worth it for a lean team or does it kill margins?]”
“$320/month is nothing if your platform is making decent money. managing your infra becomes a second job so if you value peace of mind and time then don't make huge changes especially with DB [re: Considering migrating from Supabase + Railway to a dedicated server — spending $320/month and looking for advice]”
“The problem is you are conflating deployment with maintenance. The initial setup fee covers one time, not the rest of the customer's life. You need to decouple that fee from a recurring retainer for those specific 3%. The fix is a managed infrastructure fee for the self hosted crowd. This makes the ongoing cost explicit instead of a tax on your engineers. [re: Less than 3% of our customers account for 70% of our support work]”
“we are modeling out our software expenses for the next 18 months and trying to sanity check our revops line items. our incubator gives us access to the program, but when you look closely at hubspot for startups pricing, the discount model only applies to the base subscription while add-on fees stack up fast. the moment you need extra core seats for new account executives, additional custom pipelines, or your marketing contacts cross the included threshold, those additions get billed without the”
“Hi, I’m coming up against the same issue. Would love to know your solution if possible. Thanks [re: UK open banking API pricing is insane, anyone else stuck on this?]”
“Follow-up to my drawdown thread from last week (thanks again u/AppX_Unmanaged for the object model). After that I checked how often the terms that model needs are actually written down anywhere: 64 public pricing pages of B2B companies selling credits, included usage or commit plus overage. 61/64 sell custom contracts, so the terms live in the order form, meaning whatever CPQ prints 34/47 don’t say what happens to unused allowance at period end 57/62 don’t say what happens to credits on a mid-cy”
“If you sell credits, included usage or a commit with overage, your pricing page is a contract. I scored 64 of them (dev tools, data/AI platforms, comms SaaS, all B2B) on whether they state the rules that matter at month end. Public pages only, no logins. 61/64 sell custom contracts, which is where the real true-ups happen 34/47 never say what happens to unused allowance at period end 57/62 don’t say what happens to credits or rollover on a mid-cycle plan change 6 offer rollover at all; 1 states”
“What happens An adopting app declares only dated plans ( monthly , yearly ) because its prices are not settled and it does not want to sell lifetime access on /payment . Its owner still needs lifetime access for their own account (or a complimentary account), otherwise it turns read only when the trial ends. BillingAdminPage → "Grant access" lists only declared plans ( grantPlanManually ), so lifetime cannot be granted there. grant plan refuses an undeclared plan. import entitlements supports is”
“I get why they charge per contract but it sucks when one post blows up and your bills goes up too. id rather pay based on how many messages or automations I actually use. Some people also use cloud phones for scheduling tasks across accounts so it really depends on what kind of setup you're running [re: Why do so many Instagram automation tools charge more as you get more customers?]”
“I think onboarding would make or break this. Even if customers like the idea of payroll inside the platform, having to move employee information and get everything set up again could be enough to put them off [re: How do you get customers to use payroll once you've added it to your platform?]”
“Right now all I need is checkout andd subscriptions. But if the product works, I can see needing international payments and potentially payouts to users later. I’m stuck between just integrating what I need now and shipping or choosing the setup around where the product might go so I’m not ripping out payment logic a year from now. For those who’ve dealt with this, how much did you account for upfront? building a small SaaS atm submitted by /u/Significant_Rate5448 [link] [comme”
“Before you move away from Bubble, first find out why your bill is so high. Bubble charges by workload units (WU). Your app uses some every time it does work, like opening a page or looking up data. Usually, a few parts …”
“I have clients that went from that to quoted $44000. They are on PVE now. [re: Topgolf saved over $11.3 million after leaving VMware]”
“As I said, utilizing L2s for micropayments is very impractical. And I’ve not seen a solution that makes logistical sense so far. I do see multiple L1’s that can handle low fee micro transactions, which also offer low fee stable coin transactions, however. I invest in those as that’s the direction I see this all going. Bitcoin is the main hub where the wealth will be stored, as it’s the most secure, but it’s not practice for your daily spending. [re: Crypto card CEO says most users don’t care whe”
“Different company. Different industry. Different tech stack. Same guy. You know the one. He's been there eleven years. He's the only person who understands the billing system. he has no documentation. He's not going anywhere. Everyone is very nice to him. At my first company we called him Dave. Second company, Mark. Current company: I won't say his name but he knows who he is and so does everyone else. I'm starting to think Dave is not a person. Dave is a fundamental law of s”
“the subscriptions are subsidised, API prices aren’t really. Most sources put the margin above 75% for api pricing. Could argue about cost of infrastructure etc. But even if all these companies went bankrupt, open source models like Kiki K3 or GLM 5.3 and GLM 5.3 flash don’t have the training cost baked into them so not that expensive to run inference on. API prices for GLM 5.3 flash is comically cheap like: Standard Input: $0.15 per 1 million tokens Cached Input: $0.03 per 1 million tokens Outpu”
“It is genuinely one of the most backwards business models in SaaS. You scale your team because business is booming, and your software vendor rewards you by hiking your monthly bill. It basically discourages you from getting your actual frontline staff to use the system. Flat-rate or transparent usage tiers are the only way software pricing should work if a platform actually wants to align its success with yours. [re: The per seat pricing model punishes you for growing your team]”
“Yyea, a product by product or smth like this breakdown would help show where those allocations go [re: Pump.fun’s fee total needs its revenue breakdown alongside it]”
“[ Removed by Reddit ] [re: Billing is the part of the MSP that still feels taped together]”
“I´m at a financial services company and we´ve been on Brightidea four years. The platform but we keep hitting the same frustrations: per-app pricing means every new use case might a new subscription, admin requires specialized knowledge only two people have, onboarding new departments takes longer than it should. I´m starting to evaluate Brightidea alternatives. For enterprise teams that have made the switch: what did you move to, what drove the decision and how did the transition go? subm”
“We're using wiza for outbound at an industrial maintenance SaaS right now, it's the usual thing like we go after plant and ops people in the UK, Germany and sometimes Italy. I have no problem with the linkedin side but my outbound volume is all over the place (it's an internal issue ik) Because sometimes we're running a new territory campaign and everything's on fire, then other months goes quiet and all the credits we didnt use are wasted. And I am not liking the fact that I”
“We are a small MSP, about 40 clients, mostly flat rate plus a few projects. PSA is fine. Tickets get closed. The mess starts when the invoice leaves the tool. Someone exports, someone checks the card, someone chases the late one in email, and the deposit in the bank never quite matches the batch. We put Flexpoint on the billing side so invoices, reminders, and the payment record sit in one place instead of a spreadsheet next to the PSA. It is one piece. The real headache is still clients who pay”
“We on a cloud based platform, and I noticed the provider has been charging sales tax on the monthly subscription. Did a little research for Florida. Electronically Delivered SaaS: Web-based or cloud-hosted software accessed remotely (via a browser or internet connection) is considered an intangible service and is not taxable in Florida. [1, 2] Yeah, it's only $21 a month, but that's almost $250 a year. submitted by /u/SugarShackBBQ [link] [comments]”
“And it's free on opencode. Anyone not using all the allowance on there must be a fan of losing money. It's a good model. [re: It's been 2 months]”
“https://preview.redd.it/59pim1rvd1vh1.png?width=623&format=png&auto=webp&s=ddc3723337da3b5b3a421cd7893d9c1dedfb2489 submitted by /u/Easy-Network9347 [link] [comments]”
“[QuickBooks] ★ 1/5 (v26.10.0) — Title: Hidden fees and a discouraging experience Review: I’m giving QuickBooks 1 star because the fees feel hidden and the pricing isn’t clear upfront. I signed up expecting straightforward costs, but instead kept running into extra charges that weren’t obvious until after I was already using the product. The mobile app only adds to the frustration. Basic things that should be easy—like finding merchant services/payment settings—take too much digging, and the layo”
“yeah the 2 extension cap is brutal, promo codes sound like theyd be even worse to manage at scale tbh [re: Solo-built a horse racing analysis app. The hardest part wasn’t the AI, it was subscriptions. Here’s the stack and what broke]”
I'm working on a SaaS that relies heavily on paid third-party APIs. Since every request costs money, I decided to use credits instead of fixed pricing. One thing I hadn't considered enough…
“The problem is ramp transition will cost us 3k or so for user fee meanwhile emburse bcs it's part of our corporate card will cost us 0. Which kinda sucks. [re: Currently using concur, is moving to emburse spend better? Any advice or recommendation?]”
“Since u already liked Ramp I’d push the card change question harder internally before going Emburse since the expense tool is only half the trouble For NetSuite make them show coding, receipt cleanup and month end export using your edge cases [re: Currently using concur, is moving to emburse spend better? Any advice or recommendation?]”
“Problem today Split assumes one person paid for everything and stores a single payer mobile. On a weekend away, Ana pays for the villa, Ben pays for dinner and Cai pays for the Grab. Split gets each person's share right, but it doesn't say who should pay whom. The group works out the transfers in a spreadsheet. Why it matters Apple and Tab handle one receipt at a time, while Split already handles several receipts and currencies in one split. Settling up is the step those trips are missing. Netti”
“Exactly, a wrong ledger answer is worse than a clarifying question. And yeah, the tiers are simple: 1 company on Starter, up to 4 on Growth, unlimited on Pro. [re: [Web, WhatsApp, Beta] AnalyseAI – ask TallyPrime for reports in plain language, looking for real Tally users to break it]”
“Columns > Modify columns > add 'Conv. value / cost', that's your ROAS. Heads up if using Shopify's Google channel app: it only sends product subtotal, so it understates real order value. [re: Google ads ROI Question]”
Hey guys. I know it's really really really cliche but dang does it hurt. I experienced that sh*ty time where you get a massive invoice from an API or Cloud Provider (Anthropic…
“Company pays. Enterprise license. [re: PMs with a tool budget: how much, and what did you last spend it on?]”
“definitely drop the hybrid credit model, construction ops folks hate usage math and will bounce the second they see confusing credits. i work for agentui, we see internal admin workflows like photo sheets and receipt parsing get adopted way faster when the pricing is just a dead-simple flat monthly fee per team or site. focus your landing page hero on the exact output file rather than how the tool works. [re: I automated the two most tedious daily admin tasks at work (photo sheets & receipts). N”
“Finally decided to open the billing page and do a proper audit of everything. Fifteen-ish tools, north of a grand a month, and I couldn't tell you which of them are worth it. Platform and payments, fine, those aren't going anywhere. Email and SMS I'd defend, that one shows up in revenue plainly enough. Reviews probably earn it, though I've never actually turned them off to check. Analytics I've somehow ended up with three things and I'm fairly sure there's overlap her”
“If you run it as a company later you have to bookkeep and that will give you the profit number and revenue for each month anyway.”
“Yeah, splitting them might be the better way to do it. Free users and my testing are an acquisition and R&D cost, not the cost of serving customers. I'm looking at adding that split to OpenProfit so paid usage and everything else show separately. The number I care about most is still what's left after every bill though, so I wouldn't call it fake.”
“I work for a SaaS company that provides billing software. Everyday it seems like something fairly critical to the customers business operations breaks, which can almost never be resolved within a timeframe that is acceptable to the customer. Frontline support lacks knowledge and are just not competent people that lack initiative, but the software is 20+ years old and takes a bit of time to learn in their defense. There’s been a big push from the new ownership to bring on new customers, which has”
“That’s what Carta is banking on at least, as they raise prices. We’ll see if it works or if enough folks want to save $20k for something functionally equivalent.”
“From the builder side, the breaking point is rarely an MRR number. It's usually one of three things: a failed automation nobody noticed costs you a client or an invoice, the same customer record lives in four tools and nobody trusts any of them, or someone spends a big chunk of their week copying data between apps. Before going custom, check whether one source of truth plus error alerts on the existing automations fixes most of it. Often it does. If it doesn't, I'd map the two or thr”
“Different experience on mobile. My vocab app (VibeLing) is on a cheap monthly sub and the support flood never came, App Store handles billing and refunds so what I get is mostly bug reports. What actually moved revenue for me wasn't the price, it was removing the "continue for free" option after onboarding. And I'm with the comment above, a one-time price on something with server costs worries me, mine has an AI bill every month.”
“The first paying users seem to have exposed support and billing work that was invisible before the sale. Which request surprised you first, and what had the customer already tried before asking you for help?”
“We switched off of Carta recently because of their per-stakeholder pricing (and price hiking) for what feels like basic SaaS software. Nobody really pushed back - neither the lawyers nor the investors. The new platform was 80% cheaper than Carta - no joke. Note that the lawyers had to help us with a couple of the parts of the move, so we ended up spending a good chunk of the first year’s savings in lawyers fees. Stuff like this contributes to that moat/inertia you’re talking about.”
“Agreed, though the late payment thing might not even need a mentor. With fleet tracking they already have leverage most businesses don't, a clear late fee plus pausing dashboard access after a set number of days usually fixes "consistently late" clients pretty quick.”
“Provider side here, so we look at this from the invoice end, and your framing is right: with flat pricing the average is the lie, per-customer margin is the truth. The setup that actually holds up in production is metering at the API layer, not in your billing code: - One API key per customer (or a customer header on every request) so the provider's token logs become your margin table. You stop maintaining a parallel tracker that drifts out of date. - Track retries and failed calls per custo”
“Hi everyone, I’m currently validating an idea for a web app and could really use some advice from developers/founders who have dealt with high-risk payments and "friendly fraud." The Concept: I’m building a real-time, competitive platform where users pay a small entry fee (e.g., $1–$5 for a ticket/participation) to join a specific digital event. Only one person wins the main reward, which means the vast majority of participants will "lose" their entry fee. The Problem: I have”
“We run Treg, an API marketplace. Every new account gets $1 of credit, and since we pass vendor prices straight through, every cent of it is a real vendor bill. Fine for the first couple of months, at 50 to 110 signups a day. Then one week it was 780 a day, then 2,385, with 656 accounts landing in a single hour. About 9,900 signups in ten days, where a normal ten days for us is under a thousand, and the vendor bills followed. You could see the two scripts behind them in the account names. One mad”
“fair — if overage billing already keeps margin healthy per customer, you're probably not the ICP for this anyway. mostly built for people still on flat pricing who don't want to redesign billing just to fix one heavy user.”
“Yeah, and the cost usually shows up on the engineering side first. Custom asks for one account quietly eat time for months before anyone's tallied it.”
“Hardware-enabled SaaS: GPS tracking and AI dashcams for commercial fleets. 12 years in, ~370 customers, average account around $4k/year, ~$1.6M ARR, on track for ~30% growth in our main market (Caribbean). On paper it's going fine. But I've reached the point where I don't fully trust my own read on the business anymore. I built most of it by figuring things out as I went, and I'm starting to suspect some of what I see as normal is actually a blind spot. Here's a concrete exam”
“So develop a better pricing structure for agents and licensing. Or would you rather they up the prices on coders to make up for the loss instead?”
“I run a small portfolio of ~1800 apartments and recently got a proposal to add utility bill pay to our current software package. Does anyone know if $12 per utility bill is a fair price? Feels very steep compared to other regular invoice processing service we use. I know it comes with the utility analytics and stuff, but it still seems pretty steep. It has been very difficult getting pricing comps for this without having to do a bunch of sales calls and promise to commit the whole portfolio. I k”
“the part that jumped out is support getting flooded by usage billing. i'd start with five users and ask what they thought they were paying for before changing the pricing page again. track where those same people stall during the first week of onboarding. a boring fixed plan with a clear limit may beat usage pricing until the confusing part is obvious.”
“I’m building a Construction SaaS with iOS + Android apps, and I’m trying to understand if I actually need RevenueCat. My idea is simple: users click “Purchase” in the app → go to my website → pay through Stripe → Stripe webhook updates my backend from unpaid → paid. The mobile app then checks the user’s subscription status from my backend and they get the paid features. So what exactly would RevenueCat add here? Is it mainly needed if I want to support native Apple/Google in-app subscriptions, o”
“The real pain is predicting COGS when billing is not deterministic. If users request arbitrary dimensions, rounding to whole megapixels completely ruins the unit economics. We had to normalize and clamp resolutions upstream before even sending the payload just to keep monthly spend predictable.”
