Consultants · problem and fix
Consultant proposal win rate below 60%: how to draft and tailor proposal sections on Mac
A consultant proposal win rate below 60% often comes from sections that could fit any client. The fix is to tailor the problem, approach and proof for each buyer, then track every bid so you can see what changes the result.
The short answer
- Most low win rates trace back to sections written for your firm, not the client's problem.
- Tailor three parts first: the problem statement, the approach and the proof.
- Track every bid in one Excel table, and ask lost clients why in a short email.
- Use Copilot in Word for a first draft only if your Microsoft 365 plan includes it, then rewrite by hand.
- Follow your firm's rules on client data before you put any material into an AI tool.
What low win rates on consultant proposals costs you
Hours that do not win anything
The best hard number on this topic comes from academic grants, not consulting. A PLOS ONE survey of 195 academics found the average proposal took 116 principal investigator hours and 55 co-investigator hours. That is at least about a month of full-time effort. The study did not measure consulting bids, so treat it as a pattern, not a benchmark. Loopio's 2026 statistics article puts the average RFP response at 33 hours, down from 35.
Writing time that does not predict wins
In the same PLOS ONE survey, writing time was not related to whether a grant was funded. Academics who wrote more grants also received more funding, though cause could run either way. For you, more hours on a generic draft is less likely to help than a sharper target. Measure your hours per bid before you decide that more effort is the fix.
Margin that never shows up in a report
The sources give no dollar cost per proposal. The PLOS survey measured hours and weeks, and Loopio also measured hours. So estimate your own cost. Add up the hours of staff, partners and reviewers on each bid, then multiply by the rate your firm uses for that time. Put the total next to each lost bid in your log. Blank cells hide the cost.
Accuracy risk when AI drafts go unchecked
AI makes drafts faster, but speed brings a risk. Proposal facts often sit outside what AI does reliably, such as client history, past results, dates and staffing. The BCG and Harvard summary shows correct answers falling outside the tool's strength, while users trusted the output. A wrong fact that reaches the client costs trust, and trust is hard to win back during a bid.
Bids you were never going to win
Each bid takes staff time, even the ones you lose early. A bid you cannot staff or price often loses late, after most of the work has gone in. Loopio's averages also vary by company size. Enterprise teams report 39 hours per response, and small teams 27. Compare your own log with your own history, not with a headline average.
Why it happens
Firm-first writing
Many openings describe the firm: its history, its size and its methods. Buyers read those lines looking for signs of fit, and they find little. The fix is simple but takes discipline. Move the client's problem to the top, then add the firm's credentials in one short paragraph. Writers skip this step because the firm story is easier to write, and it is the part they know best.
Boilerplate copied from old bids
Old bids carry old sector examples, old client names and last year's team. Copy and paste works until a paragraph describes a different industry. Then the reader notices, and the proposal feels generic. Check each pasted paragraph for the sector, the client's name and the year. Replace anything that does not match the request in front of you.
Late starts that force rushed drafts
A proposal written in the final days has no room for research. The writer cannot pull the client's phrases from a call or check the problem against recent news. A rushed draft also gets less review. Start the problem statement as soon as the request arrives, even before the bid decision is final.
No record of why bids were lost
Without a log, every loss looks the same. Teams guess at the reason, or they blame price by default. The same weakness then repeats across bids. A simple table with a reason column breaks that loop, because the pattern becomes visible after a few months of entries.
AI drafts accepted without checks
Most proposal teams now use AI, so the tool is not the problem. The problem is a draft accepted as fact. The BCG and Harvard summary found users were more likely to be wrong outside the tool's strength, and the summary links this to over-reliance. Checking facts is the habit that matters most.
Bidding on work the firm cannot win
Some losses start before the first word. A request may ask for experience your firm does not have, or for a sector you rarely serve. Writing harder will not close that gap. Ask whether you have a real case, a named lead and a fair price before you commit to the bid.
How to fix it
These work with or without any app.
Log every bid in one Excel table
Open a new workbook in Excel and enter one row per bid. Use columns for client, sector, date sent, hours spent, the problem named in the request, result and reason. Select the range and press ⌘T to make it a table. Your win rate is bids won divided by bids submitted in the same period. Update the row the day you hear back. This needs no add-in and no subscription.
Rewrite the first page for the client
Open the request and highlight the phrases the client repeats. Put those phrases in your opening paragraph, in the same order they appear in the request. Name the problem, the deadline and the cost of waiting, if the client gave one. Then describe your first step. Keep the firm history to one short paragraph after that. Do this for every bid, including the small ones.
Build a section library in Word
Create one Word document for each problem type your firm sells. Under each heading, paste the paragraphs you have used and would defend in front of the client. Put the sector and year at the top of each paragraph as a label. When a new request arrives, press ⌘F, search for the problem, and start from the closest paragraph. Delete the labels before you send.
Use Copilot for structure, not facts
If your firm already has Microsoft 365 with Copilot, press Control+L on a blank line in Word and ask for an outline based on the request. Edit the outline by hand, then add the client facts yourself. Skip this fix if you do not have an eligible license. Without one, a blank page and your own outline work just as well.
Debrief every loss with one email
Within a few days of a loss, send one short email. Ask what the winning firm did that you did not, and which section changed the decision. Keep it to a question or two. Log the answer next to the bid, even if the client never replies. Use the answers to rewrite your library paragraphs for the next bid in that sector.
Set a bid or no-bid rule
Write a short list of questions the team answers before any bid starts. Does the request name a problem we have solved before? Can we name the person who will lead the work? Do we understand how the buyer will decide? If the answer is no to more than one, talk it through before writing. Hold to the rule even when the pipeline looks thin.
Read the draft aloud before you send
Use Speak selection on your Mac to hear the draft. Open System Settings > Accessibility > Spoken Content and turn on Speak selection. Then select the text and press the shortcut you set for it. Listen for lines that could fit any client. Those are the lines to rewrite first.
Many consultants start a new bid from last year's proposal. They swap the client name, update the dates and send it. That habit is the first place to look when your win rate slips. A proposal can be accurate and still lose, because the buyer could not find their own problem on the first page. Tailoring is less about rewriting everything. It is about changing what the reader sees first.

Why the first page decides the bid
Readers form a first opinion early, so the opening paragraphs carry more weight than their length suggests. Put the client's problem there, in the client's words. Use the exact phrases from the request for proposal, the email thread and the kickoff notes. If the client wrote margin pressure, do not write cost optimization. Mirror their language, then explain what you will do about the pressure.
The field is large and still growing. The US Bureau of Labor Statistics counted 1,075.1 thousand management analysts in 2024, and it projects 8.8% growth to 2034. Many firms bid for the same kinds of work, so a clear first page helps you stand out.
116 hours
Average principal investigator hours to write one federal grant proposal, from a survey of 195 academics. Not a consulting figure.
To Apply or Not to Apply: A Survey Analysis of Grant Writing Costs and Benefits (PLOS ONE)33 hours
Average time per RFP response in 2026, down from 35 hours, according to Loopio's statistics article.
Average RFP Win Rates & More: 38 Proposal Statistics (Loopio)84.5%
Share of correct answers without AI on a task outside the tool's strength. With GPT plus a prompt overview, it fell to 60.0%.
Navigating the Jagged Technological Frontier: AI wiki summary of Dell'Acqua et al.The three sections to tailor first
- Problem statement: use the client's words for the issue, the deadline and the stakes.
- Approach: tie each phase to an outcome the client named, not to your standard method.
- Proof: pick one past result that matches their sector and problem, and only if your contracts allow it.
- Team: name the people who will do the work and explain why they fit this problem.
- Fees and timing: match the structure to the format the client asked for.
Tailor the approach without rewriting it from scratch
Approach sections often go generic first. Teams keep one long methodology document and paste it in whole. Try a different setup. Keep one master approach with separate modules, such as a diagnostic, a pilot and a change program. For each bid, choose the modules the client needs, then rename them with the client's terms. Your method stays intact, and the text reads as if it was written for them.
A worked example of a tailored opening
Say the request asks how a regional bank can cut churn in its card business. A generic opening says your team brings proven frameworks to improve performance. A tailored opening names the card business, the churn problem and the timeline from the request. It then says what the first month of work will produce. The second version runs longer. It is also the one the reader can check against the request.
Proof needs the same care. Pick one past result that matches the client's sector and problem. Check your contract and your non-disclosure agreement before you name a client or share figures. If you cannot name the client, describe the situation without identifying details. A vague case study gives the reader nothing to test.

Build a section library, not a template
A template gives you headings. A library gives you text you already trust. Keep one Word document for each problem type, such as cost reduction, growth or regulation. Under each heading, store the few paragraphs you have used and can defend. Label each one with the sector and the problem it fits. When a request arrives, search the library with ⌘F before you open a blank page. You still edit everything, but you start from text someone checked.
Make the summary deck match the written proposal
Many bids include a short summary deck. Build it in PowerPoint for consultants, then copy the phase names from your approach section so the two match. Speaker notes are saved inside the deck, so a sent .pptx can carry them. Keep private notes out of any file that leaves your firm. For the steps, see how to add speaker notes in PowerPoint on Mac.
Use Copilot in Word for structure, not facts
Proposal teams are already using AI. Loopio's sixth annual RFP survey, run with APMP, found 68% of teams now use AI. That is double the prior year's average. Using a tool is no longer the question. The question is how carefully you check its output.
Word for Mac can draft with Copilot. Press Control+L on a blank line to open the Draft with Copilot dialog. Microsoft says the feature needs an eligible Microsoft 365 subscription or a Microsoft Copilot license. Its support page does not list a price. The Register reported an extra $3 per month for Microsoft 365 Personal and Family in January 2025, so check current pricing before you rely on it.
Use the first draft as a rough outline, not as a bid. Copilot in Word can rewrite selected text, and it shows suggested edits for review before adding them. Select a paragraph, press Control+L, and ask for a shorter version that names the client's sector. Then check every fact yourself.
Where AI helps and where it hurts
Dell'Acqua and colleagues ran a field experiment with 758 BCG consultants. Inside the AI's strength, consultants with AI were 25.1% faster and about 40% higher in quality. Outside that strength, the picture changed. Correct answers were 84.5% without AI, 70.6% with GPT alone and 60.0% with GPT plus a prompt overview. The summary suggests familiarity led people to over-rely on the tool. The original paper was not readable when this page was checked, so these figures come from a secondary summary.
- Let AI handle structure, headings and plain-English rewrites.
- Write client facts, figures, names and past results yourself.
- Check every number against its source before it goes in.
- Ask the tool what it is unsure about, then verify that part first.
- Never paste client material into a tool your firm has not approved.
Track wins and losses in Excel so the pattern shows
You cannot fix a win rate you do not measure. Open Excel for consultants on Mac, select your bid list and press ⌘T to turn it into a table. Use one row for each bid. Add columns for client, sector, date sent, hours spent, the problem named in the request, result and reason. Win rate is bids won divided by bids submitted. Keep lost bids in the same table, or the rate will look better than it is.
After a month, filter the table by sector and by problem type. Patterns show up quickly. You might find you win short, sharp bids and lose long ones. You might lose every bid where the client set a budget you never saw. Those are habits you can change. Write real reasons in the reason column, such as price, timing or no decision, not other.

Ask lost clients why, and log the answer
A debrief is the cheapest research you can do. Send the client one short note from Outlook for consultants on Mac. Ask what the winning firm did that you did not, and which section moved the decision. Keep the reply with the bid file. Many clients will not answer. The ones who do give you the words the buyer used to decide, and those words belong in your next draft.
Protect client data while you draft
Proposals often hold client names, staff details and figures covered by a non-disclosure agreement. Check your firm's rules and your client contracts before you draft or dictate with any AI tool. Lazur sends audio and the screenshot to AI providers to answer, and does not store them. Content is never used to train AI models. Your firm's policy still comes first. If the policy says no, keep that work in approved tools.
Mistakes that keep win rates low
- Writing the approach before the client's problem is clear.
- Opening with your firm's history instead of the client's situation.
- Reusing a paragraph from another sector without changing the examples.
- Leaving the reason blank after a loss.
- Letting an AI tool invent a case study or a result.
- Bidding on work your team cannot staff.
The last mistake costs the most time. A proposal you cannot staff is a proposal you should not send. Before you start, ask the delivery lead one question: can we name the person who will do this work? If the answer is no, change the bid or decline it.
What to do next
Start with the log. Add the bids you remember from the last stretch, even without exact dates. Next, pick the bid you are writing now and tailor only the problem statement. Compare the new opening with the old one. Send it, then record the result. After a few bids, look for one pattern and change one habit at a time.
Faster with Lazur
Where Lazur helps with low win rates on consultant proposals
Hold ⌥ ⌘ and say what you want. Lazur sees your Excel window. Lazur looks at your screen and answers out loud.
- 1
Hold ⌥⌘ and talk
- 2
Lazur looks at your screen and answers out loud.
- 3
You stay in Excel. Nothing to copy into a chat window.
More things to say in Excel
- “Lazur, what does this request want in the approach section?”
- “Lazur, point at the client's problem statement in this request.”
- “Lazur, walk me through making a table in Excel.”
- “Hold fn and dictate your call notes into the proposal.”
- “Lazur, draft a first version of this paragraph in our firm tone.”
- “Lazur, research this client's recent news and summarize it.”
Free for 3 days, then $18/month. Download for Mac
You say“What does this request want in the approach section?”
Lazur · explains what's on screenLazur answers out loud. You still write the section, and you check the answer against the request.
What consultants say to Lazur for this
Each one is a single hold of ⌥ ⌘.
“Lazur, what does this request want in the approach section?”
Lazur sees your screen when you hold the shortcut and answers out loud. You still write the section.
Explains what's on screen
“Lazur, point at the client's problem statement in this request.”
Lazur draws a circle and a label around the paragraph on your screen, so you find it fast.
Points at it
“Lazur, walk me through making a table in Excel.”
Lazur guides you one click at a time and waits for each click. It does not click for you.
Walks you through it
“Hold fn and dictate your call notes into the proposal.”
Dictation types clean text at the cursor in any app. Snippets and a personal dictionary help with client names.
Types what you say
“Lazur, draft a first version of this paragraph in our firm tone.”
Lazur drafts text and types it where your cursor is. Check every fact before anything goes to a client.
Drafts it
“Lazur, research this client's recent news and summarize it.”
Research runs in Lazur's own Chrome tabs and comes back with a summary and a report. Check the sources yourself.
Researches in the background
“Lazur, remind me to send the debrief email on Thursday.”
Lazur adds the reminder to Apple Reminders by voice, so the follow-up does not slip.
Handles the small stuff
A plan you can start this week
- Monday
Start the bid log
Open Excel and make a table of the bids you remember from the last stretch. Mark unknown results as unknown instead of guessing. Keep the same columns for every bid from now on.
- Tuesday
Ask the most recent losses why
Send one short debrief email to the latest client who passed on your bid. Keep it to a question or two. Log the answer next to the bid in your Excel table.
- Wednesday
Sort the section library
Create or open one Word document for your most common problem type. Paste in the paragraphs you can defend, and label each one with its sector. Test the search with ⌘F.
- Thursday
Tailor one live bid
Rewrite the opening, one approach module and one proof point for the next bid due. Use the client's words from the request. Read the result aloud with Speak selection before you send it.
- Friday
Review and pick one habit
Update the log with any results that came in. Look for one pattern across the bids, such as sector or reason. Choose one habit to change next week, and write it at the top of the library document.
Questions people ask
Is 60% a good win rate for consultants?
None of the sources on this page set 60% as a benchmark for consultants. Loopio's statistics article gives an average RFP win rate of 45% and cites 39% elsewhere. Compare your rate with your own history first, then with the kinds of bids you actually make.
How do I calculate my proposal win rate?
Divide the bids you won by the bids you submitted in the same period. Do not count bids you decided not to send. Use the same rule for every row, so the number means the same thing each month.
Can I use Copilot in Word on Mac for proposals?
Microsoft says Copilot in Word needs an eligible Microsoft 365 subscription or a Copilot license. On a blank line, press Control+L to open Draft with Copilot. Check your firm's license and data rules before you use it on client work.
Do I need to buy anything to tailor proposals?
No. Tailoring is a writing habit. The Excel log, the Word library and the debrief email work with tools most firms already have. Copilot and Lazur are optional.
Is it safe to draft client proposals with AI?
Follow your firm's policy and your client contracts first. Lazur sends audio and the screenshot to AI providers to answer, and does not store them. Content is never used to train AI models. If your firm says no, do not use AI on that work.
What if clients never reply to a debrief request?
Expect silence sometimes. Log the bid as lost with no reason instead of guessing. Ask again only if the relationship is warm. Your pattern will still show up across several bids.
Sources
- To Apply or Not to Apply: A Survey Analysis of Grant Writing Costs and Benefits · PLOS ONE · checked 2026-11-09
- Industry and occupational employment projections overview and highlights, 2024-34 · U.S. Bureau of Labor Statistics · checked 2026-11-09
- Average RFP Win Rates & More: 38 Proposal Statistics · Loopio · checked 2026-11-09
- Loopio Releases Sixth Annual RFP Response Trends and Benchmarks Report · Loopio · checked 2026-11-09
- Navigating the Jagged Technological Frontier: AI wiki summary of Dell'Acqua et al. · businessdatasolutions.github.io (secondary summary) · checked 2026-11-09
- Welcome to Copilot in Word · Microsoft Support · checked 2026-11-09
- Use Copilot in Word with a screen reader · Microsoft Support · checked 2026-11-09
- Copilot invades Microsoft 365 Personal and Family for an extra three bucks a month · The Register · checked 2026-11-09
Fix low win rates on consultant proposals with Lazur, free for 3 days
Hold a key and ask. Lazur sees your screen, points at the button and talks you through it, in any Mac app. No credit card.