How we scope
We carry the estimation risk, not you: a written scope and a clear quote before work starts. Here is how we make that survivable.
1. Before we quote anything
We will not price work we do not understand, which means the first conversation is us asking questions rather than presenting slides.
What we are trying to establish: what already exists, what is load-bearing, which constraints are real and which are assumptions somebody made in a meeting, and where the thing breaks if it breaks. That last one matters most. Infrastructure quotes go wrong when a failure mode surfaces in week six that should have surfaced in the first hour.
2. The scoping document
You get a written scope before you get a price. It states what we are building, what we are explicitly not building, what we need from you and when, and what "done" means in terms specific enough to argue about.
If the scope is wrong, it is much cheaper to find out here.
3. What the quote actually covers
- - What is in the standard scope
- - What is billed separately
- - How change requests work
- - Payment milestones
4. How we work while building
- - Sprint length
- - Demo cadence
- - How progress is reported
- - What access is needed
- - How handover works
5. What we need from you
- - Decision-maker availability
- - Access
- - Review turnaround