Web design proposal template: what to include and how to win the project
A web design proposal template with sections for scope, timeline, pricing, and revision terms.
A web design proposal needs more detail than a generic freelance proposal. You are not just selling a service. You are defining what gets built, what the client is responsible for, how revisions work, and what happens after launch. The template below covers all of it. Copy it, customize the sections, and send it within 24 hours of your discovery call.
The full web design proposal template
Replace everything in curly braces with your project details.
Web Design Proposal: {PROJECT_NAME}
Prepared for: {CLIENT_NAME}
Prepared by: {YOUR_NAME}, {YOUR_BUSINESS_NAME}
Date: {DATE}
PROJECT SUMMARY
{CLIENT_NAME} needs {brief description of what they need and why}.
Based on our discovery call on {date}, the primary goals for this
project are:
- {Goal 1: e.g., "Increase lead generation from organic traffic"}
- {Goal 2: e.g., "Modernize the brand presentation"}
- {Goal 3: e.g., "Improve mobile experience and page speed"}
This proposal covers the design {and development, if applicable}
of a {number}-page website that {key outcome}.
SCOPE OF WORK
Phase 1: Discovery and strategy
- Review of current site analytics and performance
- Competitive audit ({number} competitor sites)
- Sitemap and wireframe creation
- Content strategy recommendations
Phase 2: Design
- Homepage design ({number} initial concepts)
- Interior page designs: {list pages}
- About
- Services
- Contact
- {Additional pages}
- Mobile responsive versions of all pages
- {number} rounds of design revisions
Phase 3: Development
- Front-end build on {platform: WordPress, Webflow, custom, etc.}
- Mobile responsive implementation
- Contact form integration ({form tool})
- CMS setup for client-editable content
- Basic on-page SEO (meta titles, descriptions, alt tags)
- Cross-browser testing (Chrome, Safari, Firefox, Edge)
- Performance optimization (target: under 3-second load time)
Phase 4: Launch
- Migration to live server
- DNS configuration
- Post-launch QA check
- 30-minute training session on CMS editing
CONTENT RESPONSIBILITIES
The client is responsible for providing:
- Final copy for all pages by {date}
- High-resolution photos and brand assets
- Logo files (vector format preferred)
- Login credentials for hosting, domain registrar, and CMS
{YOUR_NAME} is responsible for:
- Placeholder copy for design mockups
- Stock photo recommendations (licensing costs billed separately)
- Content formatting and placement
DELIVERABLES
Included:
- {number}-page responsive website
- Homepage: {number} design concepts, 1 final
- Interior pages: {number} designed and built
- CMS setup with editable content areas
- Contact form
- Basic SEO setup
- Cross-browser and mobile testing
- 30-minute CMS training session
- {number} rounds of revisions per page
Not included:
- Copywriting or content creation
- Photography or custom illustration
- E-commerce functionality
- Ongoing hosting or maintenance
- Email marketing setup
- Third-party integrations beyond {specified tools}
- Additional pages beyond the {number} specified
TIMELINE
- Project kickoff: within {number} business days of deposit
- Discovery and wireframes: {number} weeks
- Homepage design: {number} weeks
- Interior page designs: {number} weeks
- Development: {number} weeks
- Content integration and testing: {number} week
- Launch: {target date or "approximately X weeks from deposit"}
Total estimated timeline: {number} weeks from deposit to launch
Note: This timeline assumes client feedback is provided within
{number} business days of each deliverable. Delayed feedback will
shift the project timeline accordingly.
PRICING
Option A (recommended): ${AMOUNT}
- Full scope as described above
- {number} pages designed and developed
- {number} rounds of revisions per page
- CMS training session included
Option B: ${AMOUNT}
- Reduced scope: {number} pages
- {number} round of revisions per page
- No CMS training (documentation provided instead)
Optional add-ons:
- Additional page: ${AMOUNT} per page
- Blog setup and template: ${AMOUNT}
- SEO audit and keyword research: ${AMOUNT}
- Monthly maintenance retainer: ${AMOUNT}/month
REVISION POLICY
{number} rounds of revisions are included per page at no additional
cost.
A "revision" is defined as a set of feedback collected and
submitted at one time. Partial or ongoing feedback submitted across
multiple emails counts as multiple rounds.
Additional revisions beyond the included rounds are billed at
${HOURLY_RATE}/hr.
Revisions apply to the agreed scope only. Requests that add new
pages, new features, or change the approved direction are treated
as scope changes and require a written change order.
PAYMENT TERMS
- 50% deposit due upon proposal approval: ${AMOUNT}
- Remaining 50% due before launch: ${AMOUNT}
Payment is accepted via {payment method: credit card, ACH, etc.}.
Work begins after the deposit is received. The site will not go
live until the final balance is paid in full.
CHANGE ORDER POLICY
Any work outside the agreed scope requires a written change order
before work begins. Change orders will include the additional cost
and any impact on the project timeline.
Examples of scope changes:
- Adding pages beyond the original count
- Changing the platform after development begins
- Adding e-commerce or membership functionality
- Requesting a complete redesign of an approved page
OWNERSHIP AND LICENSING
Upon receipt of final payment, {CLIENT_NAME} owns the completed
website design and all custom assets created for this project.
{YOUR_NAME} retains the right to display the work in portfolio
and marketing materials unless otherwise agreed in writing.
Third-party assets (stock photos, fonts, plugins) are subject to
their respective license terms.
NEXT STEP
Reply "approved" to this proposal. I will send the deposit invoice
the same day. Once payment is received, the project will be
scheduled and I will send the discovery questionnaire to get
started.
{YOUR_NAME}
{YOUR_BUSINESS_NAME}
{YOUR_EMAIL}
{YOUR_PHONE}What makes web design proposals different
A generic freelance proposal covers scope, pricing, and terms. A web design proposal needs to go further because the work is more complex and the opportunities for misunderstanding are higher.
More stakeholders
Web projects often involve multiple decision-makers. The person on the discovery call may not be the person approving the design. Your proposal needs to be clear enough for someone who was not on the call to understand what is included.
Content dependencies
Web design projects almost always stall because of content. The client does not have their copy ready, their photos are low-resolution, or their brand guidelines do not exist yet. Your proposal needs to state who is responsible for content and when it is due.
Technical scope ambiguity
“Build a website” can mean wildly different things. A 5-page brochure site on Webflow is not the same as a custom WordPress build with e-commerce, membership areas, and third-party integrations. Your deliverables section must be specific enough to prevent this confusion.
Revisions spiral easily
Design is subjective. Without a clear revision policy, feedback rounds can multiply indefinitely. Define what a revision is, how many are included, and what happens after that.
Post-launch expectations
Clients often assume ongoing support is included. If it is not, state that clearly. If you offer a maintenance retainer, include it as an add-on in your pricing section.
How to write the project summary
The project summary sets the tone for the entire proposal. It should show that you understand the client’s goals, not just their request.
Bad example:
“We will design and develop a new website for your company.”
Better example:
“Based on our call on March 3, you need a redesigned marketing site that performs better on mobile, reflects your updated brand identity, and generates more inbound leads through improved SEO and a clearer conversion path. This proposal covers the design and development of a 6-page responsive site on Webflow.”
The better version works because it references the specific call, names the client’s goals, and defines the deliverable in one paragraph.
Include 2 to 3 specific project goals as bullet points. These become the success criteria you can reference later if the project direction drifts.
How to define scope without gaps
The scope section is where most web design disputes originate. If you are vague here, you will pay for it in scope creep later.
Break the project into phases
Phases make the work tangible. They also create natural checkpoints for feedback and payment.
A standard web design project has four phases:
- Discovery and strategy (research, sitemap, wireframes)
- Design (mockups, revisions, approval)
- Development (build, test, integrate)
- Launch (migration, QA, training)
Be specific about what each phase includes
Do not write “design the website.” Write “design the homepage (2 initial concepts, 1 final) and 4 interior pages (1 concept each, 1 final).”
Do not write “build the site.” Write “front-end development on Webflow, mobile responsive, contact form via Typeform embed, CMS setup for blog and team pages.”
List exclusions clearly
Every web design proposal should have a “not included” section. Common exclusions:
- Copywriting
- Photography
- E-commerce
- Email marketing
- Ongoing hosting
- Third-party integrations not specified
- Additional pages
If the client wants any of these, they become add-ons with separate pricing.
For a general framework on structuring deliverables, read the freelance proposal guide.
How to handle content in the proposal
Content is the most common bottleneck in web design projects. Address it directly.
State who provides content
Your proposal should have a “content responsibilities” section that clearly defines:
- Who writes the copy (client or you)
- When copy is due
- What format the copy should be in
- Who provides photos, logos, and brand assets
- What happens if content is late
Include a content deadline
Tie the content deadline to the project timeline. Example:
“Final copy for all pages is due by [date]. If copy is not received by this date, the project timeline will shift accordingly.”
This is not being difficult. It is protecting the schedule.
Offer content as an add-on
If the client does not have copy, offer copywriting as a separate line item. Do not absorb it into the design price.
How to structure pricing for web design
Web design pricing is more complex than most freelance services because the scope has more variables.
Use two options
Two options give the client a choice without creating analysis paralysis.
Option A should be the full scope. Label it “recommended.”
Option B should be a reduced version: fewer pages, fewer revision rounds, or no training session.
Include add-ons
Add-ons let you capture additional revenue without inflating the base price. Common web design add-ons:
- Additional pages ($X per page)
- Blog setup and template design
- SEO audit and keyword research
- Monthly maintenance retainer
- Social media template design
- Email template design
Price by project, not by hour
Most web design clients prefer fixed pricing. It gives them cost certainty and removes the anxiety of a running meter.
If you need help calculating your project rate, work backward from your hourly rate and estimated hours, then round to a clean number.
The revision policy that saves your margin
Revisions are where web design projects go off the rails. A clear revision policy is not optional.
Define what counts as a revision
A revision is a set of feedback submitted at one time. Not an email here and a Slack message there. If the client sends feedback in five separate messages over three days, that is one revision round if you collect it all before making changes, but five rounds if you respond to each one individually.
State this explicitly:
“A revision round is defined as one consolidated set of feedback submitted at one time. Feedback submitted across multiple messages may count as multiple rounds.”
Cap the number of included rounds
Two rounds per page is a reasonable default for most web design projects. Some designers offer three. Do not offer unlimited.
Price additional revisions clearly
State the hourly rate for revisions beyond the included rounds. This creates a natural incentive for the client to consolidate their feedback.
Separate revisions from scope changes
A revision adjusts what was already designed. A scope change adds something new. Make sure your proposal distinguishes between the two. For detailed language on handling scope changes, see the scope creep clause.
Timeline considerations for web design
Web design timelines are unpredictable because they depend on client feedback speed.
Tie the timeline to the deposit
Do not start the clock on the discovery call. Start it on the deposit.
“Project kickoff: within 3 business days of deposit receipt.”
This creates urgency for the client to pay and gives you a predictable start date.
Build in feedback windows
Your timeline should include explicit feedback windows. Example:
“Client will have 3 business days to provide feedback on each design deliverable.”
If the client takes 2 weeks to respond instead of 3 days, the project timeline shifts. State that clearly.
Add buffer before launch
Things always take longer than expected in the final stretch. Content is not ready, the client wants one more change, or a browser bug appears in testing. Build a buffer into the launch phase.
Sample timeline for a 6-page website
| Phase | Duration | Notes |
|---|---|---|
| Discovery and wireframes | 1 week | Includes sitemap, wireframes, competitive review |
| Homepage design | 1 week | 2 concepts, client selects 1 |
| Interior page designs | 1.5 weeks | 5 pages, 1 concept each |
| Design revisions | 1 week | 2 rounds across all pages |
| Development | 2 weeks | Build, CMS setup, integrations |
| Content integration and QA | 1 week | Client content, testing, fixes |
| Launch | 3 days | Migration, DNS, post-launch check |
| Total | ~8 weeks | Assumes 3-day client feedback windows |
Post-launch terms to include
What happens after the site goes live
State clearly whether your scope ends at launch or continues.
“This proposal covers work through the launch date. Post-launch support, updates, and maintenance are available under a separate maintenance agreement.”
Maintenance retainer option
If you offer ongoing maintenance, include it as an add-on:
“Monthly maintenance retainer: $X/month. Includes up to Y hours of updates, security patches, plugin updates, and minor content changes.”
Bug fix window
It is common to include a short post-launch window for bug fixes:
“Bug fixes identified within 14 days of launch will be resolved at no additional cost. Bugs are defined as functionality that does not match the approved designs. New feature requests are treated as scope changes.”
Common mistakes in web design proposals
Vague page count
“Design a website” is not a scope. “Design a 6-page website including homepage, about, services, portfolio, blog, and contact” is a scope.
No content deadline
If you do not set a content deadline, the project will stall for weeks while you wait for the client to write their copy.
Mixing design revisions with development changes
Design revisions should happen before development begins. If the client requests design changes during the development phase, that is a scope change with additional cost.
Assuming the client understands technical terms
Do not write “responsive build with Lighthouse score optimization.” Write “the site will look good and load fast on phones, tablets, and desktop browsers.”
No platform specification
State which platform you are building on. WordPress, Webflow, Squarespace, Shopify, or custom. If the client does not know the difference, explain it in the discovery call and confirm it in the proposal.
Forgetting ownership terms
State who owns the final site files and when ownership transfers. The standard is: ownership transfers upon receipt of final payment.
FAQ
How long should a web design proposal be?
Two to four pages. Long enough to cover scope, deliverables, timeline, pricing, and terms. Short enough that every stakeholder reads the whole thing. If your proposal is over 5 pages, you are probably including information that belongs in a separate discovery document.
Should I include wireframes in the proposal?
No. Wireframes are part of the discovery phase that begins after the proposal is approved and the deposit is paid. Including wireframes in the proposal means you are doing unpaid work to win the project.
How many pricing options should I include?
Two. A recommended full-scope option and a reduced option. Three works if the project has a natural third tier, but more than that creates decision paralysis.
Should I show my hourly rate?
Not in the pricing section. If you charge by the project, show the project price. Your hourly rate only needs to appear in the revision policy section as the rate for additional revisions beyond included rounds.
What if the client wants to use a different platform than I recommended?
Include your recommended platform in the proposal. If they want something different, discuss it before approval. Platform changes after development begins are one of the most expensive scope changes in web design.
How do I handle clients who want unlimited revisions?
You do not offer unlimited revisions. State the number included, the rate for additional rounds, and the definition of what counts as a revision. If a client insists on unlimited revisions, increase your price to account for the additional time.
Should I include a portfolio or case studies in the proposal?
Only if the client has not already seen your work. A link to your portfolio at the end is fine. Do not turn the proposal into a sales pitch. By the time you are sending a proposal, the selling should be done.
What is the best way to send a web design proposal?
A dedicated proposal link where the client can review, approve, and pay the deposit in one step. If that is not available, a clean PDF with a clear next step works.
The practical takeaway
A web design proposal template saves time, but the details are what win projects and prevent disputes. Define the scope in phases. List every deliverable and every exclusion. Set a content deadline. Cap your revisions. Tie the timeline to the deposit.
Start with the template above. Customize it for each client. Send it within 24 hours of the discovery call.
If you want to skip the formatting and go straight to sending, GetPaidFirst generates a complete web design proposal from your meeting notes. The client sees a clean proposal with scope, pricing, and payment terms, and can approve and pay the deposit in one step. No PDFs. No back-and-forth.
Further reading:
- Freelance proposal template (GetPaidFirst)
- Deposit strategy for freelancers (GetPaidFirst)
- Web Design Best Practices (Google Search Central)
- How to scope a web project (Smashing Magazine)