Question 1

Do you build what you design?

Accepted Answer

If you need me to. When you have developers, I work with them to get the designs built and write some of the code myself where that helps. When you don’t, I build the parts people see and use myself, in your existing code or a new project I set up.

Question 2

What do you actually do?

Accepted Answer

I design the parts of a product your customers use: sign-up, onboarding, booking, pricing, checkout and so on. Every screen, including what happens when something goes wrong. Then I either build it or work with your developers while they do.

Question 3

We don’t have a product yet. Is that too early?

Accepted Answer

No, it’s the best time. Changing your mind is cheap before anything is built and expensive after. I can help shape the first version, design it, and build it too.

Question 4

Our product is live but underperforming. Where do you start?

Accepted Answer

I go through it the way a customer would, from the first page to paying, and write down everything that gets in their way. Then I redesign the parts causing the most trouble and get the changes built.

Question 5

Do you work with our developers or replace them?

Accepted Answer

Work with them. I design, then stay involved while it gets built, and write some of the code myself when that’s quicker. I don’t hand over a file and disappear.

Question 6

How long does it take and what does it cost?

Accepted Answer

Fixing one part of a product usually takes a few weeks. Designing a new product takes a few months. I work on a day rate or a fixed price, and after a first call I’ll tell you which makes more sense for you.

Question 7

Where are you based?

Accepted Answer

Surrey, UK. I work remotely with startups and product teams, in the UK and further afield.

I have developers, but no designer

Owning the interface

Working in your codebase

Shipping pull requests

Staying a sprint or a year