Bring the product problem into focus before the build starts.
Send a brief if the scope is clear, or book a call if the problem is still taking shape. Either way the first step is the same: what you are building, who uses it, what is blocked, what already runs, the constraints that cannot move, and what would count as done.
What happens next.
The path from first contact to a scoped engagement, so the first steps are clear before anyone commits.
- 01
You reach out
Send a brief with the scope and constraints, or book a call if the problem is still taking shape. Both reach the person accountable for scoping the work.
- 02
First reply
We aim to reply within two business days. It is a target, not a service-level guarantee; if timing matters, say so in the message and email directly.
- 03
A scoping conversation
A working call to establish the real constraints: what is already running, where the problem sits, and which risks matter first. No commitment on either side yet.
- 04
A written scope
The conversation becomes a short document: the problem, what will and will not be built, and what counts as done. Nothing is billed until you have agreed to it.
- 05
Staged delivery
Work ships in reviewable increments against that scope. You check each stage as it lands, rather than waiting for one drop at the end.
Send the constraint, not a pitch deck.
A short brief is enough: what exists, what is blocked, and what has to be true when the work is done. The harder the engineering underneath it, the more useful that first message is.