Discovery & user flows
Who uses this, what they are trying to finish, and the shortest honest path to it — mapped before any screen is drawn.
UI/UX design
UI/UX design for products people actually use
Wireframes, prototypes and a reusable design system — designed against real data and real edge cases, so what ships resembles what was approved.
Design that has never met the database tends to fall apart on contact with it: the name that is 60 characters long, the table with 40 columns, the empty state nobody drew, the error nobody worded.
Because I build as well as design, the handover is not a wall. The design accounts for loading, empty, error and permission-denied states, and the component set maps to what gets implemented.
Typical stack
Related services
What's included
What this actually covers
Wireframes & prototypes
Clickable Figma prototypes for the flows that matter, so stakeholders react to something real rather than to a description.
Design systems
Type scale, colour tokens, spacing, and a component library that survives the fourth new feature without fragmenting.
Accessibility
Contrast that passes WCAG AA, keyboard paths that work, focus that is visible, and semantics screen readers can follow.
Dark and light themes
Both designed as first-class, driven by tokens rather than a filter thrown over the top.
Build-ready handover
Specs, states and assets in a form a developer can implement without a week of clarifying questions.
How it runs
From first call to production
-
01
Discovery
A working session to pin down what the system has to do, who touches it and what already exists. You get a written scope, an architecture sketch and a realistic estimate before anything is committed to.
-
02
Design & architecture
Data model, API surface and screens, agreed before the build. Designing against real data and real edge cases is what stops the rebuild three weeks in.
-
03
Build in slices
Working software every week against a staging URL you can open, rather than a big reveal at the end. Feedback lands while it is still cheap to act on.
-
04
Launch
Deployment, DNS and TLS, database migration, backups, monitoring and an handover walkthrough. The system goes live on infrastructure you own.
-
05
Run it
Optional retainer: security patches, feature work, performance passes and a person who already knows the codebase when something breaks.
Proof
Related case studies
We4Task
A customer relationship platform covering lead capture, pipeline stages, task assignment and team performance reporting.
Read the case study
Heavenera
A property rental marketplace pairing a web application with a companion Android app — listings, search, bookings and payments.
Read the case study
Questions
Frequently asked
Can you design without building it?
Yes — design-only engagements are fine, and the handover is built for another team to implement.
Can you redesign our existing product?
Often the highest-return work available. A redesign that keeps the data model and rebuilds the interface is usually faster and safer than a ground-up rewrite.
Do you do brand and logo work?
I do product interface design and will work within your brand. For identity work from scratch you want a brand designer, and I am happy to point you at one.
Next step
Need ui/ux design?
Tell me what you are trying to ship. You get an approach, a timeline and a realistic estimate — usually within a working day.