Engagements
Six ways to put me to work.
Art direction
One visual language across product, site and deck.
Interface design
Screens with the awkward states drawn too.
Design systems
Tokens, components and the rules that stop the drift.
Identity
Marks, type and colour scoped for a team with no designer.
Site build
Block-editor markup your marketing lead can run alone.
Second opinion
One week of full attention on a single flow.
How I work
Nothing exotic in the box.
Tools your team already has, files your team can open, and a handover that does not depend on me answering messages six months from now.
The shape of it
Four stages, and you see something every Thursday.
The order is load-bearing. Each stage hands the next one something it cannot start without, which is how we avoid designing a screen for a decision nobody has made.
Listen
Two calls with you, four with your customers, plus every support ticket you are willing to share. I come back with the problem in one paragraph and you tell me where I got it wrong.
Week 1Frame
Structure, flows and the hard trade-offs on paper before anything gets styled. You sign off a skeleton, which costs far less to change than a finished screen.
Week 2Draw
Full-fidelity work with real copy and the ugly states included — loading, empty, error, name-far-too-long. Reviewed live, cameras on, every Thursday.
Weeks 3–5Leave well
Component library, tokens, a written spec and a walkthrough with your engineers. A month of questions answered at no charge afterwards.
Week 6FAQ
Asked before nearly every project.
Not sure yet?
Send a paragraph about what is going wrong. If I am not right for it I will say so and name someone who is, usually the same day.
Write to meA full product engagement runs six weeks end to end. An identity is three to four. A second opinion is one week. If your deadline is tighter than that, tell me early and I will say honestly whether it fits.
Yes, wherever the scope is defined. One number, one payment schedule and a written list of what sits inside it. Anything outside becomes a conversation before work starts, never a surprise line on an invoice.
That is the normal arrangement. I join your stand-ups, write specs in whatever format your team already uses, and stay reachable for a month after handover so questions get answered rather than guessed at.
Source files, a component library with every state documented, a token sheet, exported assets and a written spec covering behaviour and edge cases. Build engagements also include block patterns and a configured theme.json.
Sometimes. A single landing page, a pricing rewrite or a one-week review all fit comfortably. Anything larger tends to work better as a short sprint than as hours scattered across a quarter.
You do, completely, once the final payment clears. Files transfer into your accounts rather than living in mine. I only ask permission to show the work publicly, and I will keep it private if you would rather.
Two slots open from September
Have you got something that deserves doing properly?
Tell me what is broken, who it is breaking for, and what happens if it stays that way. That is enough for me to come back with a scope and a number.