Consulting Proposal Template
A complete, ready-to-use consulting proposal in markdown — every section a real proposal needs, from executive summary to acceptance. Copy it or download it, fill in about 15 minutes of specifics, and send.
The template
# Project Proposal
**Prepared for:** [Client name]
**Prepared by:** [Your name / Studio]
**Date:** [Date]
**Valid until:** [Date + 30 days]
---
## Executive summary
[Two or three sentences a busy decision-maker can read on their own. Name the
problem in their words, state the outcome you'll deliver, and the headline
timeline and price.]
> Example: Northwind Labs needs a customer dashboard its support team can use
> without engineering help. This proposal covers design, build, and handoff of
> that dashboard over six weeks for a fixed fee of $24,000.
## Background & understanding
[Show you understand the situation. Summarize what you heard on the call: the
current state, what's not working, and why it matters now. Two short
paragraphs. This is what separates a proposal from a price list — it proves you
were listening.]
## Scope of work
**In scope**
- [Workstream 1 — e.g. Discovery & technical audit]
- [Workstream 2 — e.g. Design system and component library]
- [Workstream 3 — e.g. Frontend build and integration]
**Out of scope**
- [State plainly what you are *not* doing — e.g. backend API development,
content writing, ongoing maintenance after the support window. This single
list prevents most scope disputes.]
## Deliverables
| # | Deliverable | Format |
|---|---|---|
| 1 | [e.g. Audit findings & recommendations] | [PDF report] |
| 2 | [e.g. Design system] | [Figma file] |
| 3 | [e.g. Production frontend] | [Deployed app + repo] |
| 4 | [e.g. Handoff documentation] | [Markdown / PDF] |
## Timeline & milestones
| Phase | Milestone | Duration |
|---|---|---|
| 1 | Discovery & strategy | [1 week] |
| 2 | Design sign-off | [2 weeks] |
| 3 | Build | [2 weeks] |
| 4 | Review & handoff | [1 week] |
Estimated start: [Date]. Estimated completion: [Date]. Timeline assumes
feedback within [2 business days] at each review gate.
## Investment
| Item | Amount |
|---|---|
| [Fixed project fee] | [$24,000] |
| [Optional add-on] | [$3,000] |
| **Total** | **[$27,000]** |
**Payment terms:** [50%] to begin, [50%] on completion. Invoices due within
[14 days]. Work pauses on invoices [15+ days] overdue.
## Terms & assumptions
- **Assumptions:** [Client provides brand assets and content by the start of
Phase 2; one primary point of contact for approvals; access to required
accounts in week 1.]
- **Revisions:** [Two rounds] per phase are included. Additional rounds are
billed at [$150/hour].
- **Ownership:** On final payment, all deliverables and IP transfer to the
client. [Your Studio] may show the work in its portfolio unless agreed
otherwise in writing.
- **Cancellation:** Either party may cancel with [written notice]. Work
completed to date is billable.
## Next steps & acceptance
To proceed, approve this proposal by [date]. On acceptance I'll send the
kickoff schedule and the first invoice.
**Accepted by:** ______________________ **Date:** ____________ How to use this template
- 1
Copy or download the template
Use the Copy markdown or Download .md button to grab the full template.
- 2
Replace the placeholders
Swap the bracketed fields — [Client name], scope items, fees — for your engagement. Everything in square brackets is meant to be edited.
- 3
Tighten scope and deliverables
Delete anything that doesn't apply and be explicit about what's out of scope. A clear out-of-scope list prevents most disputes later.
- 4
Set your pricing and terms
Choose fixed-fee, hourly, or retainer, then state payment milestones and revision limits so there are no surprises.
- 5
Export a branded PDF
Paste the markdown into Markpdf, apply your brand kit, and export a client-ready PDF with your logo and colours.
- 6
Send it with a clear next step
Attach the PDF, restate the outcome in one line, and ask for sign-off by a specific date.
What to include in a consulting proposal (and why)
Each section of the template earns its place. Here's what goes in it and the mistake to avoid.
- Cover & prepared-for
- Client name, your name, date, and a validity date. Mistake: leaving off a "valid until" date, which lets a quote sit for months and go stale.
- Executive summary
- Three sentences: the problem, the outcome, the headline price and timeline. Mistake: making the reader hunt through the whole document to find what it costs.
- Background & understanding
- Restate what you heard, in their words. Mistake: skipping it — this paragraph is what proves you listened and separates you from a generic quote.
- Scope of work
- The workstreams you'll do, and an explicit out-of-scope list. Mistake: omitting out-of-scope — it's the single biggest source of "but I thought that was included."
- Deliverables
- The concrete artifacts and their formats. Mistake: conflating activity ("design work") with deliverables ("a Figma file and a component library").
- Timeline & milestones
- Phases with durations and review gates. Mistake: promising dates without stating your dependency on their feedback turnaround.
- Investment
- The fee, what it includes, and payment terms. Mistake: a bare number with no payment schedule or late-payment terms.
- Terms & assumptions
- Revisions, ownership/IP, cancellation, and the assumptions your estimate depends on. Mistake: leaving revisions unbounded.
- Next steps & acceptance
- Exactly how to say yes and by when. Mistake: ending without a clear call to action, so the proposal just sits.
Consulting proposal example
A filled-in snapshot for a fixed-fee analytics engagement. Numbers are illustrative — use your own.
Prepared for: Acme Retail · By: Rivera Analytics · Valid until: 30 days
Summary: Acme's marketing team can't see which channels drive revenue. This engagement delivers a single source-of-truth dashboard in 4 weeks for a fixed fee of $12,000 (illustrative).
Scope: data audit, warehouse model, and a 6-view dashboard. Out of scope: ad-platform management, ongoing reporting after handoff.
Deliverables: audit memo (PDF), dbt model (repo), Looker dashboard, 1-hour handoff session.
Investment: $12,000 fixed — 50% ($6,000) to start, 50% on delivery. (illustrative)
Fixed-fee vs hourly vs retainer
Fixed-fee works best when scope is well-defined. It's the easiest for a client to approve because the number can't move, and it rewards you for working efficiently. The risk is yours if scope creeps — which is exactly why the out-of-scope list matters.
Hourly fits open-ended or exploratory work where scope genuinely can't be pinned down. It protects you from creep but caps your upside and asks the client to sign a blank cheque, so pair it with an estimated range and a not-to-exceed ceiling.
Retainer suits ongoing relationships — a fixed monthly fee for a defined block of availability or deliverables. It smooths your income and the client's planning. Use a separate retainer proposal rather than this one when the work has no end date.
Whichever you choose, state it plainly in the Investment section and tie it to the outcome in your summary.
FAQ
- How long should a consulting proposal be?
- Long enough to cover scope, deliverables, timeline, price, and terms — usually two to four pages. Decision-makers skim, so lead with a short executive summary and keep each section tight. Depth belongs in the scope and deliverables, not in padding.
- Should I include pricing in the proposal?
- Yes. A proposal without a price forces another round of email and stalls the decision. State the fee, what it includes, and the payment schedule. If you're unsure of exact numbers, present a fixed fee or a clearly-bounded range tied to scope.
- Should I send a PDF or a Google Doc?
- Send a PDF for the final proposal: it looks finished, carries your branding, and can't be accidentally edited. Use a shared doc only when you genuinely want the client to comment or co-edit. Markpdf turns this markdown into a branded PDF in one step.
- What's the difference between a proposal and a statement of work?
- A proposal pitches the engagement and persuades the client to say yes. A statement of work (SOW) is the detailed, often contractual document that defines exactly what will be delivered once they have. Many small engagements combine them; larger ones keep them separate.
- How do I present the price without scaring the client?
- Frame it as an investment tied to the outcome you described in the summary, not as a cost. Anchor it to the value or the problem's price. Offering two or three options — a core scope and an expanded one — lets the client choose a size rather than approve or reject a single number.