Discovery
We read the product before we form opinions about it. A login, a walkthrough, the tickets and the analytics.
Products
Software that stops needing a demo
SaaS platforms, dashboards and internal tools, designed so the value is visible without a walkthrough.
Product strategy
What the product should be, ranked against what it can be this year, and research to prove it.
Interface design
Production-quality UI with every state designed, including empty, loading, error, partial and permission denied. The states nobody screenshots.
Systems and handover
A component library with tokens, documentation, usage rules and versioning, handed over in a form your engineers adopt.
The process
Six stages. A date we hold.
Research
Interviews with the daily users and with whoever signed the invoice, plus a pass through your own support calls.
Architecture
The information model, navigation, object relationships, permissions and states. The layer that decides whether it all lasts.
Prototypes
Clickable, testable, and in front of real users before anyone writes production code. Freelogo alone needed thirty-eight of them.
Interface
Production-quality UI across the flows that matter, every state included. Your own engineers review the work with us weekly.
Handover
The component library, tokens, documentation, usage rules and versioning, plus a written rationale for every structural decision we made.
FAQs
Questions we get
That’s the normal experience, because most handovers are a Figma link and a phone number. Ours is a documented library with tokens named against your code, every state specified, and time booked in during your build.
Yes, and it’s usually the best version of this. We define who owns what in week one, in writing, because that’s what slips.
Then buy part of it. Plenty of engagements are a design system on its own, or just architecture and prototypes alone.
Research with real users, an information architecture, prototypes tested before code, production-ready UI for every state, and a documented design system with tokens and governance rules. Front-end development if you want us to build it. One named senior designer throughout.
Twelve weeks for a full engagement: discovery, research, architecture, prototypes, interface and system. A design system on its own is closer to five weeks. You get the date at proposal stage, before you commit to anything at all, and we hold to it.
We’ve designed control panels, server virtualisation, hosting infrastructure and statutory compliance tools. cPanel, Plesk, WHMCS, CloudLinux, HostPapa, Servebolt, SolusVM. If your product needs a glossary before a designer is any use, that’s our normal starting position.
A component library with tokens, documentation, usage rules and a version history, so a new screen is assembled rather than drawn. You need one when your engineers start inventing components.