How I work
Most projects start with a conversation. I ask questions – about the user, the business, what success actually looks like. Not to fill out a brief, but because the right product usually lives somewhere between what you ask for and what your users actually need.
Before we go deep, I build something you can touch. A demo, a proof of concept – something real enough to react to. It's faster than describing ideas and more honest than a slide deck. The best decisions in a product usually happen around something tangible.
From there the work moves quickly. You'll hear from me often – not with status updates for the sake of it, but because something worth discussing came up. Clients consistently tell me the speed and ease of communication surprised them. That's partly because there's no one in between us.
I work on a fixed project price. That means when I notice something that should be better – a flow that doesn't feel right, an opportunity the brief didn't mention – I go after it. There's no clock running. The goal is a product you're proud of, not a brief that's been closed.
Bug fixes at release are included. You ordered a working product. That's what you get.
I work with a small number of clients at a time. Not to seem exclusive – but because this is the only way to do the work properly.


