Before You Approve a New Website: A Practical Launch Acceptance Checklist

Your developer says the site is ready and the final invoice is attached. Before you approve the launch and pay that last instalment, run one structured check: open the site on a phone, submit the contact form and tap the WhatsApp button to confirm they reach you, read every page for wrong prices or details, and confirm you can log in to the domain, hosting and email in your own name. Acceptance is the moment you agree the work is done, and the last point where fixes are still covered by the fee you already agreed.

This is for the owner about to sign off a first professional website and release the balance. Below is what acceptance means, then the checklist grouped by area, so you can walk through it in under an hour and approve with confidence.

TL;DR

• Acceptance is a decision, not a formality. You are confirming the site does the job before the final payment clears.
• Test the lead paths first. A polished site that does not deliver a form submission or a WhatsApp message to you is not finished.
• Check it on a real phone on mobile data, not just a fast office laptop, because that is how most Zimbabwean visitors will see it.
• Confirm ownership as a line item: domain, hosting and email in your business name, logins in your hands. See the website ownership handover checklist.
• This is sign-off only. It is not about ongoing hosting and support (see what happens after your website goes live) or mid-build change control (see controlling website revisions and scope).

What a launch acceptance check actually is

A launch acceptance check is the structured review you run before approving a new website and paying the final instalment. You confirm that the pages work, the site is usable on a phone, the contact form and WhatsApp button reach you, the basic Google and analytics setup is in place, the content is correct, and the accounts are in your name. Anything broken goes on a snag list to fix before you sign off.

The acceptance checklist, grouped by area

Walk through these in order. You do not need technical skills, only a phone, a laptop and about an hour. Tick each item, and note anything that fails so it lands on a single written snag list rather than a scatter of messages.

1. Core pages and functionality

• Every page in the agreed scope exists and opens without an error.
• The menu, footer links and buttons all go where they should, with no dead links.
• Your business name, address, phone number and email are correct and consistent on every page.
• Any prices, packages or service details shown are accurate and current.
• Spelling and obvious formatting are clean, especially on the home and contact pages.
• Images load, sit the right way up, and are not stretched or blurry.

2. Mobile and slow connections

Most of your visitors will arrive on a phone, often on mobile data, so this group matters more than any desktop view.

• Open the site on an actual phone, not just a shrunken laptop window.
• Text is readable without pinching and zooming, and nothing runs off the edge of the screen.
• Buttons and the menu are easy to tap with a thumb.
• The home page loads in a reasonable time on mobile data, not only on office wifi.
• The WhatsApp button and phone number are easy to reach on a small screen.

3. Lead paths: forms and WhatsApp

This is the group people skip and later regret. Test it live, with real submissions.

• Fill in and submit the contact form yourself, then confirm the message arrives in the inbox you will monitor.
• Check exactly who receives form submissions, and that it is an address someone actually reads.
• Tap the WhatsApp button and confirm it opens a chat to the correct number.
• After submitting, you land on a clear thank-you or confirmation, so a real customer knows it worked.
• Any auto-reply or notification that was promised behaves as agreed.

4. Found on Google and measured

You do not need to rank on day one, but the basics should be in place so you can be found and can see what is happening.

• Each page has a sensible title that shows in the browser tab and in search results.
• The site is not accidentally hidden from search engines, a common leftover from the build stage.
• A visitor stats or analytics tool is installed so you can see traffic once you are live.
• The padlock (HTTPS security) shows on every page, with no "not secure" warning.
• The site has a recognisable icon in the browser tab and a sensible preview when a link is shared on WhatsApp or Facebook.

5. Ownership and handover

Acceptance is the right moment to confirm control, because the final payment is your leverage. This overlaps with one dedicated question, so keep it brief here and use the full list if anything looks unclear.

• The domain is registered in your business name and you can log in to it.
• Hosting and business email are in your name, or handed to you in writing, with logins.
• You have a plain list of every account, its login, and whose name it is under.

For the full version of this group, work through the website ownership handover checklist. Ownership is easy to wave through at launch and painful to recover later.

How to run it without slowing the launch

Block out an hour and go through the five groups in one sitting, rather than sending feedback in dribs and drabs over a week. Where something fails, write it down in one place as a numbered snag list: the page, what is wrong, and what you expected. Send that single list back, not twenty separate messages, so the developer can fix the batch and you can re-check it in one pass.

Keep the standard reasonable. Acceptance is about the site doing the job you agreed, not about new ideas you have had since. A brand-new feature or an extra page you never scoped is a change request, and how those are handled mid-build is a separate discipline covered in controlling website revisions and scope. At acceptance you are checking the agreed work, not expanding it.

Where acceptance ends

Signing off says the site is built correctly and does what was agreed. It does not settle what happens next: who keeps it online, what renewal costs, and who makes small updates through the year. That is a separate conversation, and it is worth having before you need it, not after something breaks. Our guide on what happens after your website goes live covers hosting, renewal and support so you are not caught out a few months in.

How this works with a TechTribe website

On a TechTribe website, the things this checklist tests are part of the standard build: mobile-first pages designed for slow connections, a contact form and WhatsApp button, a security padlock, Google-ready setup and visitor stats, all included rather than sold back to you as extras. You can see what each package includes before committing: Starter is $350, Standard is $550, and Premium starts from $800 with a custom quote after scope.

Because the general websites are once-off with no monthly subscription, and Year 1 includes hosting, a .co.zw domain and up to five business email accounts, the ownership items on this list are straightforward to confirm at handover. When you get a quote, ask us to walk the acceptance list with you at the end, so sign-off is a shared check rather than a leap of faith.

Your next step

Do not approve a launch on a screenshot and a good feeling. Open the site on your own phone, submit the form, tap the WhatsApp button, read the pages, and confirm the accounts are in your name. Put anything broken on one snag list, get it fixed, then sign off and release the final payment.

If you want a website built to pass this checklist from the start, with the form, WhatsApp, mobile performance and ownership handled as standard, request a quote and we will walk you through acceptance before you approve the launch.

---

Author: Simon Updated: May 2026