How it works
You have four moments. We handle the rest.
Send the brief, review staging, verify handover, and answer an async ticket if needed. Between those moments, a named engineer scopes, builds, tests, and deploys to your cloud.
Interactive walkthrough
The night shift machine
Six gated stages, one continuous line. Move through the stages or play the whole cycle.
Input · document
A brief the studio can act on
- The problem and the target user
- Core features and the first launch boundary
- References, examples, or existing assets
Read details for this stage
- No specification is required. A clear problem statement is enough to start.
- The studio replies with questions only when a missing detail blocks scoping.
- Micro and Complex apps use the same intake; the difference is the size of the first launch.
Stage 1 of 6: Brief & Intake
Your side of the table
Four moments. Everything else is ours.
Select a moment to see what the studio is doing behind it.
While you do that
The studio handles:
- Triage the brief and check whether it is complete enough to scope.
- Classify the first launch as a Micro or Complex app.
- Ask only the questions that block a written scope.
No standups. No backlog grooming. No chasing engineers. Just one clear next action when the studio needs you.
SLA, without mystery
The clock runs while we work. It pauses when the next move is yours.
Micro apps run 3–6 days. Complex apps run 7–14 days. The clock measures studio execution, not time spent waiting for your review.
The clock you can audit
It runs while we work. It pauses when the next move is yours.
The SLA measures studio execution, not time spent waiting for a decision. Pick a pause reason to see what happens to the clock and what the client needs to do.
Clock running. The studio is executing the sprint.
What you actually get
Proof at every gate.
Three artifacts make the process auditable: the scope, the QA record, and the handover manifest.
Readiness gate · signed before build
A written scope, locked before code
Acceptance criteria, data model, launch boundary, and an explicit out-of-scope list. The studio can be held to it.
- Acceptance criteria for the first launch
- A named engineer and a named reviewer
- Out-of-scope work priced separately
Realistic schedules
You sleep. The work moves.
Two example schedules. The clock pauses when the next move is yours, so the date reflects studio execution rather than waiting time.
Example schedules. Actual dates depend on scope clarity, third-party access, and how quickly the next decision is available.
The night shift
You sleep. The work moves.
One illustrative Micro night, from brief to verified handover. Estimate your own window with the same SLA ranges the studio commits to.
Night shift log
One Micro night, brief to handover
- 21:10 Brief received Brief card Your move
- 21:45 Scope drafted Written scope Studio
- 23:10 Scope locked · clock starts Readiness gate Studio
- 01:30 Build in progress Commit stream Studio
- 04:20 QA gate passed Test checklist Studio
- 06:10 Staging deployed Preview URL Studio
- 07:40 Review approved Signed-off staging Your move
- 09:00 Handover verified Manifest Studio
Example timings for one Micro cycle. Actual dates depend on scope, feedback, and third-party access. The SLA clock pauses while the next move is yours.
Estimate the window
Pick a start date. See the range.
Estimated launch window
Choose a start date
Select a date to see the estimated window.
Micro 3–6 days · Complex 7–14 days. Estimates, not a contract. The clock pauses while the next move is yours.
Read the full six-stage process Stage, your action, studio action, gate, SLA behavior
| Stage | What you do | What the studio does | Quality gate | SLA behavior |
|---|---|---|---|---|
| 01 Brief & Intake | Send the problem, the people who will use it, the core features, and any reference you already have. | The studio triages the idea, classifies it as a Micro or Complex app, and checks whether the brief is complete enough to scope. | Brief received | Timer pending start |
| 02 Scope Lock & Readiness | Answer a short clarification if the studio asks. After the scope is locked, changes are handled as a separate decision. | Write the specification, acceptance criteria, data model, and out-of-scope list. Assign a named engineer and start the SLA clock. | Written scope locked | Clock starts |
| 03 Night Shift Build | Nothing. Track progress in the client dashboard and answer an async ticket only if the engineer needs a decision. | The named engineer builds the product: interfaces, data model, API, integrations, and automated tests. Commits and progress appear in your dashboard. | Build complete | Clock running |
| 04 Internal QA Gate | Nothing. The studio does not ask you to test an unfinished build. | Run type checks, unit and end-to-end tests, security checks, and responsive checks. Open blocker bugs stop the release. | QA pass · zero blockers | Clock running |
| 05 Staging Review | Open the live staging URL, test the critical paths, and approve or request an in-scope revision. | Deploy the staging build, provide test credentials, publish release notes, and pause the SLA clock while you review. | Staging approved | Clock paused · waiting on you |
| 06 Cloud Handover & Verification | Verify the repository, the live production URL, the documentation, and the handover manifest. | Deploy to your cloud account, transfer the repository to your organisation, clear studio secrets, and deliver the runbook. | Handover verified | Complete · next brief ready |
The next move is yours
Send the idea. Sleep. Wake up to shipped software.
One active app per client. A named engineer. A written scope. A clock you can audit. Code and cloud ownership transferred at handover.