Complex softwaremade readable.
I help founders make trading platforms and data-heavy products easier to use, working through the design with their engineering team.
Selected work,made readable.
Trading terminals, GPU marketplaces and AI research tools. Pick one to open its case study.
How I work
Maya R.
Ops lead · Acme
Devin K.
PM · Northwind
Sara L.
Founder · Loop
Tom B.
Designer · Vela
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 the details, because a filter that opens in the wrong place or a table that’s hard to scan changes how the whole product feels. I prototype those decisions and work with your developers to carry them through.
Blog
Why smart teams still build confusing products.
Every feature was a reasonable decision on its own. After 2 years of them the product is powerful and nobody can explain a screen without a demo.
What makes a dashboard good. Six rules from rebuilding one.
I built thirteen analytics boards for my own site and then could not find the one I needed. Six rules from taking them apart, including the number that was wrong for two weeks.
The platforms became APIs. Why AI agents still need interfaces.
Salesforce Headless 360 made the browser optional, and the wider MCP shift means the vendor no longer supplies the screen. Why that makes interface design more valuable, not less.
Latest work
Taomarketcap
Redesigning a trading platform so users can compare markets and act without losing context. Product traction: 40k monthly visitors (team analytics, Jul 2026) and a paid developer API.
Desearch
Putting AI answers beside their sources, with a playground for developers to try the API.
Drippler
A wardrobe app for building outfits from clothes you own.
Metanova
Making drug-discovery scores easier to inspect, with the result and its supporting data together.
Datura AI
A shared brand for an AI lab and its growing family of products.
Rizzy
Designing how a team configures an outreach agent and reviews its messages before sending.

Celium
Designing a GPU marketplace around comparing hardware, rental cost and running jobs.
Stack and tools
Figma
Design source of truth
System design, prototypes and specs. The canvas everything starts on.














