LET'S BUILD SOMETHING IMPOSSIBLE.

//What to send#

A paragraph is plenty. What you're building, who it's for, what's currently in the way, and roughly when it needs to exist. If there's an existing site or prototype, a link to that is worth more than a deck. If there's a budget range, saying it early saves us both a pleasant conversation that goes nowhere.

I'll reply within two working days, and the reply will be honest about fit. Roughly half the enquiries I get are better served by someone else — a design studio, a backend specialist, or an agency that can staff five people. When that's the case I'll say so and point you somewhere, because a badly matched engagement is worse than none.

//What happens next#

If it looks like a fit, we talk for half an hour. I'll ask uncomfortable questions about constraints, existing code and who actually makes decisions. After that you get a written scope with phases, a rough cost and the assumptions it depends on — so when an assumption turns out to be wrong, we can both see which part of the estimate moves.

I work in phases rather than a single fixed quote for anything longer than a few weeks. It's honest about the fact that the second month of a project is always better informed than the first.

//Elsewhere#

Code on GitHub, occasional notes in the journal, and professional history on LinkedIn. I don't post much on either — the journal here is the most current record of what I'm actually thinking about.