Use cases

SAPA’s primitives compose into ten baseline product shapes.

Product	Billing	Benefits	Recipe
Ebook	one-time	immutable download, optional customer email	Complete flow
Simple SaaS	subscription	period entitlement	Complete flow
Tiered SaaS	subscription	entitlement and resource limit	Complete flow
Usage-based API	metered subscription	period entitlement and postpaid policy	Complete flow
Team product	per-seat subscription	entitlement and seat capacity	Complete flow
Subscription desktop app	subscription	entitlement and license eligibility	Complete flow
Perpetual desktop app	one-time	perpetual entitlement and license eligibility	Complete flow
Credit pack	one-time	exact-unit usage credits	Complete flow
Desktop bundle	one-time	mixed perpetual, fixed-duration, and credit benefits	Complete flow
External course	one-time	entitlement and durable external fulfillment	Complete flow

Choose by business invariant

Start with what settlement promises, then select billing:

• A user permission is an entitlements benefit.
• Team occupancy is seat_capacity, not a quantity field on an entitlement.
• Consumable service units are usage_credits, not money.
• A downloadable file is an exact download asset revision.
• Device activation is license_eligibility attached to an entitlement.
• Work performed in another system is external_fulfillment.

Do not model everything as an entitlement boolean. Separate benefits preserve their own lifecycle, provenance, refund behavior, and operational guarantees.

Explore complete definitions for SaaS, desktop software, usage-based APIs, and digital products.