What You Need to Know Before Building a Website

What business goal should the website achieve?

A website does not start with the home page. It starts with the action you want visitors to take. For a services company, this could be a phone call or an enquiry. For a clinic, it could be booking an appointment. For a construction company, it could be sending a project, photos and a brief description to receive a quote.

Write down one primary goal and several secondary ones. The primary goal affects the structure, copy, buttons and enquiry form. If you only want to present your company, you do not need an online store. If you sell standard products with a catalogue, payment and delivery, you are talking about an online store, not a regular company website.

Also clarify where your visitors will come from. They may search for the service on Google, click through from ads, come from social media or enter the company name directly. Different sources require different landing pages and different tracking.

Which services and features should you clarify in advance?

Make a list of the services you sell, not the internal departments in your company. For each service, specify who it is for, what problem it solves, how the work is carried out and how the customer can contact you. If you have different types of customers, such as households and businesses, this may require separate pages and messaging.

Clarify from the start whether the website will include a calculator, online booking, multiple languages, a blog, portfolio, map, catalogue or CRM connection. An enquiry form can send an email, but it can also automatically create a contact or deal in CRM. A more complex process requires an API integration so data does not have to be copied between the website and your internal system.

If customers need to choose a date, service, employee or time slot, a regular contact form will not be enough. If you sell products with stock levels, cash on delivery and courier delivery, check whether the project is actually for online store development.

How should a business website be structured?

The main menu should answer the customer’s questions, not repeat the company’s organisational structure. The usual foundation includes a home page, services, pages for specific services, an about page, projects or testimonials, frequently asked questions and contact details. Not every company needs all of these pages, but every page should have a clear role.

Organise your services according to how customers search for and compare them. One general “Services” page is rarely enough for SEO or advertising. A separate page lets you explain the process, terms, ideal customer and next step.

The home page should quickly answer four questions: what do you offer, who is it for, why should customers trust you and how can they contact you? A portfolio is not just a gallery. For each project, it is useful to show the task, the work carried out and the result, whenever this information can be published.

What content should you prepare?

The provider can build the structure, design and technical foundation, but you know your customers, objections and actual terms. Prepare a list of services, prices or your quoting method, service areas, timelines, warranties, certificates, photos, logo and contact details.

Do not send only advertising phrases such as “quality and professionalism”. Give specific answers: how does the work begin, what does the customer receive, what is included, what is not included and how long does the process usually take? This information reduces unsuitable enquiries and helps the right customers make a decision.

If you do not have ready-made copy, agree on who will create it, who will provide the photos and how many rounds of revisions are included. You can also plan content creation, but approval of the facts, terminology and terms should remain with you.

How should the mobile version be planned?

The mobile version is not a scaled-down image of the desktop website. On a phone, visitors have a smaller screen, are often in a hurry and may be using mobile internet. The most important content and primary button should be visible without unnecessary scrolling.

Clarify from the start how the menu, phone button, forms, tables, gallery, map and any calculator will work. Form fields should be easy to fill in with a thumb. Large images and unnecessary animations can slow down the page.

Ask to review the key screens on a phone, tablet and computer before final development. This way, changes are made to the structure, rather than after the entire website has already been developed.

What should the enquiry form look like?

The form should collect only the information needed for the next step. For a standard service, name, phone number, email and a description may be enough. A custom quote may require a city, dimensions, preferred deadline, file or photo.

Clarify where enquiries go and who receives them. Email is a starting point, but with more enquiries, it is safer to store them in an admin panel or CRM as well. Add an automatic reply to the customer, spam protection and a successful-submission message.

Don’t forget tracking. You need to be able to distinguish an enquiry from organic search, a Google ad or a social network. Otherwise, you’ll pay for traffic without knowing which channels are generating genuine interest.

What should your SEO foundation include before launch?

SEO starts before the design. Make a list of the services and questions potential customers use to find you. Then connect those searches to specific pages. A single page shouldn’t try to rank for every service and city at once.

The technical foundation includes clear URLs, titles, descriptions, a proper heading hierarchy, internal links, a sitemap, redirects and good loading speed. Set up tracking for forms, phone clicks and other important actions. For a complete plan, see our SEO optimisation service.

If you’re replacing an existing website, the old URLs shouldn’t simply disappear. Check which pages are already appearing in Google and plan redirects to their new URLs. This way, the redesign won’t start with an unnecessary loss of accumulated visibility.

What kind of admin panel do you need?

The admin panel should match how often you actually make changes. If you publish news every week, you should be able to edit the text, image, title and SEO fields yourself. If the content rarely changes, an overly complex panel will only increase the project cost and make things harder for your team.

Define the roles you’ll need: owner, marketing employee, editor or external contractor. Not every user should be able to change the menu, delete enquiries or publish unfinished text. Ask how backups are made, how an older version is restored and what happens when something goes wrong.

Agree on who owns the domain, hosting, code, content and access credentials. The registration should be in the company’s name, not tied to an employee’s or agency’s personal email address. This matters both for future maintenance and when changing contractors.

What budget and timeline should you expect?

For a company website, the price typically ranges from €500–€5,000. The lower end usually means a clearer scope, ready-made content and few custom features. The upper end is driven by more pages, custom design, multiple languages, calculators, integrations, complex forms and migration from an old website.

This is the development price, not automatically the price of advertising, ongoing content creation, hosting and monthly maintenance. If you want the team to handle updates, checks and minor changes after launch, maintenance is planned separately in the range of €100–€350 per month.

The timeline depends mainly on how ready the content is and how quickly approvals are given. The project goes through scope definition, structure, copy and assets, design, development, testing and publishing. Delays usually aren’t caused by the code itself, but by missing images, unclear decisions or too many people providing contradictory feedback.

How do you choose a contractor without unpleasant surprises?

1. 01
   Describe the scope on one page

   Write down the objective, services, required pages, features, integrations, languages and who will provide the content. This document provides a consistent basis for comparing proposals.

2. 02
   Ask to see similar projects

   Don’t look only at the visual style. Check whether the website works well on mobile, whether the form sends an enquiry and whether the structure makes sense for your type of customer.

3. 03
   Check what the proposal includes

   Check whether the proposal covers design, development, content, the SEO foundation, migration, testing, training, access credentials and the warranty period. Don’t compare two final prices when they cover different scopes.

4. 04
   Clarify the approval process

   Decide who makes the decisions, when the structure and design are approved, and how feedback is submitted. This prevents the project from turning into an endless stream of conflicting changes.

5. 05
   Plan the launch and the following month

   Before publishing, check the forms, phone buttons, analytics, speed, backups and redirects. After launch, monitor what visitors do and which pages lead to genuine enquiries.

What should you ask for before signing?

Ask for a written description of the deliverables, stages, deadlines, price, payment terms and conditions for additional work. Clarify who approves the content, who uploads the products or services, and how each stage is accepted.

Ask what you receive at handover: admin access, domain, hosting access, a backup, the code, instructions and integration details. Also find out how future changes are requested. A clear agreement at the outset is worth more than the promise that “everything will be sorted out as we go.”

When you have a clear goal, structure and measurable actions, quotes become comparable. You can then choose a provider based on their process, communication and understanding of your business—not just the starting price.