Strategy & design

Software people understand without being told.

We design applications that work logically and efficiently for staff, customers and citizens — and that match how they actually do their work.

Discuss your project See our approach

Does this sound familiar?

Software that works technically but goes unused is an expensive form of nothing.

Staff fall back on Excel

The system exists, but people keep their own lists because it's faster. And with that, the overview the system was meant to provide disappears.

Every new hire needs training

If software only works with an explanation attached, every new starter costs time and the same mistakes keep returning.

Customers drop off halfway

Requests and orders get started but not finished, and nobody knows exactly which step is losing them.

The screen follows the system, not the work

The database structure has surfaced in the interface, so users have to think like the software instead of the other way round.

What we do

Design that does not stop at how something looks, but starts with how it is used.

User research

Sitting with the people who use the software daily, and seeing where it genuinely breaks down.

Information structure

Organising what belongs where, so people find what they need without learning where it lives.

Interactive prototypes

Clickable versions that can be tested before anything is developed.

Interface design

Screens that bring calm to complex processes, even with a lot of data on show.

Design systems

Reusable components, so new screens stay consistent and are quicker to build.

Accessibility

Usable by everyone, including with a keyboard, a screen reader or limited vision.

Proven in practice

Applications people use without instructions

Projects where the design decided whether users completed their task smoothly — or gave up.

Bike lease portal and product configurator

Employees configure a bike on their own within the applicable rules and budgets.

Digital platform for complex applications

Submitting applications, uploading documents and tracking progress without assistance.

Concept for an automated collection kiosk

A kiosk that identifies drivers in a few steps and confirms their collection.

Central management system for a beverage wholesaler

Stock, orders, sales and customer information laid out clearly in one environment.

View all projects

Our approach

Designing is deciding. We make those decisions while they still cost nothing.

Understanding who uses it

We talk to and observe the people who work with it daily. What do they actually do, which workarounds do they take and why.

Mapping the flows

The key tasks from start to finish: which steps are needed, which can go and where the decision points sit.

Designing the screens

From rough layout to finished interface, with attention to hierarchy, readability and the moments where mistakes happen.

Testing with real users

We put a clickable prototype in front of the people who will use it. Whatever isn't understood gets changed before there is any code.

Handing over to development

Designs, components and behaviour are documented so developers have nothing left to interpret.

Adjusting after launch

Real use always differs from expectation. We track where people get stuck and improve where it matters.

Frequently asked questions

Is this only about how something looks?

No. Appearance is the final piece. Most of the work is about structure, steps and decisions: what sits where, what comes first and what can go.

Our software is internal. Is design really necessary?

Especially then. Internal users cannot walk away, so poor design shows up as slower work, mistakes and workarounds in Excel — every single day.

Can you design for software that already exists?

Yes. We revise existing applications, often step by step: starting with the screens where the most time is lost or the most mistakes occur.

How much of our staff's time does this take?

Limited but not zero. A few conversations up front and one round of testing with a clickable prototype. Without that input we would be designing on assumptions.

What exactly is an interactive prototype?

A clickable version of the application with no working technology behind it. Users can carry out real tasks in it, which surfaces problems before anything is built.

Do you also build the design?

Usually. Design and development sit in one team here, so nothing is lost in handover. If you work with your own development team, we deliver the design fully documented.

How is accessibility handled?

From the outset: contrast, keyboard operation, readability and screen reader support are design choices, not corrections afterwards.

How do we know the design works?

By testing it before the build and measuring use afterwards. Task speed, error rates and drop-off points say more than opinions.