Why Web Design Needs a Different Proposal
Web design proposals are unique because clients often don't know what they need. They know they want a "better website" but can't articulate what that means.
Your proposal needs to do two things:
- Educate the client on what a good website looks like
- Sell your specific approach to getting them there
A generic proposal template won't cut it. Here's what works for web design specifically.
Section 1: Project Understanding
Start by restating what the client told you during discovery:
- Current website issues (slow, outdated, not mobile-friendly)
- Business goals (more leads, better brand perception, e-commerce)
- Target audience
- Competitor websites they admire
This section proves you listened. It's the most important trust-builder in the entire proposal.
Section 2: Proposed Solution
Be specific about what you'll deliver:
- Number of pages
- Key features (contact forms, booking system, blog, etc.)
- Mobile responsiveness
- CMS (WordPress, Webflow, custom)
- Content strategy (who provides copy and images?)
Avoid vague deliverables like "modern website." Instead: "8-page responsive website built on Webflow with custom animations, SEO-optimized copy for 5 service pages, and a contact form with Calendly integration."
Section 3: Process & Timeline
Break the project into clear phases:
- Discovery & Strategy (Week 1) — Stakeholder interviews, competitor analysis, sitemap
- Wireframes & Content (Week 2-3) — Page layouts, content gathering
- Visual Design (Week 3-4) — Style concepts, design system, mockups
- Development (Week 5-7) — Build, CMS setup, responsive testing
- Testing & Launch (Week 8) — QA, browser testing, go-live
Include what you need from the client at each phase.
Section 4: Investment
Package pricing works best for web design:
- Starter ($3,000): 5-page site, stock photos, basic SEO
- Professional ($6,000): 8-page site, custom graphics, SEO + analytics, blog setup
- Premium ($10,000): Full custom design, copywriting, 3 months post-launch support
Always include what's not included: ongoing hosting, domain registration, stock photo licenses, future content updates.
Section 5: Technology Stack
Clients (especially technical ones) want to know what you're building with:
- CMS: WordPress, Webflow, Squarespace, or custom
- Hosting: Where will the site live?
- Analytics: Google Analytics, Plausible, etc.
- Performance: Expected load times, Core Web Vitals targets
- Security: SSL, backups, updates
This builds confidence that you're making informed technical decisions.
Section 6: Terms
Web design specific terms to include:
- Revisions: 2 rounds of design revisions per page (additional at $X/hour)
- Content: Client provides all copy and images by [date] — delays push the timeline
- IP ownership: Full rights transfer on final payment
- Browser support: List specific browsers and devices
- Post-launch: What happens after launch? (support period, hourly rate for changes)
Use Kulvo to include terms directly in your proposal with built-in e-signatures.