Reprice without tickets.
Credits, tiers, hybrid seat-plus-usage, per-model rates — composed and published from the dashboard. Test a variant on a cohort, launch a new region and currency, reprice in minutes.
Updated August 2026Pricing that moves as fast as the market does.
Three steps. No engineering ticket.
Tiers, credits, hybrid seat-plus-usage, per-model rates — composed visually, no code required.
Run a variant on new signups, one region, or a percentage of traffic, and watch revenue impact per variant.
A pricing change is a publish, not a deploy. It takes effect for the next billing moment, fully versioned.
Every price is a version, not an overwrite.
Tiers, credit bundles, hybrid seat-plus-usage plans and per-model rates are all built as structured configuration in the dashboard, not code — the pricing engine treats a "price" as a versioned object with its own history, not a value that gets silently edited in place. That's what makes GTM able to own pricing directly: there's no PR to review, because there's no code changing.
Before a change goes live for everyone, it can run as an experiment — assigned to a cohort, a single region, or a percentage of traffic — with revenue impact measured per variant. That's the same mechanism whether you're testing a 10% price increase on new signups or trying a credit-bundle size in one market before rolling it out globally.
Because every publish creates a new version rather than overwriting the last one, existing customers stay on the version their contract was signed against — a customer on v9 doesn't wake up on v14 just because you published a change for new business. Enterprise commits are protected the same way: the terms a customer negotiated stay pinned to the version they agreed to, and a bad change can be rolled back as easily as it shipped.
A published price doesn't sit in a queue waiting for a deploy — it takes effect for the next billing moment and propagates instantly to everything downstream that reads the catalog: the customer portal, entitlement checks, and quote generation all see the new version the moment it's live, with nothing to redeploy or resync.
“We weren't scared of complex pricing. We were scared of the spreadsheet that made it work.”
FAQ
Does a price change apply retroactively to existing customers?
No, not by default. Every publish creates a new version rather than editing the last one, so existing customers stay on the version their contract or plan was set up against until you deliberately migrate them. New signups get the latest published version automatically.
Can I test a price change before rolling it out to everyone?
Yes — a variant can run against a cohort, a single region, or a percentage of traffic, with revenue impact measured per variant before you commit to a full rollout. This is the same experimentation mechanism whether you're testing a tier restructure or a new credit bundle size.
What happens to a customer's contract terms if I publish a new pricing version?
Nothing changes for them automatically. Enterprise commits and negotiated terms stay pinned to the pricing version a customer signed against, so publishing a new version for new business doesn't silently alter what an existing customer agreed to.
Do I need engineering to launch a new region or currency?
No — regions, currencies and localized pricing are configured in the dashboard the same way tiers and credit bundles are. It's a publish, not a deploy, so it doesn't require a sprint or an engineering ticket to go live.
Can I roll back a pricing change if something goes wrong?
Yes. Because every publish is versioned rather than overwriting what came before, rolling back a bad change is exactly as fast as the original publish was — you're switching the active version, not reconstructing what the old pricing looked like.