FAQ
Questions, answered plainly.
Not sure yet?
Send a paragraph about what is going wrong. If I am not right for it I will say so and name someone who is, usually the same day.
Write to meA full product engagement runs six weeks end to end. An identity is three to four. A second opinion is one week. If your deadline is tighter than that, tell me early and I will say honestly whether it fits.
Yes, wherever the scope is defined. One number, one payment schedule and a written list of what sits inside it. Anything outside becomes a conversation before work starts, never a surprise line on an invoice.
That is the normal arrangement. I join your stand-ups, write specs in whatever format your team already uses, and stay reachable for a month after handover so questions get answered rather than guessed at.
Source files, a component library with every state documented, a token sheet, exported assets and a written spec covering behaviour and edge cases. Build engagements also include block patterns and a configured theme.json.
Sometimes. A single landing page, a pricing rewrite or a one-week review all fit comfortably. Anything larger tends to work better as a short sprint than as hours scattered across a quarter.
You do, completely, once the final payment clears. Files transfer into your accounts rather than living in mine. I only ask permission to show the work publicly, and I will keep it private if you would rather.
Start a project
Tell me what is broken, and who it breaks for.
That is enough for me to come back with a scope and a number. I answer every message within one working day.
Two slots open from September
Have you got something that deserves doing properly?
Tell me what is broken, who it is breaking for, and what happens if it stays that way. That is enough for me to come back with a scope and a number.