Designing a subscription promise that stays coherent across billing, lifecycle states, entitlements, rewards, competitions, and Back Office operations.

Explore Ooosch+ through 4 visual stories

Overview

The work connected the customer promise to the rules and operational controls required to keep it consistent over time.

Product-system design

Connected billing, access, rewards, competitions, and future commitments as one subscription system.

Entitlement clarity

Made the distinction between fixed benefits, current estimates, lifecycle states, and allocation rules explicit.

Operational buildability

Linked customer-facing behavior with Back Office control and delivery-ready decision areas.

Delivery evidence

Subscription work in delivery

A development board showing subscription-related work moving through implementation. It demonstrates delivery context, not authorship of every visible item.

Main Challenge

01

An ongoing promise

A subscription must remain understandable after purchase, not only during checkout.

02

Connected states

Billing, access, rewards, tickets, and future commitments can change at different times.

03

Operational consistency

Customer behavior and Back Office controls need to follow the same product rules.

Supporting Decisions

Payment Retry and Semi-Active Lifecycle Behavior

Keep temporary payment disruption distinct from a fully ended subscription.

Annual ↔ Monthly Plan-Change Rules

Treat billing-cycle changes as lifecycle transitions with timing implications.

Coming Soon vs Auto-Entry Reservation Behavior

Separate product discovery from a confirmed entitlement reservation.

Selected Evidence

Subscription Lifecycle

State and transition evidence for the ongoing subscription relationship.

Operational Auto-Entry Control

Back Office evidence for managing the system behind the promise.

Lessons Learned

The promise lives beyond checkout

Entitlements need operational counterparts

Versioning protects clarity

Explore other products

Back to Home