How to Quote a Web Design Project
How to quote a web design project starts before any number is written down. A web design quote is a written estimate of the time, components, and cost required to take a project from brief to launch. Getting it right means completing a discovery call, breaking the project into its real parts, estimating hours from first principles, and presenting the number with clear scope boundaries. A quote that omits any of these steps tends to underdeliver at the same price.
Before you write a number: the discovery call
Most web design quotes that go wrong were written without enough information. A discovery conversation before quoting is not optional — it's what separates an accurate estimate from a guess with a logo on it.
The objective. What does this site need to do? Sell a product, generate leads, support a rebrand, replace an outdated site? The goal determines the complexity.
The scope. How many pages? How many distinct templates? Is there a blog, a shop, a booking system, an integration? Each adds to the estimate separately.
The content situation. Who is producing the copy, photography, and assets? If the client says "we'll handle it," build a content milestone into the project timeline — and a clause for what happens if it's late.
Third-party dependencies. CMS, payment provider, CRM integration, booking system — every external platform is a potential unknown. List them explicitly.
The revision expectation. A client who expects unlimited rounds of design revisions and one who expects two rounds are not the same project. State the rounds included in your quote.
The timeline. Artificial deadlines compress the schedule and your ability to correct mistakes. Urgency should reflect in the quote.
Breaking the project into billable components
Web projects contain more distinct phases than "design and build." Quote each separately — not because every client sees the itemisation, but because you need the breakdown to estimate accurately.
| Component | What it includes |
|---|---|
| Discovery & scoping | Client kickoff, sitemap, content audit, brief sign-off |
| Information architecture | Page structure, navigation, wireframes |
| Design concepts | Homepage concepts, style direction, revisions |
| Page design | Remaining templates, responsive states |
| Development | CMS setup, template build, functionality, integrations |
| Content migration | Moving or reformatting existing content into the new structure |
| QA & testing | Cross-browser, device, form, and performance checks |
| Launch | DNS cutover, redirects, GSC + analytics wiring |
| Post-launch support | Defined window of fixes included (e.g. two weeks) |
The components that most commonly get under-quoted: content migration, QA (should be 10–15% of development hours), and coordination overhead.
Estimating hours honestly
The most accurate estimates come from past similar projects. Start there.
Anchor on comparable work. Look at the last three projects similar in scope. What did they actually take — not the estimate, the real hours? That's your anchor.
Adjust for project-specific variables. Add time for new clients with unknown feedback style (+10–15% coordination buffer), complex CMS or custom integrations (+25–50% on development), content-heavy sites where the client is supplying copy, data or content migration, and short timelines that compress QA.
State your buffers explicitly. Don't hedge by inflating the hourly rate — inflate the hours, visibly. "12 hours development, 3 hours QA, 2 hours coordination" is more honest and more defensible than "17 hours" as a single line.
Build a revision allowance. State how many rounds of design revisions are included, what a round means (one consolidated set of feedback, not one email), and what additional revisions cost.
Choosing a pricing structure
Fixed price is the default for web projects because it gives clients budget certainty. It requires an accurate scope. If the scope is unclear, a fixed price quote either undercharges (you absorb the overrun) or overcharges (you load in a large contingency). Only quote fixed price when you've done a proper discovery.
Hourly billing suits projects where the scope genuinely can't be fixed upfront — complex integrations, legacy systems, iterative UX work. Be explicit about the estimate range and how you report hours.
Phased billing with deposits reduces the risk of getting to 60% done and having the project stall. A typical structure: 30–40% on project start, 30% at design sign-off, remainder on launch. A deposit protects you if a client goes quiet.
For most standalone web design projects, a fixed price with phased milestones is the most common structure — clear for both sides, with built-in checkpoints. For the retainer vs hourly decision on ongoing work, see the retainer vs hourly pricing guide.
What a complete quote includes
A quote for a web design project should contain:
- A summary of the project — restating what you understood from the brief, so the client can confirm you've heard them correctly.
- Itemised scope — each component listed with its hours or fixed price contribution.
- What's explicitly excluded — anything not in scope should be stated, not implied. "Content copywriting," "SEO optimisation," "ongoing hosting" are common exclusions that become disputes when unstated.
- Revision rounds included — e.g. "two rounds of design revisions on the homepage concept." Extras available at $X/hour.
- Timeline — project phases and indicative dates, contingent on client sign-off and content delivery.
- Payment terms — deposit due at start, milestones, payment method, and late payment terms.
- Quote expiry — most web design quotes are valid for 30 days.
Common quoting mistakes
Treating content as the client's problem. Content delays are the most common reason web projects run late. Build a content delivery milestone into your timeline and make it explicit that your schedule is contingent on client delivery by that date.
Ignoring third-party platform risk. CRM integrations, payment gateways, and external APIs all have their own timelines and documentation quality. Confirm feasibility before quoting — not during build.
No deposit mechanism. Quoting for a web project without a deposit is lending the client your time. A 30–40% upfront deposit separates serious clients from tyre-kickers and protects you if the project stalls.
Discounting late to win the job. If you cut the quote to win the work, you've set the budget expectation for all future work with that client. Price accurately the first time.
Under-quoting post-launch support. A site that launches is not finished. Define what post-launch support is included and for how long.
Frequently asked questions
How do I quote a web design project?+
Complete a discovery call, break the project into its real components (discovery, design, development, QA, launch), estimate hours per phase using past projects as anchors, add explicit buffers for coordination and revisions, then apply your rate. Present the result with scope boundaries and payment terms.
How much should I charge for a web design project?+
Build from hours up rather than from a market average down. Estimate the realistic hours the project requires, multiply by your rate, and confirm the rate covers your fully-loaded costs.
Should I use fixed price or hourly for web design?+
Fixed price with phased billing is the most common structure for defined web projects. Use hourly when the scope genuinely can't be fixed — complex integrations, iterative UX, or legacy system work. Never quote fixed price on an ill-defined scope.
What should a web design quote include?+
A project summary confirming your understanding, itemised scope, explicit exclusions, revision rounds included, indicative timeline, payment terms, and an expiry date. The exclusions section is as important as the scope — it defines the boundary.
How do I estimate hours for a web design project?+
Start with your last 2–3 similar projects — what did they actually take? Adjust for this project's specific variables: new client, complex integrations, content migration, short timeline. Build in explicit buffers for coordination and QA rather than burying them in a contingency rate.
How many revision rounds should I include in a web design quote?+
Two rounds is the most common standard — one initial presentation and one round of consolidated changes. State clearly that a "round" means one set of consolidated feedback, not ongoing email chains. Additional rounds are available at your hourly rate.
What deposit should I ask for on a web design project?+
30–40% on project start is standard. It confirms the client's commitment, covers your initial costs, and creates a payment rhythm. Milestone billing — start, design sign-off, launch — distributes the remaining amount across the project lifecycle.
Quote accurately, then invoice from the same source.
Ascend tracks time against each project as the work happens. At billing time, those entries generate the invoice — the quote-to-invoice cycle stays in one place rather than scattered across spreadsheets and separate billing tools. The free tier covers one client end to end.