How to get a website built: a step-by-step guide

What should you decide before you get a website built?

Before you get a website built, write down the one job the site has to do: collect enquiries, sell products, build trust or share information. That sentence makes every later decision easier. The designer knows what to put first, and the developer knows what to build.

Then describe your visitor. Who comes to the site, whether they use a phone or a laptop, and what they are looking for. Most owners know the answers, but because nobody writes them down, they get lost in the first design meeting.

Finally, decide how you will judge success. For example, the number of enquiries through the contact form, or how many visitors move from a product page to the basket. Without a measure, you cannot tell after launch what worked and what did not.

If your team and your developer are in different countries, add two more lines: which languages the site needs, and who makes decisions in which time zone. Both affect content, testing and how quickly feedback moves.

A short preparation checklist

• The purpose of the site, in one sentence.
• Your target visitor and the three questions they ask most often.
• A list of the pages you need. If you are unsure, read pages every company website needs.
• Two or three sites you like and two you do not, with reasons.
• Who will provide the text and photos.
• A budget range and the launch date you need.

How do you choose a web design company?

The most important thing to check is whether the company puts its promises in writing. A good portfolio does not tell you everything. If the date, the scope and the ownership are not written down, you have nothing to point to when something goes wrong.

• Who you talk to: a salesperson or the person who will write the code. Every extra layer loses information.
• A written end date: not "about two months" but a specific day, along with what counts as finished.
• Whose name the accounts are in: the domain and server should be registered to you, not to the agency. We cover this in who should own your domain and hosting.
• Whether you get the code: if you ever move to another team, you need access to the code repository.
• Whether leaving is easy: check the contract for penalties, lock-ins or long notice periods.

Location matters less than it used to. Many companies abroad work with teams in Turkey, and the reverse is also common. What matters is a shared written scope, one contact person on each side and a fixed rhythm for feedback.

What should a website quote include?

A good quote says what will be built, what it costs and when it will be finished, on one page. The page list, the number of languages, the admin panel, forms, integrations and support after launch should each be listed separately.

If the quote contains open-ended phrases such as "extra charges may apply", ask exactly what they cover. To see which factors move the price, read what determines the cost of a website. If you have several quotes on the table, how to compare software quotes shows how to line them up fairly.

How long does it take to build a website?

A company website usually takes a few weeks to build. The thing that delays it most is not the code but the content. If the text and photos arrive late, the site cannot go live even when it is technically ready.

So make the content plan part of the quote. Who writes the text, who takes the photos and who approves them should be clear from the start. A multilingual site needs this plan for every language.

What are the most common mistakes?

The most common mistake is asking for a price before writing down the scope. When the scope is vague, every company prices the site it imagines, and the quotes cannot be compared.

• Starting the design before the content. When the real text arrives, the layout breaks and pages are redrawn.
• Leaving approvals open. A design that five people comment on separately never ends. Name one decision maker.
• Trying to fit everything into the first version. Launch what is needed, then add the rest.
• Not taking over the accounts. When the project ends, passwords and access should be handed to you in writing.

What should you check before launch?

Before launch, check that the site works on a phone, that the forms send, and that pages load quickly. These are the first things a visitor notices.

• Does every page work on phones and laptops. This is called responsive design.
• Does the contact form really email the right address.
• Does the site have an SSL certificate, with the padlock in the address bar.
• Are page titles and descriptions filled in. What makes a website SEO friendly covers the rest of the search setup.
• If there is an old site, are the old addresses redirected to the new pages. See how to redesign without losing SEO.

What happens after delivery?

In the first weeks after delivery small bugs are normal, and who fixes them, and how fast, should be in writing. We fix any bug found in the 30 days after delivery free of charge.

After that you can choose a maintenance plan. Updates, backups and security checks fall under it. Details are on our maintenance and support page.

If you want to see how we work, our how we work page lists every step from the first message to delivery. The scope of our company site projects is on the web design page.