Web Design & Development Proposal Template
Most web design proposals lose the deal in the scope section. The client reads "responsive website build" and pictures something twice the size of what you priced. This template fixes the page count, the revision rounds and the support window in writing, so the conversation about extra pages happens before you build them, not after.
Take the whole thing
The scope, deliverables, timeline and client questions — as plain text you can paste anywhere. No signup.
The scope, as written
I'll design and build a fast, mobile-first website that reflects your brand and turns visitors into enquiries. You'll get a clean, modern site — responsive, SEO-ready, and built on a CMS you can update yourself without calling me every time you change a price. Scope, revision rounds, and what's excluded are all stated below, so there are no surprises on either side.
What this work typically sells for
US$2,500–$9,999 for most freelance website projects
That band covered 57% of respondents in the survey below, with $2,500–$4,999 the single most common answer. The sample skews US and UK freelancers, so treat it as a ceiling reference in India or Brazil rather than a target — and note the survey itself is described by its authors as directional, not statistically representative.
What's included
- Discovery call + content brief (sitemap, page goals, tone)
- Wireframes + design mockups — 2 revision rounds included, where a round is one set of consolidated written feedback
- Responsive build, up to 5 pages, on a CMS you can edit yourself
- On-page SEO setup: meta titles, descriptions, alt text, sitemap, analytics install
- Cross-browser testing on current Chrome, Safari, Firefox and Edge, plus phone and tablet widths
- Launch, CMS handover walkthrough (recorded), and 30 days of bug fixes after go-live
- Not included: hosting, domain registration, premium plugins, stock photography, licensed fonts, and copywriting — these are third-party costs billed directly to you, and you own every account
Worth adding for this kind of work
- Page-count ceiling stated in the scope, so "just one more page" is a change order rather than an argument
- Content deadline named as a client obligation — the single most common cause of a stalled build
- Browser and device support listed explicitly (which versions you test, which you do not)
The timeline
- Sign proposal & pay deposit
A 50% deposit confirms your spot in my schedule and is non-refundable, as it holds build time I turn away other work for. I'll send payment details on WhatsApp.
- Discovery call + content handover
We align on brand, goals and structure over WhatsApp or video. Please send text, images and logo within 10 days of this call — the timeline below assumes I have them.
- Design mockups delivered
Mockups shared on WhatsApp. Send one consolidated set of written feedback within 5 working days and that counts as one revision round.
- Build phase
Development against the approved designs. I post progress on WhatsApp; design changes after approval are quoted as new work rather than absorbed into a round.
- Launch + handover
Site goes live on your hosting and domain. Final invoice is sent on WhatsApp, and full ownership of the site and design files passes to you when it clears.
- 30-day support window
Anything that doesn't work as designed I fix free. Message me on WhatsApp and I'll confirm whether it's a bug or a new request before I start.
Where this proposal usually goes wrong
Quoting a website without fixing the number of revision rounds.
Two rounds, named in the deliverables. A third is billable and the client knew that on day one.
Leaving "who writes the copy?" unanswered.
Say it in the proposal. Most overruns on a small site are the four weeks spent waiting for text.
Promising a launch date that assumes the client responds instantly.
Give durations from approval, not calendar dates — "Week 2 after sign-off", not "the 14th".
Questions clients ask about this work
Who owns the site, the domain and the design files?
You do — but ownership transfers on final payment, not before. The domain and hosting are registered in your name from day one, so you keep them whatever happens between us. Until the final invoice clears, the site stays on my staging environment and I hold the licence to the design files. I also keep the right to show the work in my portfolio and to reuse my own underlying code and components on other projects; nothing of yours is ever reused.
What counts as a bug during the 30 days, and what doesn't?
A bug is something that doesn't behave as designed and approved — a broken form, a layout collapsing on a phone, a link going nowhere. That's free and I'll usually fix it same or next day. A new request is anything we didn't agree: a new page, changed copy, a different layout, a new integration. Those I quote before starting. I say this upfront because "post-launch support" left vague is how both sides end up resentful in month two.
Which browsers and devices are covered?
Current versions of Chrome, Safari, Firefox and Edge, and phone, tablet and desktop widths. Internet Explorer and browsers more than two years old are out of scope — supporting them costs real time and, in every analytics account I've looked at recently, serves a fraction of a percent of visitors. If your audience is genuinely different, tell me now and I'll price it in rather than discover it at launch.
Why are you more expensive than the quote I got elsewhere?
Often I'm not, once you compare like for like. Cheaper quotes usually price the build alone, and the parts that decide whether a site actually earns anything — the content structure, the SEO groundwork, the testing across real devices, the handover so you're not dependent on me — arrive later as extras. Ask any competing quote three questions: how many revision rounds, who owns the files, and what happens after launch. If someone answers those as clearly as this proposal does and is still cheaper, take it. I'd rather lose the job than have you feel misled six weeks in.
What if I need to pause the project, or cancel?
Life happens and I'd rather you tell me early. A pause of up to 30 days is free; beyond that I have to give your slot away, and restarting means going back into my schedule at the next opening. If you cancel, the deposit is not refunded and you're invoiced for work completed to that point — you keep everything finished and paid for, with the design files handed over. No penalty beyond that.
What happens if an invoice goes unpaid, or if you become unavailable?
If an invoice sits unpaid past its due date, work pauses and deliverables stay on my staging site until it clears — I won't stop mid-page without telling you first on WhatsApp. On my side: if I'm ill or unavailable, I message you within 24 hours with a revised date, and for anything longer than a week I introduce you to a developer I trust and hand over the files and access at no cost to you. You are never left with a half-built site and no way in.
A template gets it written. Tracking gets it signed.
You already have the document — copy it above and send it however you like. What a copy cannot tell you is whether anyone read it. Send this same template from ClosingMoment and you will know the moment your client opens it, which sections they read, and how long they spent — so you follow up while they are still deciding.