Proposal templates
Web design proposal template
Scope, design process, revision rounds, timeline and pricing — the details that actually prevent web design disputes.
Preview
See the template as a client-facing document, then open the same starting point inside Hanko.
Form Practice
Northstar website redesign
Replace a fragmented website with a clear product story, accessible page system and an editable CMS.
Approach
Start with content and user journeys. Review wireframes before visual design, then validate the responsive build against agreed launch criteria.
Scope of work
Discovery and sitemap
Wireframes and visual direction
Responsive build and CMS
Accessibility QA and launch
Deliverables and handover
Five responsive page templates
Reusable component library
CMS training and handover
Two structured design review rounds
Timeline
Discovery
Phase 140%
Design approval
Phase 230%
Launch and handover
Phase 330%
Engagement investment
Discovery
Phase 140USD 4800Design approval
Phase 230USD 3600Launch and handover
Phase 330USD 3600
Review the scope and payment schedule before accepting.
Assumptions and boundaries
Copy, brand assets and consolidated feedback are supplied by the client. Hosting and ongoing maintenance are scoped separately.
Ready to get started?
Accept this proposal to lock in the timeline and kick off the engagement.
What this is
A web design proposal defines what pages/site will be designed, the process (discovery, wireframes, design, revisions, handoff), the timeline, and the price — set up specifically to prevent the two most common disputes in web design work: revision scope and what happens post-launch.
When to use it
- Pitching a new website design or redesign project
- After a discovery call, to formalize page count, revision rounds and price
- When a client is comparing quotes from multiple designers or studios
What to include
Page/scope count
Exact number of unique page designs (not just 'a website') — templates and one-off pages priced differently if that's how you work.
Design process
The stages a client will see — wireframes, mood board/style tile, full design, revisions — so they know what to expect and when to give feedback.
Revision rounds
A specific number of included revision rounds per stage, with additional rounds priced separately — the single most common source of scope creep in design work.
What's not included
Development/build (if you're design-only), copywriting, stock photography licensing, ongoing maintenance.
Handoff
What the client receives at the end — Figma files, exported assets, a built site — stated explicitly.
Template text
Copy this into your own document, or open it directly as a branded starting point in Hanko. Bracketed text like [Client Name] is a placeholder to fill in.
Web Design Proposal — [Project Name]
Prepared for: [Client Company Name], [Contact Name]
Prepared by: [Your Studio Name]
Date: [Date] | Valid until: [Date]
Project overview
[1-2 sentences on the project — e.g., 'Redesign of [Client]'s marketing website (up to 8 unique page templates) to improve conversion and reflect the new brand identity.']
Scope
Pages included: [e.g., Home, About, Services, Case Studies (template), Blog (template), Contact — 6 unique page designs]
Responsive design for desktop, tablet and mobile: Included
Not included: [e.g., development/build, copywriting, photography, illustration beyond stock, ongoing maintenance]
Process
1. Discovery & moodboard — [X days]
2. Wireframes — [X days], [1] revision round included
3. Visual design (homepage first, then remaining pages) — [X days], [2] revision rounds included
4. Final files & handoff — [X days]
Timeline
Total duration: [X weeks] from kickoff, assuming feedback is returned within [2] business days at each stage
Kickoff: [date] | Target completion: [date]
Investment
Total design fee: $[amount]
Payment: [50%] on kickoff, [50%] on final delivery
Additional revision rounds beyond those included: $[amount]/round
Deliverables
[e.g., Figma files with all page designs, exported assets (logos, icons, images), a style guide covering colors/type/components]
Next steps
Accept below to move to a signed agreement and kickoff scheduling.
[Signature / Accept button] Date: [___]
How to customize it
- State the exact page count you're pricing — 'a website' is not a scope
- Set a specific number of revision rounds per stage, not a vague 'reasonable revisions'
- If you don't build sites, say so explicitly and note the client needs a separate developer or your referral
- Tie the timeline to a client feedback SLA (e.g., 2 business days) so a slow client doesn't silently extend your schedule for free
Common mistakes
- No stated number of revision rounds, which turns into unlimited rounds by default
- Pricing 'a website' without specifying how many unique page designs are included
- No client feedback SLA, so a client who takes three weeks to respond doesn't affect the stated timeline
- Ambiguity over design-only vs. design-and-build, discovered only after the client expects a live site
Frequently asked questions
How many revision rounds should a web design proposal include?
1-2 rounds per major stage (wireframes, visual design) is standard. State the number explicitly and price additional rounds separately — this is the most common point of dispute in design engagements.
Should the proposal include development, or just design?
State it explicitly either way. If design-only, say so and clarify the client needs separate development — don't leave it implied.
What if the client wants unlimited pages designed?
Price per unique page template rather than a flat fee for 'the whole site' — that scales fairly if the page count changes during scoping.
Other templates
Send this proposal, then bill the design fee in two payments
Build it as a branded proposal in Hanko, get it signed, and invoice the kickoff and delivery payments automatically.