Design that ships,
and a system behind it.
I take on a small number of client engagements alongside product work. Eight ways to work together. Pick one and it shows exactly what an engagement covers.
A brand that holds together after launch day.
Most identities look right in the reveal deck and fall apart on the third surface. This engagement builds the system underneath: the rules, the foundations, and the documentation that keeps surface twenty looking like surface one. Recent work: the Sunlit Porch identity behind SeniorConnect USA.
What an engagement covers- Discovery and positioning · who it is for and what it should say
- Logo and mark · primary, secondary, clear-space rules
- Colour and type foundations · palettes and pairings with usage rules
- Voice and tone · how the brand writes, with examples
- Brand guidelines document · one source of truth, made for handoff
- Rollout across surfaces · site, social, print and product
From research to screens a developer can build.
End-to-end product design for web and mobile: understanding the problem, structuring the product, and taking it to high-fidelity screens. Includes two years as sole product designer on a clinical EMR used by physicians at the point of care.
What an engagement covers- Research and interviews · grounded in real behaviour, not taste
- Information architecture · what lives where, and why
- User flows and wireframes · the paths before the pixels
- High-fidelity UI · screens with real content and states
- Clickable prototypes · for testing and stakeholder review
- Dev-ready handoff · specs, states and edge cases included
The third feature ships cheaper than the first.
Design foundations, components, states and the decision log behind them, built to be handed straight to developers. The measure of success is that new pages ship from documented patterns instead of one-off design.
What an engagement covers- Design foundations and variables · colour, type, spacing, shape
- Component library · built in Figma, mirrored in code
- States and interaction specs · hover, focus, error, empty, loading
- Documentation · usage rules a new hire can follow
- Decision log · why things are the way they are
- Adoption support · helping the team actually use it
Designed and built by the same pair of hands.
Design and build together, not handed off over a wall: semantic HTML, CSS and JavaScript, fast and responsive. This site is the working sample, designed and built end to end.
What an engagement covers- Page and layout design · from wireframe to finished screens
- Semantic HTML, CSS and JavaScript · clean, readable, maintainable
- Responsive behaviour · designed for phones, not shrunk to them
- Performance pass · fonts, images and scripts kept honest
- Accessibility checks · contrast, focus and keyboard paths
- Deploy setup · hosting, domains and redirects sorted
Native patterns, not a web page in a wrapper.
iOS and Android product design that respects each platform's conventions, from navigation to system states, informed by two shipped mobile products including a clinical EMR for iPhone, iPad and Apple Watch.
What an engagement covers- iOS and Android patterns · each platform on its own terms
- Navigation and system states · permissions, offline, interruptions
- Component kit · reusable screens and elements
- Motion and interaction specs · transitions a developer can read
- Empty, error and loading states · the screens most apps forget
- Store screens · listings that show the product honestly
Accessible from the first screen, not the last audit.
Contrast, focus, reading order and plain language treated as design inputs rather than a compliance pass at the end. Proven on a platform built for readers aged over 50, where accessibility is the product.
What an engagement covers- WCAG review · against 2.2 AA, with findings explained
- Contrast and colour system · palettes that pass without looking flat
- Focus and keyboard paths · usable without a mouse
- Reading order and structure · headings and landmarks that make sense
- Plain-language pass · copy people actually understand
- Accessible components · patterns that stay accessible when reused
Where users leak out, and what to fix first.
A structured review of an existing product or site: what works, where users drop off, and a prioritised list of fixes grounded in evidence rather than taste. Useful before a redesign, or instead of one.
What an engagement covers- Heuristic review · screen by screen, flow by flow
- Conversion leak map · where and why people give up
- Accessibility scan · the issues that exclude people
- Speed and performance read · what is slowing the pages down
- Prioritised fix list · ordered by impact against effort
- Walkthrough call · the findings, explained live
A senior eye on call, not on payroll.
Advisory work for teams shipping their own design and front-end: reviews, direction and unblocking, on call rather than embedded. The cheapest week is the one where the wrong direction gets caught early.
What an engagement covers- Design reviews · honest, specific, actionable
- Direction setting · before the expensive work starts
- Pairing sessions · working the problem together
- Unblocking decisions · a second opinion when teams are stuck
- Hiring support · portfolio review and interview help
- Retainer option · a set number of hours, monthly
How an engagement runs
Scope first, in writing: the problem, the reader it serves, and what "done" means. Work happens in visible steps, so you review rendered screens and working pages, not status reports. Handoff includes the system, not just the screens.
Looking for the case studies instead? The work lives here.