Skip to content
Numinam, home page
Redesign

Website creation in Belgium: how to compare quotes

Compare pages, content, migration, integrations and follow-up. The practical questions for choosing a provider without relying on price alone.

Website creation in Belgium: how to compare quotes
Published
Updated
Reading time
9 min
Author
SBSébastien BalieuFounder of Numinam

Two website quotes can show very different prices because they cover different work. Before you choose, ask each provider to spell out the pages delivered, the content, the features and the follow-up. A single line reading “complete website” makes any comparison impossible.

Give every provider the same brief: your business, the customers you want to reach, the action you expect on the site, the existing material to carry over and your deadlines. Flag the points you haven’t decided yet.

The brief to send before asking for a quote

One or two pages is enough. It should let each provider price the same project on the same assumptions:

  • your business and the offers the site has to present;
  • the customers you’re targeting and the decision they need to make;
  • the action you expect: quote request, booking, purchase, sign-up;
  • the current site, its address, roughly how many pages it has and its languages;
  • the content you already have and the content still to be written or translated;
  • the tools to connect, such as a CRM, a calendar or invoicing software;
  • the person who will sign off the project;
  • the target date and the reason for that date.

Attach a real customer enquiry, anonymised if necessary. It shows the provider the level of detail your prospects expect, and you can use it later to test the form.

The points specific to your type of project

ProjectPoints to clarify
First websitePositioning, site structure, content, forms and enquiry tracking
RedesignAudit of the current site, content migration, redirects and new journeys
B2B siteAudiences, offers, proof, contact enquiries and integrations
EcommerceCatalogue, payments, orders, delivery, customer accounts and support

For a redesign, the inventory and the migration are a piece of work in their own right. A redesign quote with no migration line leaves that work to you, or pushes it back to later.

The items every quote should describe

ItemAnswer to get
ScopingGoals, page structure and decisions to sign off
ContentWho writes, translates, picks the images and puts the text in
DesignPages or templates designed, mobile versions and feedback rounds included
DevelopmentFeatures delivered and the parts you can edit yourself
MigrationContent, media, URLs and redirects carried over
ConnectionsData sent, recipients and error handling
DeliveryTesting, training, access and acceptance conditions
Follow-upMaintenance, response times and excluded work

Get both proposals to answer the same questions. Add the costs left to you before comparing the totals.

A three-column table makes them easier to read: the item, the first quote’s answer, the second quote’s answer. An empty cell marks a question to ask. A quote can look cheap because it leaves out the migration, the form rules or the account set-up.

The warning signs in a quote

  • The domain name or the hosting will be registered in the provider’s name.
  • The quote fits on one line, with no list of pages or features.
  • The number of design feedback rounds isn’t stated.
  • Maintenance comes down to “support included”, with no tasks or response times.
  • No acceptance condition says when the site counts as delivered.
  • The access handed over at the end of the project isn’t listed.

One of these points on its own doesn’t rule out an offer. Ask the question in writing and keep the answer with the quote: it becomes part of the commitment.

For a B2B site, what does the provider need to understand?

A managing director, a buyer and an operations manager may look at different information before asking for a meeting. Choose the pages that answer the questions behind their decision: the service, how it works, proof and terms.

Ask the provider to show you how an enquiry reaches the salesperson. A CRM integration should specify the fields, who the enquiry is assigned to and how duplicates are handled. An email notification may be enough if the volume is low and the follow-up reliable.

Also choose the conversions your team can handle. A demo request has to reach the right person. A booking has to respect your real availability. A download is only worth having if it gives enough context to prepare a sales conversation. These choices change the forms, the notifications and the tracking, and so the quote.

If your teams need to track cases, manage permissions or handle internal data, the need goes beyond the public website. Have that tool priced separately, along with the link between the two.

The CRO guide helps you set the measures for enquiries and opportunities. Don’t ask for a sales guarantee: the site alone can’t deliver one.

How do you check references?

Look for a project that is comparable in how it’s used: languages, volume of content, publishing, a catalogue or a connection to a tool. Ask which tasks the provider carried out themselves and which results were measured.

The Nallian case study, for example, shows a B2B redesign and an admin area for the marketing team. The screenshots and testimonials let you examine the work. A rise in sales is proven with sales data; a technical performance figure only describes the site.

If you can, call a client listed as a reference. Ask how the delays, the scope changes and the first weeks after launch went.

Who will you work with?

Get the provider to name your contact, the people doing the work and the person responsible for technical decisions. Ask how often you’ll meet, which channel to use for feedback and how available they’ll be after delivery.

The set-up has to fit your publishing workload and your support requirements. On my projects, I am your contact for setting priorities. My website creation packages list the deliverables and the starting price of each format. The quote states the work committed and who is responsible for what: rely on that written scope, whatever job title is on display.

On your side, appoint the person who signs off. Have the consequences of late content, or of a new feature requested mid-project, written down.

How a project runs, step by step

Ask for a timeline by stage, with what you need to supply at each one:

  1. A first conversation about your business, your goals and the current site.
  2. Scoping: the extent of the work, the content, the journeys and the constraints.
  3. A detailed proposal with deliverables, price, indicative timeline and maintenance.
  4. Design of the site structure, the journeys and the interface.
  5. Development, content integration and set-up of the features.
  6. Acceptance testing, planned fixes and launch preparation.
  7. Deployment, checks and the start of follow-up.

The real timeline depends on the number of pages, the integrations, when the content is ready and how quickly you sign things off. Homepage copy delivered three weeks late pushes the launch back by the same three weeks. Group your feedback and give the final decision to one person.

What budget should you compare?

Separate the initial build from the costs of licences, hosting, maintenance and enhancements. Ask for taxes, deposits, invoicing stages and exclusions to be spelled out.

If your priorities change every month, compare a one-off project with monthly support. Check the capacity reserved, the deliverables and the exit terms. A monthly fee covers a limited volume of requests.

Compare costs over the same period, three years for example, by adding up the build, hosting, licences and maintenance. If your place of business is in Brussels, the Prime Digitalisation can reduce the cost of the build, provided you apply before the work starts. In Wallonia, the Digit Online loan funds the investment through credit.

Technology and independence: ask for a demo

Have the person who will publish edit a page, an image and a form. Check which tasks they can do alone and which need someone to step in.

Your needCriteria to compare
Brochure siteEditorial independence, speed, forms and room to grow
Frequent contentPublishing workflow, access rights and how simple the CMS is
Catalogue or B2BFilters, contact enquiries, product data and integrations
EcommercePayment, orders, security, delivery and maintenance
Business featureSpecifications, external connections, testing and code ownership

The WordPress and Astro comparison covers the editing and maintenance questions. The provider should justify the solution by how you’ll use it, and show how you’ll get your content and code back if you change team.

What maintenance should you have priced?

Technical maintenance covers updates, backups, monitoring, security and fixing outages. Get it in writing: how often backups run, who tests restoring them, and the response time for an outage or a routine request.

Adding a page, reworking a journey or producing content belongs on a different budget line. Keep maintenance, enhancements and editorial work separate in the contract. You’ll then know which requests are covered and which will get their own quote.

The points to lock down before you sign

Identify the accounts for the domain, the hosting, the CMS and analytics. Specify your access rights, the backups and the deliverables you can take with you when the contract ends.

Have the transfer of rights to the code, the design and the copy produced for you written into the contract, with the date it takes effect. If the provider hosts the site or receives your form data, they process personal data on your behalf: Article 28 of the GDPR then requires a data processing agreement.

Attach an acceptance checklist: pages and translations, mobile, forms received, redirects, metadata and training. Distinguish between fixing a defect, a new request and recurring maintenance.

To ask for a quote, provide your brief, an example customer enquiry and the content you have. You’ll then be comparing concrete commitments. If you’re replacing an existing site, the free audit identifies its main blockers before you write the brief.

Frequently asked questions

Agency or freelancer: how do you choose?

Compare the written commitments. An agency often splits strategy, design and development across several people; a freelancer does a larger share of the work themselves. In both cases, check who answers your questions, who builds the site and who handles follow-up after launch.

How long does it take to build a website?

It depends on the scope. Ask for a timeline by stage, with the content and sign-offs expected from you, and ask what happens to the schedule if you run late.

Do you have to pay a deposit?

The quote states it. Tie each payment to an identifiable deliverable, such as sign-off of the mock-up or the launch, and ask which amounts are due if the project stops partway through.

Who owns the website at the end of the project?

The contract should say. Have it set out the transfer of rights, the list of access handed over and the format in which you’ll get the code and content back.