· 7 min read

Proposals & Quotes

How to Quote a Web Design Project Without Under- or Over-Bidding

Web design has the most unpredictable scope of any creative service. This step-by-step quoting process, with real time estimates by project type and the 8 questions to ask before naming a number, keeps you from eating overruns or losing deals to a high quote.

How to Quote a Web Design Project Without Under- or Over-Bidding

A web designer quotes a brochure site at $4,500 based on a one-paragraph email brief. She wins the project. Then the client mentions they need blog functionality, a client portal, three language versions, and wants all copy written by the designer. The original quote is now worth $4,500 for what’s actually a $22,000 project. She either eats the difference, blows up the relationship renegotiating, or delivers half the work and calls it done. The disaster started not when she said yes, but when she named a number before she understood the project.

Web design scope is uniquely unpredictable. Every project is custom. “Website” can mean five static pages or a full application stack. Getting the quote right requires a consistent pre-quote process, eight specific questions, before any number gets discussed.

Ask these 8 questions before you quote anything

Never quote a web project without clear answers to all eight. If a client won’t give you 20 minutes to answer them, that’s a signal about how they’ll behave when scope expands during the project.

1. How many pages, and what are they? “A website” is not a scope. “Homepage, About, Services (with 4 sub-pages), Contact, Blog with pagination” is. Get the full sitemap before quoting. Every unspecified page is a potential scope dispute.

2. Is there an existing site, or is this net new? A redesign is different from a greenfield build. Redesigns involve content migration, dealing with legacy code, matching (or improving) existing functionality. That’s typically 20–40% more time than a new build.

3. Does the client provide copy and images, or do you? Copywriting alone adds $2,000–$8,000 to a project. Photography sourcing or original photography adds more. These need to be explicit line items or explicit exclusions.

4. What functionality does the site need? Contact form, payment processing, membership/login, booking system, live chat integration, video hosting, search functionality, multilingual support, each one adds time. A contact form adds 2 hours. A membership portal with user accounts, subscription billing, and a dashboard adds 40–80 hours.

5. What platform or CMS? WordPress, Webflow, Squarespace, Shopify, custom React, each has a different development time profile. A Webflow brochure site takes a third of the time of the same project in custom React. Platform choice is the biggest single variable in development time.

6. Who handles hosting and domain setup? Some clients expect this in scope. Most shouldn’t, it’s a separate line item or explicitly excluded.

7. What does the revision process look like? How many people will be reviewing designs? Does the client have a legal or compliance team who reviews content? Does the CEO make final decisions on visuals? Multiple stakeholders with veto power is a major scope variable. A single decision-maker takes one revision round. Four stakeholders with conflicting opinions can take six.

8. What’s the timeline? Rush projects, anything with less than 6 weeks for a brochure site, less than 12 weeks for a complex site, require rush pricing. Rushed timelines compress your ability to manage workload, require faster client turnaround on feedback, and often lead to more revision requests when clients haven’t thought things through. A reasonable rush surcharge is 25–40% of the base quote.

Time estimates by project type

How to quote a web design project
Every section of a proposal should move the client closer to yes.

These ranges reflect the full project arc, discovery, design, development, QA, launch, at mid-market proficiency. Use them to sanity-check your own estimates.

Brochure site (5–8 pages, WordPress or Webflow, no e-commerce): 40–60 hours

  • Discovery and wireframing: 4–8 hours
  • Design (desktop + mobile): 12–20 hours
  • Development: 16–24 hours
  • Content integration, QA, launch: 8–12 hours

E-commerce site (Shopify or WooCommerce, up to 50 products, standard theme): 60–90 hours

  • Discovery and setup: 6–10 hours
  • Theme customization and design: 16–24 hours
  • Product setup, payment integration, shipping config: 18–30 hours
  • QA, cross-browser testing, launch: 10–16 hours

E-commerce (custom design, complex product catalog, 100+ products): 90–140 hours Add: custom product pages, advanced filtering, integration with inventory management, multi-currency or international shipping.

Custom web application (user login, dashboards, complex data interactions): 150–300+ hours Design and development are separate tracks at this scale. Budget architecture and technical planning separately. This size of project is rarely quoted as a fixed price, phased quoting with estimates per phase is more appropriate.

Marketing site with animations and interactive elements: Add 20–40% to brochure site estimates for GSAP animations, scroll effects, and interactive components.

The most dangerous number in web design quoting is the one you give before seeing the sitemap. “How much for a website?” is not a question you can answer honestly. “How much for a 6-page Webflow site, homepage, about, services, 2 case studies, contact, with client-supplied copy and one round of design revisions?” is a question you can quote accurately. Never name a number until you can answer that version of the question.

Handling the “just give me a ballpark” request

Comparacion software propuestas freelance
The best proposals read like the client wrote them.

Every web designer has been here. The client calls, gives a 90-second description of their project, and says “I just need a rough number, I’m not going to hold you to it.”

You will be held to it. The number you say becomes the anchor for every conversation that follows. They’ll negotiate down from it, not up to a properly-scoped number.

The redirect:

“I want to give you a number that’s actually useful, not one that’s so wide it means nothing. Can we do a 20-minute call where I walk through a few scope questions? That way I can give you a real range instead of a rough guess that might be off by $15,000 either way.”

If they won’t agree to a scoping call, give a wide range with an explicit disclaimer:

“Without knowing the scope in detail, something like this typically runs $6,000–$40,000, that’s genuinely the range depending on functionality and complexity. A 30-minute scope conversation would get me to a real number for you.”

The wide range accomplishes two things. It’s honest. And it frames the scoping call as something that benefits the client (a real number vs. a wild guess), not as an obstacle you’re putting in front of them.

Revision rounds: the language that prevents scope creep

The single most common source of scope creep in web design is undefined revisions. A quote that says “website design” implies unlimited input until the client is happy. A quote that says “2 rounds of design revisions per page template” does not.

Write it explicitly every time:

“This quote includes 2 rounds of revisions per design template. A revision round is one consolidated set of feedback, all requested changes combined into one document or call, then implemented in one update. Additional revision rounds are available at $150/hour.”

“Consolidated” is the key word. Without it, clients send revisions in drips, one email Tuesday, three more Wednesday, another thought Saturday. Every drip is a separate round. “Consolidated” means they gather all their feedback, send it once, and you implement it once.

The web design quote structure that closes

Once you have all eight answers and your time estimate, the quote structure:

  1. Project summary (2–3 sentences): restate what the client told you, in your words. This confirms you understood the brief and catches any miscommunication before it becomes a problem.

  2. Scope of work (bulleted): every page, every feature, explicit inclusions. Then: “The following are not included: copywriting, photography, domain registration, hosting, third-party plugin licenses.”

  3. Timeline: project start date (pending acceptance), expected completion, key milestone dates.

  4. Investment: line items by phase or component, then a total. Use “Total Investment,” not “Total Cost.”

  5. Payment terms: deposit on acceptance, milestone payment on design approval, final payment on launch.

  6. Revision terms: the exact language above, rounds, what counts as a round, rate for additional rounds.

  7. Validity: “This quote is valid for 14 days. After that, rates may be updated.”

  8. Acceptance: one clear action to confirm, reply, sign, click.

Send it within 24 hours of the scoping call. Follow up on Day 3 if no response.

Ready to send stronger proposals?

Build, send, and track proposals in one place so follow-up is easier.

Start your free trial →