Premium design
Interfaces that look and feel best-in-class.
Service 06 of 15
UI / UX design
Research, interface design and design systems for every screen.
- Typical timeline
- 3–8 weeks
- Pricing
- Fixed quote
- Team
- Product designer + researcher
Our 3 promises
Your users. Our goal.
Three promises we make on every design project.
Easy to use
Every key flow tested with real users before it is built.
Built to grow
A design system that keeps every new screen consistent.
Tech stack
The stack behind your ui / ux design
Proven, well-supported tools at every layer. Picked for your product, never for our habits.
- ResearchLookback
- DesignMost requestedFigma
- ResearchHotjar
- DesignMost requestedFigJam
- SystemsStorybook
- MotionRive
- ResearchMost requestedMaze
- MotionFramer
- SystemsMost requestedDesign tokens
- StandardsApple HIG
- StandardsMaterial
- MotionMost requestedLottie
- StandardsMost requestedWCAG 2.2
What’s included
What you get
Everything in scope, from first workshop to launch.
01StartResearch
Interviews and testing with real users.
Read more +Show less −
Research is where we talk to and test with your real users, so design decisions rest on evidence rather than guesswork. You get a short findings report showing the problems users hit most and what to fix first. It usually takes 1–2 weeks at the start of the project.
What you get
- Recorded one-to-one interviews with your users or customers
- Usability tests of your current product or close competitors
- Findings report ranking problems by their impact on users
- User personas and the key tasks each one needs to do
- Heatmap and session review in Hotjar where data exists
How it works
- Agree research goals and who we should speak to
- Recruit participants with your help and book sessions
- Run interviews and usability tests using Maze and Lookback
- Share findings in a review call and agree priorities
Good to know: Introductions to a few of your real customers make research faster and far more useful than recruiting strangers.
02DesignUX flows
Journeys and wireframes for every key task.
Read more +Show less −
UX flows map how users move through each key task, step by step, before any visual design starts. You get user flows and wireframes for every main journey, so structure and content are agreed while changes are still cheap. This stage usually runs in weeks 2–3.
What you get
- User flow diagrams for every key task in FigJam
- Information architecture and navigation structure
- Low-fidelity wireframes of each main screen in Figma
- Notes on edge cases, empty states and error messages
- Clickable wireframe prototype for early feedback
How it works
- List the key tasks users must complete, based on research
- Map each journey as a flow, including errors and edge cases
- Sketch wireframes and link them into a simple prototype
- Review with you and agree the structure before visual design
Good to know: Changing a wireframe takes minutes but changing a built screen can take days, so this is the moment to challenge the structure.
03DesignUI design
Clean, consistent screens for web and mobile.
Read more +Show less −
UI design turns approved wireframes into finished, high-fidelity screens for web and mobile, in your brand colours and type. You get a clickable Figma prototype you can test and share, reviewed with you every week. Screens are designed to WCAG 2.2 AA accessibility standards.
What you get
- High-fidelity Figma designs for every agreed screen
- Desktop, tablet and mobile layouts for each page
- Clickable prototype for stakeholder reviews and user testing
- Accessibility checks for contrast, focus states and type size
- Motion specs for key interactions using Lottie or Rive
- Design files owned by you from day one
How it works
- Agree a visual direction on two or three sample screens
- Design the remaining screens in batches, reviewed with you weekly
- Test the prototype with real users and refine
- Sign off final screens ready for the design system
Good to know: Bring brand guidelines, logos and any existing assets to the first review, as it saves a round of changes.
04DesignDesign system
Reusable components your developers can build from.
Read more +Show less −
A design system is a library of reusable components, tokens and guidance that keeps every screen consistent and makes building faster. You get a documented Figma library your developers can build from, with design tokens for colour, type and spacing. It grows with your product, so new features reuse parts instead of starting from zero.
What you get
- Figma component library with every variant and state
- Design tokens for colour, type, spacing and radius
- Usage guidelines for each component, with do and don't examples
- Accessibility notes for every interactive component
- Optional Storybook setup matching design components to code
How it works
- Audit screens to find repeated patterns and inconsistencies
- Define tokens, then build core components with all states
- Document usage rules and review them with your developers
- Publish the library and update it as screens are added
Good to know: Even a small product benefits from a system, and starting with core parts such as buttons, forms and cards is usually enough.
05LaunchDev handover
Specs and support while the product is built.
Read more +Show less −
Dev handover gives your developers everything they need to build the designs accurately, with a designer on hand while they do. You get annotated specs, exported assets and design QA reviews of the built product against the approved screens. Support runs for the length of the build, whether we build it or your own team does.
What you get
- Annotated Figma files with spacing, states and behaviour notes
- Exported icons, images and design tokens ready for code
- Handover walkthrough call with your developers
- Design QA reviews of built screens against the designs
- Prioritised list of visual fixes for each sprint
How it works
- Walk developers through the files and answer questions
- Design any missing states that come up during the build
- Review each built feature against the approved designs
- Log fixes and sign off screens once they match
Good to know: Ask for design QA in every sprint, not only at the end, because small visual drift is easier to fix early.
How it works
From idea to launch
Every service runs through the same five steps. Here is what each one means for UI / UX design.
01of 05
UnderstandWeeks 1–2Once
Research with your users to learn what they need and where they struggle.
You getResearch findings
What we do
- Stakeholder workshop
- User interviews and analytics review
- Audit of your current product
You get
- Research findings
- User personas
- UX audit
From you
- 2–3 hours for workshops
- Access to 5–8 users
Tools
- Maze
- Notion
02of 05
PlanWeek 2–3Once
User flows, information architecture and a fixed quote.
You getFixed quote & timeline
What we do
- User flows and sitemap
- Low-fidelity wireframes
- Design plan and milestones
You get
- Fixed, itemised quote
- Flows and wireframes
- Timeline with milestones
From you
- Review and approve the plan
Tools
- FigJam
- Figma
03of 05
DesignWeekly reviews↻ Repeats
High-fidelity screens and prototypes, reviewed with you every week.
You getClickable prototype
What we do
- Visual design for key screens
- Clickable prototype
- Design system of components
You get
- Clickable prototype
- Design system
- Weekly design review
From you
- Weekly 30-minute review
- Feedback within 3 working days
Tools
- Figma
04of 05
Test & handoverEach round↻ Repeats
Testing with real users, then developer-ready files.
You getTested designs
What we do
- Usability tests with real users
- Accessibility checks
- Developer handover and specs
You get
- Usability test report
- Final Figma files
- Developer handover pack
From you
- Final sign-off
Tools
- Maze
- Figma Dev Mode
05of 05
Support & growAfter handover↻ Repeats
Design support during build and new screens as you grow.
You getOngoing improvements
What we do
- Support your developers during build
- New screens and features
- Review of live usage data
You get
- Updated designs
- Design QA notes
From you
- Monthly 30-minute review
Tools
- Figma
- Hotjar
FAQ
UI / UX design questions
What is the difference between UI and UX?
UX design is how the product works: user journeys, structure and ease of use. UI design is how it looks: layout, type, colour and components.
What does your design process include?
Discovery and user research, user flows, wireframes, clickable Figma prototypes, user testing, then a final UI and design system ready for development.
Can you design only, or must you build too?
Both work. Many clients use us end to end, but we also deliver design-only projects with developer-ready Figma files.
Do you design for accessibility?
Yes. We design to WCAG 2.2 AA: colour contrast, keyboard use, readable type and clear focus states, checked before handover.
How long does UX/UI design take?
A UX audit takes 1–2 weeks. Designing a new product typically takes 3–8 weeks, depending on the number of screens and the user testing involved.
Who owns the code?
You do. All IP is assigned to you in the contract, and the code, accounts and documentation are yours from the first sprint.
Let’s talk
Let’s talk
A 30-minute call with an engineer and a clear next step for your project.