Answer
How long does a Production Build take?
A Production Build takes six weeks from the access gate to release, followed by a 30-day live-use acceptance window. The clock pauses while work is blocked on the client side, with the reason recorded.
What the six weeks cover
A Production Build is scoped in the Spec to the problem you have, for a named group of users, with up to two standard integrations. In six weeks it ships the tool with instrumentation, training, operating documentation and a handover pack. The scope is kept tight on purpose. Adoption is the hard part, and it can only be measured when the workflow, the crew and the before and after are all clear.
Start, pause and finish
The clock starts at the access gate, not at contract signing. The access gate is the point where the four roles on your side are named, access is granted and the usage threshold is signed. Starting there keeps the six weeks honest: time spent waiting for access is not counted as build time.
If the work is blocked on your side after that, for example while waiting on data or a decision, the clock pauses and the reason is written down. It ends at release to the agreed production environment with the agreed user group.
After release
Release is not the finish line. A 30-day live-use acceptance window follows, and the final 20 percent of the fee depends on whether the crew is actually using the tool by the end of it. The full terms are on how we work.
Questions people ask
When does the six-week clock start?
At the access gate: when the four roles on your side are named, access is granted and the usage threshold is signed.
Can the clock pause?
Yes. It pauses while the work is blocked on your side, and the reason is recorded each time.
What happens after the six weeks?
The tool is released to the agreed production environment with the agreed user group, and a 30-day live-use acceptance window begins.