A freelancer in Portland sends a web design proposal: two pages, a list of deliverables, a flat price at the bottom. Three days later the client replies with "we went with someone else." The freelancer assumes they were too expensive. They were not. The proposal was too generic to justify the price.
The proposals that close $10,000 projects do not look like invoices. They look like business cases. Every section answers one question the client is silently asking: "Why should I spend this much money with you?"
Here is the exact structure.
Section 1: The business problem (not the project brief)
Most proposals open with "Project Overview" or "Scope of Work." This is a mistake. It positions the document as a cost estimate rather than a solution.
Open instead with the client's business problem in their own words. If you had a discovery call (and you should have), pull directly from what they told you.
The Challenge
Right now, Thompson Plumbing is spending $2,400 per month on Google Ads, driving roughly 230 visitors to a website that converts at about 1.5%. That means you are paying $10.43 per visitor and getting 3 to 4 leads per month from that spend. Your competitors in the Phoenix metro are converting at 5-7% with modern, mobile-optimized sites. The gap between your current conversion rate and the industry benchmark represents approximately $8,000 to $12,000 per month in unrealized revenue.
This paragraph does more selling than the entire rest of the document. The client sees their own situation reflected back with numbers they recognize. They understand the problem is not "our website looks old." The problem is "we are bleeding money."
Section 2: The proposed solution
Now describe what you will build and, critically, why each piece matters to their business. Do not list features. Connect every deliverable to revenue.
Bad:
- 8-page responsive website
- SEO optimization
- Contact form
Good:
What We Will Build
A conversion-optimized website designed to turn your existing ad traffic into leads at 3-4x your current rate.
Mobile-first design. 74% of local service searches happen on mobile. The new site will load in under 2 seconds on mobile devices (your current site averages 6.8 seconds) and feature a persistent click-to-call button on every page.
Service area pages. Individual pages for each city you serve (Phoenix, Scottsdale, Tempe, Mesa, Chandler), each optimized for "[service] in [city]" searches. This targets the exact keywords your customers are typing.
Trust-building elements. Your 4.7-star rating with 280 Google reviews is a major asset that your current site does not surface. The redesign places reviews, licensing, and insurance badges above the fold on every page.
Lead capture system. Click-to-call, a 3-field contact form above the fold, and an emergency service banner that adapts based on time of day. No visitor should need to scroll to find out how to reach you.
Notice that every bullet connects to either revenue or conversion. The client is not buying pages. They are buying a system that turns ad clicks into phone calls.
Section 3: The ROI case
This is the section most freelancers skip, and it is the section that justifies the price. Place it before the pricing section so the investment number lands in context.
Projected Return
Based on your current traffic of 230 monthly visitors and an industry-benchmark conversion rate of 5-7%:
- Conservative estimate (5% conversion): 11.5 leads/month, up from 3.4
- Mid estimate (6% conversion): 13.8 leads/month
- Aggressive estimate (7% conversion): 16.1 leads/month
At your average job value of $3,200, each additional lead that closes is worth $3,200 in revenue. Even at the conservative estimate, 8 additional leads per month at a 40% close rate produces 3.2 additional jobs per month, or roughly $10,200 in incremental monthly revenue.
The website investment pays for itself within the first 30 to 45 days.
You do not need to guarantee these numbers. The word "projected" does the work. But showing the math transforms the proposal from "here is what it costs" to "here is what you gain."
Section 4: Three tiers, not one price
A single price forces a binary decision. Three tiers shift the question from "should we do this?" to "which option fits our goals?"
Investment Options
Essential ($5,500) 6-page responsive site, mobile optimization, basic on-page SEO, click-to-call integration, contact form, Google Analytics setup. 3-week delivery. 14 days of post-launch support.
Professional ($8,500) (recommended) Everything in Essential, plus: individual service area pages (5 cities), Google Business Profile optimization, review integration, speed optimization to sub-2-second load, conversion tracking setup, and 30 days of post-launch support with one round of data-driven adjustments.
Growth ($12,000) Everything in Professional, plus: dedicated landing pages for Google Ads campaigns, call tracking integration, monthly performance reports for 3 months, content strategy for 6 blog posts targeting local search queries, and priority scheduling.
Price the Essential tier at what you would have charged as your only option. Research on the compromise effect consistently shows that buyers gravitate toward the middle option when presented with three choices. The Growth tier exists to make Professional feel reasonable and to capture the 15-20% of clients who genuinely want the top package.
Mark the middle tier as "recommended." This is not manipulative. It is genuinely the best fit for most clients, and labeling it reduces decision fatigue.
Section 5: Timeline and process
Keep this short. Clients want to know when they will have a working site, not the details of your design sprint methodology.
Timeline
- Week 1: Discovery and content gathering
- Week 2-3: Design and development
- Week 4: Review, revisions, and launch
Total: 4 weeks from project kickoff. Kickoff begins within 5 business days of signed agreement and deposit.
Two things to note. First, include a specific start date trigger ("within 5 business days of deposit"). This creates urgency without being pushy. Second, do not overexplain your process. The client does not need to know about your wireframing tool or your staging environment. They need to know when the site goes live.
Section 6: Payment terms
State terms clearly and anchor them to milestones, not dates.
Payment Schedule (Professional tier)
- 40% at signing ($3,400): secures your spot and begins discovery
- 30% at design approval ($2,550): begins development
- 30% at launch ($2,550): site goes live
Accepted: bank transfer, credit card (3% processing fee applies), or check.
The 40/30/30 split protects you from scope creep and no-shows while keeping the per-payment amount manageable. Never accept 100% at completion. By that point, the client has the work and your leverage is gone.
For projects over $8,000, consider adding a monthly payment option. "3 monthly payments of $2,833" lands differently than "$8,500 upfront" even though the total is identical. Offering this proactively signals confidence and removes a common objection before it surfaces.
Section 7: What happens after launch
Most proposals end at delivery. The best ones show that the relationship continues.
Post-Launch Support
Your Professional package includes 30 days of post-launch support: bug fixes, minor text changes, and one round of conversion-rate adjustments based on the first month's analytics data.
After the initial support period, ongoing maintenance and optimization is available at $500/month and includes hosting management, monthly backups, security updates, performance monitoring, and one content update per month.
This does two things. It reassures the client that they will not be abandoned after launch. And it plants the seed for recurring revenue, which is where the real long-term profit in web design lives.
What to leave out
Your bio. The client already vetted you before requesting a proposal. A paragraph about your passion for clean code adds nothing. If you must include credentials, make it one line: "Over the past 3 years, I have built 40+ websites for local service businesses, averaging a 3.2x improvement in lead generation."
Technical jargon. "React framework with headless CMS and JAMstack architecture" means nothing to a plumbing company owner. Speak in outcomes: faster, more leads, higher conversion, better rankings.
A long list of add-on services. This is a proposal, not a menu. Present the three tiers and stop. You can upsell SEO retainers and content packages after the site launches and the client has seen results.
The proposal is a filter, not just a pitch
A well-built proposal does two things simultaneously. It closes the clients who are ready, and it filters out the ones who are not. If someone reads a proposal with clear ROI projections, three sensible pricing tiers, and a professional timeline, and still wants to negotiate you down to $1,500, they were never going to be a good client.
The proposal that closes $10,000 projects is the same proposal that repels $500 clients. That is a feature, not a bug.
Gathering the specific business data that makes proposals this concrete, things like site speed, conversion estimates, competitor benchmarks, and ad spend context, takes time when done manually. Tools like Reapify can surface much of this data automatically by auditing prospect websites and scoring them across 14 quality signals. But whether you collect the data by hand or with software, the principle holds: a proposal built on the client's actual numbers will always outperform one built on generic promises.
Related reading