Design partner program · 20 places · launching Q1 2027
Pricing, with an undo button.
Raise prices on the customers you already have: at renewal, in waves, against a holdout. If it misses, undo it in one click, without touching a single finalized invoice. Stripe keeps moving the money.
Curious how it works? Try the undo button below.
- Wave 110%
- Wave 240%
- Wave 3rest
- Customers on v4
- 0
- Increase realized
- —
- Churn vs holdout
- —
- Finalized invoices edited
- 0
- D−30v4 approved by Product and Finance
- D−30Notice sent to wave 1, per contract
The price-realization gap
You planned +10%.
You realized +4%.
Grandfathering by spreadsheet
Every past price lives on in a tab somebody maintains by hand. Nobody can say what moving those customers is worth.
Every change is a sprint
Pricing sits in product code, so a new tier waits for engineering, and the increase waits for next quarter.
There is no way back
Stripe Billing can't version a plan or reverse a rollout. So teams don't raise prices on the base. They just hope.
Free, no strings
Get a pricing teardown of your current plans.
We read your public pricing page and pull its history as far back as we can find, up to 24 months. You get one page back, scored on a fixed rubric, with what we observed kept apart from what we suspect.
- Value metric, packaging and price architecture, against your peers
- How your pricing has changed, and what that left behind: legacy plans, grandfathered customers
- Repricing readiness: what breaks when you next change pricing
- Three hypotheses, each with a cheap test you could run
How it works
Propose. Simulate. Approve. Roll out. Roll back.
Pricing changes with a review process, not a Slack thread and a spreadsheet.
- 01
Connect
Import your Stripe catalog with a dry-run. Map customers and vaulted cards. Stripe stays as the payment rail.
- 02
Version
Define plans, add-ons, credits and entitlements as versions. Existing customers are grandfathered by default.
- 03
Roll out
Simulate a new version on twelve months of real data, approve it, and release it at renewal to a cohort, never before a customer's notice period allows.
- 04
Measure and decide
Watch MRR, churn and NRR against the holdout at Day 30, 60 and 90. Keep it, roll it back, or resolve the losing cohort in one click.
Keep Stripe. Own the rest.
Your pricing logic shouldn't belong to your payment processor.
Infinery is the source of truth for plans, entitlements, proration, tax and invoices. Stripe executes charges against vaulted cards and knows nothing about why.
- Flat price. Never a percentage of revenue for billing logic.
- Portable. Changing processors later means moving a vault, not rebuilding pricing.
- Seats to outcomes. Seats, credits, actions and outcomes on one ledger, each move a versioned change.
Selling in the EU
Peppol-ready, for teams staying on Stripe.
Stripe Billing has no native Peppol. Infinery includes Peppol e-invoicing, VIES reverse charge and gapless numbering, so your invoices land in procurement systems and get paid faster.
- Belgium
- B2B e-invoicing since 1 Jan 2026 · penalties since 1 Apr 2026
- France
- Obligation to receive e-invoices since 1 Sep 2026
- Every invoice
- Gapless numbering, VIES checks, UBL output
Design partner program
Your migration, done for you. Half the launch price, locked in.
20 B2B SaaS teams on Stripe who expect to change pricing in the next 12 months. We run your migration, you pay half of what Infinery will cost at launch until a year after it, and you help decide what we build next.
Managed migration
The founders move your catalog, subscriptions and customers off Stripe Billing and run the cutover. Cards never leave Stripe. After launch, this is a separate service priced at $2,000–$5,000.
50% of the launch price
A flat monthly subscription at half what Infinery will cost at launch, never a percentage of your revenue. The price after that is agreed at signing.
A say in the roadmap
Tell us which features and capabilities would help you most, and they move to the top of the list. You get a direct line to both founders while we build.
Also included
- A trapped-revenue model. How much MRR sits on old prices, cohort by cohort, and what moving it is worth.
- Your first repricing, run with us. Waves, notice periods, a holdout, and a rollback plan you hopefully never need.
What we ask
- A flat monthly subscription at 50% of the launch price. Never a percentage of your revenue.
- Your time. A short feedback call every two weeks while we migrate and run your first rollout.
Who it's for
- B2B SaaS, 10 to 200 people, selling to human business buyers
- On Stripe Billing, or on Chargebee, Paddle or Lemon Squeezy and feeling the ceiling
- Roughly €1M to €10M ARR. Smaller teams with a repricing on the calendar are welcome too
- A pricing change you expect to make in the next 12 months
Not for
- B2C subscription apps
- Marketplaces
- Anyone who wants a merchant of record
From application to first rollout
- Apply
Six fields, two minutes. No commitment.
- 20-minute call
We look at your catalog and the next price change you have in mind.
- Scope fixed
Migration date, deliverables and your locked price agreed by the second call.
- Migration
Dry-run, reconcile, cut over on the agreed date. Stripe Billing stays intact until then.
- First rollout
Your next price change shipped in waves, with the undo button live.
From the founders
Pricing is the biggest growth lever a SaaS company has, and the one it pulls least. Not because teams lack ideas, but because every change is a one-way door. We're building the billing layer that makes it a two-way door, and we're looking for 20 teams to build it with. If your next price change is already on the calendar, let's talk.
Questions
What partners ask before they sign.
What does becoming a design partner cost?
A flat monthly subscription at 50% of the launch price, locked until a year after launch; the price after that is agreed at signing. The managed migration is included. After launch it becomes a separate service priced at $2,000–$5,000. Beyond money, we ask for a short feedback call every two weeks while we migrate and run your first rollout.
How long does the migration take?
It depends on the catalog. Seat tiers move quickly; credits, add-ons and bespoke enterprise plans take longer. You get the date on the second call, and nothing changes for your customers until the agreed cutover.
What if it doesn't work out, or you disappear?
You keep everything. Stripe Billing stays intact until the agreed cutover and for 30 days after it, Stripe keeps the cards, and your full pricing history, customer and invoice data export at any time in open formats. Nothing is trapped.
We're on Stripe Billing and it works.
It works until the first price change. Stripe Billing has no plan versioning, no cohort rollout and no rollback. We import your Stripe catalog with a dry-run and keep Stripe as the rail.
Do we have to leave Stripe?
No. Stripe keeps your cards and moves the money. Infinery replaces Stripe Billing: the plans, subscriptions and invoices that decide what to charge.
We don't have the traffic to A/B test prices.
Most SaaS at your size don't. The rollout is the product: waves, notice periods, rollback. The holdout is a safety check, not a statistics project.
We'll build it in-house.
Most teams build a plan table and an entitlement check. Nobody builds renewal-aligned cohort rollout, notice-period gating, GAAP-safe rollback and gapless invoicing in-house, and the team that does maintains it forever.
Can't we just use a Stripe App for Peppol?
For transmission, yes. It won't fix VIES reverse charge, gapless numbering, or the invoices you issue when you next change prices.
Is the teardown really free?
Yes, and unconditional. You send a pricing page and get a one-page teardown within a week, whether or not we ever talk. The 20-minute walkthrough that comes with it is optional.