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

Designing a subscription promise that stays coherent across billing, lifecycle states, entitlements, rewards, competitions, and Back Office operations.
The work connected the customer promise to the rules and operational controls required to keep it consistent over time.
Connected billing, access, rewards, competitions, and future commitments as one subscription system.
Made the distinction between fixed benefits, current estimates, lifecycle states, and allocation rules explicit.
Linked customer-facing behavior with Back Office control and delivery-ready decision areas.
A development board showing subscription-related work moving through implementation. It demonstrates delivery context, not authorship of every visible item.
A subscription must remain understandable after purchase, not only during checkout.
Billing, access, rewards, tickets, and future commitments can change at different times.
Customer behavior and Back Office controls need to follow the same product rules.
Keep the promised ticket entitlement stable while presenting its current estimated euro value as changeable context.
ContributionClarified the customer promise and its changing estimate
Make limited competition capacity and the handling of subscription entitlements explicit.
ContributionStructured allocation and carry decision areas
Preserve the offer a subscriber accepted and make unfavorable future changes explicit.
ContributionDefined offer-version and change-management principles
Keep temporary payment disruption distinct from a fully ended subscription.
Treat billing-cycle changes as lifecycle transitions with timing implications.
Separate product discovery from a confirmed entitlement reservation.
State and transition evidence for the ongoing subscription relationship.
Back Office evidence for managing the system behind the promise.