How to Price Web Design Projects (Without Losing Money)

A step-by-step guide to pricing web design projects — from estimating hours per phase to setting margin targets and avoiding the most common pricing mistakes.

Most agencies underprice web design projects. They estimate design and development hours, add a buffer, and call it a quote. What they forget: project management, revisions, QA, client communication, and content entry. The result? Projects that look profitable on paper but lose money in practice.

When you only price the visible work — the designs, the code, the launch — you're missing 30–40% of the actual effort. Status calls, feedback loops, content wrangling, and QA don't bill themselves. They either get absorbed as a loss or they get rushed, which hurts quality and client relationships.

The fix isn't working harder or cutting corners. It's building a pricing process that accounts for every phase of the project — including the invisible work that clients never see but that eats your margin. This guide walks you through that process with real numbers and a concrete example you can adapt for your next quote.

The Phase-by-Phase Breakdown

Every web design project has the same phases. The hours vary by scope and complexity, but the structure doesn't. Here's what to budget for each:

Discovery & strategy (8–16 hours)
Kickoff meetings, stakeholder interviews, competitive analysis, sitemap, content strategy, and technical requirements. Small sites need less; complex projects with multiple stakeholders need more. Don't skip discovery to save time — a poorly scoped project will cost you twice as much in revisions later. Budget 2–4 hours for kickoff and stakeholder alignment, 4–8 hours for research and sitemap, and 2–4 hours for technical requirements and content planning.

Design — wireframes + visual (20–40 hours)
Wireframes, visual design, component libraries, and design handoff. A 5-page brochure site might land at 20–25 hours; a 15-page site with custom templates can hit 40+. Factor in revision rounds: most clients need at least two rounds of feedback before sign-off.

Development (30–60 hours)
Front-end build, CMS setup, integrations, responsive implementation, and basic performance optimization. Custom functionality, animations, and third-party integrations add time quickly. If the client wants a custom contact form, newsletter integration, or CRM sync, add hours explicitly — don't assume it's "included." A simple 5-page static build might be 25–30 hours; add 10–15 hours for CMS setup and 5–10 hours per major integration.

Content entry & revisions (10–20 hours)
Client-provided content entry, copy edits, image optimization, and revision rounds. Most agencies underestimate this. Clients rarely deliver content on time or in the right format. Expect to chase copy, resize images, and reformat spreadsheets. Budget 2–4 hours per page for content entry and revisions on a typical project.

QA & launch (8–16 hours)
Cross-browser testing, mobile testing, accessibility checks, staging review, DNS/SSL, and go-live support. Don't skip this — launch-day issues are expensive. A broken form or broken layout on day one erodes trust and generates emergency support requests you didn't price for.

Project management (15–20% of total)
Status calls, email threads, feedback coordination, timeline management, and internal coordination. This isn't optional. Add 15–20% of your total project hours as PM overhead. If your project is 100 hours of execution work, plan for 15–20 hours of PM. Agencies that skip this end up with project managers working for free.

Worked Example: Pricing a 5-Page Business Website

Let's price a typical 5-page business website: Home, About, Services, Case Studies, Contact. No e-commerce, no complex integrations. Standard CMS (e.g., WordPress or custom), responsive design, basic contact form, and client-provided content.

Phase estimates:

Why these numbers? Discovery: 12 hours covers kickoff, stakeholder interviews, sitemap, and technical requirements. Design: 30 hours for wireframes, visual design, and two revision rounds. Development: 40 hours for build, CMS setup, responsive implementation, and basic testing. Content entry: 15 hours for chasing copy, formatting, and image optimization. QA: 10 hours for cross-browser testing, mobile check, and launch support. PM: 15% of 107 = 16 hours for status calls, email, and coordination.

Cost calculation:
Assume a blended team rate of $100/hour (designer + developer + PM, including overhead):

123 hours × $100/hour = $12,300 cost

Margin target:
If you want a 55% delivery margin (meaning 55% of the price is profit after delivery costs):

Price = Cost ÷ (1 − Margin)
Price = $12,300 ÷ (1 − 0.55)
Price = $12,300 ÷ 0.45
Price = $27,333

Round to $27,500 for a clean client-facing number. At that price, your cost is $12,300 and your profit is $15,200 — a 55% margin.

Optional scope buffer:
If you add a 15% buffer for scope creep and revision overruns:

$27,500 × 1.15 = $31,625 → round to $31,500

Use the buffer when you're uncertain about scope or working with a client who tends to request changes. For a well-scoped project with a clear scope document, the base price may be sufficient.

What if your blended rate is higher? At $125/hour, cost = $15,375. At 55% margin: $15,375 ÷ 0.45 = $34,167 → round to $34,500. At $150/hour, cost = $18,450. At 55% margin: $18,450 ÷ 0.45 = $41,000. Adjust the numbers to match your actual team costs.

Presenting the price: Tie the quote to a detailed scope document. List every page, every deliverable, and every phase. When the client sees "$27,500" next to "5-page website with discovery, design, development, content entry, QA, and launch," they understand what they're paying for. Vague quotes invite scope creep; detailed scopes protect your margin.

The 5 Most Common Pricing Mistakes

1. Not charging for project management time
PM isn't free. Status calls, email, feedback loops, and coordination add up. A typical 100-hour project might require 15–20 hours of PM — status calls, email threads, feedback collection, timeline updates, and internal handoffs. Build 15–20% PM overhead into every estimate, or you'll absorb it as a loss. Project managers who work for free don't scale.

2. Giving unlimited revision rounds
"Two rounds of revisions" is standard. "Unlimited revisions" is a recipe for margin erosion. Clients who get unlimited revisions often request five or six rounds. Each round burns design and development time. Define rounds in the scope document — e.g., "Two rounds of revisions per page" — and charge for additional rounds via change orders. A third round might add 5–10 hours; price it and get approval before starting.

3. Underestimating content entry and QA
Clients rarely deliver content on time or in the right format. You'll chase copy, reformat Word docs, resize images, and fix broken links. Budget 10–20 hours for content entry, image optimization, and revision cycles. QA and launch support often take 8–16 hours — cross-browser testing, mobile checks, staging review, DNS/SSL, and go-live support. Don't skip them. Launch-day bugs are expensive and embarrassing.

4. Using your junior rate when seniors will do the work
If your senior designer and developer will do the work, use a blended rate that reflects their cost. A senior designer might cost $80/hour loaded; a junior might cost $45/hour. Bidding at junior rates while assigning senior staff guarantees a loss. Know your true blended rate (salary + benefits + overhead ÷ billable hours) and use it in every estimate.

5. Forgetting to scope what's excluded
List what's not included: ongoing maintenance, hosting, copywriting, photography, video, SEO, analytics setup, training beyond X hours. Explicit exclusions prevent scope creep and awkward conversations later. When a client asks for "just a quick SEO audit" or "can you add a video to the homepage?", you can point to the scope document and say, "That's outside scope — here's a change order." A simple "Excluded" section in your proposal saves countless hours of unpaid work.

How to Protect Your Margin After the Quote

Pricing correctly is half the battle. Protecting that margin during the project is the other half. Scope creep doesn't announce itself — it arrives as "just one more thing" and "can you also…" requests. Here's how to defend your margin:

Change orders:
Any work outside the original scope gets a change order. Define the process in your contract: client approves in writing, you add the hours and cost, then proceed. No "quick tweaks" without documentation. A change order doesn't have to be formal — an email with "Per our call, adding 8 hours for the newsletter integration at $100/hour = $800. Proceeding upon your confirmation." is enough. The key is written approval before you do the work.

Weekly time reviews:
Compare actual hours to your estimate each week. If you're burning through discovery or design faster than planned, flag it early. Maybe the client added stakeholders, or the content strategy is more complex than expected. Adjust scope or communicate with the client before you're 20 hours over. "We're 5 hours over on discovery — here's what we've learned and what we recommend" is easier than "We're 20 hours over and need to discuss scope."

Milestone billing:
Bill at key milestones (e.g., 30% at kickoff, 40% at design approval, 30% at launch) instead of one lump sum at the end. This improves cash flow and surfaces scope issues earlier. If the client balks at a milestone payment, that's a signal. If they keep requesting changes before design approval, you can pause and discuss scope before burning more development hours.

Track actual vs. estimated: After each project, compare your estimate to actual hours. Did discovery run over? Did content entry take twice as long? Use that data to refine your next estimate. Over time, your estimates will get more accurate and your margins will hold. Tools like Corcava's project profitability reports make it easy to see estimated vs. actual hours by phase, so you can spot patterns and adjust your pricing templates.

This pricing process fits into the complete agency profitability guide. Use our project scope template to document what's included. Check your numbers with the project profitability calculator. And track hours per phase with the billable hours calculator.