What does a website cost? It depends on what it must do, who supplies the content and how many features are needed. A useful quote separates what is included from what is not, and ties the price to a clear scope.

What determines the price

The price depends on five things: page complexity, content to produce, features, integrations and timeline. A brochure site and a portal with a customer area do not require the same work.

Quality counts too: photography, copy, structure and speed take time, and that time sits in the quote.

How many pages you actually need

Page count is a rough indicator. What matters is how many pages have a different job: home, service, case study, contact, privacy, blog.

Ten almost identical pages cost less than five pages with journeys, filters and custom content. The right question is what each page must do.

Content, photos and copy: what comes from you

If the copy is written and the photos are ready, the project starts ahead. If we have to write, photograph or organise scattered material, that work goes into the quote.

A site with client-supplied content still needs a review: who approves, by when and with how many rounds of changes.

Features that raise the quote

Customer area, e-commerce, bookings, multiple languages, integrations with a management system or CRM, internal search and special formats all add work. Each one should be judged on what it solves in the workflow.

Integrations are the least predictable item: they depend on APIs, permissions and the schedule of whoever runs the other system.

Why we do not publish a price list

The same site can require very different scopes. The quote we prepare starts from an analysis of the scope; a fixed price without it forces you to cut features or ask for extras during the project.

The quote arrives within 48 hours of first contact, after two or three useful questions. It states what is included, what is not and how many revision rounds are covered.

How to read a quote: scope, exclusions, timelines

Read each line: pages, features, content, integrations, training, support. Check the exclusions and the conditions for changes.

Ask about timelines and dependencies: what you need to provide, what can delay delivery and what happens if content arrives late. Typical timelines are about 10 days for a landing page, 3 to 4 weeks for a business site, 6 to 10 weeks for an e-commerce store or an app.

What to ask before signing

Domain, hosting, code and access should belong to the company, and the contract should say how you can leave. Ask for examples of similar projects and check that they are still online.

Ask how support after launch works: who answers, how quickly and during which hours. Support stays available 365 days a year, holidays included; ordinary requests follow office hours, Monday to Friday, 9am to 7pm CET/CEST.

Three mistakes that inflate costs

Postponing content, changing the scope mid-project, choosing on the lowest price alone. The first stretches the timeline, the second blurs responsibilities, the third moves the cost later.

A clear quote makes risks visible and says how they are handled. If you want an opinion on your scope, email us: we reply within 24 working hours.

If you are deciding whether to rebuild or fix the current site, here are the signals to assess.