Six stages. Each with a job, and a clock.
No open-ended engagements. From the first call to the day we hand over the keys, here's exactly what happens and roughly how long each stage takes — durations vary with scope, and we confirm exact timing in the proposal.
Discovery Call
1–2 daysA focused conversation about what you're trying to achieve — the problem, the current setup, constraints, and what "done" looks like. No deck, no pitch, just questions.
- Call notes
- Initial fit check
Proposal & Scope
2–3 daysA written proposal: what we'll build, the architecture direction, what's explicitly out of scope, a timeline, and a fixed or milestone-based cost — so there's a shared, specific reference point before anything starts.
- Scope document
- Timeline
- Cost estimate
Kickoff & Architecture
3–5 daysWe design the system before we build it: infrastructure layout, service boundaries, data flow, and the tooling choices — reviewed with you before a single line of production code is written.
- Architecture diagram
- Tech decisions log
Build & Iterate
2–6 weeksDelivery in short, visible cycles — regular check-ins and working demos rather than a single reveal at the end. Scope changes get discussed against the timeline as they come up, not absorbed silently.
- Working builds
- Progress check-ins
Testing & Handover
~1 weekFunctional and load validation, then the full handover: source code, infrastructure as code, architecture documentation, runbooks, and access transfer — plus a live walkthrough session.
- Test results
- Full source code
- Architecture docs
Launch & Support
OngoingGo-live. Because you hold full ownership at this point, continued support is available if you want it — never required to keep your own system running.
- Go-live
- Optional support plan
What determines whether a build takes 2 weeks or 6?
Scope. A single monitoring stack or a focused API is closer to two weeks; a full EKS platform with CI/CD, IaC and application migration runs longer. The proposal stage fixes this before work begins.
Can scope change mid-project?
Yes — we just surface the timeline and cost impact when it happens, rather than quietly absorbing it or quietly ignoring the request.
What happens after handover if we find a bug?
Since you own the full source code and documentation, your team (or ours, under an optional support plan) can fix it directly — there's no dependency on us being available.