Consumption pricing
Move from seats to agent runs, tokens, workflows, credits, or any metered unit your product team can defend.
PRODUCT CATALOG
Model every pricing change on one commercial record.
Your pricing keeps changing. Credits now, hybrid pricing next. Product Catalog lets teams launch each change without rebuilding billing.
6,500+businesses globally
40+payment gateways
100+billing currencies
AI PRICING PRESSURE
AI products make packaging a moving target.
New usage units, credit rules, service tiers, regional prices, and enterprise exceptions appear before the last pricing motion has settled.
Bundling & unbundling
Bundle platform access, credit wallets, premium agents, onboarding, and support without creating a parallel price book.
Market expansion
Add currencies, billing frequencies, invoice descriptions, tax profiles, and accounting codes per market.
Assisted-sales GTM motion
Carry ramps, add-ons, one-time services, and entitlement limits into the subscription and revenue schedule.
The catalog is the control layer. It decides what can be sold, how it is priced, where it appears, what the customer gets, and how finance treats it downstream.
CATALOG MODEL
Give every sellable object a downstream job.
Operating your Revenue GTM from one unified catalog makes monetization and business model pivots possible.
Product families
Set boundaries for suites, brands, regions, and business lines so teams don't mix unrelated offerings.
Plans
Define the subscription promise: billing cycle, trial, metered setting, portal visibility, and plan identity.
Addons
Attach recurring expansion paths such as credit wallets, premium agents, support tiers, and usage overages.
Charges
Represent one-time or event-based work such as onboarding, implementation, migration, or termination fees.
Price points
Hold the market-specific version: currency, frequency, price model, invoice name, tax, and accounting fields.
PRICING MODELS
Model AI-native pricing first. Support the classics too.
Start with usage, credits, commitments, and hybrid subscriptions. Then layer in flat fee, per unit, tiered, volume, stairstep, and package pricing.
AI-native models
Metered usage
Agent runs, API calls, tokens, executions.
Credit wallets
Prepaid credits across usage tiers.
Committed usage
Upfront commitments with overages.
Hybrid
Base fee + usage + addons.
Classic models
Flat fee
Fixed recurring.
Per unit
Seats, agents.
Tiered
Prices per range.
Volume
Single band.
Stairstep
Flat per band.
Package
Blocks, bundles, tiers.
PRODUCT TOUR
Configure what customers can buy, use, and renew.
Define the subscription promise
Plans define the subscription promise: who can buy it, how long the trial runs, when billing starts, what renews, and whether usage is measured.
- Create plans inside a product family.
- Set trial behavior and billing cycle rules.
- Choose whether the plan appears in checkout and self-serve portal.
Create Plan
Product familyAI Support SuitePlan IDagent-platform-enterpriseMetered planEnabledCheckoutHidden for enterpriseTrial period30 daysPortal visibilityVisible to admins
Price Points
| Currency | Freq | Model | Price |
|---|---|---|---|
| USD | Monthly | Package | $125,000 |
| USD | Annual | Tiered | $1,320,000 |
| EUR | Annual | Volume | €1.260.000 |
| GBP | Quarterly | Per unit | £310,000 |
Localize offers without fragmenting the catalog.
Price points carry regional and term-specific variants. Change currency, frequency, invoice language, tax treatment, and accounting fields without multiplying plan records.
- Set customer-facing and system names for each price point.
- Configure flat fee, per unit, tiered, volume, stairstep, or package pricing.
- Add descriptions and invoice notes for customer-facing clarity.
FINANCE FIELDS
Set tax, accounting, and revenue rules at the SKU level.
When a SKU is created, attach taxability, accounting code, revenue category, invoice description, and service-period logic so downstream teams don't need to rebuild that context later.
01Tax profile
EU VAT, US sales tax, GST, exempt rules
Mapped02Accounting code
Deferred, services, and overage revenue
Synced03Service period
Start and end dates for revenue schedules
Required04Invoice notes
Customer-facing description and quote copy
VisibleENTITLEMENTS & USAGE
Control access, track consumption, and bill overages.
AI products need more than feature gates. Plans and addons should define usage limits, credit allowances, consumption rules, rollover behavior, and the overage charges that apply when customers grow past their included usage.
- Map features, usage limits, and credit allowances.
- Track consumption against included agent runs, credits, or API calls.
- Apply metered overages or expansion charges when usage crosses the limit.
Usage and entitlement matrix
| Control | Starter | Growth | Enterprise |
|---|---|---|---|
| Agent runs included | 10k | 100k | Custom |
| Usage tracking | Monthly | Real-time | Real-time |
| Overage rule | Blocked | Per 1k runs | Contracted |
| Credit rollover | No | 30 days | Custom |
| MCP access | No | Read | Read + act |
QUOTE TO REVENUE
Move from approved offer to financial outcome.
A pricing decision is only complete when the quote, subscription, invoice, collection workflow, and revenue schedule can all read the same terms.
Configure and quote from approved terms
Product, RevOps, and finance define the commercial object once. Sales quotes from approved products, addons, charges, coupons, billing frequencies, price points, and discount rules.
Catalog → CPQConvert the deal into billing instructions
Accepted quotes become subscriptions with plan quantity, recurring addons, one-time charges, trial rules, renewal terms, ramp terms, usage rules, and entitlement access.
CPQ → BillingRecognize, report, and query the same record
Revenue recognition uses service period, accounting code, charge type, contract context, and invoice line detail. Finance, RevOps, and AI clients query the same operational record.
Billing → RevenueAI-NATIVE CATALOG
Let agents inspect live commercial terms.
AI workflows become more useful when they can inspect live plans, price points, usage rules, invoice lines, collection status, and revenue treatment.
$ find plans where credits expire before renewal
$ list addons with metered usage and no tax profile
$ show price points used by enterprise AI contracts
$ summarize packaging changes for finance review
Catalog review artifact
3 geos need tax-invoice reviewHIGH
EU VAT included, US tax excluded, India GST included. Review invoice language before launch.
1 plan has RevRec-sensitive service periodHIGH
Enterprise onboarding charge
2 addons carry metered behaviorMEDIUM
Credit Wallet, Agent Run Overage
Frequently asked questions
What does Product Catalog include?
It includes product families, plans, addons, charges, coupons, coupon sets, and price points. Every quote, invoice, credit note, report works on top of the same product catalog.
Which pricing models can it support?
Metered usage, credit wallets, committed usage, hybrid subscriptions, flat fee, per unit, tiered, volume, stairstep, and package patterns.
How does Product Catalog help finance?
Your teams can use the same catalog configuration for both self-serve and sales-assisted workflows. This means every deal and trial cycle borrows from the same shared understanding of your plans, products, and pricing. It also means Finance can build guardrails around the selling process and ensure prevention of incorrect deal configurations or discount coupons that could otherwise lead to revenue leakage or reconciliation issues.
What is the advantage of a unified catalog for self-serve (PLG) and sales-assisted (SLG) use cases?
Shared catalog context means companies have the flexibility to pivot from one GTM model to another or implement a hybrid model where complex deals or products are sold via sales-assisted workflows while straightforward operations or products can be managed via self-serve means. A unified catalog also means everything from quoting to invoicing to collections to revenue recognition operates in sync, with a clear understanding of what was sold, provisioned, and consumed.
How does it connect to entitlements?
Features, usage limits, credit allowances, and overage rules can be mapped to plans and addons so product access follows the commercial terms.
What can my team ask the MCP server?
Real revenue questions, in plain language: "What is the revenue per plan distribution today?" "Which plans should I retire based on MRR growth and customer churn data?" "Pull the average discount applied per plan." See the full set in the MCP recipe library, with 25+ verified prompts for finance, CS, RevOps, and product.
Change packaging without losing financial control.
Keep each pricing motion connected to the systems that quote, bill, collect, recognize, report, and answer questions about revenue.