7 Things to Decide Before You Build a Business Website

Most website projects go wrong before a single page is designed — not because of bad execution, but because of decisions that were never made. If you're about to build a business website, working through these seven questions first will save you weeks of revisions later.

1. What is the single job this website has to do?

A website trying to do everything — sell, inform, recruit, and entertain — usually does none of it well. Decide the one primary action you want a visitor to take: book a call, request a quote, make a purchase, or fill a form. Everything else on the site should support that one goal, not compete with it.

2. Who is actually going to land on this page?

A website for local customers walking into a shop needs different information than one for enterprise buyers comparing vendors across countries. Write down two or three real visitor types before deciding on layout, tone, or even how much text a page should carry.

3. What content already exists, and what's missing?

Design moves fast once real content is in hand — and stalls badly without it. Before development starts, gather your actual service descriptions, pricing structure, photos, and any testimonials you already have. If key content doesn't exist yet, plan time to create it rather than discovering the gap mid-build.

4. How will people find this site in search?

A beautiful website that no one can find is a cost, not an asset. Decide early which few keywords actually matter for your business, and make sure your page structure, headings, and URLs are planned around them from day one — retrofitting SEO onto a finished site is always harder than building it in.

A site built with search in mind from the start needs far less rework later than one where SEO is added after launch.

5. Who will update this site after launch?

Prices change, services get added, blog posts need publishing. Decide upfront whether you, your team, or your agency will handle updates — and make sure the platform you choose actually matches that answer. A site only you can edit, when you don't have the technical skill to edit it, becomes stale fast.

6. What happens if something breaks?

Hosting issues, bad plugin updates, and accidental deletions happen to real businesses regularly. Decide on a backup plan before launch, not after a crisis — see our note on backups, cloning, and migration if you're not sure where to start.

7. What does success look like in 90 days?

"More traffic" isn't a measurable goal. Pick two or three numbers you'll actually check — enquiries received, quote requests, or organic visits from a specific set of keywords — so you can tell whether the new site is actually working, not just whether it looks good.

Bringing it together

None of these questions require technical expertise to answer — they require clarity about your business. Once you have that clarity, the design and development process becomes dramatically faster, because there's far less guessing and far fewer rounds of "actually, can we change this?"