YIRUO

Chrysalis

How I redesigned and shipped the Admin Console's subscription flow to transition 8x8 from rigid licensing to a modular consumption model, helping drive 60% year-over-year growth in usage-based revenue.

Context

Project Chrysalis marked a strategic shift from the bundled X-Series model to a granular "Lego Block" approach.

Problem statement map outlining core friction and opportunity areas.

The Goal

Consumption-based model

Move from manual CPQ flows to self-service consumption.

Additional revenue

Enable modular monetization tied to growth goals.

Partner empowerment

Let partners configure accounts independently.

Design Strategy

Modular assignment

Flexible capability assignment.

Dependency intelligence

Auto-add prerequisites with clear guidance.

Bulk operations

Scalable bulk assignment/editing.

MVP Partner Flow

MVP partner journey and redesigned subscription assignment workflow.
Before: assigning rigid X-Series licenses in the legacy flow.
After: assigning modular subscriptions in the new Chrysalis flow.

Impact

  • Usage-based revenue grew nearly 60% year-over-year.
  • Partners reported clearer, more intuitive workflows.
  • Modular setup increased product adoption.

Future Vision

Partner hierarchy, direct customer management, and scalable bulk assignment for enterprise scale.

Problem framing 1
Problem framing 2
POC walkthrough: partner customer-to-user navigation model.
POC walkthrough: high-volume bulk assignment at enterprise scale.
Next case study: Contact Center Script Redesign