Last week I met a Voice AI company. We barely talked product. The real heat was pricing, not how much, but what exactly are we charging for?
They don t want per-minute, per-seat, or per-API-call anymore. They want per resolved call, per booking, per qualified lead, per deflection.
Sounds clean. Until you try to define resolved.
Who validates it?
What if their CRM says something else?
What if attribution breaks?
At that point, the metric becomes the product. And the infrastructure behind that metric becomes the business model.
Flexprice
Hey Product Hunt 👋
I'm Manish, founder of @Flexprice . After spending over couple of years building billing systems, I’ve felt this pain deeply: building products is getting easier, but charging for them is still hard.
Modern AI and API-first products need usage-based pricing, credit systems, free tiers, and feature access but implementing all of that feels like starting a second startup just to manage billing 😅.
We tried everything like Stripe Billing, Chargebee, and a few newer tools but none truly solved our needs beyond basic subscriptions. Eventually, we built our own billing system from scratch. It took us over 6 months and still felt like a never-ending cycle of bugs and edge cases.
Every developer or founder I’ve spoken to who deals with anything usage-based had a similar story
@Flexprice is an open-source billing and metering infrastructure built specifically for today’s AI and API-first products. You send your app’s usage events (API calls, GPU time, etc.) and @Flexprice takes care of🧑💻
Usage metering
Calculating charges or credit consumption
Feature access management
Generating accurate invoices
Launch Special 🚀
Use code PH200 for $200 off our hosted version (valid until June 30th)
We’ll be here all day to answer questions and share our building journey
Let’s chat!