Pricing and Packaging
Pricing and packaging determines what a software customer receives, what unit they pay for, and how the bill changes as their needs grow. It connects product value to plans, limits, and billing rules.
itEngineering leadership and delivery management | OpenSkills.info
Course pathWalk it in order
Look it upDip in anytime
Go furtherLeaves this page
Don't Panic
Don't Panic: Pricing and Packaging
A price is a rule for turning a customer's choice and use into a bill. A package is the set of capabilities and limits they get for that bill. If the package promises shared dashboards and the application does not grant them, the beautiful pricing page has achieved very little.
Start with the job the customer is trying to do. Then ask what grows when that job grows. That is the value metric: perhaps active users, processed transactions, or stored data. The thing you can count and charge for is the billing unit. It may be a useful stand-in for value, but it does not become value merely because a database can count it. A meter that counts retries as fresh work can make an invoice accurate to the wrong number.
Plans turn this into choices. A starter plan might include a smaller allowance. A team plan might add collaboration and administration. An upgrade should correspond to a new need or larger scale that the customer recognizes. Otherwise the tiers are a collection of names asking to be decoded. An entitlement is the product's access rule for each plan. The name on the invoice and the feature check in the application need to describe the same purchase.
There are several ways to calculate the amount. A flat fee stays the same through the billing period. A seat fee depends on a defined seat count. Usage billing depends on measured units. A hybrid adds a recurring base to a usage component. Each choice moves work somewhere. The predictable flat fee needs clear package boundaries. The usage model needs a trustworthy meter and a customer-visible usage total, because nobody enjoys discovering a billing rule for the first time on an invoice.
One small trap deserves its own flashlight: “tiered” does not specify the calculation. Volume pricing chooses one rate from the final quantity and applies it to every unit. Graduated pricing applies each band's rate only inside that band. The same tiers can produce two different totals. Write the calculation, including what happens exactly at the threshold.
The useful next stop is the Slides tab for the whole path from customer job to invoice. The Cheatsheet gives the formulas and boundary cases. The Practice Reference turns them into a scenario table, and the Exercise lets you calculate a fictional two-plan offer. Use the Reference tab when a real billing system needs exact configuration. Pricing research never ends with a plausible number; it ends when buyers can predict the offer and the product can deliver it.
Where this skill leads
Relevant careers
See how this topic contributes to broader role-level skill maps.
Sources
- https://stripe.com/resources/more/saas-pricing-and-packaging-strategy
Supports
- Pricing versus packaging, value metric, plan structure, and performance signals
- Intro, slides, cheatsheet, quiz, and reference rationale
- https://stripe.com/guides/atlas/saas-pricing
Supports
- Practitioner examples of low-touch SaaS package grids and pricing decisions
- Reference rationale and Field Notes context
- https://docs.stripe.com/products-prices/pricing-models
Supports
- Flat, per-seat, usage, volume, graduated, and hybrid model mechanics
- Pricing calculations and quiz answers
- https://stripe.com/resources/more/hybrid-pricing-models
Supports
- Base fee plus usage structure
- Hybrid model quiz answer
- https://docs.stripe.com/billing/subscriptions/change-price
Supports
- Subscription price changes and proration behavior
- Change-management section and quiz
- https://stripe.com/blog/how-we-built-it-usage-based-billing
Supports
- Usage event processing and accurate price changes
- Field Notes metering card and reference rationale
- https://www.chargebee.com/docs/billing/2.0/product-catalog/plans
Supports
- Plans, price points, tier methods, and existing subscriber behavior
- Intro, product landscape, and reference rationale
- https://www.chargebee.com/docs/billing/2.0/entitlements/managing-item-price-entitlements
Supports
- Price-level feature entitlement mapping
- Intro, quiz, and reference rationale
- https://developer.paddle.com/build/products/create-products-prices/
Supports
- Product and price catalog distinction
- Paddle landscape placement
- https://support.withorb.com/articles/1957651072-understanding-plans-in-orb
Supports
- Fixed and usage price components in plans
- Orb landscape placement
- https://getlago.com/
Supports
- Usage, subscriptions, credits, and entitlements
- Lago landscape and Awesome Links rationale
- https://stripe.com/billing
Supports
- Stripe Billing subscriptions and usage-based pricing
- Stripe landscape placement
- https://www.paddle.com/billing
Supports
- Paddle subscription billing
- Paddle landscape placement
- https://www.chargebee.com/billing
Supports
- Chargebee billing and plan models
- Chargebee landscape placement
- https://www.withorb.com/
Supports
- Orb metering and billing positioning
- Orb landscape placement
- https://github.com/sindresorhus/awesome
Supports
- Starting index for the actual topic awesome list
- https://github.com/kdeldycke/awesome-billing
Supports
- Discovery of Lago and MeterGuard as relevant ecosystem projects
- https://github.com/geminimir/meterguard
Supports
- Deduplication and invoice reconciliation project behavior
- MeterGuard Awesome Links rationale
