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 SaaS Founder
This is exactly the usage tier I'm planning: metering through a non-rate-limited Usage API, five pricing models (fixed, tiered, volume, stairstep, ramp up to twelve intervals), charge by price-per-unit or percentage, and a recurring plan fee that can be set to $0 for a strictly usage-based plan. Trials, renewals, expiry through dunning and a hosted account-management page for billing updates are all handled by the system, and an entitlements endpoint exposes grants to my application. Two caveats: the pricing model is locked at plan creation, and usage can only be logged via API, so structural changes mean new plans rather than edits. 5 6 2 14 12