How much does a website cost in 2026, and what determines the price?

The question “how much does a website cost?” becomes useful when you describe what it needs to do for the business. A brochure website, a catalogue with quotation requests and a booking platform have different requirements, even if they initially look similar. Before asking for a price, write down who will use it, what information they need and what action they should be able to complete without help.

Turn the goal into a practical journey: the visitor finds the right service, understands the offer and submits an enquiry. For each step, identify the necessary information and features. This helps separate essential elements from ideas that can wait for a later phase.

Prepare a short brief covering your audience, goals, estimated structure, languages and examples of visual preferences. State who approves the project and who supplies the materials. A clear brief does not guarantee a low price, but it reduces assumptions and makes proposals easier to compare. Ask the supplier to explain what is included and excluded, rather than simply providing a total.

Page count matters, but it does not describe the effort on its own. A page built from an existing template differs from one with a specially designed structure, illustrations and interactions. Likewise, a simple form does not involve the same work as a process that checks availability, calculates a quotation and sends information to other applications.

Content also affects the budget. Copy, photographs, translations and information organisation need to be prepared, reviewed and added to the website. Missing materials or changes after design approval can lead to rework. Establish early whether the proposal includes copywriting, image selection and content entry, or only the technical tools to support them.

Integration with payments, inventory management, bookings or a customer relationship management system adds external dependencies. Ask for the documentation and available access to be checked before estimating. Also ask about mobile display, accessibility, performance and testing. These should not be treated as mere visual effects, but as verifiable requirements suited to the project’s purpose. A good proposal describes the expected outcome, not just the technologies used.

A website’s budget does not end at publication. The domain, hosting, licences and external services may carry recurring costs. Maintenance adds updates, checks, backups and intervention when problems occur. Request separate lists for initial expenses, periodic charges and work billed separately.

Check exactly what the proposed maintenance means. Does it include technical updates only, or content changes as well? Who checks that forms are working? Is there a procedure for restoring backups? What happens when an extension is no longer compatible? The answers should be clear before you sign the contract.

Clarify control over resources too. The domain, important accounts and administrative access should be managed under an explicit agreement. Ask how you receive your data and materials if you change suppliers. A seemingly convenient solution can become difficult to manage if every change depends on one partner. Evaluate the total cost of ownership and the internal effort required, not just the starting amount. Keep a contingency for justified adjustments after launch as well.

Two proposals are comparable only if they cover roughly the same need. Create a table covering the website structure, features, included content, integrations, testing, training and post-launch support. Mark assumptions and optional items separately. If a supplier leaves an important point unclear, ask for clarification before choosing.

Set acceptance criteria you can verify: forms send messages to the correct recipients, essential pages work on mobile, editors can update the agreed information, and measurement respects applicable consent choices. Define approval stages and how additional requests will be estimated. This prevents changes from being confused with obligations already included.

If the budget is limited, reduce the scope of the first version, not the clarity of the requirements. You can launch a useful core and add features after observing actual needs. Choose the proposal that best explains what you receive, what your responsibilities are and how the result will be maintained. The right price relates to clearly defined work, not a vague promise of a “complete” website.