Introducing: Prompt to Plan in Flexprice
Setting up billing is one of the most time-consuming parts of launching a product. Teams often spend hours defining plans, configuring pricing and wiring everything together before they can even start charging customers.
We wanted to simplify this.
Prompt to Plan introduces a new way to set up billing in @tryflexprice. Instead of manually configuring plans, prices, meters and entitlements, you can describe your pricing model in plain english and generate your plans.
The chat workflow supports:
• Plans across subscription, usage-based, and hybrid models
• Credit-based pricing with grants and expiration
• Add-ons and entitlements
You can preview the generated setup and push it live once it looks correct and tweak it later.
For teams that prefer a starting point, the "Prompt to Plan" workflow also includes 5 templates based on real-world pricing models. These can be customized and deployed directly as well.
The goal for us is simple.
Reducing the time required to go from pricing idea to a working billing system, without compromising on flexibility is where we’re headed and this is just the start.
Prompt to Plan is now live in Flexprice. Try it out.
Indian startup funding continued its volatile streak, with total capital infusion falling 44% this week. Between May 25–29, 14 startups collectively raised $52 Mn, down from the $92.2 Mn recorded in the previous week👇
🔹 https://t.co/vFL68SAvzJ led the charts with a $15 Mn Series A round, helping Ecommerce reclaim its spot as the most funded sector with over $21.4 Mn raised across four deals.
🔹 Advanced Hardware & Technology showed strong momentum in deal volume, securing the second-highest number of deals as three startups in the sector raised over $2.4 Mn.
🔹 Seed-stage funding took a significant hit, shrinking 78% to just $1.6 Mn across three deals, compared to the $7.6 Mn infused into early-stage startups last week.
🔹 High-profile individual backers remained active, with actor Kriti Sanon investing in D2C brand GIVA, and Anupam Mittal co-leading the seed round for AI startup Flexprice.
🔹 Significant capital is waiting on the sidelines as Fundamentum’s Ashish Kumar launched a ₹2,000 Cr deeptech fund, and Physis Capital marked the final close of its ₹400 Cr maiden fund.
#Inc42 #trending #StartupFunding #IndianStartups #FundingNews #VentureCapital #StartupEcosystem #Ecommerce #DeepTech #AI #SeriesA
Introducing: Whop Integration in Flexprice
If you are selling through Whop, collecting payments usually means managing invoices and payment status across two systems manually in certain cases.
You finalize an invoice in your billing system, then figure out how to get it into Whop, generate a payment link, and keep track of whether it actually got paid.
Most teams end up building webhook handlers and sync scripts to hold it together. We wanted to fix that.
With @tryflexprice + Whop, invoice sync and payment reconciliation now work end-to-end:
- Finalized invoices in Flexprice automatically push to Whop
- Every synced invoice gets a Whop-hosted payment link
- When a customer pays through Whop, the invoice is automatically marked as paid in Flexprice
- Payment status stays in sync between both systems through webhooks
Flexprice handles usage, pricing, and invoices.
Whop handles payments.
The two stay in sync without you writing glue code or reconciling manually.
Happy Building! ✨
Docs: https://t.co/vUlNhnjCHG
Introducing : Environment Cloning in Flexprice
Every developer knows you do not test in production. You have a staging environment, you validate everything works, and then you push to production with confidence.
Mistakes in staging are free. Mistakes in production are not.
For a product team that wants to experiment with pricing, the absence of a safe place to test outside of pre-existing environments where mapped out logics live is usually the reason the experiments never happens at all.
Environment Cloning in @tryflexprice fixes this.
Now, you can copy any Flexprice environment to a new one or a pre-existing one.
Everything comes with it, including plans, prices, features, credits, entitlements.
Your entire billing setup duplicated exactly.
Let your product team run pricing experiments without filing an engineering ticket or touching anything real customers see.
Environment Cloning is live now for all users.
Introducing: Prompt to Plan in Flexprice
Setting up billing is one of the most time-consuming parts of launching a product. Teams often spend hours defining plans, configuring pricing and wiring everything together before they can even start charging customers.
We wanted to simplify this.
Prompt to Plan introduces a new way to set up billing in @tryflexprice. Instead of manually configuring plans, prices, meters and entitlements, you can describe your pricing model in plain english and generate your plans.
The chat workflow supports:
• Plans across subscription, usage-based, and hybrid models
• Credit-based pricing with grants and expiration
• Add-ons and entitlements
You can preview the generated setup and push it live once it looks correct and tweak it later.
For teams that prefer a starting point, the "Prompt to Plan" workflow also includes 5 templates based on real-world pricing models. These can be customized and deployed directly as well.
The goal for us is simple.
Reducing the time required to go from pricing idea to a working billing system, without compromising on flexibility is where we’re headed and this is just the start.
Prompt to Plan is now live in Flexprice. Try it out.
Introducing: Customer Hierarchy in Flexprice
Enterprise billing almost always involves more than one entity. A parent company with subsidiaries. A reseller managing multiple clients. A central finance team paying for several departments.
But most billing systems force you to either restructure your entire customer data model to support this, or build custom invoice routing logic on top.
We wanted to fix that.
Customer Hierarchy in @tryflexprice lets you configure billing relationships at the subscription level without touching customer records.
Two modes, depending on your use case:
- Consolidated Subscription:
One parent plan covers multiple customers. Usage from all children rolls up into a single invoice to the parent.
- Delegated Payer:
Each customer keeps their own subscription and usage tracking, but invoices, wallet drawdown, and tax go to a different billing customer entirely.
The important shift here is that who uses the product and who pays for it no longer need to be the same entity. And you configure this per subscription, not per customer, so you can mix models across contracts without restructuring anything.
Happy Building!
Docs: https://t.co/lk1LOeTzIN
Can Flexprice Handle It? | Ep. 02: @cursor_ai
Last week we replicated Replit's pricing from scratch.
Cursor just launched Cursor 3 and completely changed how their pricing works.
It is no longer just a Pro plan and a Business plan. They now have to price around AI agents that consume unpredictable amounts of compute depending on the task, model-specific request limits, and a usage ceiling that behaves differently for fast vs. slow requests.
So I took it up and replicated their pricing plans in @tryflexprice just like how we did with Replit.
The thing I find most interesting about Cursor's modeling of pricing is that it is a preview of where every AI product's pricing is headed.
You cannot charge a flat rate when your costs change based on which model the user's agent decides to call.
Most teams hack this together with Stripe metadata and a prayer. It does not have to be that painful.
Drop your suggestion for Episode 03 in the comments. We have not picked one yet and the more complex the pricing, the more fun it is to replicate!
Introducing: Revenue Dashboard in Flexprice
Until now, understanding your revenue meant pulling invoice data, stitching it together in a spreadsheet, and hoping the numbers added up.
You could see individual invoices. You could see individual customers. But there was no single place to answer the question: How much revenue did we actually generate this quarter, and where is it coming from?
We wanted to fix that and as a start the - Revenue Dashboard - in Flexprice now gives you a complete view of your billing revenue in one place:
- Net revenue, contract revenue, and usage revenue broken down at a glance
- Per-customer revenue breakdown so you can see exactly who is driving what
- Filterable by time period and customer
and more updates coming sooner than you can expect.
The important shift here is that basic revenue visibility is no longer something you build on top of your billing system. It lives inside our tool itself.
No more exporting CSVs to figure out which customers are growing, which are churning, or where your usage revenue is concentrating. It is all there, updated as invoices finalize.
We are constantly iterating on the Revenue Dashboard and have a lot of updates in line.
Happy Building! ✨
Introducing: Decoupled Commitment and Billing Periods in Flexprice
In most billing systems, the commitment period and the billing period are assumed to be the same thing. But in real enterprise contracts, they rarely are.
A customer signs an annual commitment but wants monthly invoices.
Usage needs to accumulate across all 12 billing cycles against a single commitment threshold. Overages should only trigger when the commitment window closes, not at every invoice.
We kept running into this. So we built native support for it.
You can now configure subscriptions where the commitment period operates independently from the billing cycle.
@tryflexprice handles:
- Cumulative usage tracking across billing cycles within a commitment window
- Overage and true-up calculations at the commitment boundary
- Proportional allocation of committed amounts across line items
- Mixed billing cadences within one subscription
Commitment logic and billing logic no longer need to be the same thing.
Define the commitment window, define the billing cadence, and the system keeps them in sync.
Happy Building! 💙
Join Community : https://t.co/yf4UfzmArR
Introducing: Can Flexprice Handle It? 👀
A new month and I am starting yet another new series where we pick a product with notoriously complex pricing, and replicate the pricing inside Flexprice from scratch!
(Now, THAT should be fun, right?)
The first episode follows @Replit.
If you have ever looked at how Replit prices things, you know it is not simple. It's calculative as well.
They have a hybrid model with subscriptions, usage-based compute credits, feature gating across tiers, and credit grants that behave differently depending on your plan.
But with the help of our MCP server and claude, we did it in about 4-5 minutes.
The reason I wanted to start this series is that the most common question we get from founders is some version of "can Flexprice actually handle my pricing?"
And the honest answer is that no amount of documentation or feature lists will convince someone the way a live demo will.
So instead of telling people what Flexprice can do, we are going to show it every week with real pricing models from real companies.
The part that still surprises me is how much of this can now be done through a conversation with Claude using our MCP integration.
Pricing should NEVER be the bottleneck for your growth. If you want to add a new tier, experiment with usage-based billin or layer in credit bundles, that should take minutes, not sprints.
We have not picked the next company yet. If there is a product whose pricing you think is fun, do drop it in the comments. The wilder the better.
Introducing the Pricing Lab Series - Tool No. 02 is now LIVE! 🎉
To those who have not been in the loop, a week ago I released a fairly simple Pricing Roast tool and it got way more traction than we expected.
Founders were running their pages through it and the conversations that followed were some of the most interesting I have had since joining @tryflexprice.
But there was a question that kept coming up in my DMs: Should I even be doing usage-based pricing in the first place?
It sounds like a simple question. It is not.
So, as the second tool in this series I built a quiz that answers this in under 60 seconds and here's how it works!
You answer 7 simple questions about your product and billing setup.
- It scores you on a scale from flat-fee to hybrid to full usage-based pricing,
- Tells you exactly why that model fits your situation
and gives you three concrete next steps too!
We will be calling this series Pricing Lab because that is what it is. I am building small, useful tools that help founders make better pricing decisions without needing to hire a consultant or read a 40-page white-paper.
Tool No.01 was out of curiosity. The rest are going to be intentional
Try it at https://t.co/Wi77oj3elU and let me know what you get.
Introducing: Draft Subscriptions in Flexprice
When a customer is onboarded, creating a subscription workflow usually triggers billing immediately.
But a subscription setup is rarely perfect on the first attempt. A wrong plan or misconfiguration can fire an incorrect invoice, and you’re suddenly stuck voiding and reissuing instead of fixing things upfront.
We kept seeing this happen. So we built draft subscriptions.
You can now create subscriptions in a DRAFT state without triggering invoices or payments. This gives you space to configure plans, pricing, and entitlements properly before anything goes live.
You can preview the invoice, verify the setup, and only activate the subscription when everything looks correct, with a controlled start date.
Creating a subscription no longer means committing to billing immediately. You get a safe setup phase before anything impacts the customer.
Happy Building!
Introducing: Paddle Integration in Flexprice
If you're using Paddle, billing doesn’t actually live in one place.
You end up managing customers, invoices, checkout, and payment reconciliation across multiple systems, and most of the logic sits in custom code.
We wanted to fix that
With @tryflexprice + Paddle, you can now run the entire billing flow end-to-end:
• Create and sync customers (including required address mapping)
• Generate invoices and convert them into Paddle transactions
• Launch checkout via Flexprice with Paddle handling payments
• Automatically reconcile payments through webhooks
• Keep invoices, payments, and status in sync without manual work
The important shift here is that your pricing, billing logic, and payments now operate as a single system.
Flexprice handles usage, pricing, and invoices. Paddle handles payments.
The system stays consistent without you writing glue code or running reconciliation loops. No partial states. No manual fixes.
Happy Building!
Docs : https://t.co/yUDbUmvEqT
Worried about your billing falling apart?
Join 300+ founders and builders discussing pricing and receive feedback in under 4hrs in our OSS Community : https://t.co/yf4Ufzn8hp
Looking for cracked engineers for @tryflexprice.
We're:
- Fast shipping (real fast.)
- Are at a place where we have literally 0% churn
- High ownership
- Serve our customers with the bestest of support and want to not ship anything that is sub-par
- AI native and reward agency
If you want to be a part of a ship that's on a roll and has exponential value of currently solving one of the most toughest infra problems for 100+ AI companies, come join us: https://t.co/Ww6Wz5W6lf