A good web design quote should clearly define what is being built, what the client needs to provide, the project price, recurring costs, revisions, timeline, ownership, domain/hosting arrangements, launch work and important exclusions.
A quote exists to remove ambiguity.
It does not need to predict every conversation in the project.
It should make it difficult for either side to say:
I assumed that was included.
The project objective
A useful quote can begin with a short description of the goal.
For example:
Design and build a new five-page website for a Longford bookkeeping practice, focused on improving credibility and generating consultation enquiries.
That gives context.
The site is not merely five URLs.
It has a business job.
The pages
List them.
Home.
Services.
About.
Work.
Contact.
If service subpages are included, say how many.
If the final architecture may change during discovery, explain the allowance.
"Up to six standard content pages" can be perfectly reasonable.
The important thing is that scope is measurable.
Design scope
Is the design custom?
Template-based?
Existing brand applied?
New visual direction?
How many concepts?
Is logo design included?
Typography?
Mobile design?
Do not assume "web design" includes a full branding project.
If it does, price and scope it.
Content responsibilities
Who writes the copy?
Client supplies finished text?
Designer shapes rough content?
Copywriter included?
How many pages?
Is proofreading included?
Does the client approve factual accuracy?
This is one of the biggest project-delay areas.
Put it in writing.
Photography and imagery
Who supplies images?
Are stock-image licences included?
Is professional photography separate?
Will existing client images be edited?
Are custom graphics included?
If the website depends on photography and nobody has any, discover that before design begins.
Functionality
Define the useful features.
Contact form.
WhatsApp link.
Booking integration.
Payment links.
Newsletter signup.
Map.
Blog.
CMS.
E-commerce.
Do not hide significant functionality behind:
standard features included.
"Standard" means different things to different people.
Third-party integrations
If the site connects to:
Calendly;
Stripe;
Mailchimp;
booking software;
CRM;
analytics;
explain what is included.
Usually the quote should also clarify whether the client pays the third-party subscription separately.
The developer cannot guarantee another company's future pricing.
Revisions
State the revision process.
Two design rounds?
Reasonable revisions within agreed scope?
Changes after sign-off billed separately?
There are several valid models.
The client needs to know the model.
Unlimited revisions can sound generous and create endless ambiguity.
Timeline
Give an estimated timeline.
Then explain dependencies.
Client feedback.
Content.
Photography.
Access.
Third parties.
A two-week build cannot finish in two weeks if the About copy arrives in month three.
The quote should set expectations on both sides.
Worth knowing
The headline build price is only one number. A useful quote should make the first-year and ongoing cost understandable enough that the client can compare two proposals without discovering later that hosting, licences, maintenance or support were treated as separate assumptions.
Price and payment schedule
Clear total.
VAT treatment where applicable.
Deposit.
Milestones.
Final payment.
Any cancellation terms.
Do not make the client reconstruct the total from six optional line items.
If optional extras exist, label them.
Domain
Is domain registration included?
Who pays renewal?
Whose account?
Who controls it?
Will the designer configure DNS?
These details are small until there is a dispute.
I prefer client-controlled domain ownership.
Hosting
What hosting arrangement?
How much?
Who pays?
What does the fee include?
Is it necessary?
Can the site move?
If the hosting cost is effectively zero under the chosen architecture, say that too.
A quote should not invent a hosting line item simply because website quotes traditionally have one.
Maintenance and support
What happens after launch?
Bug-fix period?
Content edits?
Ongoing plan?
Hourly support?
No required support?
If a monthly plan exists, explain it.
This is where hidden website costs often appear.
Ownership and licences
Who owns bespoke work?
What rights does the client receive?
What third-party licences remain?
Can the client move the site?
This does not need to become a copyright essay inside the quote.
It should be clear enough that the commercial expectation is understood.
SEO
Define what "SEO included" means.
Technical foundations?
Metadata?
Sitemap?
Search Console?
Keyword research?
Content strategy?
Ongoing optimisation?
Backlink work?
Do not use "SEO friendly" as a vague value-add.
Say what gets done.
Analytics
Will analytics be installed?
Who owns the account?
Is consent/cookie implementation included where required?
What will be measured?
A simple business site may only need a straightforward setup.
Still document it.
Launch
Does the quote include:
deployment;
domain connection;
SSL;
testing;
redirects;
Search Console submission;
sitemap;
form testing?
A website sitting on a staging URL is not launched.
Define the finish line.
Exclusions
This is one of the healthiest sections.
Not included:
logo design;
professional photography;
ongoing SEO;
e-commerce;
custom backend;
copywriting beyond agreed support.
Exclusions prevent scope creep and help the client compare quotes fairly.
A quote should not hide behind "bespoke"
"Bespoke" is sometimes used as an excuse not to give detail.
Every project varies.
The quote can still state what this particular project includes.
If everything is genuinely unknown, the provider may need a paid discovery phase before quoting the build.
That is more honest than a vague number.
My Built by Gavin quotes
I want a small-business client to be able to read the quote and understand:
what I am building;
what I need from them;
what it costs;
what it will cost later;
what they control;
what happens next.
The language should not require a procurement department.
Clarity is part of the service.
Gavin's take
A good quote is not impressive because it is twenty pages long. It is good because the client can tell what is being built, what they need to provide, what they own, what they will pay now and later, and where the boundaries are. Clarity protects both sides.
The bottom line
A web design quote should make the project legible.
Scope.
Pages.
Content.
Features.
Revisions.
Timeline.
Price.
Domain.
Hosting.
Ownership.
SEO.
Launch.
Support.
Exclusions.
If a meaningful part of the deal is missing, ask before paying.
Want to compare a quote with a simpler structure?
Send me the project details or look at my published service pricing.
The objective is not the shortest quote.
It is the fewest expensive surprises.
---