A prospect asks for your proposal. You send over a Google Doc that lists some services, a rough timeline, and a total price. They say they'll "circle back." Two weeks later, nothing. You follow up. They've gone with another agency.
It probably wasn't the price. It was the proposal.
Clients make buying decisions based on how confident and organised you appear, not just what you're offering. A vague proposal signals a vague project. A clear, structured proposal that walks through scope, deliverables, timeline, and investment tells the client exactly what they're paying for and why you're the right team for it.
This guide covers what a solid agency project proposal includes, what separates winning proposals from losing ones, and gives you a free template you can download and start using today.
What a Project Proposal Is (and What It Isn't)
A project proposal is a structured document that outlines what you're going to do for a client, how you're going to do it, and what it will cost. It's a sales document and a scope-setting document at the same time.
It's not a legal contract.
The proposal comes before the contract. Once the client approves it, you convert the agreed scope and pricing into a formal agency contract and get signatures. Some agencies combine the two, but keeping them separate gives you more flexibility to adjust terms before locking anything in.
A good proposal does three things well: it confirms you understand the client's problem, it lays out your solution clearly, and it removes the guesswork from the buying decision.
What Separates a Good Agency Proposal from a Bad One
Most bad proposals fail in the same ways. Here's what the good ones do differently.
1. Scope is explicit, not implied
Weak proposals say things like "we'll handle the design." Strong proposals say "we'll deliver three homepage concepts, two revision rounds per concept, a mobile-responsive build in Webflow, and a 30-minute handoff call." The more specific the scope, the less room there is for scope creep, and the easier it is for a client to say yes.
2. They address the client's actual problem first
Before listing your services, a strong proposal briefly restates the client's situation and what they're trying to achieve. This confirms you listened during discovery and positions everything that follows as a solution to their problem rather than a generic services menu.
3. Pricing is broken down, not buried
A single lump sum invites negotiation because clients don't know what they're negotiating over. Line-item pricing (service, hours, rate, total) makes the cost feel earned. It also makes it easier to reduce scope if budget is tight rather than losing the deal entirely.
4. There's a clear next step
Every proposal should end with an explicit action: "To proceed, sign below and pay the 50% deposit." Clients who are ready to move forward need to know what to do. Proposals that end with "let us know if you have any questions" leave the decision open indefinitely.
What to Include in Every Agency Project Proposal
A complete proposal covers eight areas. Here's what each one does and why it matters.
Project Overview
Basic metadata: client name, agency name, project title, project type, preparation date, and who prepared the document. This section exists to confirm you're both talking about the same thing and to give the document a professional header. It also makes filing and retrieval easier when you have multiple active proposals.
Executive Summary
A short paragraph (3 to 5 sentences) that restates the client's situation and your approach. Write this last. It should read like a confident summary of everything below it, not a generic "we're excited to work with you" opener. Clients often read this section first to decide if they'll read the rest.
Project Scope
Three sub-sections: what's included, what's not included, and your assumptions. The "not included" list is the most underused tool in agency proposals. Explicitly stating that ongoing maintenance, copywriting, stock photography, or third-party tool costs are not in scope prevents misunderstandings and protects your margin. Assumptions cover things like "client provides all brand assets by [date]" — dependencies that need to be true for your timeline to hold.
Deliverables
A table listing what you'll produce, a brief description of each item, the format it'll be delivered in, and the due date. This is the most tangible part of the proposal. Clients read it closely. Be specific: "Webflow site build" is less useful than "10-page Webflow site: home, about, services, blog (template), contact, and 5 inner pages."
Timeline and Milestones
A phase-based view of the project with start and end dates, key milestones, and who owns each one. Even if your timeline will shift once work starts, having an initial structure shows you've thought through the project realistically. It also sets expectations around when clients need to provide feedback, approve deliverables, or supply materials.
Investment
A line-item breakdown of services, hours, rate, and total for each line. Follow this with the total project investment, payment terms, and the deposit amount required to begin. Three payment structures work well for most agency projects: 50% upfront and 50% on delivery, 33/33/33 (start, midpoint, completion), or monthly retainer billing for longer engagements.
For ongoing retainer clients, see the client onboarding process for how to structure the start of a recurring relationship.
Terms and Conditions
Keep this section concise. Cover four things: how long the proposal is valid (30 days is standard), your revision policy, when IP transfers to the client, and a basic confidentiality note. You don't need legal language here. Plain English is fine. The full terms live in your agency contract.
Sign-off
Two signature blocks: one for the agency, one for the client. Name, title, signature line, and date for each party. Some agencies also include a checkbox next to payment terms so the client explicitly confirms they've read and agreed. Once both parties sign, you move to the contract stage.
Project Proposal Template
The template below covers all eight sections in a fillable dark-mode PDF format, designed for agencies working across web design, branding, marketing, and development projects.
Download Free Project Proposal Template (PDF) →
The PDF includes:
- Fillable AcroForm fields for every section
- Pre-structured tables for deliverables, timeline, and investment
- Sign-off blocks for both parties
- An embedded JSON schema for AI-assisted completion
How to Customise This for Different Project Types
The template is built to work across project types with minimal changes. Here's how to adapt the key sections.
Web Design Projects
In the scope section, specify which pages are in scope (and the page count). In deliverables, list phases: discovery and wireframes, design concepts, revisions, development handoff, and launch. In timeline, include a separate phase for client review at each stage. Set a clear policy on what happens if the client misses a feedback deadline.
For web projects with a client portal component, note in the scope section which platform the portal will be built on and whether training is included.
Branding Projects
Break deliverables into discovery, concept, refinement, and delivery phases. List every asset that will be produced: primary logo, secondary marks, colour palette, typography guide, icon set, brand guidelines document. Be explicit about file formats: AI, PDF, PNG, SVG. Clients often don't know to ask for specific formats until they need them later.
Marketing Retainers
For retainers, replace the project-based timeline with a monthly deliverables list. State the billing cycle (invoiced on the 1st of each month, due within 14 days), the minimum commitment term, and the notice period for cancellation. Include a quarterly review checkpoint in the timeline section. This is where the payment terms section becomes especially important: monthly retainers should specify what happens if a payment is missed.
Development Projects
Scope is everything in development proposals. Specify technology stack, browser and device support, third-party integrations, and who is responsible for hosting and domain management. Break the investment table into discovery, architecture, development, QA, and launch phases. Include a line for post-launch support (even if it's a short warranty period) so clients aren't surprised when bug fixes outside the warranty are billable.
Common Proposal Mistakes That Cost Agencies Clients
Even experienced agencies lose deals to avoidable mistakes in their proposals.
Sending a proposal without a discovery call first. A proposal without prior conversation is a guess. Clients can tell. Run at least one call before writing a word. Your proposal should feel like a natural summary of that conversation.
Making the proposal about you. The opening pages of many agency proposals are about the agency's history, team, awards, and philosophy. The client cares about their problem. Lead with that. Save the agency overview for an appendix if you need it at all.
No expiry date. Proposals without a validity period stay open indefinitely, which means your pricing commitment stays open indefinitely. A 30-day expiry is standard and creates natural urgency without being pushy.
Attaching a Word document instead of a PDF. Word documents look unfinished and invite editing. Clients have copy-pasted scope from Word proposals into different agency documents and presented it as their own brief. Send a PDF. Lock the document. Use fillable fields for the parts you want them to interact with.
Leaving the next step vague. If a client likes your proposal but isn't sure what to do next, they'll pause. Be direct. "To kick things off, sign page 6 and send the 50% deposit to [account]." Give them the steps and the payment details in the same document.
Frequently Asked Questions
What should a simple project proposal template include?
At minimum: a scope section (what's in, what's out), a deliverables list, a timeline, a pricing breakdown, and a sign-off block. The more complex the project, the more you'll want to add an executive summary and assumptions section. For most agency projects, all eight sections in this template are worth including.
How is a project proposal different from a project proposal template word?
A Word template is a starting point for building a proposal. The document you send to clients should be a polished PDF, not a raw Word file. Word documents look unfinished and are easy for clients to edit. Convert to PDF before sending, or use a fillable PDF template like this one from the start.
How long should an agency project proposal be?
For projects under $20,000: 3 to 5 pages. For larger or more complex projects: 6 to 10 pages. Avoid padding. Every page should contain information the client needs to make a decision. Background on your agency, case studies, and team bios can go in a separate credentials deck if needed.
Should I include case studies in my project proposal?
Only if they're directly relevant to the project at hand. A case study from a similar industry or project type can reinforce your credibility at the right moment. A generic case study in every proposal just adds length. If you're going to include them, put them at the end of the document and reference them in the relevant scope or methodology section.
Can I use this template for a retainer proposal?
Yes, with adjustments. Replace the one-time project timeline with a monthly deliverables structure and add a recurring billing section to the investment table. Update the terms section to cover minimum commitment period and cancellation notice. Everything else (scope, assumptions, sign-off) works the same way for retainers as for project-based work.