Zero to launch
A clear path for custom sites and apps — from consultation through launch, training, and support. Each phase has a concrete done criterion so project status stays honest.
Sum of phases 1–7 for a standard site: about 14–28 working days (Sat–Thu team days — not calendar days). Phase 8 is post-launch and is not included in that total.
All timelines on this page are working days (team working days; typically Saturday–Thursday). Fridays and public holidays are not counted.
Percentage labels below are approximate shares of the standard path — not a live completion meter for your project. Real status is defined by each phase’s delivery criterion.
1
2
3
4
5
6
7
8
Clear start
Discovery + estimate
Approved design
Before development
Secure launch
Testing + SSL
After delivery
Training + support
Phase 1 · Approximate path share: 0–10% of path
1–2 working days
We clarify business goals, audience, must-have features, budget, and timeline so the path is clear from day one.
Done when…
Agreed requirements list and initial time/cost estimate have been sent to you.
Phase 2 · Approximate path share: 10–20% of path
1 working day
We recommend the right package, document scope, and after agreement the project officially enters execution.
Done when…
Scope, package, and phased schedule are written; formal project start is confirmed.
Phase 3 · Approximate path share: 20–35% of path
4–9 working days
About 2–4 working days of team design + about 2–5 working days for your review and sign-off. We do not start coding without written design approval. Late approval shifts the overall timeline.
Done when…
Desktop/mobile designs for main pages have your written approval (up to two review rounds in the standard scope unless otherwise agreed in writing).
Phase 4 · Approximate path share: 35–65% of path
5–10 working days
Custom code for site or app; admin panel, integrations, and scalable architecture in this phase.
Done when…
A reviewable staging build is available and agreed features for this phase are implemented.
Phase 5 · Approximate path share: 65–75% of path
1–3 working days
Copy, images, products, or services are entered; SMS, analytics, and gateways are wired. Missing content from your side extends this phase.
Done when…
Essential v1 content is entered and agreed integrations work on staging.
Phase 6 · Approximate path share: 75–90% of path
1–2 working days
Performance, mobile, speed, and security checks plus technical SEO foundations for Google.
Done when…
Internal test checklist is closed and launch-blocking issues are fixed.
Phase 7 · Approximate path share: 90–100% of build path
1 working day
Go live on production domain; admin training so you can update content yourself.
Done when…
Site is live on the main domain, credentials are handed over, and admin training/guide is completed.
Phase 8 · Approximate path share: After delivery
Outside the 14–28 day total
Post-launch support continues per your package. This phase is not part of the initial build total; response times follow that package’s SLA.
Done when…
Support channel is active and post-delivery requests are handled under package terms.
Consultation & discovery
1–2 working days
Technical proposal & kickoff
1 working day
UX & UI design + your approval
4–9 working days
Custom development
5–10 working days
Content & integrations
1–3 working days
Testing, security & technical SEO
1–2 working days
Launch & training
1 working day
Support & growth
Outside the 14–28 day total
Approx. minimum: 1+1+4+5+1+1+1 ≈ 14 working days · Approx. maximum: 2+1+9+10+3+2+1 ≈ 28 working days (phases 1–7, including your design-approval window).
Final timing depends on scope, content readiness, and review rounds. After discovery we share a day-by-day plan. Delays in design approval or content from your side push the schedule forward.
If after agreement you want to add/remove features, pages, or integrations: 1) send a written request, 2) we estimate impact on time and cost, 3) after your written approval, scope and schedule are updated. Until then we continue on the contracted scope — no silent scope creep.
Pick the path that matches your goal — the execution roadmap is similar for all.
Tell us your goals and we will propose a clear path, timeline, and package.
