Web Design Proposal Template

Web design projects rarely go wrong on design. They go wrong on the things a proposal forgets to pin down: how many pages, how many rounds of revisions, and who is writing the copy. Every one of those is a scope argument waiting to happen three weeks in.

The template below puts each of them in writing before the work starts. Download it for Word or copy it as text, replace anything in [brackets], and delete what does not apply. Nothing is gated and there is no signup.

The template

Proposal for: [Client company] Prepared by: [Your name, your studio] Date: [Date] Valid until: [Date, 30 days out]

1. Situation

[What the current site is failing to do, in their words. The traffic that does not convert, the CMS nobody can update, the brand that has moved on since the site was built.]

2. Objectives

By launch, [Client company] will have:

• [Objective stated as a business outcome, for example "a site the marketing team can update without a developer"]
• [Objective]
• [Objective]

3. Measures of success

4. Scope

Pages included: [Number] unique page templates: [Home, About, Services, Service detail, Case study, Blog index, Blog post, Contact].

Pages beyond this list, or additional unique layouts, are quoted separately.

Platform: [WordPress / Webflow / Shopify / Next.js].

Responsive: Designed for [desktop, tablet and mobile]. Tested in [current versions of Chrome, Safari, Firefox and Edge].

Not included: [Copywriting, photography, illustration, translation, ongoing hosting, third-party licences, SEO campaign work].

5. Approach

Phase 1: Discovery [Stakeholder session, analytics review, competitor scan, sitemap and page-level content plan.]

Phase 2: Design [Wireframes for key templates, then visual design. Presented for review at each stage.]

Phase 3: Build [Development, CMS setup, responsive testing, accessibility and performance passes.]

Phase 4: Launch [Content load, redirects, analytics, final QA, go-live and handover training.]

6. Revisions

Each design stage includes [two] rounds of consolidated feedback. A round means one set of comments gathered from your side, not sequential requests from different reviewers.

Further rounds, or changes to a direction already signed off, are billed at [rate].

7. Content and assets

[The single most common cause of delay on a web project.]

• Copy is written by: [client / us, quoted separately]
• Images and video supplied by: [client / us, quoted separately]
• Brand assets, logos and fonts supplied by: [client]
• Content deadline: [date, before build begins]

If content arrives after [date], the launch date moves by the same number of working days.

8. Timeline

This timeline assumes [feedback within [X] working days at each review, and all content supplied by the date above].

9. Investment

Third-party costs: [Theme, plugin and stock licences are billed at cost and listed before purchase.]

Hosting and domain: [Client holds the accounts, or we manage them at [amount] per month.]

Payment: [50% to book the start date, 50% on launch / three milestone payments].

10. After launch

[Thirty] days of bug fixes at no charge, covering anything that does not work as specified.

Ongoing support, content updates and new features are available on a retainer at [amount] per month, or ad hoc at [rate].

11. What we need from you

• A named decision-maker who can sign off each stage
• Consolidated feedback within [X] working days
• Content and assets by [date]
• Access to [hosting, domain registrar, analytics, existing CMS]

12. Scope and changes

This proposal covers the work described above. Additional pages, templates or features are quoted before work begins. Either party may end the engagement with [notice period] written notice, with fees due for work completed.

[Add ownership of the finished site and source files on final payment, confidentiality, and liability here, or reference the master agreement.]

13. Next steps

1. Select an option and sign below, or reply with questions.
2. We confirm the start date and issue the first invoice.
3. Discovery session in the first week, with [named stakeholders].

14. Acceptance

Option selected: [A / B / C]

Signed for [Client company]: ______________________ Date: __________

Signed for [Your studio]: ______________________ Date: __________

What to include in a web design proposal

Web design proposals fail in predictable places, and each of those places is a section above.

Count the templates, not the pages. A twelve-page site with four unique layouts is a smaller job than a five-page site with five. Scoping by page count invites the client to add "just one more page" that turns out to need a new design. Say how many unique templates are included, and price additional layouts separately.

Define what a revision round is. Most disputes about revisions are really disputes about what counted as a round. One consolidated set of comments is a round. Three people sending separate emails over a fortnight is three rounds. Writing that sentence down saves the argument.

Name who writes the copy. Missing content is the single most common reason a web project slips, and clients frequently assume copy is included. Put the owner and the deadline in the proposal, and state plainly what happens to the launch date if content is late.

Say what happens after launch. A proposal that ends at go-live leaves the client assuming indefinite free support and leaves you fielding requests for months. A fixed bug-fix window and a priced retainer sets the boundary, and it is the natural route into recurring revenue.

List third-party costs separately. Themes, plugins, stock images and font licences are the client's costs, not your margin. Saying so up front avoids an awkward invoice later.

How to price a web design proposal

Offer three options rather than one number. A single price is a yes or no decision. Three make it a choice between versions of yes, and which one the client picks tells you what they value. Build them so each adds scope: A is design and build, B adds copywriting, C adds a care plan.

Price by value and complexity, not hours. Hourly pricing on web projects punishes experience: the faster you work, the less you earn. It also invites the client to audit your time rather than judge the result. Use fixed fees per option, with a stated hourly rate for work outside scope.

Charge a deposit that books the date. Half up front is normal, and it is the fee that protects your calendar. A booking fee makes clear that the start date is being reserved, not just intended.

Build the retainer into the proposal. A site needs updates, plugin maintenance and security patches from the week it launches. Presenting a care plan as Option C, or as a line under the fee table, is far easier than selling it as a new project three months later.

Quote a range before writing. If the client's budget is [X] and your smallest option is triple it, both of you have wasted a week. A single question about budget before you write is worth more than any amount of proposal polish.

Common questions

How many pages should a web design proposal include?

Scope unique templates, not page count. Say how many distinct layouts the fee covers, list them, and price extra layouts separately. A blog index and a blog post are two templates however many posts eventually exist.

How many revision rounds should I offer?

Two per design stage is standard, with a clear definition that a round is one consolidated set of feedback. Offering unlimited revisions sounds generous and reliably costs more than the project earns.

Should the client or the designer write the website copy?

Whichever you choose, decide it in the proposal. Clients usually assume copy is included, designers usually assume it is not, and the project stalls in week four while everyone waits. If the client is writing it, set a content deadline and state that the launch date moves if it is missed.

What should a web design proposal say about hosting?

Say who holds the accounts and who pays. The cleanest arrangement is the client owning the hosting, domain and analytics accounts, with you holding access. If you manage hosting, price it as a monthly line rather than absorbing it.

How long should a web design proposal be?

Long enough to pin down scope, revisions, content ownership, timeline, fee and what happens after launch. That is usually five to nine pages. Portfolio work belongs in an appendix or a separate link, not in the middle of the scope.