Discovery
Typically one to three weeks
Conversations, existing systems review, task mapping and a first prototype. Ends with a written plan, an estimate range and the assumptions behind it.
Method
Our method is simple enough to fit on a page and specific enough to hold us to it.
Typically one to three weeks
Conversations, existing systems review, task mapping and a first prototype. Ends with a written plan, an estimate range and the assumptions behind it.
Usually the first fortnight of build
Repository, pipelines, environments, design tokens and the data model. Unexciting, essential and visible to you.
Repeated fortnights
Planning, building, preview, feedback, release. Each phrase has a short written summary.
Planned from week one
Store submissions, final checks, staged rollout and a watch period during working hours.
Ongoing
Updates, fixes and improvements under an agreed support arrangement.
Estimates are ranges, not single numbers, and each range comes with the assumptions that would move it. We break work into pieces small enough to reason about, estimate those, add explicit allowances for integration and testing, and show you the arithmetic. When we are uncertain, we say what a short spike would cost to reduce that uncertainty.