Data-intensive platform design

311% user growth, 325% lift on pricing tools

When the data is the product, the interface is where it either becomes useful or stays noise. We design platforms for people who make costly decisions quickly: analysts, traders, originators and the teams who answer to them.

The problem with data products

Most data platforms fail in the same way. The data is sound, the coverage is good, and nobody can find the number they came for. Screens fill with everything the system knows rather than the handful of figures that change a decision, and every new release adds another panel.

The work is deciding what earns its place on screen, what belongs one click away and what should never have been surfaced at all. That is a product judgement before it is a design one, and it needs someone who can hold both.

What we do

We start with the decision, not the dataset. Who is looking, what are they about to commit to, what would change their mind, and how long have they got. From there the structure of the product usually declares itself.

Then the detail: pricing views that survive a volatile day, comparison tools people trust enough to act on, multi-currency and multi-market handling that does not leak into the interface, and reporting that holds up when it is forwarded to someone senior.

Where this comes from

Product direction and experience design for market intelligence and trading tools in renewable energy, supporting more than 32 GW of investment decisions, with 311% growth in users and a 325% lift on the pricing tools specifically. Alongside that, enterprise analytics and multi-currency systems in regulated financial environments.

Do you need domain knowledge in our market?
Not at the start. We have worked in energy, financial data and insurance, and the pattern is the same: the people who understand the market are already in your building. Our job is to ask them the right questions and turn the answers into a product, not to arrive as instant experts.
We already have the data. Is this just an interface job?
Usually not. Most of the value comes from deciding which figures earn a place on screen and which decision each view is meant to support. That is product work, and it tends to change what the data layer is asked for.
Can you work alongside our existing engineering team?
Yes, and that is the normal arrangement. We bring product direction and design, and work to your team's stack and release process rather than asking them to adopt ours.

Talk to us about this kind of work.

Tell us what you are building and what makes it hard. A short note is plenty, and it comes straight to Juan and Andrew.

Start a conversation