The methodology
How we work. Take it, use it, copy it.
Every Engine Labs build follows the same six steps in order: brief, scope, build, acceptance, handover, and an optional run mode. Cadence is weekly checkpoints during build, a defect-fix period (7–14 days) after acceptance, and opt-in Support after that. Process is not a moat — showing you how we work is faster than telling you we're good.
How it works
What are the six steps of the Build → Run loop?
One loop, six steps, same for every build.
- 01
Brief
Use the Control Centre. Two to four minutes. You get a recommendation and a draft Statement Of Work (SOW). Briefs that fall inside our exclusion list are politely declined and we explain why.
- 02
Scope
We review the draft, refine it, and send a final SOW with a fixed price for in-scope work. Larger or ambiguous briefs start with a paid scoping workshop credited against the final fee.
- 03
Build
Weekly checkpoints. Your access stays your access — we work in your tools where possible. No surprises, no big-bang reveals.
- 04
Acceptance
Tested against the acceptance criteria written into the SOW. No “is it done?” — there's a checklist.
- 05
Handover
Repo, credentials, prompts, run-book, known limitations. Yours to keep. The Engine runs in your tools, on your accounts, with your data.
- 06
Run mode (optional)
If you want us to keep an eye on it, you choose a Support plan (Basic Care, Standard Care, Priority Care). If not, you own it and we're available for Change Requests.
Boundaries
What does this methodology not replace?
A real conversation with a lawyer or accountant. The six steps above describe how Engine Labs builds — they are not legal counsel, not a regulated compliance framework, and not a substitute for the contract pack (MSA, SOW, SLA and Addendum) we attach to every engagement.