About

We start by narrowing the scope. Most projects arrive as a broad idea, and the first real piece of work is agreeing on what gets built. That conversation usually takes a few days and saves a few weeks.

We work in two-week cycles. At the end of each one there is a build you can click through and try for yourself. If something has slipped, that is when you find out, while there is still room to change course.

Infrastructure and the release process are part of the product, and we build them at the same time as everything else. This is slower in the first month and considerably faster after that. By the time you launch, deploying is something someone does on a Tuesday without thinking about it.

When the work ends you get the source, the deployment pipeline, and written notes on anything only we touched. We stay reachable afterwards, though most teams stop needing us within a month.