What to get in order before you commission a website

The quality of a website project is decided, to a surprising degree, before any design or code begins. The projects that go smoothly tend to start with a client who arrived prepared — not with technical knowledge, but with clarity about a few ordinary things.

Here's what's worth having in order before you start talking to anyone. None of it requires expertise. All of it will save you time, money, and a particular kind of frustration.

Know what the site is for

It sounds obvious, and it's the thing most often skipped. "We need a website" isn't a goal; it's a category. A site meant to book appointments is a different object from one meant to establish credibility with investors, which is different again from one meant to sell products directly.

Before you brief anyone, finish this sentence honestly: the single most important thing a visitor should do on this site is ___. You're allowed secondary goals, but if you can't name the primary one, the project has no way to make trade-offs later — and every project is a series of trade-offs. The clearer you are here, the better every decision downstream becomes.

Gather your content early — it's always the bottleneck

The most common cause of a delayed website is not design, and it's not development. It's content. The photographs that never quite get taken, the "about" text that sits half-written for three weeks, the product descriptions someone keeps meaning to finish. Design can move quickly. Waiting on words and images usually can't.

If you do one thing before a project starts, gather what you have: your logo in its original file, real photographs rather than placeholders, the text for your key pages even in rough form, any testimonials or client names you're permitted to use. Rough is fine — rough can be edited. Missing is what stalls a project for a month.

Separate what the site must do from what would be nice

Early conversations tend to accumulate ideas — a blog, a booking system, a members' area, a shop, a newsletter. Each is reasonable. Together, they can quietly turn a six-week project into a six-month one, usually without anyone deciding that on purpose.

It helps to separate, in your own mind, what the site must do to be worth launching from what could be added later. A site that does one thing well and ships is worth more than an ambitious one that never quite launches. A good firm will help you draw this line — but arriving with a sense of it already makes you a better client, and the project a better project.

Know what you're buying beyond the build

A website isn't a thing you buy once. It needs somewhere to live, a domain that stays registered, updates as the software beneath it changes, attention to security, and someone to call when something breaks. These aren't optional extras. They're the ordinary cost of a site that keeps working.

So before you commission a build, ask what happens after launch. Who maintains it? What's included, and what's billed separately? A site handed over with no plan for its upkeep isn't finished — it's abandoned on a schedule. The answer to "what happens after launch?" tells you whether you're buying a project or a relationship. For most businesses, the second is what you actually want.

The questions worth asking

You don't need to interrogate anyone's technical choices. A few plain questions tell you most of what matters:

• What happens if you're late?
• Can I see something you've built that's live right now?
• Who owns the site and the code when it's done?
• What do you handle after launch, and what falls to me?

Clear, specific, unhurried answers are a good sign. Vagueness — or a faint discomfort at being pinned down — is worth noticing.

You're not simply buying a website. You're choosing who to trust with what's often the first thing a customer sees of your business. Preparing well is how you make that choice from a position of confidence rather than hope. And the people worth choosing tend to meet that preparation in kind — asking as many questions as they answer, because understanding what you actually need is where any good build quietly begins.