How to Manage a Website Development Project (Without Delays or Surprises)

Website projects look simple from the outside, and that is exactly why they slip. A build quoted at six weeks quietly becomes five months because the About page copy never arrived, three directors gave conflicting feedback on the homepage, and nobody could find the login details for the domain bought four years ago.

The project management involved is light, but it has to be deliberate. What follows is a practical operating manual for a Nigerian business commissioning a new site or a redesign — whether it is a five-page company site, a 30-page corporate site or an e-commerce store.

What a website project actually involves

A website project is three streams of work running at once: design, development and content. Your developer controls the first two. You control the third, and the third is usually the critical path.

A realistic duration for a Nigerian business site, assuming the client responds promptly:

Indicative ranges only; actual timelines depend on scope, team size and how quickly approvals and content arrive.

The client-side job has four parts: supply content, approve designs, test before launch and control changes. Everything in this guide is an expansion of those four.

The five stages, and what each one produces

Ask your developer to structure the engagement around named deliverables you sign off, not around dates alone.

1. Brief and planning. Produces a project brief, a sitemap (the list of pages and how they nest), and a content plan naming who writes what and by when. Sign off the sitemap; adding pages later is where budgets expand.
2. Design. Produces homepage and key inner-page designs, usually desktop and mobile versions. Sign off the design before development begins. Changing a layout in design costs an email; changing it after build costs a rebuild.
3. Build. Produces a working site on a staging link, with real content populated. You should have that staging link within the first week of build, not at the end.
4. Review and testing. Produces a single consolidated feedback list from you, and a fixed site after the agreed revision rounds.
5. Launch and handover. Produces the live site plus the handover pack: domain and hosting access in your name, CMS admin accounts, analytics access, backups and a short training session.

Stage sign-offs matter because they create a shared record. "Approved on 12 March" prevents the week-nine conversation that starts with "actually, we never liked that layout".

The real cause of most delays: content

Across the majority of website projects, the schedule slips because text, images, staff photographs, product details or legal pages arrive late. Treat content as a project workstream with owners and deadlines.

Content you must plan for:

• Page copy for every page in the sitemap, including the small ones nobody remembers (privacy policy, terms, delivery information, FAQ).
• Company photography. Team portraits, premises, products or project photos. Generic stock imagery weakens credibility, particularly for Nigerian service firms whose buyers are checking whether you are real.
• Logo files in a usable format, plus brand colours and fonts if they exist.
• Product data for e-commerce: names, descriptions, prices, variants, weights for delivery, and images at consistent dimensions.
• Proof elements: certifications, memberships, client logos you are permitted to use, genuine testimonials with consent.
• Legal and compliance text: privacy notice reflecting the Nigeria Data Protection Act 2023, returns and delivery policies for stores, and any regulator-required disclosures for your sector.

Three practical rules. First, set the content deadline before the design stage ends, because designing around real copy produces a better site than pouring copy into a finished layout. Second, if you cannot produce copy internally, pay for copywriting rather than delaying eight weeks — many Nigerian agencies price this as an add-on, indicatively ₦30,000–₦120,000 per page depending on research required. Third, nominate one person to collect everything into a single shared folder.

Who approves what, and how to give useful feedback

Design feedback is where projects lose weeks, because design attracts opinions from everyone.

• Appoint one approver. Consult whoever you like internally, but one person sends the final, consolidated feedback.
• Give feedback once per round, in one document, not in a stream of WhatsApp voice notes over five days.
• Comment on outcomes, not decoration. "A first-time visitor cannot see what we do within five seconds" is actionable. "Make it pop" is not.
• Refer to specifics: page, section, and what should change.
• Separate must-change from nice-to-have, so the developer knows what blocks sign-off.
• Check on your phone. Most Nigerian visitors will see the site on a mid-range Android device on mobile data. Review the mobile version with the same attention as the desktop one.

A feedback template that works: Page → Section → Issue → Desired outcome → Priority (must/should/could).

Revision rounds and how to use them well

Unlimited revisions sound generous and cause disputes. A defined allowance protects both sides.

Indicative industry norms, not fixed rules; confirm the exact allowance in your contract.

Define clearly that a defect (a broken form, a layout error on mobile, a typo the developer introduced) is fixed free, while a change (new section, different structure, new feature) consumes a revision round or is quoted separately. Writing that distinction into the proposal prevents the most common argument in Nigerian website projects.

A week-by-week plan for a typical eight-week build

An indicative plan for a 10–15 page custom business site. Adjust to your scope.

1. Week 1: Kick-off, brand and competitor review, sitemap agreed, content plan issued with named owners and deadlines.
2. Week 2: Copy drafting begins; developer prepares wireframes or structure for key pages; you gather photography.
3. Week 3: Homepage design presented. You return consolidated feedback within three working days.
4. Week 4: Inner page designs and mobile views presented and approved. Content deadline falls here.
5. Week 5: Development begins; staging link shared; core templates built.
6. Week 6: Content populated; forms, WhatsApp click-to-chat, maps and any payment integration configured.
7. Week 7: Your full review on staging, on both phone and desktop; consolidated feedback issued; fixes applied; speed and mobile checks.
8. Week 8: Final approval, launch, analytics and Google Search Console connected, handover session and documentation.

Notice that two of your obligations — feedback within three working days and content by week four — determine whether week eight is realistic. Put both in the contract.

Managing payments, scope and change requests

For website projects, a two- or three-instalment structure is normal in Nigeria:

Indicative structures; vendors differ and some request 50% upfront and 50% on completion. What matters is that a meaningful balance remains payable after the handover pack is delivered.

For scope, agree the page count and the feature list in writing. Common additions that are genuinely extra work, and should be priced rather than assumed: a blog, a careers section with application forms, multi-language versions, a customer login area, online payments, booking systems, and integrations with your CRM or accounting tools.

Keep a simple change log with three columns: request, quoted cost, decision. It takes five minutes a week and removes all ambiguity at final invoice.

The pre-launch review

Work through this on the staging site before you approve go-live. Do it on a phone as well as a laptop.

• Every page in the sitemap exists and is reachable from the menu
• Business name, address, phone number and email are correct and consistent
• All phone numbers are tappable and the WhatsApp link opens the right number
• Contact and enquiry forms deliver to a monitored inbox — test each one
• No placeholder text or stand-in images remain anywhere
• Images are compressed; pages load acceptably on mobile data, not just Wi-Fi
• Spelling, currency formatting (₦) and dates reviewed by a second person
• Mobile layout checked on at least two Android screen sizes and one iPhone
• SSL certificate active and the site loads over https
• Favicon, page titles and meta descriptions set for each page
• Privacy policy present and reflecting how you actually handle customer data
• Payment checkout tested end to end with a live low-value transaction, if selling
• Delivery options, fees and coverage areas correct, if selling
• Analytics and Google Search Console connected
• Backups configured and the restore process explained to you
• Admin accounts created in your company's name, with the developer as an additional user rather than the owner

Launch day: domain, hosting and protecting your search visibility

Launch is a technical event with business consequences. Three things deserve attention.

Domain and DNS. The domain must be registered in your company's name in the registrar account you control, whether it is a .com.ng registered through a NiRA-accredited registrar or a .com. Changing DNS to point at the new host can take a few hours to propagate. Schedule the switch for a low-traffic window, and never let launch day be the day you discover the domain is in a former developer's personal account.

Email continuity. If your business email runs on the same domain, confirm that MX records are preserved when DNS changes. Losing email for a day because the new host reset the records is a common and entirely avoidable incident.

Search visibility on a redesign. If you are replacing an existing site that already ranks, protect what you have:

• Export a list of current page URLs before launch.
• Map every old URL to its new equivalent and set 301 redirects.
• Keep existing page titles and headings where they already perform well.
• Do not block the new site from being indexed — a staging setting left on after launch removes a site from search results entirely.
• Submit the new sitemap in Google Search Console and monitor coverage for four weeks.

Agree in writing who is responsible for redirects. It is frequently assumed and frequently forgotten.

Example (hypothetical): a Lagos law firm rebuilds its website

Example (hypothetical). A six-partner commercial law firm in Victoria Island replaces a dated site. Indicative budget ₦1,400,000, target eight weeks.

What the managing partner does differently from the firm's last attempt:

• Names the practice manager as the single approver. Partners give input to her; she issues one feedback document per round.
• Agrees a 14-page sitemap up front, with a separate page for each practice area, and records "client portal" and "Hausa and Yoruba versions" as out of scope for this phase.
• Books a photographer in week two for partner portraits, because the previous site's stock images had undermined credibility.
• Commissions the agency to write the practice-area pages at an indicative ₦60,000 per page, having watched the previous project stall for four months waiting on partner-written copy.
• Contracts three design revision rounds and a 30-day defect warranty.
• Reviews the staging site on her own phone on mobile data and rejects a hero image that pushed the enquiry button below the fold.
• Requires the domain, registered years earlier by a former IT contractor, to be transferred into a firm-owned registrar account before the launch date is fixed. Recovering it takes eleven days, which is exactly why she started in week one.
• Maps 22 old URLs to new ones with 301 redirects, and monitors Search Console for a month after launch.

The firm launches in nine weeks rather than eight. The extra week came from the domain recovery, not from the build.

What changes for Nigerian businesses

• Mobile is the default, not a variant. The majority of visits to a Nigerian business site come from phones. Review, test and approve the mobile version first.
• Data cost is a design constraint. Heavy image sliders and uncompressed hero videos burn a visitor's data and lose them before the page renders. Ask for compressed images and a page-weight target.
• WhatsApp is part of the funnel. A click-to-chat button, a tested number and a plan for who responds within working hours will often produce more enquiries than a contact form. Decide who monitors it before launch.
• Trust signals carry extra weight. Nigerian buyers check whether a business is real: a physical address, CAC registration details where appropriate, real photographs, genuine named contacts, and a working phone number.
• Domain and hosting ownership is a recurring problem. Many Nigerian SMEs discover their domain sits in a previous developer's account. Resolve ownership in week one of any project.
• Local payment expectations for stores. Card, bank transfer and USSD flows through providers such as Paystack, Flutterwave, Interswitch or Moniepoint should each be tested with a real low-value transaction before launch, not assumed to work.
• Power and connectivity affect your team, not just visitors. Schedule approval meetings when your approver has reliable power and data, and share designs as files that can be reviewed offline.

Mistakes to avoid

• Starting design before content is planned. It guarantees a redesign or a site full of filler text.
• Letting five people give feedback separately. Contradictory instructions become paid rework.
• Approving designs only on a laptop. Your customers are on phones.
• Paying 100% upfront. Keep a balance tied to handover.
• Leaving the domain in the developer's personal account. It is your business asset; register or transfer it in your company's name.
• Skipping redirects on a redesign. You can lose established search visibility overnight.
• Launching without testing forms and payments. Enquiries that vanish are worse than no form at all.
• No handover session or documentation. You should be able to update basic content yourself.
• Treating launch as the finish line. Budget for maintenance: indicatively ₦20,000–₦150,000 per month or a yearly retainer, depending on the site and support level.

Conclusion

A website project is manageable with modest effort if you control the few variables that matter: one approver, content delivered on a deadline, staged sign-offs, a defined number of revision rounds, a payment balance held until handover, and a launch checklist that covers domain, forms, payments and redirects. Developers rarely cause the delays that frustrate business owners; unowned decisions and missing content usually do.

If you are about to start a build or a redesign and want a clear stage plan, content schedule and handover arrangement agreed before work begins, Linestech can help you structure the project and the brief so the timeline you are quoted is one you can actually meet.

Frequently asked questions

How involved do I need to be in a website project?

Budget two to four hours a week: reviewing designs, approving stages, supplying content and testing. The heaviest weeks are the design review and the pre-launch review. Projects where the client disappears for a month almost always finish late, because the build stops at the first unanswered question.

What should I do if my website project has stalled?

Ask for a written status summary listing what is complete, what is outstanding on each side and a revised date. Most stalls are caused by an unanswered question or missing content, so check your own outstanding items first. If the developer is unresponsive for weeks, rely on your contract's termination terms and ensure you hold the domain, hosting and any completed files.

Can I change the design after development has started?

You can, but it is the most expensive point at which to do it, because layouts, templates and responsive behaviour may all be rebuilt. Expect it to be quoted as additional work. This is why design sign-off is a formal stage rather than a casual "looks fine".

Who should own the hosting account?

Your business. Open the hosting and domain accounts in your company's name and email address, then add the developer as a user. It costs nothing extra and removes the single most common source of disputes when a working relationship ends.

How many pages should we launch with?

Launch with the pages that answer a buyer's questions: what you do, proof that you can do it, who you are, and how to contact you. A focused 8–12 page site that is complete beats a 40-page site half full of placeholder content. Add depth after launch when you can see what visitors actually search for.

Should the developer also write my content?

If your team cannot realistically produce copy within the project window, yes. Paid copywriting is cheaper than a three-month delay, and a writer who interviews you will usually produce clearer pages than an internal draft written between other duties. Give the writer access to someone who knows the business well.

What should I receive at handover?

Domain and hosting account access in your name, CMS admin credentials, a list of plugins or services used with their renewal dates, analytics and Search Console access, backup arrangements, design source files where the contract provides for them, and a short training walkthrough. Get this in writing before the final payment.

Sources and further reading

Figures, platform rules and regulations change. These are the primary references behind this article and the places to check before you act on it.

• Corporate Affairs Commission (CAC)
• Nigeria Data Protection Act 2023 — NDPC
• Nigeria Internet Registration Association (NiRA)
• Paystack developer documentation
• Flutterwave developer documentation
• Google Search Central Blog
• Cloudflare Learning Center