— get a project quote or start an engagement
Have a role, a project, or a hard problem? Wherever you're based, I read every message and reply within a couple of days.
What happens next
I read every message myself and reply within a couple of days. A useful first message says what you are building, roughly when you need it, and any constraint that is already fixed — an existing codebase, a platform, a deadline. From there the next step is a conversation, then a written scope. No scope, no quote.
What to include in a brief
- What the product does, in a sentence — the problem before the solution
- Whether this is a new build, an addition to something live, or a takeover
- Any technology already chosen, and whether that choice is fixed
- The date that matters, and what happens if it moves
- Roughly what the budget is — it changes the shape of the answer, not the welcome
Response time and working across time zones
Messages get a reply within a couple of days, wherever they are sent from. The way I work does not depend on us being online together: scope is written, decisions are recorded, and progress is visible without a status call. When a call is the fastest way to settle something, it gets scheduled around your day rather than mine.
Trusted by teams at
