Web Design Quote Template: How to Price Any Website Project

Web design projects are notoriously hard to quote. The scope can range from a $500 template installation to a $50,000 custom application, and clients often have no frame of reference for where their project falls. Vague estimates — or estimates with a single lump-sum number — lead to scope disputes, underpayment, and clients who feel they were misled.

The solution is a detailed, itemized quote that separates each phase of the project and makes the scope explicit. This guide covers every line item a web design estimate should include, realistic pricing ranges, a sample estimate for a five-page business website, and the mistakes that kill web design projects before they start.

---

Line Items Every Web Design Estimate Needs

Not every project requires every item on this list — but you should consciously decide what to include or exclude, not discover missing scope mid-project.

Discovery and Research

This phase covers initial client interviews, competitor analysis, sitemap planning, and content audit if the client has an existing site. Discovery is where you define what you are actually building. It is a billable service and should appear on the estimate.

Typical range: $300–$1,500 depending on project complexity and number of stakeholders.

Wireframes and UX Planning

Wireframes define page layouts and user flows before any visual design work begins. They are the architectural drawings of the website. Skipping this step leads to expensive revisions in the design phase.

Typical range: $200–$1,000 per page or $500–$3,000 for a full site wireframe package.

UI Design

The visual layer: color, typography, imagery, iconography, and the actual look of every page template. Quote this per unique page template, not per total page count. A site with 10 pages but only 3 unique layouts should be quoted on the 3 layouts.

Typical range: $300–$1,500 per unique page template.

Development

Front-end development (HTML/CSS/JavaScript), CMS integration, and back-end functionality (forms, e-commerce, memberships, APIs). Development is typically the largest line item on any web project.

Break development into sub-items where possible: theme customization, custom functionality, third-party integrations, and CMS configuration are all separately quotable.

Typical range: $1,500–$15,000+ depending on complexity.

Content Migration

If the client has existing content — blog posts, product pages, team bios — moving it to the new site takes time. Clients consistently underestimate this, which means you will either absorb the labor or have a conversation after signing that you would rather have before.

Typical range: $100–$500 for small sites; $500–$2,000 for large content libraries.

Testing and Quality Assurance

Cross-browser testing, mobile responsiveness checks, form testing, speed optimization, and accessibility review. QA is not optional. Include it as a line item so it is not compressed when the project runs behind schedule.

Typical range: $200–$800 depending on site complexity.

Hosting Setup and Launch

Domain configuration, DNS setup, SSL certificate, hosting environment configuration, and go-live deployment. Even if the client manages their own hosting account, your time to configure and launch is billable.

Typical range: $150–$500.

Post-Launch Support

A defined period of warranty support after launch — typically 30 days. Specify what is covered (bug fixes, minor adjustments) and what is not (new features, content changes, training hours beyond scope).

Typical range: $200–$600 for a 30-day support period.

Training

If you are handing a CMS-based site to a non-technical client, they need to know how to update it. Quote training separately — it prevents the situation where a "quick explanation" turns into a three-hour screen-share session you did not charge for.

Typical range: $100–$300 per hour; most clients need 1–3 hours.

---

Sample Estimate: 5-Page Business Website

This is a realistic breakdown for a professionally designed five-page business website with a CMS (such as WordPress, Webflow, or Squarespace) for a small service business. The project includes the following pages: Home, About, Services, Blog, and Contact.

Line Item	Description	Price
Discovery and Research	Client intake session, competitor review, sitemap	$500
Wireframes	Low-fidelity wireframes for 3 unique page layouts	$600
UI Design	Visual design for 3 page templates + mobile versions	$1,800
Development	CMS setup, theme customization, responsive build, contact form, blog	$2,400
Content Migration	Copywriting provided by client; designer formats and places content	$300
Testing and QA	Cross-browser, mobile, forms, and speed testing	$400
Hosting Setup and Launch	DNS configuration, SSL, go-live deployment	$200
Post-Launch Support	30-day bug fix warranty	$300
Total		$6,500

Deposit required: 50% ($3,250) before work begins
Balance due: Upon launch
Revision rounds included: 2 per design phase
Estimate valid for: 30 days

This falls in the lower-mid range for a professionally built five-page site. Entry-level web designers working from templates might quote $1,500–$3,000. Senior designers or agencies working with custom code and advanced UX would be in the $8,000–$20,000 range for the same scope.

---

Realistic Pricing Ranges for Common Web Design Deliverables

Use these as benchmarks when you are building a new estimate from scratch.

Deliverable	Low End	Mid Range	High End
5-page brochure site	$2,000	$5,000	$10,000
E-commerce site (under 50 products)	$3,500	$8,000	$20,000
Portfolio site (designer/photographer)	$1,500	$3,500	$7,000
Landing page (single page)	$500	$1,500	$4,000
Website redesign (existing site)	$2,500	$6,000	$15,000
Custom web application	$10,000	$30,000	$100,000+
Monthly maintenance retainer	$150	$350	$750

These ranges reflect freelancer and small agency pricing in the U.S. market. Geographic location, designer experience, and whether the project involves custom code vs. template customization all influence where a project lands.

---

Common Web Design Pricing Mistakes

Quoting a single number

A project-wide lump sum gives you no protection when scope changes — and scope always changes. If you quoted $5,000 total and the client asks for an additional page, a new feature, and two extra rounds of revisions, you have no baseline to reference. Itemized quotes make change orders natural and defensible.

Not separating design from development

Designers who build as well as design often quote the whole project as a single service. This makes it impossible to explain to a client why two comparable-looking sites have very different prices — because the complexity is in the development, not the design.

Ignoring content

"Client provides all content" is not a plan. Content delays are the single most common reason web projects run over schedule. Even if you are not writing content, include a content delivery deadline in your timeline and note that launch dates will shift if content arrives late.

Underpricing revisions

If your estimate says "revisions included" without specifying how many and what counts as a revision, you will give away significant time. Two rounds of revisions on a page design is standard. State it explicitly.

No late delivery clause

Projects slip, often due to the client. Include language in your estimate stating that delays caused by late client feedback or missing content may result in revised delivery dates and, in some cases, revised pricing.

Pricing to win instead of pricing to profit

Cutting your estimate to beat a competitor's price works once. It sets an expectation for future projects, creates a client relationship built on a race to the bottom, and leaves you resentful of the work. Price what the project is worth and let the estimate quality do the persuasion.

---

Building and Sending the Estimate

Once you have your line items defined, the delivery format matters. A well-structured estimate sent as a professional link — not a Word attachment — positions you as someone who runs a real business.

EstimateForge lets you build web design quotes with line items, automatic totals, and your branding, then send them as a trackable link so you know when the client has viewed the estimate. That visibility changes how and when you follow up.

For a broader look at how to structure the quoting process from first contact through approval, see the estimate template overview and the freelance rates by industry guide for context on where your pricing stands in the market.

---

How to Scope a Web Project Before Writing the Estimate

The estimate is only as accurate as the discovery conversation that preceded it. If you write a quote before understanding the project, you will either overbid on simple work or underbid on work that turns out to be complex.

Before you open your estimate template, get clear answers to these questions:

What is the site's primary goal? A brochure site that drives phone calls has different design priorities than an e-commerce site that converts visitors to buyers. The goal shapes every decision about functionality, copy, and design complexity.

Who is building the content? This is where most estimates go wrong. If the client is providing all copy and images, set explicit deadlines for delivery — and include a clause that launch dates shift when content arrives late. If you are writing copy or sourcing photography, those services need to appear on the estimate.

What platform? WordPress, Webflow, Squarespace, Shopify, and custom-coded sites each have different development costs and long-term maintenance implications. Establish the platform before quoting. Switching platforms after the project starts is expensive.

What integrations are required? Booking systems, CRM connections, email marketing integrations, payment gateways, and third-party tools all add development time. Clients often mention these as afterthoughts: "Oh, and it needs to connect to our booking software." Catch this in discovery, not in week three of development.

What is the deadline? Rush projects cost more. If the client needs the site live in three weeks, that timeline affects your scheduling, potentially requires overtime, and may limit how much QA testing is realistic. Price the timeline, not just the scope.

---

How to Handle Scope Changes on Web Design Projects

Scope changes are inevitable. A client approves the wireframes, then decides they need a fifth page template. Another asks for an e-commerce shop two weeks into a brochure site build. How you handle these requests determines your profitability on the project.

Establish a change order process in the estimate. Your terms section should state that any work outside the defined scope will be quoted separately as a change order before it begins. This sentence prevents the "I thought that was included" conversation.

Price change orders at a premium rate. Changes mid-project are more expensive than work quoted upfront because they disrupt the workflow, require rework of completed elements, and compress the remaining timeline. Charge accordingly — typically 10–25% above your standard rate for mid-project additions.

Get change orders in writing. An email confirmation is fine for small additions. For anything over a few hundred dollars, a short written change order with the scope and price restates what was agreed.

Distinguish between revisions and scope changes. Two rounds of design revisions are included in your estimate. A revision is a change to something within the defined scope. A scope change is adding something new. Keep that distinction clear and refer to it consistently.

---

Structuring Payment for Web Projects

Payment structure matters for cash flow and for project dynamics. The way you stage payments affects both your financial exposure and the client's incentive to stay engaged.

Standard three-payment structure:

• 50% deposit before work begins
• 25% at a mid-project milestone (design approval or development handoff)
• 25% upon launch

Two-payment structure (for smaller projects):

• 50% deposit before work begins
• 50% upon completion

Monthly billing (for large or long-running projects):

• Monthly invoices based on work completed, with a deposit covering the first month

The deposit is non-negotiable for any significant project. It covers your initial discovery and design time, which cannot be recovered if the client changes their mind. Always state in the estimate that work does not begin until the deposit is received.

For clients who push back on deposits, explain the business reason: you are committing your schedule and beginning work on their behalf. A deposit confirms their commitment to the project. Any client unwilling to put down a deposit before you start a multi-thousand-dollar project is a risk worth pausing on.

For projects where you want momentum at the point of approval, look for tools that connect estimate delivery with a clear payment step so the client can confirm and pay in a single flow.

---

Web Design Estimate FAQ

Should I include hosting costs in the estimate? Hosting is typically the client's ongoing expense, not yours. Include your one-time setup fee for configuring hosting, but bill the monthly or annual hosting cost to the client's own account. This avoids the situation where you are perpetually responsible for a client's server costs.

How do I quote for an unknown content volume? Cap it. State clearly: "The estimate covers up to X pages of content input. Additional pages or content beyond this scope will be quoted as a change order." This protects you from a client who hands you 200 blog posts to migrate when you quoted 20.

What if the client asks for a fixed-price quote but the scope is unclear? You have two options: complete discovery first (charge for it) to define scope clearly enough for a fixed price, or provide a range estimate with a clear note that the final price depends on decisions made during the project. Avoid giving a fixed price before scope is clear — you will regret it.

How long should a web design estimate remain valid? For most web projects, 30 days is standard. If the client has not responded within 30 days, your schedule and pricing may have changed. Resend a revised estimate rather than honoring an outdated one automatically.