Usage Overview Product
Problem

Some of Zype's users we're increasingly running into issues in which they were getting slapped with a costly usage bill at the end of the month that they didn't foresee. At the time we didn't have an automated way of billing clients or showing them their current usage for the month, which understandably was frustrating for our clients.  

Working closely with the Project Manager, the Billing team and developers, I helped split this product up into phases since we needed to get the MVP launched quickly and we had limited developer resources. Although it wasn't necessary, I decided roughly mocking up our ideal billing dashboard would help dictate the MVP + iterations as to minimize the workload for our developers with each phase of the project. The MVP started with just showing their current usage that they would have to calculate themselves, unfortunately, to keep up with their balance. 
Wireframes:
The iterations above show how we decided to split up the feature launches.
 
MVP: Users can see their current usage for any specific month.
V2: From the backend, we would pull a user's unique overage thresholds based on their contracts and show them in the interface as a reference.
V3: To eliminate all annoying work for the user, we would pull the rate of these overage per individual client contract; with these numbers we could them calculate the overage balance and display in the interface.
V4: At this point, we could add all the bells and whistles of a true billing dashboard including the client's plan, current and past invoices, and a drilldown into their current usage (which could link to our already developed V3 interface).
Designs for the MVP, V2, and V3: 

After some sketching and iterating, I landed on a table format in V3 so that a user can quickly and easily scan to understand his/her usage balance and how we calculated this. The green and red colors within the progress bar of V2 and V3 give the user a quick hint at how much usage they have left for the month and if they've already exceeded this number. Each phase leads nicely into the next for minimal front-end development work.  
Usage Overview Product
1
37
0
Published:

Usage Overview Product

1
37
0
Published: