Design for technical products — by someone who builds them by Jessy MariauDesign for technical products — by someone who builds them by Jessy Mariau
Design for technical products — by someone who builds themJessy Mariau
Cover image for Design for technical products — by someone who builds them
Who this is for: you're shipping something technical — a dashboard, an AI tool, an internal system, a data-heavy product — and the design either doesn't exist yet or was made by someone who'd never open the codebase.
The problem with the usual arrangement: a designer hands over a beautiful file that doesn't survive contact with real data. Empty states nobody drew. Tables that break at 40 columns. A loading state for the happy path only. Then it gets built badly, and everyone blames the build.
I design and I wire. Same person. So the thing I hand you accounts for the states your data actually produces, and I can build it if you'd rather not brief someone else.
What I bring: brand and identity, interface and dashboard design, motion and 3D where it earns its place, and diagrams rendered from data rather than screenshotted from a whiteboard. My own multi-brand operation runs on systems I designed and built end to end — nine projects, one visual language.
How it works: you show me the product and what it's for. I come back with a direction and an honest read on what's worth designing versus what's fine as it is. Nothing gets built before you've seen the shape and agreed it.
FAQs

Contact for pricing
Duration2 weeks
Tags
Brand Designer
Design Systems Specialist
Motion Designer
UI Designer
Web Designer
Service provided by
Jessy Mariau proLondon, UK
4
Followers
Design for technical products — by someone who builds themJessy Mariau
Contact for pricing
Duration2 weeks
Tags
Brand Designer
Design Systems Specialist
Motion Designer
UI Designer
Web Designer
Cover image for Design for technical products — by someone who builds them
Who this is for: you're shipping something technical — a dashboard, an AI tool, an internal system, a data-heavy product — and the design either doesn't exist yet or was made by someone who'd never open the codebase.
The problem with the usual arrangement: a designer hands over a beautiful file that doesn't survive contact with real data. Empty states nobody drew. Tables that break at 40 columns. A loading state for the happy path only. Then it gets built badly, and everyone blames the build.
I design and I wire. Same person. So the thing I hand you accounts for the states your data actually produces, and I can build it if you'd rather not brief someone else.
What I bring: brand and identity, interface and dashboard design, motion and 3D where it earns its place, and diagrams rendered from data rather than screenshotted from a whiteboard. My own multi-brand operation runs on systems I designed and built end to end — nine projects, one visual language.
How it works: you show me the product and what it's for. I come back with a direction and an honest read on what's worth designing versus what's fine as it is. Nothing gets built before you've seen the shape and agreed it.
FAQs

Contact for pricing