Plan logic spread across systems
Commercial rules become difficult to maintain when product, billing and finance each hold part of the subscription model.
Revenue / Subscription Revenue
Run the complete subscription revenue lifecycle from plan to billing.
Connect plans, pricing, usage, proration, upgrades, downgrades and billing in one subscription revenue model.
Plans · Pricing · Usage · Proration · Upgrades · Downgrades · Billing
Commercial modelBilling outcome
PlanGrowth
PricingRecurring + usage
UsageCurrent period
LifecycleRecalculateApply proration and plan changes before the next bill
BillingNext period prepared
UpgradeApplied
ProrationIncluded
Why it matters
Subscriptions change after the customer signs up.
Plan, pricing and usage decisions continue throughout the relationship. Billing has to reflect upgrades, downgrades and proration without losing commercial context.
Without the right operating layer
Usage disconnected from pricing
Usage-based components lose accuracy when usage and commercial rules are processed separately.
Manual proration
Mid-cycle changes create operational work when upgrades and downgrades are not modeled as lifecycle events.
Billing without lifecycle context
An invoice can be technically correct but still fail to reflect the customer's actual subscription state.
With Zopio
Model plans and pricing
Keep the subscription commercial model explicit instead of embedding it in billing code.
Connect usage to revenue
Use usage as part of the current subscription revenue calculation where the pricing model requires it.
Handle lifecycle changes
Treat upgrades, downgrades and proration as first-class subscription events.
Produce billing from current state
Generate billing behavior from the active subscription model rather than historical configuration.
How it works
How subscription state becomes billable revenue.
Subscription Revenue keeps the commercial model current as plans, usage and lifecycle changes evolve during the billing period.
- 01Plan
- 02Price
- 03Measure
- 04Change
- 05Bill
Define the plan
Represent the commercial package the customer is subscribed to.
Apply pricing
Attach the recurring and usage pricing logic that defines the revenue model.
Measure usage
Bring current-period usage into the model where the subscription requires it.
Process lifecycle changes
Apply upgrades, downgrades and proration according to the current subscription state.
Prepare billing
Turn the active subscription model into the billable outcome for the period.
Core capabilities
Commercial subscription logic before the invoice.
The canonical scope covers the model that determines what should be billed as the customer relationship changes.
Plans
Represent the subscription packages available to customers.
Pricing
Define how recurring and other subscription charges are calculated.
Usage
Include measured usage when the commercial model depends on consumption.
Proration
Adjust revenue when subscription state changes during a billing period.
Upgrades
Move customers to higher subscription configurations without losing lifecycle context.
Downgrades
Apply lower subscription configurations according to the commercial rules.
Billing
Produce the billable outcome from the current subscription state.
Commercial lifecycle
Keep the subscription model independent from the systems that present or collect it.
Subscription Revenue owns the commercial state that determines what is billable, while collection and payment execution remain separate operating concerns.
Plans · Pricing · Usage · Billing · Recurring Collections · Payment Execution
Commercial stateKeep the current plan and pricing configuration explicit for every subscription.
Change traceabilityPreserve the lifecycle events that changed the billable outcome.
Usage alignmentConnect measured usage to the pricing model that consumes it.
Billing consistencyProduce billing from the same subscription state used to make commercial decisions.
Common use cases
Use Subscription Revenue where recurring relationships have changing commercial state.
The product is designed for subscription models that extend beyond a fixed monthly charge and need lifecycle-aware billing.
Plan-based subscriptions
Manage subscription revenue around explicit plans and pricing rules.
Usage-based components
Combine recurring subscription logic with usage-driven revenue where required.
Mid-cycle plan changes
Handle upgrades, downgrades and proration without manual billing reconstruction.
Subscription billing operations
Keep billing aligned with the customer's current commercial state.
Part of Zopio RevenueExecute → Repeat → Monetize → Recognize
- 01Revenue Execution
- 02Recurring Collections
- 03Subscription Revenue
- 04Revenue Recognition
Revenue Recognition is coming soon.
Modular by design
Start with what you need. Expand when you need more.
Use Subscription Revenue to own the commercial lifecycle from plan to billing, then connect recurring collection and payment execution when the bill becomes cash.
Talk to an expertRelated resources
Explore all resources