How does delivery usually work?
A typical path runs from discovery to go-live; calendar and outputs are written per project.
Delivery is not a single “done” click. Many engagements follow a rough path: discovery → proposal/scope → design or architecture → build → testing → go-live → short stabilisation. That sequence is a template; depth of each step shrinks or grows with your project.
Without acceptance criteria, “finished / not finished” debates appear. Environment (staging/live), browsers/devices, content, and access needs should be clarified in the plan. We do not advertise a universal “live in X days for every site” promise—timelines depend on content readiness, approvals, and third-party access.
If assets, logins, or decisions arrive late on your side, the calendar shifts—that is normal and is revised openly. We also surface dependencies and risks as early as we can.
Delivery runs on a written plan for your work, not on slogan timelines.
