Design debates that never resolve
Decisions are settled by seniority because there is no user evidence in the room.
Test it before you fund it
Prove the experience before a line of code.
Research, personas, journey maps, wireframes, and clickable prototypes tested with real users, so the build starts from evidence instead of an internal opinion.
Scope agreed upfront
No lock-in
You own the data
Where this helps 01
Three signs this is the right conversation.
Changing a prototype costs an afternoon. Changing a live platform costs a release cycle and the goodwill of everyone who uses it. This is where the expensive mistakes get caught.
Best suited to: Teams about to invest in a new site, portal, booking flow, or product experience.
Assumed users, not observed ones
The team can describe the target customer, but nobody has watched one attempt the journey.
Repeated post-launch rework
Every release is followed by a round of fixes for problems a prototype test would have surfaced.
What is included 02
The work itself, written down.
Scope is agreed in writing before we start, so there are no surprises about what this engagement does and does not cover.
User research
Interviews, surveys, analytics review, and support-ticket analysis to establish what people are really trying to do.
Personas and jobs to be done
Evidence-based audience profiles that describe motivation and context, not demographics for their own sake.
Journey and service maps
Every touchpoint from first search to repeat purchase, with friction and drop-off marked where it occurs.
Wireframes and prototypes
Low-fidelity structure through to clickable, testable prototypes of the flows that carry the most value.
Usability testing
Moderated sessions with representative users, recorded, with findings ranked by severity and effort.
Accessibility review
WCAG 2.2 checks applied at design stage, when they are still cheap to act on.
Our approach 03
Four stages, each with something to show.
You see progress at every stage rather than waiting for a reveal at the end. If something is not working, we find out early enough to change it.
Discover
Gather qualitative and quantitative evidence about the current experience and the people using it.
Define
Turn findings into personas, journeys, and a prioritised list of the problems worth solving.
Prototype
Design the flows, screens, and interaction patterns at the fidelity the question requires.
Validate
Test with users, iterate, and hand over a specification developers can build from without guessing.
Tools we work in
- Figma
- Maze
- Hotjar
- Lookback
- Optimal Workshop
- Axe DevTools
Specialist capabilities 04
6 areas you can engage individually.
Take the full service, or start with the single capability that addresses your most pressing constraint.
01
User Persona Development
Evidence-based audience profiles describing goals, context, decision criteria, and objections, so design and content decisions have a person to answer to.
2–4 weeks Explore 02Customer Journey Mapping
End-to-end mapping of how customers move from first awareness to repeat purchase, with friction, emotion, and drop-off marked where they genuinely occur.
3–5 weeks Explore 03Wireframing & Prototyping
Structure, layout, and interaction worked out in wireframes and clickable prototypes, so the build starts from a specification rather than a conversation.
2–6 weeks Explore 04Usability Testing & Heuristic Analysis
Moderated usability sessions with representative users, plus expert heuristic review, producing a severity-ranked list of problems and the evidence behind each.
2–4 weeks per round Explore 05A/B Testing & Data-Driven UX Optimisation
A disciplined experimentation practice: hypotheses drawn from research, tests powered correctly, results read honestly, and every outcome documented.
Ongoing, 2–4 week cycles Explore 06UI/UX Accessibility Compliance
WCAG 2.2 audit, prioritised remediation, and design-system changes that keep your site accessible as it grows, covering DDA obligations and real usability alike.
3–6 weeks for audit and plan ExploreWhat you end up with 05
Measured against what we agreed.
Success measures are set before the engagement starts and reported honestly, including the parts that did not work.
Typical timeline
3–8 weeks
Engagement model
Research and design sprint
Sits within
Digital Strategy & Transformation
Questions 06
The things clients always ask first.
Straight answers, including the times the honest answer is that this service is not what you need.
Five to eight per audience group surfaces the large majority of usability problems. Beyond that you are paying to confirm what you already know.
Yes, and it is often the higher-return option. Fixing a live journey with known traffic pays back faster than designing a replacement.
Yes. Figma files with a component library, states, responsive behaviour, and annotated interaction notes.
We will say so plainly, with the evidence. A cancelled build is a far cheaper outcome than a launched one nobody uses.
Works well with 07
Rarely bought on its own.
Ready to talk about
UX/UI Research & Prototyping?
Tell us what you are working with today and what you need it to do. We will tell you plainly whether this is the right service for that, and what it would take.
Book a strategy conversation No obligation. A useful first conversation.
No obligation
100% free consultation
Expert guidance
Tailored to your goals
Actionable insights
Real strategies that work