Complex softwaremade readable.
I design products people can understand at a glance, and prototype them in code so they get built the way they were designed.
Selected work
How I work
Services
Find where users lose track of what matters, and decide what to fix first.
What you get
- An annotated review of the agreed flows
- The fixes I would prioritise
- A walkthrough with your team
Work through an unclear product decision before your team commits to building it.
What you get
- Framed problem statement + success metrics
- Concept sketches and option exploration
- Just-enough screens to test the direction
- Feedback from available users or stakeholders
- A clearer direction ready for further testing
- Decision log so the "why" survives
Give each screen a clear job, with the right information and actions within reach.
What you get
- Screen structure, so each screen has one clear job
- Tables and filters built at real data density
- Navigation between the screens people use most
- Primary actions placed where the decision is made
- Key states designed, such as loading, empty, error and needs attention
- Reusable patterns the rest of the product can build on
- For AI products: review queues, confidence and sources where the workflow needs them
Try the important interactions before your team builds them.
What you get
- A working, clickable prototype in real React code
- The core interactions work, with sample data or agreed integrations
- A deployed preview URL to share and test
- Clear notes on what’s validated vs still stubbed
- A focused prototype built to test the core flow
Give your team patterns to reuse as the product grows.
What you get
- Design tokens — colour, type, spacing, radius, elevation
- Core component set with variants and key states
- Usage specs with clear do / don’t guidance
- Figma library aligned with the existing codebase where possible
- Basic accessibility guidance for key components
- Migration notes for adopting it incrementally
Work through the implementation with your developers so the design details carry through.
What you get
- Annotated handoff specs with measurements + tokens
- Pairing sessions with the engineers building it
- Pixel, state and interaction QA passes on staging
- Bug list with screenshots and expected behaviour
- QA checklist for the releases included in the scope
I’m particular about details, where a filter opens, how a table reads. It all comes back to one question: what does this person need to know right now.
Latest work
- TaomarketcapRedesigning a trading platform so users can compare markets and act without losing context.Case study
- CeliumDesigning a GPU marketplace around comparing hardware, rental cost and running jobs.Case study
- MetanovaMaking drug-discovery scores easier to inspect, with the result and its supporting data together.Case study
- Datura AIA shared brand for an AI lab and its growing family of products.Case study
- RizzyDesigning how a team configures an outreach agent and reviews its messages before sending.Case study
- DesearchPutting AI answers beside their sources, with a playground for developers to try the API.Case study
- DripplerA wardrobe app for building outfits from clothes you own.Case study
Stack and tools
Figma
Design source of truth
System design, prototypes and specs. The canvas everything starts on.
