A product that works but nobody can figure out how to use is not ready to sell.

User research that grounds design decisions in evidence rather than assumption. User interviews with your actual customers to understand their jobs-to-be-done, current workarounds, and frustration points. Usability testing on existing products to identify where users struggle with video recordings and timestamped findings. Survey design for quantitative validation of qualitative research findings. Competitor UX analysis to understand the interface expectations your users bring from adjacent products. The research that answers whether you are building the right thing before you invest in building it well.

The structural design of your product before any visual design is applied. Navigation structure and menu hierarchy. Page layouts and content organisation. User flow mapping from entry point through task completion. Low-fidelity wireframes in Figma that communicate structure and flow without the distraction of visual design. Wireframe prototypes that users can click through for early usability testing. The design decisions made at the wireframe stage are the most consequential and the cheapest to change. We invest here before moving to high-fidelity work.

Card sorting sessions (open card sort to understand how users group information, closed card sort to validate a proposed structure) inform navigation hierarchy before a single wireframe is drawn. Tree testing with Optimal Workshop validates whether users can locate specific items in the proposed navigation structure without any visual design context, catching information architecture problems before high-fidelity work begins. Annotated wireframes document interaction specifications for the engineering team: what each element does, what triggers a state change, what the edge case layout looks like when the user has zero items or 1,000.

Pixel-accurate UI design in Figma for web and mobile applications. Component design with all states (default, hover, active, disabled, error, loading). Responsive design across desktop, tablet, and mobile breakpoints. Consistent application of a visual system: colour, typography, spacing, iconography. Dark mode design where required. Illustration and custom icon sets for products that need a distinctive visual identity. Accessibility-first design: colour contrast compliance, focus indicator design, and touch target sizing for mobile. The high-fidelity designs that give your development team a clear, unambiguous target.

A component library and visual token system that makes your product consistent at scale. Figma component library with all interface components defined and variants documented. Design token definitions: colour scales with semantic names (--color-surface-primary, --color-text-dim, --color-border-subtle rather than raw hex values), typography scale with modular scale ratios (Major Third: 1.25 or Perfect Fourth: 1.333), spacing scale on a 4px base grid with named sizes, border radii, shadow levels, and z-index layers. Each token is named for its role, not its value, so a brand colour rebrand propagates to every component that uses the semantic token rather than requiring a search-and-replace across the codebase.

Component usage guidelines for designers and developers: what each component is for, when to use it, when not to use it, and the variants available. React or Vue component library aligned to the Figma system so design and code share the same component language, developers reference the same component names from the design file. Storybook documentation for developer reference: every component rendered in isolation with its variants, a code snippet showing the API, and visual regression tests that run on every PR to catch unintended visual changes. Style Dictionary build step exports tokens as CSS custom properties, Tailwind config, and JavaScript constants simultaneously, eliminating the "Figma says 16px but the code has 14px" class of discrepancy. The foundation that lets your team build new features at pace without the interface becoming inconsistent as it grows.

Facilitated 5-day design sprint workshops for teams that need to validate a product direction or solve a specific design problem quickly. Problem definition and success criteria on Day 1. Solution sketching and competitive analysis on Day 2. Decision and storyboarding on Day 3. Prototype development in Figma on Day 4. User testing with 5 real users on Day 5. Written findings report with what worked, what did not, and recommended next steps. For organisations that want to test a direction before committing to a full build or that need to quickly break a team disagreement about product direction with evidence.

Structured review of an existing product against UX heuristics, user task completion paths, and conversion friction points. Expert review by an experienced UX practitioner working through your product's core user journeys and documenting usability issues with severity ratings and specific improvement recommendations. Screen recordings of real users attempting key tasks in moderated testing sessions. Prioritised findings report: the 10 changes that would have the most impact on task completion and conversion, ordered by effort and impact. For products that work but are underperforming on activation, retention, or user satisfaction metrics.