Internal tools deserve good design too
Staff use internal tools for hours every day, often far more than customers use your public product. Designing them well is one of the most direct ways to save time and reduce errors.
Service 07
Product design grounded in how people really use software
We design interfaces for web and mobile products, from early prototypes to complete design systems. Because we also build software, our designs account for real data, edge cases and technical constraints, so what you approve is what gets shipped.
- Outcome
- Software that people understand quickly and use without needing to be trained.
- Typical stack
- React, Next.js, TypeScript, Flutter
When this is the right call.
Users struggle with your product
Support requests, abandoned sign-ups and training sessions suggest people cannot find their way through the software on their own.
You need to test an idea
Before committing to a build, you want a clickable prototype that you can put in front of customers or investors to test the concept.
The interface has grown inconsistent
Different screens use different patterns, colours and components, making the product feel disjointed and slowing down development.
Internal tools slow people down
Staff use clunky admin screens all day. Small improvements to those workflows would save a noticeable amount of time across the team.
What you get.
User research and discovery
Interviews, workflow observation and analysis of existing usage to understand what people need and where they get stuck.
Journeys and information architecture
Clear structures for navigation, content and user flows, mapped out before any screens are designed.
Interactive prototypes
Clickable prototypes for testing ideas with real users and aligning stakeholders before development begins.
Interface design
Detailed, accessible screen designs covering real content, empty states, errors and loading, not just the ideal path.
Design systems
Documented components, tokens and patterns shared between design and code, so the product stays consistent as it grows.
Usability reviews
Expert review and user testing of existing products, with prioritised recommendations your team can act on.
How we approach it.
Good design starts with understanding the work people are trying to do. We talk to users, watch them use existing tools and look at the data before sketching anything. For internal and B2B software especially, the gains come from removing steps, reducing decisions and showing the right information at the right moment, rather than visual polish alone.
We move from rough to refined deliberately. Low-fidelity flows let us test structure cheaply; clickable prototypes let users and stakeholders react to something concrete; detailed designs come only once the direction is settled. Accessibility is part of every stage, from colour contrast and type sizes to keyboard navigation and clear error messages.
Designers and engineers work together throughout, which avoids the familiar gap between what was designed and what can be built. Designs account for real data lengths, permissions and failure states, and are delivered as a component-based system that maps directly to code. All design files and assets belong to you and are organised so another team can pick them up.
Tools we use for this work.
From first conversation to production.
- DiscoverUnderstand the business, the users and what success looks like.
- DefineRequirements, architecture, scope and a roadmap you can plan around.
- DesignThe product experience, tested before it is expensive to change.
- BuildEngineering in short cycles, with working software to review every sprint.
- LaunchTesting, deployment and making sure it holds up in production.
- EvolveSupport, improvement and scaling once real usage starts.
Common questions.
Can you design without building, or build from our designs?
Both. We can run a design-only engagement and hand over files and specifications to your developers, or build from designs your team has created. Many clients find it efficient to have design and build under one roof, but it is not a requirement.
What drives the cost of design work?
Mainly the number of distinct user journeys and screens, how much research is needed, and whether a design system is part of the scope. Redesigning an existing product also depends on how much of the current structure can be kept. We scope design in phases so you can review direction before committing to detail.
Do you conduct user research?
Yes, and we scale it to the project. That might be a handful of interviews and observation sessions, testing a prototype with target users, or reviewing analytics and support tickets. Even a small amount of research tends to prevent expensive wrong turns.
How do you make sure designs are accessible?
We design to WCAG guidance from the outset: sufficient colour contrast, legible type, clear focus states, meaningful labels and layouts that work at different sizes. Accessibility issues are much cheaper to prevent in design than to fix in code.
What do we receive at the end?
Organised design files, a documented component library or design system, prototypes and any research findings. If we also build the product, the design system is implemented in code as well. Everything is yours to keep and reuse.
Often paired with.
- Web Application DevelopmentCustomer-facing platforms, dashboards and portals built with React, Next.js and TypeScript.
- Mobile App DevelopmentCross-platform iOS and Android apps built with Flutter, with the backend services and release process to support them.
- SaaS DevelopmentMulti-tenant SaaS platforms with subscriptions, team accounts and an architecture that grows with your customer base.
Have a product worth building?
Tell us what you are trying to achieve. The first conversation is about understanding the problem — not selling you a solution.