The maths of over-bidding is simple. A major pursuit costs thousands of hours once you count the ones that never hit a timesheet: the project director borrowed from a live job, the estimator's weekends, the design hours consultants want back in the fee. At a one-in-five win rate, bidding everything means spending five bids' worth of your best people to buy one project. Most bid teams know this. The gate still approves almost everything, because declining feels like turning away revenue.
The more useful argument is that the no is a tool, and most firms use it badly. They just don't lodge, or send procurement two lines of nothing, and burn the relationship the no was meant to protect. Done well, declining is a rare kind of client contact, one where you're not selling anything. That's exactly why it gets remembered.
Decline in three parts
- Decline fast. Within days of deciding. Withdrawing early does the client's procurement team a real favour, and they know it.
- Decline honestly. Give the real reason plainly: current delivery commitments, a capability gap on one part of the scope, a team you won't split. “Our program is full” is one of the most credible signals a contractor can send.
- Decline forward. Write the sentence most firms never do: what would need to be true for you to bid the next one, and who will stay in touch until then.
A client who gets that letter learns you're disciplined, candid and busy. A client who gets your fifth mediocre bid learns something too.
Track the no like a bid
Log your declines in the pipeline alongside your bids, each with an owner and a next contact date. A well-handled no is early positioning for a pursuit you haven't seen yet.
Try this: count the declines across two years of go/no-go calls. A gate that has never said no is a ritual, not a gate.
Free tool: Go/no-go scorecard. Fill it in online with your team, then save it as a PDF.
Free downloads: Go/no-go gate scorecard and decline log (Excel) and the decline letter template (Word).