The first week is where most engagements fail
If week one is fuzzy, every week after gets fuzzier. Our entire scoping process exists to make sure week one delivers a written, agreed plan.
The discovery sprint
Two weeks. Engineers, designers, and the client's stakeholders, on calls and in docs together. Outputs: a written spec, a system architecture diagram, a risk log, and a milestone plan with named owners.
What we say no to
We will turn down work where the brief is "just build us X." If we can't see who's using it and why, we don't have enough context to ship something good.
The handover
After discovery, the client knows exactly what they're paying for and we know what we're committing to. No surprises at week eight.