Four stages, and no ambiguity about which one you are in.
Progress should be something you can read or click, not a percentage in a status meeting. This is the sequence every engagement follows, whatever its size.
-
1
Scope
A call about the problem, the constraints and what has already been tried. Afterwards we send a written summary of what we heard and what fixing it involves. This stage costs nothing and carries no obligation.
-
2
Plan
We turn the summary into a scope you can sign off on: milestones, assumptions, exclusions, and the decisions we need from you. Anything we are not certain about is listed as an assumption rather than buried in an estimate.
-
3
Build
Work runs in cycles, and each cycle ends with a demo on an environment you can reach yourself plus a short written note on what moved and what did not. Nothing is reported as complete until it is deployed somewhere you can see it.
-
4
Handover
Documentation, access, and a walkthrough with whoever owns the system next, whether that is your team or another vendor. We stay available for a defined support window, agreed in the engagement letter rather than improvised.
When scope changes
It usually does. The point of writing the scope down is not to freeze it, it is to make a change visible before it becomes an argument.
Raised in writing
Any change to scope is written down with its effect on cost and dates before work on it starts.
Priced, not absorbed
We do not quietly absorb changes and then use them to explain a slipped date.
Your decision
You choose to add it, defer it, or trade it against something already in scope.
What we commit to
These go in the engagement letter, not just on a website.
- 01
The engineers who scope the work are the engineers who build it.
- 02
No substitution of named team members without your agreement.
- 03
Overlap hours agreed before kickoff and held for the engagement.
- 04
Code and infrastructure definitions live in your repository from day one.
- 05
If we think the work should not be done, we say so before invoicing for it.
Speak to an engineer, not a salesperson.
Book a 45 minute technical assessment in your timezone, or send the details and we reply within one business day.