Product & UX Design
Test the Product Before You Build It
The main journey from your brief turned into a clickable prototype and put in front of target users before any code is written, then MVP screens, onboarding and accessibility done properly, so build time goes on what people need.
What you get at each stage
Sized to where your product is now, and built so the next stage adds to it rather than starting again.
Idea & validation
Find out if people get it before you write code
- Problem interviews and the main user journey mapped
- Low-fidelity wireframes of the core flow
- A clickable prototype tested with target users
- A short findings report with what to change in your brief
MVP & launch
Design an MVP people can use without help
- Screens for the Must-have journeys, for web or mobile
- Onboarding and a first-run experience aimed at activation
- Accessibility built in from the first screen
- Design files and specs handed straight to the developers
Growth & scale
Improve the product with evidence, not opinions
- Usability testing of new features before release
- Analytics reviews of where users drop off
- A design system shared by design and engineering
- Accessibility audits and fixes against WCAG
What is included
User journeys
The main journeys from your brief, mapped from first visit to the moment a user gets value.
Wireframes and prototypes
Clickable prototypes built in a design tool, so you can test ideas before paying for development.
Usability testing
Sessions with people who match your target users, watching where they hesitate and what they misread.
Onboarding and activation
Sign-up, first-run and empty screens designed to get new users to their first useful result.
Accessibility
Colour contrast, keyboard use, screen reader labels and clear forms, checked against WCAG from the start.
Design handover
Annotated designs, components and states handed over so the developers build what was tested.
Everything in Product & UX Design
12 services. Take one or combine several: we size each to your stage and agree the scope and a fixed price before work starts.
User experience
- User research and personasTalking to real users and turning what you learn into personas that guide decisions.
- User journey mappingThe main journey from your brief mapped step by step, with the moments to improve marked.
- Information architectureContent and features organised so people find what they need first time.
- Wireframes and prototypesClickable concepts to test and refine before anything is built.
- Usability testingWatching real users try the design, then fixing what trips them up.
- AccessibilityDesigns that work for disabled users and meet the WCAG accessibility guidelines.
- Mobile-first designDesigned for phones first, then scaled up to larger screens.
User interface
- Interface designClear, attractive screens for your web or mobile product.
- Onboarding and first runSign-up, first-run and empty screens designed to get new users to their first useful result.
- Design systemReusable components and rules that keep the product consistent as it grows.
- Interactive prototypesHigh-fidelity prototypes for user tests, demos and investor meetings.
- Developer handoverSpecifications and assets prepared so engineering builds what was tested.
Scope it free, then build it
Your MVP brief is the brief
The brief you write in the free MVP builder is what we quote from. It tells us who the product is for, the Must-have features, the main journeys and the budget, so work on Product & UX Design starts from your brief, not a blank page. It fits these stages:
In your brief
The sections it builds on
- Problem and users
- User journeys and screens
- Validation plan
For established companies
New products and ventures, scoped first
Established companies use the same process to test a new digital product, an internal tool or a new customer journey with real users before committing a development budget, and to bring an existing product up to current accessibility standards.
Tell us about your projectQuestions founders ask
Why prototype before building?
A clickable prototype is much cheaper to change than working code. Putting it in front of a small group of target users shows where they get stuck or misunderstand the idea, so you fix it in the design rather than after launch.
Do we need a design system for an MVP?
Not a full one. A small set of reusable components, colours and type styles keeps the MVP consistent and quicker to build. A fuller design system is worth it once several people are designing and building at the same time.
Do accessibility rules apply to startups?
Often, yes. In the UK, the Equality Act requires service providers to make reasonable adjustments for disabled people, and that can include websites and apps. If you sell into the EU, the European Accessibility Act also covers many digital services, with an exemption for some very small businesses. We design to WCAG AA as a practical standard; for a legal view on your situation, take advice.
Is design part of the fixed-price MVP build?
Yes. When we build your MVP, design is part of the fixed price for the Must-have scope. You can also book design on its own, for example to test a prototype before you decide whether to build.
Who does the design work?
Our own team, working from your MVP brief alongside the developers who will build it: one brief, one point of contact and no hand-offs between agencies.