Lost Bid Tracking: Use Your CRM to Learn Why You Lose
Ask a contractor why they lost their last ten bids and the answer is almost always the same: “We were high.” Ask them to prove it and the room goes quiet. Nobody wrote it down. The opportunity was dragged to Lost, the reason field was skipped, and the lesson went out the door with it.
That is a fixable problem, and it is a CRM problem more than a sales problem. If every lost bid carried a reason, a competitor and a price gap, you would know within a quarter which work you should stop chasing and which work you lose for reasons you can control. This guide shows how to set that up so your team actually uses it.
Table of Contents
“We Were High” Is Usually a Guess
Price matters, but it is rarely the whole story, and contractors often do not know the real story at all. A 2014 bid cost survey by MarketingWorks with Professor Will Hughes of the University of Reading, summarized by Constructing Excellence in February 2016, found:
The reason was unknown for 15% of lost bids and 11% of won bids.
About half of the reasons given for losing were price-related.
21% of losing-bid responses cited a combination of factors.
So roughly half the time, something other than price, or price plus something else, decided the job. The author’s conclusion was that both owners and bidders undervalue feedback, and bidders without facts on why they lose “may repeat mistakes or bid for work they cannot win.”
Know Your Bid-Hit Ratio First
Before you track why you lose, track how often. Your bid-hit ratio is bids submitted divided by bids won, written as X to 1. Bridgit’s summary of George Hedley’s survey of more than 5,000 contractors gives these typical ranges:
Work type | General contractors | Subcontractors |
|---|---|---|
Public works | 6:1 to 10:1 | 7:1 to 11:1 |
Private bid work | 4:1 to 6:1 | 4:1 to 6:1 |
Negotiated work | 2:1 to 4:1 | 3:1 to 4:1 |
Design-build | 2:1 to 4:1 | 3:1 to 4:1 |
The same summary notes that fewer than 6% of contractors know and track their ratio. Sunflower Bank’s guidance adds that for public works the ratio should not exceed 10 or 11 to 1, because “higher than 11 to 1 will cost your company too much in estimating expenses.”
The ratio tells you that you have a problem. Lost reasons tell you what the problem is. If you have not built a bid pipeline yet, start with our bid pipeline management framework.
Build a Lost Reason List That Fits Construction
Generic CRM loss reasons like “budget” and “timing” do not tell an estimator anything. Use a short list in your own language. Keep it to eight or fewer so people actually pick one:
Price: outside 5%. We were clearly high.
Price: within 5%. We were close. Something else likely tipped it.
Scope or qualification gap. Our exclusions or clarifications hurt us.
Schedule. Our duration or start date did not work.
Team or experience. The owner preferred another team or résumé.
Relationship. The job went to an incumbent or preferred contractor.
Project cancelled or on hold. Nobody won.
Unknown. We asked and did not get an answer.
Splitting price into “outside 5%” and “within 5%” is the single most useful change. A loss by 1.5% is a different problem from a loss by 12%.
The Fields to Capture on Every Lost Bid
A reason alone is not enough. Add a few custom fields to the opportunity so the data can be sorted later:
Lost reason (dropdown from the list above)
Winning contractor (text)
Our number and winning number, if known (currency)
Gap percentage (number)
Project type, size band and delivery method (dropdowns)
Estimating hours spent (number)
Did we ask for feedback? (yes or no)
Bridgit recommends segmenting bid-hit data by project type, size, location, new construction versus remodel, negotiated versus bid, and owner. If those fields do not exist on the record, you cannot segment anything later.
Set It Up in Your CRM
In GoHighLevel, marking an opportunity as Lost prompts for a lost reason from a dropdown, and you can add your own reasons. Its own help documentation notes a catch: clicking Cancel still marks the opportunity lost without a reason. That is how blank data creeps in.
Close the gap with process and automation:
1. Make the reason part of the close-out
Write the rule down: no bid moves to Lost without a reason and a competitor. The estimator who owns the bid fills it in.
2. Use a workflow to catch blanks
Trigger a workflow when an opportunity status changes to Lost. If the reason or competitor field is empty, create a task for the estimator due in two business days.
3. Automate the feedback ask
The same workflow can send the estimator a reminder to call or email the owner or GC for feedback. Keep the ask short: “Thanks for the opportunity. Would you share where our number landed and what drove the decision?” The proposal follow-up process you already run is the natural place to add this step.
4. Build the dashboard
HighLevel’s dashboard widgets include “Lost Opportunities By Reason,” Won and Lost Opportunities counts, and “Lost Opportunity Value.” Its documentation also notes a reporting detail: the Status Change date reflects the most recent status change, so for stable historical win and loss counts, use Created On with a Status filter.
Turn the Data Into Bid Decisions
Data you never look at is just typing. Put a 30-minute lost-bid review on the calendar once a month with your chief estimator and whoever makes go/no-go calls. Look at three things:
Where you lose on price by more than 5%. If it clusters in one project type or one owner, stop bidding it or reprice your approach.
Where you lose within 5%. These are winnable. Look at scope clarity, schedule and team.
Where the reason is “Unknown.” If that bucket is bigger than any other, your feedback habit is the first fix.
Feed what you learn straight back into go/no-go. Bridgit’s summary puts it simply: “Play where you win the most.” Pair this review with your bid cycle pipeline reports and you have a real picture of where estimating hours turn into revenue.
Common Setup Mistakes to Avoid
Most lost-bid tracking fails in the first 60 days, for the same handful of reasons:
Too many reasons. A dropdown with 20 options gets “Other” picked every time. Eight is plenty. If a new pattern shows up, add one reason, not five.
No owner. If “the team” fills in lost reasons, nobody does. Assign it to the estimator of record on each bid.
Mixing “no bid” with “lost.” A job you declined is not a loss. Give declined invitations their own status or stage so they do not distort your ratio.
Tracking only GC-level wins. Subcontractors often bid the same project to several GCs. Track each GC bid as its own opportunity, tied to the project, so you can see which GCs actually award you work.
Never closing the loop. If the owner or GC does share where your number landed, record it right away. A gap percentage entered three weeks later is a guess again.
Skipping won bids. Ask why you won, too. Constructing Excellence’s summary found that the reason was unknown for 11% of won bids. Knowing what worked is as useful as knowing what did not.
None of these need new software. They need a written rule, a dropdown and a workflow.
What I’ve Seen Inside Contractor Shops
From the office side of construction, the shops with the worst lost-bid data are not lazy. They are busy. The estimator finishes one bid at 2 PM and starts the next at 2:05. Nobody is going back to fill in fields on a job that is already gone.
That is exactly why this belongs in the CRM and not in someone’s memory. When the workflow creates the task and sends the reminder, the habit holds even in the busy season. I am an advocate for this kind of automation because it does the follow-through that busy people skip.
The other pattern: the first time a shop looks at three months of honest lost-bid data, someone is surprised. Usually it is a project type the owner loves chasing that has never once been profitable to bid. That one insight tends to pay for the whole setup.
Next Step
If you want lost reasons, feedback workflows and win-rate dashboards set up in your CRM without building it from scratch, see the R.CS product lineup or call (219) 600-5908.
Sources
Philip Collard, “Bid Cost Survey Blog 2: Improving the win rate,” Constructing Excellence, February 4, 2016: constructingexcellence.org.uk
Bridgit, “5 Tips for Tracking and Improving Your Bid-Hit Ratio”: gobridgit.com
Sunflower Bank, “Is Your Bid-Hit Ratio Okay?”: sunflowerbank.com
HighLevel changelog, “Enhanced Tracking with Lost Reason for Opportunities”: ideas.gohighlevel.com
HighLevel Help, “Opportunities Widgets in Dashboards and Reports”: help.gohighlevel.com
FAQ
What is a good bid-hit ratio for contractors?
Survey benchmarks put general contractors at roughly 6:1 to 10:1 on public works, 4:1 to 6:1 on private bid work, and 2:1 to 4:1 on negotiated and design-build work. The right target depends on your market and estimating cost.
Why should contractors track lost bid reasons?
Because price is not the only reason bids are lost. Survey data shows that about half of losing-bid reasons are price-related, and for 15% of losses the contractor does not know the reason at all.
What lost reasons should a construction CRM include?
A short list such as price outside 5%, price within 5%, scope or qualification gap, schedule, team or experience, relationship, project cancelled, and unknown.
How do I make sure my team fills in the lost reason?
Make it part of close-out and add a workflow that creates a follow-up task whenever an opportunity is marked lost with the reason or competitor field blank.
How often should we review lost bids?
Monthly works for most contractors: a short review of losses by reason, project type and price gap, fed directly into go/no-go decisions.
