In 2023, about 23% of support calls from site hosts were about understanding revenue sources
They had to reach out to account managers to get their quarterly data for bookkeeping, business analysis, identifying key cash losers, etc.
My role for this project was that of a product partner & designer.
Key Contributions:
Challenging product assumptions
Identifying key customer pain points
Planning for scalability
Content Tagging
User Interviews
Collaborators
Front End Engineering Team (4)
VP of Engineering
Product Manager
Co-founder, President
The legacy interface was designed for engineers, not site hosts
“I don’t know how much money I’m actually making”
This severely undermined the station’s business viability and hurt the company's opportunities.
“I can’t get the numbers I need without emailing someone”
Account Managers and the engineering teams found themselves manually generating repetitive reports for the site hosts who called.
"I can't compare past performances without scrolling like a crazy person"
Without clear visual hierarchy or design intent, hosts were overwhelmed and under-informed—unable to make revenue-impacting decisions from the sessions page.
The dashboard they had wasn't much help either
So, the goal was simple.
Remove the need to handle a gazillion spreadsheets, & bring the right data to the business without manual outreach.
The solution that made it to production
New badges for each Payment type (see color badges)
Now, the viewer could tell exactly how the charging session was started, aka the source of the revenue.
Mobile app, roaming partners, guest charging or payment terminal on a station.
The idea was for the Payment Activity filter dropdown to look like a cashflow statement.
Outbound (lost revenue) and Inbound (incoming revenue) categories separated, just like CFO or an accountant would like to see.
Real numbers and the filtering capability all in the same view!
Historical data is now just a click away
24 hours, 3 months, quarterly, for a whole year or a custom time duration of user's choice.
Of course, we could never achieve clarity without better data hierarchy - one that made intuitive sense.
So, we:
Rearranged the columns
Added more meaningful columns like State of Charge.
Most importantly, we removed data like station serial numbers, address of the site and other information that made sense hidden from the main view.
Updated future state
Allowing the user to download the data as a csv report. This was not included in the MVP due to the complex nature of the data aggregation required, which would surpass the time constraints for the project.
Adding more source types like unexpected, "unbillable" sessions. These are sessions that are not billed due to technical issues (with our system, the payment processor) and therefore, cannot be paid out.
Building the rest of the payments ecosystem, like payout information, contract details and more customized reporting.