UI/UX and product design
Interfaces people can use without being trained.
Flows, wireframes, interface design and a reusable design system, tested against real screen sizes and accessibility requirements rather than a designer's monitor.
Who this is for
- A product with features people cannot find
- A team redesigning something already in use by real customers
- A new build that needs its flows settled before code starts
What you get
Everything below is stated explicitly in your scope, with anything excluded named just as clearly. Nothing here is implied and then invoiced.
- User flows and information architecture
- Wireframes, then interface design for every state
- A design system: type scale, spacing, colour, components
- Accessibility and contrast checked, not assumed
- Developer-ready handoff with specs and assets
Quoted per scope. See how we quote.
How it runs
Discovery and goals
We start with what the business needs to happen, not with a feature list. What is the outcome, who is it for, and how will we know it worked?
Scope, proposal and milestones
A written scope with what is included, what is not, the milestone plan and the price. Nothing starts until you have that in hand.
Design and technical architecture
Interface design and the architecture underneath it — data model, roles, integrations — reviewed with you before code.
Development, QA and review
Built in milestones you can see. Every milestone is tested and reviewed with you before the next one starts.
Launch, measurement and support
Deployment, analytics, handover documentation and a support arrangement — so the project does not end the day it goes live.
Where we have done this
Ooruva
A hyperlocal discovery platform for real neighbourhood businesses — a customer app, a vendor app and an admin console that share one verified business directory.
See the project →InkNexis
Multi-tenant SaaS covering the whole tattoo studio lifecycle: customer history, design and placement preview, quote, booking, consent, session, aftercare, artist commission and analytics.
See the project →About ui/ux and product design
Can you design without building it?
Yes. We hand over a specification another team can build from. We would rather do that well than hold a project hostage.
What if we already have a design?
We review it against how it will actually be built and used, tell you what will not survive contact with real screens, and fix those parts. We do not redesign work that is already good.
Do you test with real users?
Where the budget allows, yes, and it is worth arguing for. Five real users will find problems an internal review never will.
Tell us what you need
Describe the problem and we will come back with questions, an approach and a written scope. The scope costs you nothing.