From mail to launch.

If the mail looks like a fit, we book a short call. The goal isn't to sell — it's to find out what you actually want, not just what you wrote down. Most briefs change after this call, and that's a good sign. After it, I send a quote: scope, timing, fixed price. No hourly billing, no surprises.

Questions I always ask: who is the audience, what problem are we really solving, what does success look like in three months, what have you tried that didn't work?

Once the quote is signed, I build a prototype — a real, clickable, mostly-working first version. Not slides, not flat mockups: something you can use. If it's a website, you get a link. If it's a brand, you see the system applied to real touchpoints. We review it together. Adjust. Approve.

Designs in isolation lie. A prototype tells the truth — you click it, you feel it, you know whether it's right. Faster to build, cheaper to change, easier to ship.

Approved? I finish it. Full design system, production-ready code, brandbook or guideline doc, all assets organised the way your team will actually use them. A short handover so you know how to run it yourself. I stay available for questions afterwards — no clock running.

Launch isn't "files in a zip". It's making sure you can run what I built without me — clean code, clear docs, real handover. That's the difference between delivery and ownership.