Website design quote: how to price and write one (with example)

A good website design quote starts with a short discovery conversation, then breaks the project into clear phases: discovery and strategy, design, development, content, SEO basics and launch, with hosting and maintenance as a separate recurring item. Each phase gets its own line items with quantities, prices and what is included, followed by the number of revision rounds, a payment schedule and a validity date. Offering two or three packages instead of one price makes it easier for the client to say yes.

This guide walks through each step: what to ask before you price anything, how to choose a pricing method, how to structure the quote, and a worked example for a small business website. Whether you are a solo designer or a small studio, the same structure applies. If you want a general checklist first, see what to include in a quote.

Gather requirements before you quote

Most website projects that go over budget were underquoted, not badly executed. The cause is usually a missing question at the start: nobody asked who writes the copy, how many languages the site needs or whether the booking system has to talk to an existing tool. A twenty-minute discovery call, or a short questionnaire, saves you from guessing.

Discovery questions to ask

• Goals: what should the website achieve? More enquiries, online bookings, sales, recruitment, credibility?
• Audience: who visits the site and what do they need to find quickly?
• Pages and structure: roughly how many pages, and which ones are unique layouts versus repeats of the same template?
• Content: who writes the copy and supplies the photos? Is existing content being migrated, and how much?
• Functionality: contact forms, a blog, bookings, a shop, a members area, integrations with tools they already use?
• Languages: one language or several? Multilingual sites add design, build and content work.
• Branding: is there a logo and style guide, or does that need to be created first?
• Platform: does the client have a preferred CMS or need to edit the site themselves?
• Timeline: is there a hard deadline, such as a launch event or campaign?
• Budget: is there a range they have in mind? Asking openly saves you from designing a package nobody can afford.
• Decision-makers: who approves the design, and who signs the quote?

Choose a pricing approach

There is no single correct way to price a website. Most designers and agencies use one of four approaches, or a mix of them.

For a small business website, a fixed price built from clear line items is often the easiest for the client to approve: they know what they will pay, and they can see where the money goes. Behind the scenes you can still calculate each line from an estimate of days at your rate. Just remember to add a buffer for project management, meetings and feedback rounds, which are easy to forget and rarely small.

Structure the quote by phase

Break the project into phases that match how you actually work. Clients trust prices they can follow, and separate lines let them adjust the scope instead of asking for a discount on the total.

1. 1Discovery and strategy: kick-off workshop, goals, sitemap, page structure and, if needed, wireframes.
2. 2Design: visual design of the homepage and each unique page template, for desktop and mobile, with a fixed number of revision rounds.
3. 3Development: building the templates in the chosen CMS, responsive behaviour, forms, and any specific functionality such as a blog or booking tool.
4. 4Content: entering or migrating content, and copywriting or photography if you offer it. Be explicit when content is the client's responsibility.
5. 5SEO basics: page titles and meta descriptions, clean URLs, redirects from the old site, basic performance checks and submitting a sitemap. Keep the wording modest; this is a foundation, not an ongoing SEO campaign.
6. 6Launch: testing across browsers and devices, going live, and a short training session so the client can update the site.
7. 7Hosting and maintenance: a recurring monthly or yearly item for hosting, updates, backups and small changes. Keep it separate from the one-off project price.

offinal.com/q/7hX2kP

UX & visual design€2,400

Wireframes, prototypes and a complete design system.

Development€4,800

Responsive build, CMS setup and performance tuning.

Launch & training€900

Go-live support and a hands-on team workshop.

In a PDF there is a constant trade-off between detail and readability. With interactive line items you can keep the overview short and let the client open the full description, a screenshot of a previous design or a sample wireframe for each line.

A worked example: small business website

Here is an example quote for a local physiotherapy practice that wants a new website with about eight pages, a contact form and a simple blog. The client supplies the copy and photos. The prices below are an illustration of the structure only, not market data. Rates vary widely by country, experience and type of client, so use your own numbers.

A few things make this example work. The design and development lines are counted per template, not per page, so the client understands why eight pages do not cost eight times as much. The revision rounds are written into the line item itself. Copywriting is not on the list, and the assumption that the client supplies content is stated. Hosting is shown separately as a recurring option, so it does not inflate the project price and the client can choose it or not. The VAT rate is an example for a Belgian business client; apply the rate and treatment that fit your situation.

Offer three packages instead of one price

A single price invites a yes-or-no decision. Three packages turn it into a choice between options, which is a much easier conversation. For the example above, the packages could look like this:

• Essential: up to five pages on two templates, contact form, SEO basics, one revision round.
• Standard: the full quote above, with the blog, four templates and two revision rounds.
• Complete: everything in Standard plus copywriting for the main pages, a second language and three months of maintenance included.

Make the middle package the one you would recommend, and make the differences easy to see. Our guide to good-better-best pricing explains how to design the tiers so they help the client decide rather than confuse them. With interactive pricing, the client can pick a package and tick optional extras such as maintenance or an extra language, and the total updates as they go.

Handle revisions and scope creep

Website projects are especially prone to scope creep, because clients often only realise what they want once they see the first design. That is normal. The quote should simply make clear what happens when it occurs.

• Set the number of revision rounds per design phase, typically two, and define a round: one consolidated set of feedback, not a stream of separate emails.
• Define what counts as a change request. New pages, new functionality or a change of direction after design sign-off are outside the agreed scope.
• Price extra work in advance. State your rate for additional revision rounds or extra pages, for example as an hourly or day rate, so there is no negotiation later.
• Use sign-off points. Ask for written approval of the sitemap and the designs before development starts. Changing a design in Figma is cheap; changing it after it has been built is not.
• Quote changes separately. When the client asks for something new, send a short additional quote rather than absorbing it.

Set a payment schedule

For a project that takes weeks or months, waiting until launch to be paid puts all the risk on you. A milestone-based schedule is common and easy to explain:

Some designers ask for 50% upfront, others split the payment into more steps on larger projects. Whatever you choose, link each payment to a milestone the client can recognise and state the payment period on your invoices. Add a line about what happens if the project stalls on the client's side, for example invoicing the next milestone after a set number of weeks without feedback. These are commercial choices, not legal requirements; check your own terms and conditions, and for anything specific to your country, ask your accountant or a legal adviser.

Send it so the client can choose and comment

A website quote rarely gets approved without questions. Can the blog be added later? Is the second language included in maintenance? If those questions travel by email, the answers get lost and the quote ends up in several versions.

Sending the quote as a link instead of a PDF keeps everything in one place. The client picks a package and options, and can use comments on the quote to ask about a specific line item. You reply and update the quote in the same thread, so everyone sees the latest version. When they are happy, they approve it online. Our guide on how to write a quote clients approve covers presentation and timing in more detail.

Offinal is built for exactly this kind of project-based quoting. See how it works for agencies and freelancers.