A consulting proposal template should split the assessment from the implementation, say what the client gets at each phase, what you need from them and what you won't promise. Below is the full template filled in with a $12,000 assessment, the three ways to bill for consulting and what to cut before you send it.
What does a consulting proposal need that a service proposal doesn't?
Five things a regular service proposal template leaves out, because you're selling a recommendation, and the client's team does the execution:
- An assessment phase with its own price. The client buys the answer to "where is the problem" first, then decides whether they want help fixing it.
- Deliverables that are decisions, not hours. "40 hours of consulting" doesn't tell the COO what lands on the table. A report, an action plan and a readout meeting do.
- What you need from them. Consulting stalls without data access, interviews and calendar time. If the proposal doesn't say so, the delay becomes your fault.
- What you won't promise or do. You recommend; the client decides and executes. Put it in writing before someone holds you to an outcome that depended on their own people.
- Confidentiality. You'll see margins, payroll, vendor contracts and internal problems. The client wants to know, in writing, what happens to all of it.
What does a filled-in consulting proposal look like?
The example is made up: an operations consultant hired to find out why Northfield Supply, a regional building-materials distributor, started shipping late. Swap the field and the numbers. The order and the clauses work for finance, sales, HR or marketing consulting.
1. Cover
Order-to-delivery assessment · Northfield Supply · prepared for Dana Reyes, VP of Operations · valid for 15 days from the date sent.
2. What we heard
On our September 12 call, you said average order-to-delivery time went from 2 to 4 business days over the past year. Expedited freight to cover late orders runs about $20,000 a month, and the shipping team is already at capacity. The working theory inside the company is that you need more trucks. Nobody has measured where the extra 2 days show up.
Why: these are the client's numbers, in the client's words. This section proves you listened, and it sets up the pricing math later.
3. The question this assessment answers
Between the order coming in and the truck leaving, where are the extra 2 days, how much of the delay does each cause account for, and which changes bring delivery back to 2 business days?
Why: one question, written so it can be checked. At the end of the project, the client knows whether it was answered.
4. Phase 1: assessment (4 weeks)
- Week 1: 45-minute interviews with 8 people (sales, picking, shipping, finance and 2 freight carriers) and a review of order data in your ERP.
- Week 2: time measured for each step on 200 orders from the last 90 days, from order entry to signed delivery.
- Week 3: root-cause analysis and how much each cause contributes, reviewed with your point person.
- Week 4: a 2-hour readout with the leadership team and the final report.
You receive a report of up to 25 pages with the current process map, the measured causes and a 90-day action plan. Actions come in priority order, each with a suggested owner. You also get the leadership readout and 30 days of email questions after delivery.
5. Phase 2 (optional): implementation support, 3 months
Your team runs the plan. We support it: a weekly call with your point person, a monthly session with leadership, plan revisions when a metric goes off track, and average delivery time tracked every week. Up to 10 hours a month; unused hours don't roll over. Either side can end the retainer with 30 days' notice.
Phase 2 starts only if you want it, after you've seen the report. Scope follows the action plan, and the price holds for 30 days after the report is delivered.
6. What we need from you
- Read-only access to the ERP and an export of the last 90 days of orders by business day 3.
- All 8 interviews scheduled within week 1.
- A point person with 2 hours a week for the length of the project.
A delay on any of these moves the timeline by the same number of days, at no extra cost for up to 10 business days.
7. Not included
- Selecting, buying or implementing software (ERP, routing, inventory).
- Negotiating with carriers on Northfield's behalf.
- Making the changes in the plan during phase 1.
- Hands-on training for your staff.
- Hiring or termination decisions.
The assessment delivers the measured causes and the plan. Decisions and execution belong to Northfield, so this proposal does not promise a final delivery time.
8. Confidentiality
Your data and the interviews are used for this project only. In the report, quotes appear without the speaker's name. Nothing goes out with Northfield's name on it, including as a case study, without your written OK. If you have your own NDA, we'll sign it before week 1.
Why: the same rule applies to the case studies you show in this proposal, which need your past clients' OK. How to pick and write them is in how to use case studies in a proposal.
9. Fees and payment terms
- Option A: assessment. $12,000. A $6,000 deposit on signing and $6,000 on delivery of the report, net 15.
- Option B: assessment + implementation support. $25,500. The $12,000 assessment on the same terms, plus a $4,500 monthly retainer for 3 months, invoiced on the 1st, net 15.
Travel outside your metro area is billed at cost, with receipts, and approved in advance.
10. Next steps
Pick an option, accept the proposal and name your point person. We start the Monday after you accept, and the ERP access request goes out the same day.
Should the assessment and the implementation be in the same proposal?
Yes, as two options with separate prices. The client can say yes to the smaller decision without saying no to you. And the implementation price is already on the table when the report lands, so you don't start a new sale from scratch.
Price the implementation by time, not by outcome, because the plan doesn't exist yet when you write the proposal. That's why phase 2 has a short price window and the line "scope follows the action plan." If the assessment finds something else, you rewrite phase 2 without breaking a promise.
Should you bill consulting by project, on retainer or by value?
Bill by project when the scope has an end, on retainer when you're selling ongoing support, and by value when the client knows what the problem costs. In the template above, the assessment is a fixed project fee and phase 2 is a 3-month retainer.
| Model | Use it for | The proposal says |
|---|---|---|
| Fixed project fee | Scope with an end | Deliverables, dates, payments |
| Monthly retainer | Ongoing support | Hours per month, rollover, notice |
| Value-based | Client knows the cost | Their number and the math |
On a fixed fee, payments are tied to milestones. On a retainer, the proposal states what happens to unused hours and how much notice ends it. On value-based, you're paid for the work, and the math uses the client's number.
The value math uses the client's number, not a savings figure you estimate. Northfield said expedited freight costs about $20,000 a month; the assessment costs $12,000, or 60% of one month of the problem. Put that math in the fees section. The client checks the arithmetic instead of taking your word for a result.
Leave hourly billing out of the assessment: the client starts watching the clock instead of the deliverable, and you earn less the faster you solve it. For how to present the number without losing to a cheaper bid, see how to price services in a proposal. On a five-figure engagement, the order (problem, root cause, strategy, scope, investment) is laid out in high-ticket proposal structure.
In Nepfy, that math goes in the Investment section exactly as you typed it: "Write with AI" never writes a price, and the extension never pulls a figure from a meeting transcript. After you send, the proposal detail shows whether any visit Reached the price, so you know the client read the math before you call. See what tracking shows.
What should you cut from a consulting proposal?
Cut anything that doesn't help the client decide. These are the parts that make a consulting proposal long without making the decision easier:
- The methodology essay. One line per phase on what you do and what they get is enough. The framework diagram can wait for the readout.
- The firm history and team bios. Two sentences on who does the work, then the case studies that match this problem.
- Hourly line items on the assessment. They invite the client to negotiate hours instead of scope.
- Outcomes that depend on their team. "Delivery time down to 2 days within 90 days" or "freight spend cut in half" is a promise you can't keep alone. Promise the deliverable, the date, the method and how it gets measured.
- Vague deliverables. "Insights and recommendations" says nothing. Name the report, its page cap, the plan and the meeting.
- Ten pages of legal terms. Liability, termination and IP belong in the consulting agreement, not in the document the buyer reads to decide.
If you want to share risk, tie part of the fee to a metric with a baseline, a measurement date and who measures it, and write it into the agreement.
How do you send a consulting proposal and see how it's read?
In Nepfy, the proposal is a web page you send as a link. The Minimal template already comes with sections for the challenge, scope, timeline, cases and investment, so the example above fits in as is: you fill it in instead of building it.
Three parts of the product fit consulting work:
- The client's numbers stay locked. The proposal quotes their internal data. The link can have a password and an expiration date; after that date, anyone who opens it sees an expired-link page and the proposal shows as Expired.
- The client picks the option in the link. The investment section can show "Assessment" and "Assessment + implementation," and they pick one when they accept, without creating an account.
- Your discovery call becomes the draft. On Pro, the extension reads live captions in Google Meet, Zoom on the web and Teams on the web, and never records audio or video. It creates a proposal from the meeting, and you still type the price yourself.
For the leadership readout, Present mode turns each section into a slide, with speaker notes in a separate window only you see.
After you send it, you see how many times the proposal was opened, how far it was read and whether anyone reached the price, section by section. Visits are anonymous: you know it was opened, not by whom. Acceptance captures a name, signature and timestamp; it shows agreement and doesn't replace your consulting agreement.
See how the extension turns a call into a proposal.
Start free: 14 days of Pro, no credit card.
Frequently asked questions
Should I offer a free assessment to win the implementation work?
Charge for it. The discovery call before the proposal is free; the assessment is the work itself, with interviews, measurement and a plan. If you want a lower barrier, shrink the phase 1 scope instead of dropping its price to zero.
Do I still need a consulting agreement if the client accepts the proposal?
Yes. The proposal covers scope, price and terms; liability, termination, confidentiality and who owns the work product go in the agreement, and it's worth having a lawyer review it.
Can I use the client as a case study afterward?
Only with written permission. Build it into the confidentiality clause and ask right after you deliver the report.
What if the client wants implementation without an assessment?
Write down the assumptions you're making in place of the assessment and schedule a scope review in week 2. If the assumptions don't hold, scope and price get revised there, not at the end of the project.
