Home / Contact
Contact · usually a contract conversation
Tell me the role. I will tell you straight away whether I am a match.
Including when I am not, which saves you a submission and me a call. Most of what reaches me is a six to twelve month contract for a senior UX designer or a product owner, remote. If that is what you have, the fastest route is the spec itself.
The fastest thing you can send is the job specification itself, with the start date and whether it is part time or full time. I read it and answer with a yes or a no.
A no is not a brush-off, it is the useful answer: it saves you a submission and saves me a call. If you want the facts before you write, they are all on the Services page.
Before you write anything
Four questions, answered in ten seconds.
This is the same screen I would do in my head on the first call, so you may as well have it now. Nothing is sent and nothing is stored: it only changes what the panel on the right says.
Straight through
No form in the way, if you would rather not.
The spec as an attachment is perfect. I read everything and I answer everything, including the ones where the answer is no.
Free, and genuinely thirty minutes. Bring the role and the constraint. You will get a straight answer on fit and availability before it ends.
Fine for a first contact, though the detail usually ends up in email anyway. I do not keep other social accounts for work.
The formal version, for when your system needs a document rather than a link. The case studies on this site have considerably more in them.
Or write here
Everything below is optional except a way to reply.
What gets a faster answer
Three things that save us both a round trip.
"Senior UX designer" tells me nothing about whether I am useful. "Our underwriters cannot compare risk data and they keep exporting to spreadsheets" tells me everything, and I can answer it in one reply.
These decide fit more often than the skills do. Six to twelve months, part time or full time, fully remote. If any of the three is different, say so early rather than discovering it on the second call.
If there is an in-house designer, a previous agency, or a version that shipped and underperformed, that is context not embarrassment. It is usually where the real constraint is hiding.
Not a role. Just need something built?
A small business that needs its calls answered and its jobs booked, a website for a trade, a one-off page. That is a different conversation and my hourly rate is a bad answer to it. ParrotB is the product I built for exactly that.