Proposal templates
Scope, design process, revision rounds, timeline and pricing — the details that actually prevent web design disputes.
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.
Exact number of unique page designs (not just 'a website') — templates and one-off pages priced differently if that's how you work.
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.
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.
Development/build (if you're design-only), copywriting, stock photography licensing, ongoing maintenance.
What the client receives at the end — Figma files, exported assets, a built site — stated explicitly.
Copy this into your own document, or build it directly as a branded page 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: [___]
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.
State it explicitly either way. If design-only, say so and clarify the client needs separate development — don't leave it implied.
Price per unique page template rather than a flat fee for 'the whole site' — that scales fairly if the page count changes during scoping.
Build it as a branded proposal in Hanko, get it signed, and invoice the kickoff and delivery payments automatically.
Product
InvoicingProposalsAgreementsClient portalsSolutionsCompareAlternativesBest ofTemplatesPricingProduct updates and the occasional tip, about once a month.