What should a business website quote include?

"How much does a website cost" only has an answer once the scope is known. The same figure can mean a template with three pages, and it can mean custom design, a content management system, several languages and integrations. So rather than hunting for an average price, it is more useful to prepare a comparison sheet: once every quote answers the same points, the numbers finally become comparable and the differences become explainable.

In short

• A price without a scope is not information. Align what each quote covers before you compare totals.
• The biggest differences usually come not from design but from content, the number of languages, integrations and how much you can edit yourself.
• Ownership and licensing belong in writing: who owns the domain, the code and the design, and what happens when the contract ends.
• Agree who writes the copy. Unsettled content is the most common reason a project stalls.
• Write acceptance in measurable terms. "Fast and SEO-friendly" is not a criterion; measurable figures are.

Why two quotes at the same price are not the same thing

The difference is usually not in the visible part but in what happens after launch. One quote may end with a delivered design and a few static pages that only its author can change. Another may include an editing system so you can change the copy yourself, several languages on their own URLs, and handover documentation. Both can be appropriate — but only one of them lets you work without calling the supplier for every sentence.

What a comparable quote has to cover

Use this as a sheet each supplier fills in. If a point is unanswered, that is your first question rather than a detail.

• The list of pages, and which are unique versus repetitions of one template.
• Languages: how many, who translates, whether each language has its own URL, and whether translation is in the price.
• Content management: which fields you will be able to edit yourself and which stay in the code.
• Design scope: custom or an adapted template, and how many review rounds are included.
• Responsiveness: which screen widths are checked, and whether keyboard and screen-reader use is tested.
• Integrations: forms, email delivery, analytics, payments, CRM or other systems — each as its own line.
• SEO foundations: URL structure, headings, metadata, sitemap, redirects from old addresses.
• Legal items: privacy policy, cookie consent, company details, consent records.
• Ownership and licensing: domain, hosting, code, design, fonts, photography.
• Acceptance criteria: what has to be true for the work to count as delivered.
• Handover: access, documentation, training, and what happens after the defect-fixing period.
• After launch: updates, backups, monitoring, and who is responsible for them.

What genuinely moves the price

• The number of unique templates. Ten pages on one template and ten different templates are different jobs.
• Content. If copy and images have to be created rather than migrated, that is separate work with its own deadlines.
• Languages. A second language is not just translation: it means separate URLs, separate metadata and twice the content upkeep.
• Editing freedom. The more fields you want to control yourself, the more has to be built and tested.
• Integrations with external systems. Every boundary between systems is something to build and test.
• Migration from an existing site. A URL inventory and redirects are separate, and routinely underestimated, work.
• Accessibility and performance requirements. If they are in the acceptance criteria they get planned for, rather than hoped for.

Ownership, licensing and editing

This part does not change the price, but it changes what you will be able to do in a year without asking permission. It helps if the quote states it briefly and unambiguously: the domain is registered in the company's name, the hosting account is yours, the code is handed over to you, and the licences for the fonts and images cover your intended use. If some part stays on the supplier's side that can be perfectly reasonable — what matters is that it is a decision rather than a surprise.

• Domain: registered in the company's name, with access held by you.
• Code and design files: what is handed over, and in what form.
• Fonts and images: the licence type, and whether it covers your use.
• Content management system: proprietary, open source or the supplier's — and whether you can move it.
• When the contract ends: what stays with you, and how quickly access is transferred.

Who writes the content

In practice this is the most common reason things stop. The design can be ready and the system working while launch waits because there is no copy. A quote should make clear whether text is migrated from the existing site, written fresh, or written by you. If you are writing it, agreeing a deadline and a delivery format helps — otherwise the deadline belongs to nobody.

How to describe acceptance measurably

"Modern, fast, SEO-friendly" is not a criterion, because it cannot be checked. Some figures can be. Google publishes the Core Web Vitals thresholds treated as good: LCP up to 2.5 seconds, INP up to 200 milliseconds and CLS up to 0.1. They are assessed on real user data at the 75th percentile, not from a single lab measurement. That is exactly why they are useful — you check a number rather than an impression. One caveat worth keeping: meeting those thresholds is not a promise about search positions. It is a quality criterion, not a ranking mechanism.

• Performance: the named Core Web Vitals thresholds, and on which pages they are checked.
• Accessibility: keyboard navigation, a visible focus state, text alternatives for images, sufficient contrast.
• Responsiveness: specific screen widths, not "works on mobile".
• SEO foundations: unique titles and descriptions, a working sitemap, accurate canonical URLs, redirects from old addresses.
• Forms: where the message arrives, what happens on failure, and whether consent is recorded.
• Legal items: the privacy policy and cookie consent behave as described.

An illustrative example

Illustrative scenario, not a description of a client project. A company receives two quotes at very similar totals. The first covers eight pages on one template, migrates the existing copy and ends at launch. The second covers four unique templates, an editing system for descriptions and prices, a second language on its own URLs, and redirects from the old addresses. The number is the same — but these are answers to two different questions. A comparison sheet shows that in minutes; without one, the difference surfaces after launch.

What this guide does not tell you

It contains no totals and no calculator. Any figure written here would be an assumption rather than an estimate: cost follows the scope, the state of your existing systems and how much content has to be created. Nor is it legal advice about licensing or contracts — ownership questions are worth checking with your own lawyer. Its purpose is different: to let you compare quotes against each other and understand what you are paying for.

Questions to ask before signing

• Which text and which fields will I be able to change myself, without a developer?
• How many unique templates are being built, and how many pages reuse them?
• What happens to the old URLs, and who prepares the redirect list?
• Who owns the domain, the code, the design and the font licences?
• Which measurable criteria have to be met for the work to be accepted?
• What happens after launch: updates, backups, and whose responsibility are they?

If you fill in just one part before the conversation — the list of pages and which fields you want to edit yourself — quotes become comparable immediately, and the conversation about price becomes a specific one.