Updated 2026-08-15 · 6 min
What actually happens in the first two weeks
Week one is listening, not designing screens
We ask where time, revenue, or visibility is lost. We want the person who lives the problem, not only the person who signed the enquiry. We collect access to the tools you already use, with your permission.
You will be asked to decide
Who the first users are. What version one must finish. What can wait. Who inside your company owns the project on your side. Software without an internal owner becomes our problem and then your disappointment.
You leave week two with paper, not vibes
A written scope, a sequence, a cost, and the trade-offs. If we cannot see a finish line, we will not pretend we can. That document is what you approve before build hours start in earnest.
Related: How we work
Questions
Do we need a long brief before the first call?
No. Bring the problem. We will tell you if we need documents after the call.
When do we pay?
Commercial terms sit in the proposal. Discovery is scoped so you are not funding an open-ended chat.