Course outline
Learning from wins and losses: debriefs that change your next bid
Every result is feedback. After a loss, ask the client a short, specific question — how close you were, and whether it came down to price, scope or something else — and record the reason in fixed categories. After a win, check whether you left money on the table and whether the job earned what you estimated. Review results by client, project type and size every quarter, and change what they point to: which jobs you bid, how you price them, and what your proposals say.
After this lesson you can
- Ask clients for useful feedback without being pushy
- Record loss reasons in categories you can compare
- Turn a quarterly review into changes in bidding and pricing
How do you ask a client for feedback?
- Ask soonWithin a few days of hearing the result, while the bid tab is fresh in the estimator's mind.
- Keep it short and specificOne or two questions they can answer in a sentence.
- Ask the person you worked withThe estimator who invited you and built the bid.
- Accept whatever they shareSome clients share a gap, some share nothing. Don't argue with the answer.
- Thank them either wayAnd say you'd like to stay on their list.
“Thanks for letting us know. So we can sharpen up for your next one — were we close, and was it mainly price, scope, or something else?”
Record a reason you can actually use
| Reason | What to capture |
|---|---|
| Price | The gap, as a percentage, if the client shared it |
| Scope | What your proposal included or excluded that others didn't |
| Relationship or incumbent | Another sub had history with the GC or owner |
| Schedule or capacity | Your lead times or availability didn't fit |
| Qualifications | Prequalification, bonding, certifications or references |
| Project didn't proceed | Cancelled, over budget, or rebid |
| Unknown | No feedback — still worth recording |
Keep the categories fixed. “Price” written five different ways can't be counted; one category can.
Wins need a debrief too
- How far below the next number were you? If you were far under, you may have left margin on the table.
- Did the job earn what you estimated? Compare actual production, material and labor with the estimate at closeout.
- Where did change orders come from? Frequent change orders on scope you thought you'd covered point at your inclusions and exclusions.
Run a quarterly review
- Group resultsBy client, project type, size and labor type — measured correctly, as the win rate guide explains.
- Look for patternsAlways high on healthcare work? Losing to scope with one client? Winning only when a job is small?
- Change your bid decisionsAdjust the weights in your bid-or-no-bid worksheet.
- Change your pricingUpdate production rates and overhead where the jobs say you're off.
- Change your proposalsFix the inclusions and exclusions that keep causing scope losses or change orders.
Frequently asked questions
How do I find out why I lost a bid?
Ask the client's estimator soon after the result with a short, specific question — how close you were and whether it was price, scope or something else — and accept whatever they're willing to share.
What loss reasons should subcontractors track?
Use fixed categories such as price, scope, relationship, schedule or capacity, qualifications, project didn't proceed, and unknown, and record the price gap when you have it.
How often should a contractor review bid results?
Quarterly is a practical rhythm — often enough to spot patterns by client, project type and size, and long enough to have enough results to compare.
Key points
- Ask every client a short, specific feedback question.
- Record loss reasons in fixed categories, and debrief wins too.
- Review quarterly and change bidding, pricing and proposals.
Results by client, not by memory
IntelBid records each client's outcome on every bid and reports win rates on the dashboard — counting bids that never got an answer as losses, so the number isn't flattered by silence. It's the starting point for the quarterly review.
Start your free trialEvery trial starts with a sample project loaded, so you can try this before connecting anything.
Get new lessons, plus $100 toward IntelBid
New modules as they're published. Confirm your email and we'll send a $100 credit toward your IntelBid membership.