A new website is one of the few freelance projects where the client cannot picture the finished product until weeks into the work. They know they want "something modern that brings in leads," and you know that sentence hides a sitemap, a CMS choice, a content plan and at least one argument about the homepage hero. The proposal is where you turn the vague request into a defined build.
This template is written for designers and small studios building a site from scratch: a new business, a product launch, or a company that has never had a proper site. If the client already has a site and wants it replaced, the website redesign proposal is the better fit, because it adds an audit, content migration and redirects.
TL;DR
The web design proposal template covers a new site build: sitemap and page count, page templates, CMS and hosting, who supplies copy and images, a five-phase timeline, pricing, and acceptance. Send it after the discovery call and before any design work. The key practice is pricing by template and feature, then tying the final payment to launch so the balance is paid before the domain goes live.
What's inside
- Project summary: the business goal of the site in one paragraph, plus launch date and total fee.
- Sitemap and page inventory: every page listed, grouped by the template it uses.
- Functionality: forms, booking, blog, ecommerce, integrations, each priced or marked out of scope.
- Content responsibilities: who writes copy, who sources images, and the deadline for each.
- Technical setup: CMS, hosting, domain, analytics, browser and device support.
- Phased timeline: discovery, wireframes, visual design, build, QA and launch.
- Investment and payment schedule: build fee broken into phases, deposit, milestone and pre-launch balance.
- Launch support and add-ons: the bug-fix window after launch and optional care plans.
- Acceptance block: signatures and the date the project starts.
When to use it
Send it when a client wants a site that does not exist yet and you have had at least one call to understand the business. A good trigger is the moment you can write the sitemap from memory. If you cannot, run a paid discovery session first and price the build afterward.
Use it for brochure sites, portfolio sites, service-business sites with a contact or quote form, and small product sites. It also works for landing-page projects if you trim the sitemap to one page.
Do not use it when:
- The client has an existing site with traffic and rankings to protect. Use the website redesign proposal instead.
- The project is mainly an application with logins, dashboards or custom logic. Use the app development proposal.
- The client only wants ongoing updates to a site you already built. Quote that with a website maintenance SOW.
How to scope pages, CMS and content
Web projects go over budget in three predictable places, and the proposal is your chance to fence each one off.
Templates, not pages. A client hears "ten pages" and thinks ten designs. You know most sites run on three to five templates: home, standard content page, service detail, blog post, contact. Price the templates you design, then state how many pages you will populate. "Five templates, up to 15 pages populated with client-supplied content" is a scope. "A 15-page website" is a negotiation waiting to happen.
Content is the critical path. The build stalls when copy arrives late, arrives as a 40-page Word document, or never arrives. Pick one of two models and write it down. Either the client supplies final, approved copy for every page by a date before the build phase starts, or you add copywriting as a line item. If the client supplies images, specify format and minimum resolution. Add a clause that placeholder content will be used if material is late and the launch date moves by the length of the delay.
Functionality changes the price more than page count does. A contact form is trivial. A booking system, member area, multi-language setup or product catalog with variants is not. List every feature that sends data somewhere or depends on a third-party service, and price each one or mark it out of scope. "Newsletter signup connected to [EMAIL PLATFORM]" is a line. "Integrations as required" is a blank check.
On price, many independent designers quote small business sites in the low-to-mid thousands and larger custom builds well above that. Your number should come from the templates and features you counted, not from what the last client paid. The freelance pricing guide walks through turning an estimate into a fixed fee.
Finally, define "launched." Write down the browsers and devices you test on, the accessibility baseline you design to, and the length of the post-launch support window. Fourteen to thirty days of bug fixes is common. After that, changes are billed or handled under a care plan.
Customize it in your COLO workspace
In COLO Proposals you can rebuild this structure as a saved proposal template, with line items for each page template and feature, each carrying a rate, hours, tax and discount. Set an expiry date, export a PDF if the client wants to forward it, and let the client accept or decline from the client portal. An accepted proposal can be converted into an invoice, so the deposit line does not have to be retyped.
Once the build starts, set it up as a project with tasks for each phase in project management, and choose which tasks the client can see. Uploads, comments and chat stay attached to the project rather than scattered through email.
Common mistakes
- Quoting before you know who writes the copy. If that question is open, the timeline is fiction.
- Leaving the revision count vague. Say how many rounds apply at wireframe and design stages, and what counts as a round.
- Taking the final payment after launch. Once the site is live, you have nothing left to hold. Bill the balance on approval of the staging site.
- Bundling hosting into the build fee. It hides a recurring cost inside a one-off price and makes you the support desk forever.
- No expiry date. A proposal that sits open for three months will be accepted at last quarter's price.
FAQ
Q: What should a web design proposal include?
A short summary, a sitemap with page counts, the page templates you will design, the CMS and hosting setup, who supplies copy and images, a phased timeline, pricing with a deposit, and an acceptance block.
Q: How do I price a website in a proposal?
Price by page template and functionality rather than by hour. A five-page brochure site and a twenty-page site built from the same three templates can cost similar amounts, while a booking or ecommerce feature changes the price far more than page count.
Q: Who should write the website copy?
Decide it in the proposal. Either the client supplies final copy by a fixed date, or you quote copywriting as a line item. Waiting on copy is the most common reason web projects run late.
Q: Should hosting be part of my web design proposal?
List it separately. Quote setup as a one-off item and ongoing hosting or maintenance as an optional monthly add-on, so the build fee stays clean and the client can choose.
Q: How much deposit should a web designer ask for?
Many web designers take 30 to 50 percent to start, a milestone payment on design approval, and the balance before the site goes live. Keeping the final payment before launch means you are not chasing money after the domain points to the new site.