SaaS MVP Development
A single operational view built for a team that currently has to check three or four separate systems to answer one customer question.
Project Overview
The client was an operations team at a mid-size SaaS company whose account data — usage, billing, support history, and plan status — lives in separate systems that don't talk to each other.
Problem
Answering a simple question like "is this account at risk of churning" means checking a billing system, a usage analytics tool, and a support ticket history separately, then piecing the answer together by hand.
Discovery
Discovery centered on which questions the operations team actually asked day to day, and which existing systems hold the answer to each one, so the dashboard surfaces what's genuinely useful rather than everything that's technically available.
Solution
A unified dashboard pulls account, usage, and support data into one view per customer, with a small set of derived signals — like a usage trend line or a recent support escalation — surfaced automatically instead of requiring a manual cross-reference.
Design Process
Wireframes focused on the single-account view first, since that's where an operations person spends most of their time, before expanding to the account-list and filtering views.
Technical Architecture
A backend service aggregates data from the billing API, the product's own usage events, and the support system on a scheduled sync, normalizing it into a shared account model that the dashboard queries directly.
Implementation
Built incrementally, starting with read-only reporting before layering in any actions the operations team could take directly from the dashboard, such as flagging an account for follow-up.
Technologies Used
Key Features
One unified account view combining billing, usage, and support data
Automatically surfaced signals like usage trend lines and recent escalations
A scheduled sync layer normalizing data from three separate systems
Read-only reporting first, with account actions layered in incrementally
Challenges
Billing, usage, and support systems each have their own definition of an "account," and reconciling those into one consistent model is most of the real engineering work.
It's easy to keep adding metrics until the dashboard is as hard to parse as the separate tools it replaced — restraint in what gets surfaced matters as much as the data pipeline itself.
Outcome
The result gave the operations team a single, trustworthy view of account health instead of manually cross-referencing multiple systems for every customer question.
Lessons Learned
Reconciling three systems' different definitions of "an account" turned out to be most of the real work — and restraint in what gets surfaced mattered as much as the data pipeline itself, since it's easy to rebuild the same sprawl the dashboard was meant to replace.
More Capability Showcases
