Valmond SaaS

Valmond SaaS Project Overview

A dashboard for a fintech platform whose customers were drowning in their own data. The design problem was not visualisation — it was deciding what a person needs to know in the ninety seconds they actually spend here.

The Brief

Valmond's existing dashboard showed forty-one metrics on one screen, all of them accurate and none of them ranked. Support tickets were dominated by questions the dashboard was supposed to answer, which is the clearest possible signal that it was not answering them.

Ranking Before Rendering

We started by interviewing users about what they check first, and built the page in that order.

• Three headline figures, sized to be read across a room
• One trend, with the comparison stated in words
• Everything else one deliberate click away

Nothing was deleted. It was demoted, which is a different argument to have with stakeholders and a much easier one to win.

Making Numbers Legible Under Pressure

Financial data is read quickly, often on a phone, sometimes by someone who is already worried.

• Tabular figures, so columns align at every value
• Colour used only for direction, never for category
• Every percentage paired with its absolute number
• States for loading, empty, stale and error, all designed

The stale state mattered most. A dashboard that silently shows yesterday's numbers is worse than one that admits it cannot reach the server.

A System the Team Could Extend

Valmond ships new modules monthly, so the handover was a set of composable blocks with their spacing and states already decided — not a set of finished screens that would be out of date by the second release.

Outcome

Dashboard-related support tickets fell by more than half in the first quarter, and the team has added nine modules since launch without a single new layout decision reaching the design queue.