What to Prepare Before Building a Website (So It Does Not Stall)

Knowing what to prepare before building a website is the difference between a three-week project and a six-month one. Websites almost never stall on design or code. They stall waiting for content — the photos nobody took, the services nobody wrote down, the prices nobody decided. That wait is invisible in every quote you will receive, and it lands squarely on you.

Here is the list to have ready before anybody starts.

The decisions only you can make

1. Who the site is for

Not "everyone". Name the customer you most want more of — their situation, their size, where they are. Every later decision, from wording to structure, depends on this and cannot be made without it.

2. What you actually sell, listed

Each service or product, what it includes, what it does not, and roughly what it costs. If you have never written this down, do it now — it is the highest-value hour in the whole project and it improves the business regardless of the website.

3. What you want a visitor to do

One primary action. Call, book, request a quote, buy. Sites with four equal calls to action get none of them done.

4. What you are not

Who you are not for. This makes everything else more credible and filters out enquiries that waste your time.

The content that must exist

This is where projects die. Assume nothing is coming from the designer unless it is written in the scope.

Item	Why it holds things up
Photos of real work	Stock imagery is recognised instantly and reduces trust
A photo of you or the team	Highest-trust image on most small business sites
Service descriptions	Only you know the specifics that make them credible
Price shape	Ranges, starting points, or what moves the number
The ten questions customers ask	Becomes your FAQ, your snippets, and your AI-answer material
Logo files, in a usable format	A logo pulled off an old flyer will look bad at every size
Legal and policy text	Terms, privacy, cancellation — needed before launch, not after

The photography problem

For most small businesses this is the single biggest hidden cost and the one that most affects whether the site works. A page of genuine photos of your actual work outperforms a page of professional-looking stock every time.

Decide early: are you shooting this, are you paying someone, or are you launching with fewer, better images rather than many weak ones? The last option is usually right and rarely offered.

The practical items to have in hand

Domain access. The login for wherever your domain is registered, in your own account. If you do not know where it is, find out now — this stalls launches constantly.

Existing hosting details, if you have any.

Analytics access, if a previous site had it. Historic data is worth keeping.

A list of what currently ranks, if you have an existing site. Pages that already bring traffic must be preserved or redirected, not silently deleted. This is the most expensive mistake in a rebuild.

Every place your business is listed — maps, directories, social profiles. They will need the new address.

What to prepare before building a website: a two-week runway

If you do nothing else, do this in the fortnight before the project starts:

1. Days 1–2: Write who it is for and what you sell, with prices or price shape.
2. Days 3–4: Write down the ten questions customers ask, with real answers.
3. Days 5–7: Take photos, or book someone. This is the long pole — start it first.
4. Day 8: Find and confirm domain and hosting access.
5. Days 9–10: List existing pages worth keeping and where each should redirect.
6. Days 11–14: Draft your service descriptions. Rough is fine; a designer can edit prose but cannot invent your specifics.

A project that begins with these in hand moves at the speed of the build. One that begins without them moves at the speed of whoever is busiest.

Two things worth deciding early

Who writes the words. The most common unspoken assumption in web projects, and the most common cause of delay. Name a person before starting.

Who maintains it after launch. Updates, backups, and noticing when a form breaks. If the answer is nobody, decide that deliberately rather than by default.

FAQ

Can I start without the content ready?

You can start design, but the project will pause. Most designers will begin with placeholder text and every week after that is spent waiting for you.

How many pages do I need?

Usually six to ten: home, a page per service worth being found for, a few real-question pages, contact. Fewer, better pages beat many thin ones.

What if I do not know my prices?

Then decide the shape — what is flat, what needs a quote, what drives it up. Publishing nothing at all costs you visitors who assume the worst.

Do I need to write everything myself?

You need to supply the specifics. Somebody else can shape and order them, but nobody can invent what only you know.

What is the most common thing people forget?

Redirects from an old site. Pages that already rank disappear at launch and nobody notices for months.

Want a runway you can actually follow?

If a previous website project stalled, it almost certainly stalled here — and the fix is a checklist, not a different designer.

We run these properly, including what to ask whoever builds it. If you want a straight read on what your project actually needs before it starts, you can start it here.