Sign in →
1 min read

Pricing Studio — Overview

Turn billable units into priced offers customers can buy. Plan Studio designs the rate card, Offerings packages it, Subscriptions bind customers to it, and Invoices bill it.

Updated 2026-07-29Suggest edits

Pricing Studio is where catalog items become money. You design rate cards in Plan Studio, package them into offerings customers can subscribe to, run promotions and sales-led quotes against them, manage the subscriptions that result, and produce invoices + revenue-recognition entries on the other side. Nine pages, one workflow.

What Pricing Studio is for#

It owns every commercial artifact between "you defined what to count" (Catalog) and "money landed in your ledger" (Intelligence + ERP Sync). Rate cards encode the maths. Offerings encode the shopfront SKU. Subscriptions encode the contract. Invoices encode the bill. Revenue Recognition encodes the accounting. CPQ adds a sales-led layer when self-serve doesn't fit.

The end-to-end flow#

pricing-studio.flowLIVE
DESIGN
Plan Studio
visual editor
Pick a pricing model + billable unit, set rates, included quotas, tiers.
minutes
PACKAGE
Rate Cards + Offerings
bundle for sale
Group rate cards into offerings with billing mode (PREPAID / POSTPAID / HYBRID).
—
PROMOTE
Promotions
coupons + discounts
Time-bounded codes (% off, $ off, free trial days). Per-customer or per-offering scope.
—
SELL
Subscriptions or CPQ
self-serve vs sales-led
Customer subscribes via storefront, OR sales sends a quote → approval → acceptance.
—
BILL
Invoices
bill runs
10-stage pipeline: Aggregate → Rate → Discount → Tax → Route → Settle.
periodic
RECOGNIZE
Revenue Rec
ASC 606
Schedule recognition by performance obligation, post journal entries to GL.
monthly
catalog → pricing studio → intelligence + ERP sync// p95 < 5ms

Pages in this section#

Rate Cards
CRUD on rate cards, version pinning to subscriptions, M:N product + metric associations.
Open
Offerings
Bundle one or more rate cards into a buyable SKU. Billing mode, billing cycle, currency, status.
Open
Promotions
Coupon engine. Percentage / fixed / free-trial-days. Eligibility filters by customer or offering.
Open
Subscriptions
Customer ↔ offering binding. 9-state lifecycle (TRIALING, ACTIVE, PAST_DUE, …), upgrade / downgrade / pause / cancel.
Open
Invoices
Invoice lifecycle (DRAFT → OPEN → PAID / VOID / UNCOLLECTIBLE), credit notes, dunning, PDF, ERP sync.
Open
Revenue Recognition
ASC 606 performance obligations, deferred / recognized revenue schedules, journal-entry export.
Open

Self-serve vs. sales-led#

Pricing Studio supports both motions in the same engine. The difference is the contract-creation path; everything downstream (billing, recognition, dunning) is identical.

DimensionSelf-serve (Offerings)Sales-led (CPQ)
Customer signs up viaStorefront page or APISales rep emails a signed-URL quote
Pricing isPublished rate plan, list priceNegotiated — discounts gated by approval rules
Contract artifactSubscription record on acceptQuote PDF accepted via click-through, then subscription
Best forMid-market, PLG motion, repeatable SKUsEnterprise, negotiated terms, custom commits
Where to readSubscriptions + OfferingsCPQ

Six pricing models, one engine#

Every rate card uses one of six models. The bill-run pipeline computes them identically — pick the one whose maths matches the deal, not the one with the longest feature list.

ModelMathsUse when
PER_UNITunits × rate (after included free)Steady per-call pricing — APIs, tokens.
FLAT_RATEfixed price regardless of usageSeat-based, platform fees, "starting at" SKUs.
PERCENTAGEraw units × rate / 100, with optional minFee floorMarketplace take-rate, % of GMV.
INCLUDED_QUOTAfree up to N, then per-unit OR per-block overageTiered SaaS with included credits.
GRADUATEDeach tier charged at its own rate (staircase)Volume discount that applies per-tier — first 1k at $0.05, next 9k at $0.04, …
VOLUME_TIEREDentire volume charged at the tier the total falls intoCliff pricing — cross 10k and the whole bill drops to $0.04.
PRO TIP
Plan Studio ships a built-in bill simulator — drop in a synthetic month of usage and see what each pricing model would have invoiced before you publish. Use it on every non-trivial rate-card change.

Subscription lifecycle in one breath

A subscription walks a 9-state machine: CREATED → TRIALING → ACTIVE → {PAST_DUE | PAUSED | EXPIRING_SOON | SUSPENDED} → {EXPIRED | CANCELLED}. Cancel is terminal. Upgrade / downgrade / pause / resume / retry-payment / convert-trial are the six lifecycle actions exposed on the subscription. Read the Subscriptions feature page for the per-action semantics and the state diagram.

After pricing: invoices and revenue#

Once a subscription is generating events, the bill-run pipeline kicks in. The 10 stages are: QuotaCheck → Rollover → Aggregate → Allowance → Rate → Commit → Discount → Tax → Route → Settle. Each one is documented in the reference. Revenue Recognition runs in parallel — every invoice line maps to a performance obligation with its own recognition schedule.