A friend tells you, "You really should have a website by now." So you decide to talk to a web designer. In the first meeting you are asked: Do you have a domain name? What format is your logo in? Which websites do you like? You only came to say, "I'd like a website."
What do you need to get a website built? The answer is actually short: a few pieces of information, a few files and a few decisions. If you gather them beforehand, the process moves faster and there are fewer misunderstandings. In this article I walk through what to prepare before you start, in a plain checklist.
First ask yourself: what will the site do?
Before you meet a designer, write down a one-sentence goal. For example: "get people to book by phone", "get quote requests through a form" or "bring direct bookings to my hotel". If the goal is unclear, the site may look nice and still do nothing for you.
Then think about who it is for. Who will open your site? A household in the neighborhood, or a manager at a company in another city? Are your customers on a phone or a computer? These answers shape how the pages are built. If most of your customers call in a hurry from their phones, your phone number and directions should sit in the most visible spot.
Domain name: your site's address
A domain name is your website's address on the internet (for example, yourcompany.com). Have a few options in mind before you start. A good address is short, easy to say aloud and hard to misspell when you read it over the phone.
The most important point is this: the domain must be registered in your name. If you already bought one, find out which company you bought it from and with which email address. That information will be very useful later. Owning the address means owning the site.
Business details and text
You are the source of everything that goes on the site. Collect these in one document:
- Your business's official name, address, phone and email
- Opening hours
- A list of your services, with two or three sentences on each
- A short "about" text: how long have you done this work, and who do you serve?
- The questions customers ask most often
- Any certificates, licenses or professional bodies you belong to
You do not have to write perfectly. Write as if you were explaining to a customer over the phone. Messy notes are a fine start. But the information has to come from you. Nobody but you knows which treatments a dentist offers or which neighborhoods a plumber covers.
What legal details must appear on a site differs by country and profession. Ask your accountant or professional association, and tell your designer what you learn.
Logo, photos and example sites
Logo: If you have one, ask for the highest quality file. A phone photo of your logo will not do. If you have no logo, say so from the start; it can be discussed as part of the job.
Photos: This is where many businesses get stuck. Customers want to see real people, a real office, real work. Clear, well-lit photos you take yourself usually build more trust than stock photos. These help:
- You and your team
- Your workplace, shop, clinic or hotel rooms
- Examples of work you have done
Do not use blurry photos or photos taken from other sites; using them without permission can cause trouble. If you hired a photographer, ask whether you have the right to use the files on your site.
Example sites: Show the designer three to five sites. They do not have to be competitors, only sites that feel right to you. What matters is saying why you like them: "It's clean and easy to read", "The booking button is right there", "The photos are lovely". Show the ones you dislike too. For a designer, "I don't want this" often explains more than "I want this".
Who decides, and how approvals work
This item looks small but eats the most time. At each stage, who says "OK"? If you run a business with partners, each partner giving separate opinions stretches the process. Choose one person with authority; the others pass their views to that person.
Also think about how quickly you can respond. When a draft is sent and your reply is delayed by a few weeks, the whole schedule slips.
Budget and timeline expectations
I am not writing any figures here; it varies widely with the scope of the work. What you can do is know roughly how much you can set aside and say it openly. The designer can then plan what comes first and what comes later.
Ask yourself these timeline questions:
| Question | Why it matters |
|---|---|
| Is there a date the site must go live? | A season, an opening or a campaign may set it |
| When can I hand over the text and photos? | Most delays come from here |
| Who looks after it after launch? | The job does not end when the site is finished |
Think about what happens after launch. A site is not a sign you put up once and forget; phone numbers change, services are added, hours are updated. Talk at the start about who will make those updates. Be realistic. If you have holidays, a busy season or a sick relative coming up, share that in advance too.
Frequently asked questions
I have nothing ready. Can I still start?
Yes. You can have the first meeting and list what is missing together. But the earlier you start preparing text and photos, the smoother the process.
Do I have to write the text myself?
You need to provide the information. A designer or copywriter can help with wording and editing. Agree from the start who does what.
How many pages should the site have?
To begin with, a home page, services, about and contact are usually enough. A separate page for each important service makes it easier for customers to find what they want. You can add pages as the business grows.
Can the designer buy the domain for me?
They can, but it must be registered in your name and the login details must be handed to you. Get this in writing.
Conclusion
The preparation list may look long, but what is asked of you is not perfection, only order. Once you have your goal, your information, your files and your decision-maker, the first meeting is far more productive. If you would like to start your site together, you can reach me through my website design page.