A website design proposal template is a reusable structure for pitching a small business website: goal, scope, timeline, proof, price, and next step. Use it to state exactly what you will build, what you will not build, and what you need from the client. Below is the full structure with a filled-in sample, plus notes on length, proof, pricing, and timing.
I learned this the awkward way. On Fiverr I sent long polite proposals about me and almost nothing about the client's week after launch. And clients skipped to the price, got confused, and vanished. The fix was a clearer skeleton they could scan in two minutes.
What sections must I include so the client says yes?
A small business website proposal needs seven parts in this order: goal in client words, scope, timeline, proof, price, terms, and signature. Keep boilerplate after scope so the decision comes first. This order matches what most winning templates already use.
The pattern below is the whole template. Copy it, then read the notes under each later section before you fill it in.
| # | Section | What goes in it | Filled-in example |
|---|---|---|---|
| 1 | Goal | One paragraph in client words plus one measured baseline | You told me phone bookings drop after 7pm because the form takes six fields on mobile. Your homepage loads in 4.1s on mobile today. |
| 2 | Scope | Counted pages, templates, integrations, plus not included | 6 templates, 14 named pages, booking integration, contact form with 4 fields. Not included: copywriting, photos, hosting fees. |
| 3 | Timeline | Weeks with owner dependencies | Week 1: copy from you. Weeks 2 to 3: design plus build. Week 4: testing plus launch. |
| 4 | Proof | Max two relevant items | One bakery site with online ordering plus one paragraph on method. No logo dump. |
| 5 | Price | Bundled options with middle marked Recommended | Starter, Standard Recommended, Premium with launch support. See pricing notes. |
| 6 | Terms | Deposit, revisions defined, ownership | 50 percent to start, two consolidated revision rounds, client owns site plus domain at final payment. |
| 7 | Next step | One date, one signature link, one contact | Valid until Friday. Sign here to hold the Week 2 start. Reply with copy by Monday. |
Why seven? In vendor datasets, winners averaged about seven sections while losers averaged eight, with advice to keep only sections that help the decision (Proposify closing data). Guides converge on the same order: cover, problem, solution, scope, timeline, pricing, terms, next step (practitioner comparison).
For context on pipeline, I keep proposals tied to how I find work in the first place, which I wrote about in how agencies find clients. A proposal is easier to write when discovery already gave you the client's phrases.
How do I describe scope so nobody argues about it later?
State scope as counted nouns plus explicit exclusions plus client inputs with dates. Name every page or template, define what one revision round means, and list what you need from the client. Put this on one or two pages before the timeline.
Most scope fights I have seen were never about bad intent. They were about vague nouns. These 14 specific pages ends in a finished site. Roughly 10 pages ends in an argument, a point redesign buyer guides stress when they ask sellers to name inventory by URL (redesign scope guide). Count templates too, because 40 pages on six templates is less work than 12 bespoke pages, a distinction RFP guides make explicit (RFP scoping guide).
Use three blocks:
Included: numbered deliverables with names. Example: Homepage, Services index plus three service templates, About, Contact with four-field form, booking embed tested on mobile, 301 redirect map as CSV for redesigns.
Not included: copywriting, photography, logo design, hosting and licenses, extra pages beyond the count, app store work. Say it plainly. The highest-leverage lines are the ones sellers skip, which scope-creep templates keep repeating (scope of work pattern).
Dependencies: one point of contact, feedback within four business days, copy by week one, logins plus hosting access by kickoff. Add what happens if inputs slip: timeline moves by the same days.
Here is my theory, stated as a theory: a scannable scope summary may reduce misunderstanding because buyers skim. I have not seen a clean test that one page of scope lifts close rate by itself, so I treat layout as hypothesis. What would prove it is an A/B of identical scope in paragraph form versus counted form with exclusions. Until then I use both layers: a short checkable summary up front plus the full list in an appendix for complex builds.
For redesigns, add one risk block. Name URL inventory, keep or merge or retire decision per key URL, one-hop 301 map tested in staging, content responsibility, and who watches traffic after launch. Technical guides agree redirects are often the most important redesign item (HubSpot redesign SEO), and buyer-side comparisons warn that the cheapest quote can look cheap by omitting migration work (buyer comparison guide). For a low-risk refresh with no URL changes, keep this to one line about parity plus backup. For a new build, swap it for sitemap plus starter structure.
How long should my proposal be for a small business site?
Keep it short enough to send fast and long enough to remove doubt: about three to six pages for jobs under 10,000 dollars, six to twelve for larger custom builds. For a simple brochure site, three to five pages is often enough. Push detail to an appendix.
The datasets point the same way without agreeing on an exact number. One benchmarking synthesis reports six to eight pages closing at about 48 percent versus about 24 percent for 20-plus pages in its sample, with average reading time falling from over seven minutes to about three and a half as length grows (benchmark synthesis). A separate vendor analysis of 2.6 million proposals reports about a 50 percent chance for five pages versus about 35 percent for 30 pages (proposal length analysis). I read those as correlational, not causal: bigger deals need more proof and attract more stakeholders, which also changes length.
Practitioner interviews note freelancers often win with one to three pages while agencies use four to eight, with one studio staying under five pages including cover (Wix studio interviews). Deal-size bands agree: small brochure work at three to five pages and custom commerce at ten plus, always with a skimmable summary (length bands guide).
What proof can I add when I have few past projects?
Show max two proofs, closest match first, each with deliverable plus constraint plus outcome plus one link. If you have no match, show reasoning: a brief audit of their site, your method in four lines, and an offer of paid discovery that produces a portable plan.
Buyers hire confidence you can solve their problem, not a gallery of ten links. That helps newcomers more than they think. A bakery owner I built a site for cared less about my homepage hero than about whether I noticed her booking form asked for too much on a phone. And that is the shape to copy: one screenshot, one baseline, one fix.
A useful substitute is a mini audit tied to their goal. Check homepage-level facts you can observe directly: does the tap-to-call work, is there a booking button, is the form short, does HTTPS hold, does the footer say 2015. LeadsAgent does this kind of homepage check at scale when prospecting, covering status, platform and outdated signs, mobile HTML issues, conversion paths, and speed on a shortlist, which is handy for finding outdated sites before the call. I use the same lens manually in proposals because it gives me one honest number to open with.
If you go the paid discovery route, keep it small and portable. A survey of 208 web designers found only about 15 percent charged for discovery yet those who did were about twice as likely to land larger projects in that sample (pricing survey). I treat that as survey signal, not proof, because confident sellers self-select into charging. What would settle it is a controlled comparison by segment, which I have not seen.
Here is what I suspect is going on, framed as hypothesis: diagnosis may build trust faster than history when history is thin. The test is simple: try a free micro-audit versus paid discovery across similar leads and track replies, calls, and closes separately for warm versus cold. Expect friction on cold outreach when you ask a stranger to pay for diagnosis. For more on opening those cold conversations, see cold outreach scripts.
If conversion evidence is your angle, the guide to selling websites to local businesses pairs well with this section because it frames proof around bookings and calls rather than pixels.
How do I present price so it looks fair and clear?
Show bundled options with outcomes, put Recommended on the middle, and place pricing after value at about two thirds through. Use a single fixed price only when scope cannot vary, for renewals, or when an RFP demands one number.
The mechanism is choice, not padding. Bundles avoid line-trimming where buyers delete hours to cut cost. One vendor compilation citing about 25,000 proposals reports bundled acceptance around 47 percent versus itemized around 34 percent (pricing compilation). I cite that as a vendor report, not a law, because sampling and controls are not published and a critique of generic lift figures makes the same warning (pricing critique). What feels solid is the direction: describe what each tier is for, build middle-out, and make premium a credible anchor rather than a decoy stuffed with filler.
| Approach | When to use it | Example for a 5,000 dollar site |
|---|---|---|
| Three bundled tiers | Flexible scope, buyer can choose depth | Starter 3,400, Standard Recommended 5,000, Premium 7,800 with 30-day launch support |
| Single fixed price | Fixed spec, renewal, RFP demands one number | Website redesign, 14 named pages, 5,200 fixed, two revision rounds |
| Never | Hourly for a full build, or padding tiers to push middle | Avoid: 60 hours times 90 dollars with no outcome tied to each block |
Keep deposits boring and clear: 50 percent to start is common for small builds, with the rest tied to demo and launch. Name revision math: two consolidated rounds means all feedback in one document per round, structural changes count as new scope, copy changes after approval count as extra. And tie payment to the same proof you showed earlier, so price reads as the cost of the outcome they already want.
If budgets are the worry, it helps to qualify before you price. I wrote about finding owners who can actually pay in finding local leads, which is the step before any tier table matters.
For a stronger close after pricing, try LeadsAgent free at leadsAgent.io/download when your next proposal needs real audit evidence: run a homepage check for outdated platform, HTTPS, and conversion gaps, then paste one baseline into the goal section instead of guessing.
When should I send the proposal after the discovery call?
Agree the send date on the call, send a five-line recap within two hours, then deliver a signable proposal quickly, often within one to two business days when scope allows. Book the 20-minute walkthrough before you hang up, then follow up the same day it gets opened.
Speed data is directional but messy. One compilation citing vendor datasets reports about a 42 percent conversion lift when proposals go out within 24 hours with faster signing times (statistics compilation). Another benchmark reports most winners opened within two hours and a large share closed within a day of opening, with unopened proposals after five days rarely closing (benchmark synthesis). I read those as qualified-buyer effects as much as speed effects: hot deals both move fast and close. Still, delay compounds. Enthusiasm decays daily and the first credible proposal frames how later ones get judged, a point practitioner playbooks make explicitly (send-timing guide).
So use a cadence. On the call, confirm budget range, decision date, and who else decides. Within two hours, send recap: goal, must-haves, start window, walkthrough time. Walk through live for 20 minutes, then send signing link plus PDF. If it sits unopened, nudge once with one new line of value.
For timing context by niche, the plumber outreach notes are useful because trades often decide fast once proof and price are clear. Adjust slower for larger redesigns with more stakeholders.
A softer next step if timing keeps slipping: get a cleaner shortlist before discovery at leadsAgent.io/download. Finding businesses with no site, a broken listing page, or an outdated footprint means your recap writes itself and your proposal arrives while the pain is fresh.
FAQ
Should I attach the proposal as PDF or send a link? Send both. Use a trackable signing link as the main action so you know when to follow up, plus a PDF for forwarding to other deciders. Then walk through the key pages live instead of letting the document defend itself alone.
Do realtor or nonprofit sites need a different proposal? The skeleton stays the same, but swap two lines. For realtor sites, name IDX or listings integration, photo galleries, and lead routing. For nonprofit sites, name donation flow, event pages, and accessibility basics. Keep both as prose tweaks, not separate templates, unless volume justifies it.
What if the client asks for unlimited revisions? Offer two consolidated rounds with a clear definition and a change-order rate after that. Explain that consolidated means all feedback at once in one document. Most disputes drop once revision math is written down.
Can I reuse the same template for redesign and new build? Reuse the seven sections, but change the scope block. Redesigns need inventory, redirect ownership, and content parity. New builds need sitemap, fresh information architecture, and starter visibility basics. For background numbers on businesses without sites, see businesses without website statistics.
