Consulting Proposal Template: Three Pricing Options Beat One Number

A consulting proposal template is a decision-forcing device, not a document. Most of the free ones online are a cover page, an "about me" section, and a block for a single price, which is exactly the format that loses deals to silence. The client reads it, says "let me think about it," and you spend three weeks wondering whether they are thinking or gone.

Below is a structure that fits on four pages and answers the questions a client is actually asking while they read. It leans on a few opinions, and I will say why for each.

Open with their problem, in their words

Page one is not about you. It is two or three paragraphs restating what the client told you on the call: what is broken, what it is costing them, and what they want to be true in ninety days. Use their phrasing where you can. If the COO said "we keep re-doing the vendor onboarding," write "vendor onboarding gets redone."

This does two things. It proves you listened, which is rarer than it should be. It also gives the client a chance to correct you before you have priced the wrong project. A proposal that gets a "no, the real issue is actually..." reply is a good result. You just saved a scoping fight in week three.

Scope: say what is out as clearly as what is in

Write the deliverables as nouns a person could check off. "Current-state process map for vendor onboarding, up to 12 steps." "Recommended redesign, one document." "Two working sessions with the ops team, 90 minutes each." Then add a short list headed Not included. Implementation. Training. Anything touching their ERP vendor. Ongoing support after the final readout.

The exclusions list is the part consultants resist, because it feels negative. It is the cheapest scope-creep protection you will ever write. When the client asks in week five whether you can also look at the invoicing process, you point to the page they signed. You are not being difficult. You are using their own document.

Offer three prices

This is the opinion I hold hardest. Give the client three options instead of one. A narrow version, your recommended version, and a larger one. For example: diagnostic only at $6,000, diagnostic plus redesign at $14,000, and diagnostic, redesign and a 60-day check-in at $19,500.

A single number invites a yes-or-no decision, and "no" is the easy default. Three numbers change the question to "which one," which is a smaller commitment to make. The middle option, which is the one you want them to pick, is also easy to defend because it sits between two reference points. Some clients will pick the cheapest. That is fine. A small signed project beats a large unsigned one, and small projects expand when they go well.

The risk is that you underprice the narrow option and the client takes it. Price every tier so you would be glad to do it. If you would resent the cheap one, raise it or drop it.

Terms that belong in the proposal, not buried later

Put the payment schedule on the page where the price is. Half upfront, half at final delivery works for short projects. Monthly in advance works for retainers. State the invoice terms, whether that is net-15 or due on receipt, and what happens on a late payment. Mention the timeline, with a start date contingent on signature, and the dependencies you need from them: access to people, data, systems.

Dependencies are where projects quietly slip. If you need the customer export by the 3rd and it arrives on the 19th, say in the proposal that the schedule moves day for day. You will be glad you wrote it down.

Make signing the obvious next step

The last section should contain exactly one instruction. "To start, choose an option and sign below by Friday the 14th, and I will send the first invoice." Give a date. Proposals without an expiry sit forever, and a date creates a reason to answer. It does not have to be aggressive. Two weeks is normal.

Then make signing take under a minute. If the client has to print, sign, scan and email, a meaningful number simply will not. A proposal that turns into a signed agreement on the same page closes the gap between "sounds good" and "we are on."

What to cut

Cut the credentials section down to three lines and one relevant example. Cut the methodology diagram unless the client asked for it. Cut anything that begins "Our approach is rooted in." The client already decided to talk to you. They are now deciding whether the price and the plan are acceptable, and everything else is friction.

A realistic target is 800 to 1,200 words plus the pricing table. If it is longer, the extra length is probably hedging.

The template is the easy part

Having the structure above in a doc you duplicate each time is useful, but the weak point is what happens after the yes. The proposal numbers need to turn into a contract, the contract into a project with a budget, the project into time entries, and the milestones into invoices. If each of those is a separate file you retype, errors creep in, and the first one is usually that the invoice does not match the option the client picked.

That chain is the reason we built FocalVA's contracts, projects and invoicing to share the same record, so a signed option becomes the engagement you bill against. If that sounds like your workflow, see how it works for consultants and creatives. Either way, steal the three-option table and the exclusions list. Those two changes alone will do more than any redesign of the cover page.