Fazley RabbiA website project usually runs through six stages: a first conversation, a written proposal, content and design, development, testing, and launch, followed by a short settling-in period. The building itself is rarely what causes delays. Projects mostly slow down while they wait: for content, for feedback, for a decision, or for access to an account. Knowing what each stage needs from you is the simplest way to keep your project on schedule.
The stages, one by one
1. First call (discovery)
You explain the business, what the site must do and any deadline. A good developer asks more than they talk: who the visitors are, what happens today when a customer gets in touch, which systems you already use, and who makes decisions. Bring a brief if you have one; writing a website brief shows how.
2. Proposal and scope
You receive a written scope: the pages and features, what is not included, the timeline, the payment stages, and who provides what. Read the "not included" part carefully. Many later disagreements come from things each side simply assumed.
3. Content and design
Content (text, photos, product lists, prices) and design move together. Usually you see a layout or one sample page first, then the remaining designs. This is the stage where your input matters most, and also where projects most often lose time.
4. Development
The site is built on a staging (test) address that the public cannot see. You may be shown progress along the way. Small changes here are cheap; changes that alter structure already agreed are not.
5. Testing and review
Both sides check the site on phones and computers: forms send, payments work, pages load reasonably on mobile data, Bangla displays correctly and links lead where they should. You send one combined list of corrections rather than a stream of separate messages.
6. Launch
The domain is pointed to the new site, HTTPS is checked, redirects from old pages are put in place, and analytics and Search Console are connected. Launch is best scheduled for a working day when both sides are available, not the evening before a long holiday.
After launch
Expect a short period of small fixes as real visitors use the site, followed by the handover of logins, code and documents; see the website handover checklist.
Where delays usually come from
| Cause | What it looks like | How to prevent it |
|---|---|---|
| Content not ready | Design waits for text and photos that "will come next week" | Give every page to a named person with a deadline before the project starts |
| Too many decision-makers | Each partner or family member gives different feedback | Name one person who collects feedback and gives final approval |
| Scope creep | "Can we also add..." in the middle of development | Keep a list of new ideas for a second phase |
| Third-party approvals | A payment gateway or business account waiting on documents | Start applications early |
| Lost access | Nobody knows the domain or hosting login | Find all logins in the first week |
| Slow feedback | Days of silence after each review | Agree response times in both directions |
Payment gateways are a common example of the third row. Merchant approval follows the provider's own process and paperwork, so it is worth starting as soon as you know you need it; see taking online payments on your website.
Some delays are nobody's fault: illness, festivals, power cuts or internet outages on either side. A realistic plan leaves a little slack for them.
Waiting that is not really delay
Some time is simply part of the process. DNS changes can take a while to reach every network after the domain is pointed to a new server. A new site can take time to appear in Google search results. Provider reviews follow their own schedule. Pressure does not speed any of these up, so plan around them rather than treating them as problems.
How to keep your project moving
- Write a brief before the first call.
- Start gathering content early, even as rough drafts.
- Choose one decision-maker on your side.
- Reply to review requests within the agreed time, in one combined message.
- Hand over existing logins in the first week.
- Park new ideas for a second phase instead of adding them mid-build.
When I plan a project, I share a simple list of what I need from the business at each stage, with dates, so nobody is surprised halfway through. If you are planning a website, see my web development service or get in touch.