Plans, pricing models & subscription lifecycle
How this is scored
How the product models what is sold and to whom: plans, add-ons and price points, trials, upgrades and downgrades with proration, usage-based and seat-based pricing, contract terms and renewals, quotes, and a self-service portal where the customer changes or cancels their own subscription.
0 — No subscription model; recurring charges are set up by hand per customer or per invoice.
3 — A recurring invoice or a fixed plan that repeats on a schedule, but no proration, no trials, no add-ons and no usage component.
5 — Plans with add-ons and trials, upgrades and downgrades with proration, renewals and cancellations handled by the system, and a customer portal for viewing and changing the subscription.
8 — Usage-based, tiered, volume and seat-based pricing with metering through an API, contracts with minimum terms, ramps and notice periods, quotes that convert into subscriptions, multiple currencies and price books, and the subscription history kept per customer.
10 — The commercial model lives in the product: hybrid pricing (commitments, prepaid credits, overage) without custom code, price changes rolled out to existing customers with grandfathering, entitlements exposed to the selling application, and every change to a subscription versioned and attributed.
The Service-Business Owner
The pages describe a single billing core that natively supports usage-based, subscription, hybrid and outcome-based models with multi-currency operations, pricing changed through configuration rather than custom code, renewals and credits surfaced in the Salesforce and ServiceNow applications, and events for service provisioning and entitlement management. I found no public information on trials, proration, quotes converting into subscriptions, minimum contract terms or a self-service customer portal, so the commercial engine looks deep while the lifecycle details my maintenance contracts depend on stay undocumented. 3 4 5