Freelance product designer in the UK. I help companies launch new products and improve existing ones.

You know what you want to make, but not what the first version should be. I help you work out who it’s for and what can wait. You leave with a one-page brief and the main journey mapped out from start to finish.

Slides can’t tell you whether a product works. Using it can. I build working prototypes early, usually a few different takes on the idea, so you can click through it before paying for the full build. By the end we’ve picked one.

Then every screen needs designing, including the ones nobody remembers: the page before anything has loaded, the list with nothing in it yet, the message when something breaks. I design them all from one set of parts, so the product looks like one thing. The design files are yours to keep.

If you have developers, I work with them to build it. If you don’t, I build the parts people see and use myself, and set it up so whoever you hire next can pick it up. After launch I can stay on for what comes next.

If fewer people sign up or come back than you’d expect, something is usually in the way. I go through the product as a customer would, from the first page to paying, and find it. You get the problems screen by screen, with the fixes in the order I’d make them.

A lot of products are laid out the way the company thinks, not the way customers do. I redesign the main journeys around what people came to do, and try them as working prototypes first. The new designs fit the product you already have, so nothing starts from scratch.

When lots of people have worked on a product, it stops looking like one thing. Buttons stop matching, and there are four greys where there should be one. I find what’s drifted, pull it back to one set of rules, then put the fixes into the code.

A redesign doesn’t help anyone until it’s live. I work alongside your engineers to get it there, and send the changes as pull requests they can check first. If there’s no one to hand them to, I build them myself.

Without a designer, every screen is a developer’s best guess, and nobody is looking at the product as a whole. While I’m on the team, that’s my job. I review every screen and keep a running list of what needs fixing.

I stay on hand until what was designed is what gets built. Sometimes that’s feedback to your developers as they go. Sometimes it’s me making the changes myself, in your codebase.

Some changes are quicker to make than to explain. For those I skip the mockup and open a pull request. For everything else, I review what the team builds before it goes out and catch the small things that slip.

Some teams need a designer for one feature. Others need one for a year while they grow. I do both: a fixed piece of work, or joining the team for as long as you need. Either way, you know the price before we start.