A clock you can audit.
Micro apps run 3–6 days. Complex apps run 7–14 days. The clock starts at scope lock and pauses when the next move is yours.
Watch the clock pause.
The SLA measures studio delivery time, not time spent waiting for client input. Pick a pause reason to see what stops and what you need to do next.
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.
Interactive example only. The written scope sheet defines the committed window for your app; the clock state in your dashboard is the operational record.
Three risk states, defined.
Status is always shown with a label, not colour alone. The definitions below are the same ones used by the studio dashboard.
The studio owns the next action and the remaining committed window still contains the planned build, QA, staging, and handover work.
A dependency or remaining buffer threatens the committed window, but the clock can still finish on time if the next action lands promptly. The studio flags it in the dashboard.
The committed window has passed while the next action was the studio’s. The studio reviews the cause and the remedy in writing; this page does not promise automatic compensation.
Risk labels are operational guidance, not an automatic refund or credit promise. Any remedy follows the written scope, the Refund Policy, and the Code Retention Policy.
Estimate your window.
Choose an app type and a start date to see the PRD range. Actual dates depend on scope, feedback, third-party access, and whether the clock pauses.
Estimated launch window
Choose a start date
Select a date to see the estimated window.
Estimate, not a contract. The simulator shows the standard Micro 3–6 day and Complex 7–14 day windows; it does not promise a date or imply compensation.
The full rules.
Open any section for the detail that used to sit in the static tables.
When the clock starts, pauses, and holds Micro, Complex, and on-hold rules
| Type | Window | Clock starts | Clock pauses |
|---|---|---|---|
| Micro | 3–6 days | When the scope is locked and the app enters Start | When we need data, review, or a decision from you |
| Complex | 7–14 days | When the scope is locked and the app enters Start | When we need data, access, review, or a decision from you |
| On hold | — | — | While the app is on hold for a client or third-party dependency |
What pauses the clock Four normal pause reasons and their effects
| Event | Effect |
|---|---|
| Intake item missing | Clock pauses; client action is created. |
| Staging review pending | Clock pauses until approve or revision. |
| Infra access missing | Clock pauses until access is ready. |
| Scope change requested | Scope change is priced and scheduled separately; the SLA does not absorb it. |
Two example schedules Illustrative day-by-day examples
Micro
3–6 daysDay 0 brief, Day 1 scope lock, Day 3 staging review, Day 5 handover.
Complex
7–14 daysDay 0 brief, Day 1 scope lock, Day 5 QA, Day 7 staging review, Day 11 handover.
The clock measures studio execution, not waiting time. It does not create an automatic refund, credit, or penalty; remedies follow the written agreement and policies.
See the timeline, then the price.
Every plan uses the same clock rules. The difference is scope and quota.