A fixed-price starting point, not an open-ended estimate

What this looks like in practice

In practice: we schedule two to three working sessions with your team in the first week to map the workflow end to end — what breaks today, what the software needs to do, and who uses it. You get a written scope document, a proposed architecture, and a fixed price and timeline for the full build within one to two weeks. There's no obligation to continue, and if you do, the fee is credited toward the project.

What this looks like in practice

In practice: work is broken into milestones agreed in the Discovery Sprint's scope document — typically a core build phase, then feature milestones, then launch prep. Each milestone ends with a working demo you review before approving the next one and releasing that milestone's payment. You always know what's shipping next and what it costs, and scope changes are priced separately as a change order rather than silently added to an invoice.

What this looks like in practice

In practice: at launch you get the full source code, technical documentation and admin access to every account and service the project depends on — nothing is held back pending a support contract. If you want us to keep maintaining it, that's a separate Ongoing Partnership retainer you can start, pause or cancel independently of the build itself.