A web design proposal does two things: it shows the client you understand their problem, and it makes the case for why you're the right person to solve it.
Most web design proposals fail at the first part. They jump straight to deliverables, timelines, and pricing without ever showing the client that you listened.
This guide covers every section your proposal needs — in the order that actually converts.
The Section Order That Works
1. The Problem (Not Your Services)
Open with what the client is facing, in their own terms.
If they came to you because their site looks dated and isn't converting leads, say that. If their site doesn't work on mobile, say that. If they're launching a new brand and have no web presence, say that.
One paragraph. No jargon. Show them you were listening.
This is the section most designers skip. It's also the one that separates proposals clients read from proposals clients skim.
2. The Proposed Solution
Now introduce your approach — not a list of features, but a direction.
What kind of site? What will it accomplish? What's the experience you're designing toward?
Keep this concise. You're not delivering a spec sheet — you're telling a story about the outcome.
3. Scope of Work
This is the detailed section. List exactly what you're delivering.
Discovery and strategy:
Client questionnaire and kickoff call
Competitive review
Sitemap and page architecture
Design:
Wireframes for key pages
Visual design (number of concept directions, number of revision rounds)
Mobile and desktop comps
Development:
Platform (WordPress, Webflow, Squarespace, custom)
Number of pages included
Contact forms, integrations, third-party tools
Speed and performance optimization
Content:
Whether you're writing copy or working from client-provided copy
Image sourcing or client-provided photos
Launch:
QA testing
Go-live support
Post-launch support window (if included)
Be specific. Vague scope leads to scope creep, which leads to disputes.
4. What's Not Included
List what you're explicitly not delivering.
Common exclusions: ongoing hosting, content writing (if not in scope), SEO strategy, e-commerce setup, third-party platform fees, future updates beyond the support window.
This section protects you. If it's not listed here, clients will assume it's included.
5. Timeline
Map out the project in phases with estimated durations.
| Phase | What happens | Duration |
|---|---|---|
| Discovery | Kickoff, questionnaire, sitemap | Week 1 |
| Design | Wireframes → visual comps → revisions | Weeks 2–4 |
| Development | Build, content entry, testing | Weeks 5–7 |
| Launch | QA, go-live, handoff | Week 8 |
Tie milestones to client deliverables too — when you need copy, photos, or approvals by.
A project without a timeline is a project without a deadline. Proposals with timelines close faster because they create urgency.
6. Investment
Present pricing clearly. Don't bury it.
Flat project fee works well for defined scopes. Present a total with a payment structure.
A common structure: 50% due at signing, 50% due at launch. For larger projects, split into thirds: signing, design approval, launch.
If you offer tiered options, present two or three — not five. Three choices is a decision; five is paralysis.
Example pricing block:
Standard — $3,500
5-page website, 2 design concepts, 2 revision rounds, Webflow development, mobile-optimized, 14-day post-launch support.
Growth — $5,500
8-page website, 3 design concepts, 3 revision rounds, blog setup, SEO-optimized pages, 30-day post-launch support.
Don't include hourly rate breakdowns in a proposal. Flat fees are easier for clients to approve and protect you from scope-time arguments.
7. Why You
This is the shortest section and should be.
Two to three sentences on your relevant experience, a link to your portfolio, and one client result if you have it.
No biography. No origin story. Just enough proof that the client feels confident moving forward.
8. Next Steps
End the proposal with a clear, specific call to action.
"To move forward, sign the attached contract and pay the project deposit by [DATE]. Questions? Reply to this email or schedule a call here."
Don't leave the close open-ended. Proposals without next steps die in inboxes.
Format and Delivery
Send proposals as a PDF. Not a Google Doc, not a Canva link that requires a login.
A PDF looks professional, displays consistently across devices, and can be forwarded to decision-makers without formatting issues.
Tools like FileCurrent let you attach a contract directly to the proposal — the client reviews, signs, and pays in one flow. No "I'll send the contract separately" delay that lets the deal go cold.
What to Include in the Contract (Not the Proposal)
A proposal is a sales document. The contract is the legal agreement.
Don't put payment terms, late fees, or intellectual property language in the proposal — put those in the contract. The proposal presents the work; the contract governs it.
For what belongs in the contract, see our web design contract template.
Frequently Asked Questions
How long should a web design proposal be?
Long enough to cover scope, timeline, and pricing clearly — short enough that the client reads it. Most proposals that work well are 2–5 pages. A 15-page proposal sends signals about how complicated the project will be to manage.
Should I include pricing in the proposal?
Yes. Proposals without pricing create a second round of back-and-forth that slows down the close. State your fee clearly, with the payment schedule.
How many revision rounds should I include?
Two rounds of design revisions is standard for most projects. Define what a revision is (changes to the approved direction) versus what constitutes a new concept or full redesign (additional fee). This is the most common source of scope creep in web design.
Should I send a proposal before or after a discovery call?
After. Never send a proposal without a conversation first. The proposal should reflect what you learned in the call — if it doesn't, it's a generic template the client will treat as one.
What if the client wants changes to the proposal before signing?
That's negotiation — it's normal. Keep track of what changes were made and make sure the final signed contract reflects the agreed scope, not the original proposal.
The Bottom Line
A web design proposal that wins has three things in common with the client's actual situation: it names their problem, proposes a specific solution, and makes the next step obvious.
Scope clearly, price directly, end with a call to action.
FileCurrent lets you attach a contract to your proposal so signing and payment happen in one step — 7-day trial, no card required.