Case Study · B2B SaaS · Revenue Analytics

ReveniQ

Transforming revenue analytics and usage-based billing for SaaS finance teams.

I redesigned a complex revenue analytics dashboard and helped shape the product’s move toward usage-based billing. This work combined UX architecture, customer research, and product strategy to make financially dense workflows clearer, faster, and more actionable.

Role

Product Designer & Strategist

Platform

B2B SaaS · Web

Focus

Revenue analytics dashboard · Usage-based billing

Timeline

2024

Overview

Simplifying complex subscription revenue data for finance teams.

ReveniQ is a subscription analytics platform that helps SaaS finance teams understand and manage revenue, from complex breakdowns to usage-based billing.

My work focused on two critical areas: redesigning the revenue breakdown dashboard to make complex subscription data intuitive, and leading product thinking around the platform’s shift toward usage-based billing.

The Challenge

Finance teams were drowning in data.

Geographic analysis was slow and hard to compare across markets
Dense dashboards made revenue patterns harder to spot
Usage-based charges created cluttered invoices and time-consuming reconciliation
Reporting workflows required too much manual effort to prepare for board and stakeholder review

User Signal

“I spend 2 hours every week just trying to understand our revenue breakdown by region.”

Problem

Revenue analytics and usage billing workflows were too dense, too manual, and too hard to interpret quickly.

What I owned

Dashboard redesign, user research synthesis, dashboard architecture, billing workflow direction, and invoice consolidation thinking.

Constraints

Finance-heavy workflows, multi-market analysis, dense datasets, and a strategic shift into a new billing model.

Outcome

A clearer analytics experience plus a product direction for usage-based billing that improved reporting and billing clarity.

Solution 01

Dashboard redesign — a four-zone architecture

I redesigned the revenue breakdown dashboard around four functional zones, each optimized for a specific job in the analysis workflow. Instead of treating the page like one dense surface, I made it easier for users to orient themselves, filter data, change visualizations, and compare time periods without losing context.

My role here

Conducted user research with SaaS finance teams to understand reporting pain points
Defined the four-zone dashboard architecture to organize tasks by workflow intent
Redesigned the primary analytics interface around clarity, speed, and comparison

Main Dashboard View

Geographic Filtering

Multiple Chart Types

Time Period Comparison

Zone 1 · Geographic filter

Used a hierarchical filter model — Global → Region → Country → City — so users could begin broad and progressively drill down without facing a wall of locations.

Zone 2 · Main visualization

Gave the chart area most of the screen because it is where insights happen. Supporting controls were organized around it instead of competing with it.

Zone 3 · Chart controls

Allowed users to switch chart types and save views without resetting their selected data, preserving flow for recurring analysis and reporting.

Zone 4 · Time controls

Supported interval switching, quick ranges, and compare mode so users could understand both current performance and period-over-period change.

Decision

Organized the interface by analysis task rather than by data source, reducing cognitive load for finance users who cared about answers, not system structure.

Why it matters

This work demonstrates product thinking at the workflow level: not just “better charts,” but a clearer path to insight and faster recurring reporting.

Solution 02

Usage-based billing — pivoting toward a clearer invoice model

Beyond dashboard design, I helped lead the strategic shift toward usage-based billing — a critical need for modern SaaS companies moving beyond fixed subscriptions.

The problem was not only feature expansion. It was invoice clarity. Multiple prorated usage charges were creating cluttered invoices, reconciliation headaches, and a poor customer experience.

What I proposed

Invoice consolidation to reduce clutter from many prorated charge lines
Clearer billing summaries that improve readability for finance teams and end customers
Product positioning that strengthened ReveniQ’s relevance in a usage-based market

Strategic Contribution

I wasn’t only designing screens here — I was helping define how the product should evolve to serve a changing SaaS billing model.

The value of the solution

Clarity — simplified statements that are easier to understand at a glance
Time savings — less manual effort spent deciphering invoice complexity
Accurate reporting — improved transparency for finance teams
Better customer experience — clearer bills for end users