Async intake

Write it down. Get a written answer.

This is the whole process. Describe the problem the way you would describe it to a colleague, and the reply is a specific written response about your situation rather than an invitation to book a call.

Why write

There is no calendar on this page on purpose. A meeting costs both of us the scarcest thing we have, and it happens before either of us knows whether there is anything to discuss. A written brief takes ten minutes, survives time zones, and can be read properly instead of half-remembered.

What happens next

You submit the brief. It lands with me directly, not in a queue.
I read it and come back in writing, usually with questions and sometimes with a scope and a price.
If it turns out we should talk, that is the point where a call becomes useful, and it will be a short one.
If the honest answer is that you do not need this built, the reply says so.

The brief

Required · Optional

NameRequired

However you would like to be addressed in the reply.

EmailRequired

The address the written reply goes to.

Company / project websiteOptional

A URL tells me more than a company name will.

What is this mainly about?Required

The same six options as the scheduling form, so writing instead of booking loses nothing.

What is the situation, and what are you trying to reach?Required

The more concrete the better: what breaks, how often, who it costs, what you have already tried. Rough notes are fine.

What would you expect to receive?Optional

A running system, a handover, documentation, training: whatever you would call a good outcome.

Budget rangeOptional

A band is enough. It decides whether this is a scoped sprint or an implementation.

TimingOptional

When you would want this running.

Anything I should read first?Optional

Specs, a repo, a deck, a recording: paste anything that saves me asking.

How would you like to be answered?Optional

The default is a written reply.

Written reply — I would rather not have a callWritten reply first, then a short call if it looks worth itI would prefer to talk it through

If you would rather have a conversation than write, the scheduler is here.

Used to answer your brief and nothing else. No newsletter, no list, no third party. Send only what you would be comfortable putting in an email.

Not sure yet? The portfolio has the architecture, the guardrails and the figures for all six systems.

See the full portfolio

Write it down. Get a written answer.Write it down. Get a written answer.

Write it down. Get a written answer.