Design Team - Anas, Ruthiran, Sathyan

Backstory

RevenueStory is Chargebee’s subscription analytics platform that enable our merchants to take better business decisions with data. Revenue Story was built as a sepearte product that focuses on Subscription Analytics. A couple of years of its existence, a decision was made to bring it as a part of the core Billing Product (Chargebee) There was a significant design debt as the team had constantly catered to the unique requirements of the Customers. The time was right for a revamp which focuses on building a UX System which scales to cater to varied use cases such as Report builder and embedded Analytics

It was a multi year project which saw Stakeholders changing across the teams.

Customer Feedback

"The platform isn't flexible, and we can't customize reports to fit our business needs. There are too many reports, and it's difficult to find the ones our users need. The reports are scattered in different places, and some look similar, making it confusing. We're not sure how Chargebee constructs reports, and we have to use external BI tools for in-depth analysis because Chargebee doesn't have that feature. Startups hope that Chargebee can be an all-in-one solution for billing and subscription analytics, saving them time and money."

Workshop and Vision

We had to regroup to understand the vision for the revamp. "Revamps are expensive and clearly need to articulate the need and the RoI of the same. It was clear that the current system won't scale and can't be adopted by aquired products.

Opportunity Areas

The workshop and customer feedback help identify the following opportunity areas: Deep dive into a report should be available across the system starting with the dashboard Enable quick slice & dice of data with various parameters. Scale to meet the usecases of acquired Offering - RevRec and Receivables. Explore the possibility of core Analytics module being the central platform to cater all analytics needs across products UX and UI System for Embedded analytics

Prototype

An exhaustive Figma Prototype was created to validate the system design with the customers. With postive feedback on the approach the team set out to deliver the MVP which gathers positive feedback from all stakeholders.

Customer Validation

The team created early prototypes that was valdiated with the customers. The feedback was positive and we were able to identify the gaps in the current system.

Future

The system developed has been adopted by 2/3 acquired products; The underlying experience layer is governed by the technology and this needs to be power all the analytics going forward.