Website Proposal Template
Template for Website Proposal. Customize this template for your specific needs.
For Informational Purposes
This document template is provided for informational purposes. Customize it for your specific needs.
Document: Website Proposal
Template Preview
Version 1 • Last updated 6/4/2026
Website Proposal
Prepared for: [Client name / company] Prepared by: [Your studio / name] Date: [Date] Valid until: [Date + 30 days]
1. Executive summary
[In 2–3 sentences: what the new website needs to achieve for the business, your proposed approach, the headline timeline and price, and the single most important outcome. Write this last, read it first.]
2. Goals and success metrics
[State the business reasons for the project and how success will be measured after launch. Record today's baseline so the improvement is provable.]
| Goal | Metric | Baseline (today) | Target |
|---|---|---|---|
| [e.g. More online sales] | [Conversion rate] | [x%] | [y%] |
| [e.g. Faster site] | [Mobile load time] | [x s] | [under y s] |
| [e.g. More enquiries] | [Form submissions / mo] | [x] | [y] |
3. Scope and sitemap
[List the pages and templates you will build. Distinguish reusable templates from one-off pages, and state what is out of scope.]
- Pages / templates: [Home], [Category], [Product / service], [Blog], [About], [Contact], [Checkout]
- Content responsibility: [Who writes copy and supplies images]
- Out of scope: [e.g. ongoing content, photography, translation, third-party app fees]
4. Design and build approach
[Explain how you work and what the client will see at each stage. State the number of design and revision rounds included.]
- Discovery — [goals, audience, content audit, technical requirements]
- Design — [wireframes, then high-fidelity mockups of key templates for sign-off — X rounds]
- Build — [front-end development, responsive, accessibility, CMS/commerce setup]
- QA and review — [cross-device testing, content population, structured client review]
5. Integrations, CMS and analytics
[List the platforms and services the site will use, and any accounts or licences the client must provide.]
| Area | Tool / platform | Provided by |
|---|---|---|
| CMS / e-commerce | [e.g. platform name] | [You / client] |
| Payments | [Gateway] | [Client account] |
| Email / marketing | [Tool] | [Client account] |
| Analytics | [Tool] | [You set up] |
6. Timeline and phases
| Phase | Work | Milestone | Dates |
|---|---|---|---|
| 1 | Discovery & planning | Sitemap signed off | [Week 1] |
| 2 | Design | Mockups approved | [Weeks 2–3] |
| 3 | Build & integrations | Staging site ready | [Weeks 4–6] |
| 4 | Content, QA & launch | Site live | [Weeks 7–8] |
[Note any dependencies — e.g. design cannot start until content/branding is supplied.]
7. Pricing
| Item | Detail | Price |
|---|---|---|
| Discovery & design | [Detail] | [$] |
| Build & integrations | [Detail] | [$] |
| Content & migration | [Detail] | [$] |
| Total | [$] |
Payment terms: [e.g. 40% to begin, 30% at staging, 30% on launch. Invoices due within 14 days.]
8. Hosting and post-launch support
- Hosting: [Where the site lives, who pays, any platform/licence fees]
- Handover: [Admin access, documentation, training]
- Support: [Post-launch fix window, then optional monthly care plan and what it covers]
- Ownership: [What the client owns at the end — site, code, content, accounts]
9. Assumptions
- [e.g. Client supplies brand assets and final copy by the agreed date]
- [e.g. Required third-party accounts and API keys are available at build time]
- [e.g. One consolidated round of feedback per review stage]
10. Next steps
[One clear action. e.g. "To get started, sign below or reply to this email and we'll send the deposit invoice and book your discovery workshop."]
Accepted by: ______________________ Date: ____________
About this Template
Part of the Website Proposal document collection
Document Type
Website Proposal
A proposal for designing and/or developing a website, including scope, features, timeline, and costs.
Complexity
Format
Estimated Time
60 minutes