How to Choose a Web Design Company: 10 Questions to Ask

You got quotes from several companies to build your website, and they all look alike. The designs are sleek, the claims are bold and the timelines look close to each other. To see the difference, you need to ask the right questions. The ten questions below will help you whichever company you work with. The aim is not to put the company to the test but to make expectations clear from the start so you don't face surprises later. A good company won't be bothered by any of these questions; in fact, it will explain most of them before you even ask. The list needs no technical knowledge, and under each question you will also find what a good answer looks like.

1. Which sites have you built for businesses like mine?

Seeing a list of client references isn't enough; open the live sites on your own phone. Do they load quickly, can you easily find the information you're looking for, is the contact button easy to see? If possible, have a short talk with a business the company has worked with. Having worked in the same sector isn't essential, but it matters that the company tries to understand how your customers make decisions. A company that only talks technology in the first meeting and never asks about your business will build the site from its own point of view too. Look not only at whether the reference sites look good but also at whether they bring customers to the business; the owner of that business can tell you this best.

2. Whose name will the domain name, the site and the content be in?

This is the most important question on the list. Your domain name (your web address) should be registered in your name or your company's name. The site's files, the content and access to the admin panel should also belong to you. Otherwise, when you want to change companies later, you may struggle to get your address or your site back. Also confirm that the login details for the admin panel, the hosting account and the domain name panel will be handed over to you at delivery. If the answer isn't clear, have this written into the contract.

3. Which platform do you recommend, and why?

Be careful with a company that recommends the same platform for every job. For a standard brochure site, a ready-made system such as WordPress can be quick and economical. For work that needs special functions, high visitor numbers or a high level of security, a fully custom build may be the better choice. A good answer doesn't start with "always this" but with "this, for your needs, because". Also ask whether the recommended platform is suited to growing later. Today you may want a five-page site, but tomorrow you may want to add e-commerce or more languages.

4. Will I be able to update the site myself?

Having to write to the company every time for a new photo, an announcement or a small text change wastes both time and money. Ask whether there is an admin panel, how easy it is to use and whether you will get training on using it. If possible, try the panel yourself before delivery. Knowing from the start what you can change in the panel and what you will still need the company for prevents disappointment later. Also find out whom to ask when you get stuck later on.

5. What exactly is included in the quote, and what isn't?

Looking only at the total figure when comparing quotes is misleading. How many pages will be built, how many revision rounds are included, who will prepare the texts and photos, whether domain name and hosting costs are included in the quote, and whether maintenance after launch is charged separately should each be written down. Two quotes that look alike can be very different in scope. For every item that stays vague, ask "Is this included?" and get the answer in writing. Also discuss which stages the payments are tied to.

6. What will the timeline be, and what happens if there is a delay?

A realistic timeline also includes what you need to deliver: content, approvals and access details. Ask when each stage will finish and where delays usually come from. Be cautious with a quote that promises a very short time without stating any conditions; speed is often paid for with skipped tests. Also find out who your contact person will be during the project and which channel you will communicate through; getting regular replies to your questions matters as much as the timeline.

7. How is the site tested on phones and for speed?

Most of your visitors will probably come to your site from a phone. Ask how the site is tested on different screens and how its loading speed is measured. A company that knows the measures Google uses to assess page experience (Core Web Vitals) will give a concrete answer to this question and can show you the measurement results. Also ask whether the forms, the call button and the map link are checked before launch to make sure they really work on a phone.

8. What do you do from the start for search engines and AI search?

Reaching the top of Google takes effort after launch too, but the foundation has to be laid correctly from the start: page titles, descriptions, clean page addresses, fast loading and a clear content structure. Today, AI tools such as ChatGPT also draw information from websites when answering questions. Ask what the company does on these two fronts from the start and what counts as a separate service. Be skeptical of guarantees such as "We'll get you to the top spot", because nobody can guarantee that. If you have an old site, also ask whether the old page addresses will be redirected to the new pages. If this isn't done, the visibility built up over the years can be lost.

9. How will maintenance and support work after launch?

A website still needs updates, backups and security monitoring after it goes live. Ask what maintenance covers, whom to contact and how when there is a problem, and how quickly you will get a reply. It is also worth asking how updates are done without breaking your site, where the backups are kept and how often they are taken. A site left without maintenance slows down over time, and the risk of security holes grows.

10. What happens if I want to leave?

Nobody wants to start a job thinking about parting ways, but this question measures trust. Ask how all access details, files and backups will be handed over to you when the working relationship ends. A company that gives a clear and relaxed answer on this isn't trying to keep you tied to its system. The answer to this question also shows how confident the company is in itself and its work.

How should you evaluate the answers?

What you should pay the most attention to in the answers is clarity. Instead of vague answers such as "We'll handle it" or "No problem", look for concrete answers that can be put in writing, then ask to see those answers in the quote or the contract. Price matters, of course, but the lowest quote may also be the one with the narrowest scope. When comparing, make sure you are comparing the same scope. The attitude a company shows when answering matters as much as the answers themselves. An approach that rushes you or brushes off your questions may show itself throughout the project as well.

You can ask Adorb all of these questions too. With us, the domain name, the site and the content belong entirely to you. We choose the platform together based on your needs, teach you how to use the admin panel, and provide maintenance and support after launch. We can go through these ten questions one by one in a free discovery call.