What a website price actually covers

Two quotes for the same website can differ fourfold. The difference is almost never in how it looks — it is in the line items the cheaper quote simply does not have.

You get two quotes for the same website. One for three thousand, one for twelve. Both describe "a company website with a contact form", both have similar screenshots in the portfolio.

The difference is almost never in how it looks. It is in the line items the cheaper quote does not have — not because anyone is cheating, but because nobody asked about them.

What can be counted straight away

Visual design and coding are usually a third of the work. The rest spreads across things that only become visible after launch:

  • hosting and SSL certificate setup
  • backups, and a check that they can actually be restored from
  • a contact form with a consent mechanism that satisfies GDPR
  • language versions, if there are to be any
  • structured data and the link preview in messengers
  • speed and accessibility measured before publication, not after a complaint

None of these shows up in a screenshot. All of them show up in the bill if they have to be added later.

Three questions that separate the quotes

Whose name will the domain be registered in? If it is the contractor's, the site is not entirely yours, and you will find that out on the day you want to move it.

Will we get access to the code and to the server? "You will get an admin panel" is not an answer to that question.

What happens in a year? Updates, monitoring and support are separate work. It can be inside the implementation price, it can be a subscription, it can be absent entirely — but it has to be named before you sign.

When the cheap quote is fine

Often. A five-page business-card site with no integrations, no language versions, and copy you supply yourself really can cost three thousand and be well made.

The trouble starts when a cheap quote is the answer to expensive requirements. The difference does not disappear then. It only moves to later.

What we cannot check from the outside

Looking at somebody else's website, we can see how it is built technically: whether it loads fonts from external servers, whether it has a certificate, whether it responds quickly, what a search engine crawler sees in it. That does not need guessing — it is measured, and we measure it with a free scan.

What we cannot see is what was in the contract. Or how much of what is visible was built inside the price, and how much as fixes after the fact.

If you have two quotes in front of you and cannot tell where the difference comes from, the simplest thing you can do is ask both questions — about the domain and about the access. The answers usually explain the bill faster than the specification does.

Do you have the same problem?

Start with the free scan — it will show whether what is described above applies to your site. Or book a call and we will go through it together.