Show Notes
Most bid/no-bid conversations jump straight to judgment — incumbency risk, relationships, competitive fit — without ever running the numbers that should come first. This episode of
Development makes a case that's simple but easy to overlook: arithmetic is the gate, and judgment is only useful once a pursuit clears it. The discussion is grounded in
the bid/no-bid arithmetic article from RFP.co, which lays out the underlying model in full.
Here's what the episode covers:
- The expected-value formula. A bid's worth equals the probability of winning multiplied by the contract's margin contribution, minus the fully loaded cost of the pursuit — a calculation most teams never write down.
- Why pursuit cost matters as much as win rate. Two pursuits chasing the same contract can have opposite expected values purely because one costs more to execute, and lowering bid cost is mathematically equivalent to raising win probability by the same proportion.
- Break-even win rate as a decision tool. Dividing pursuit cost by contract contribution produces the minimum win probability a bid must clear before it's worth starting — a number teams already have before the solicitation is even opened. Tools like go/no-go scoring can formalize that threshold before the conversation gets emotional.
- The hidden cost of "bid less, bid better." Concentrating resources on opportunities where qualification, past performance, and opportunity matching are already strong dramatically shifts the portfolio math — without requiring any improvement in win rate.
- Protests through an arithmetic lens. GAO data from fiscal year 2025 shows a 52% "effectiveness rate," but most of that relief is agency-initiated re-runs — a remedy that costs money, reveals your pricing, and compounds the original loss rather than correcting it.
- Sequencing as the real leverage point. The bid/no-bid gate is the only moment in the pursuit lifecycle where saying no costs nothing; once resources are committed, every subsequent decision carries sunk-cost pressure.
The episode draws directly on the RFP.co article linked above — worth reading alongside a pursuit calendar, especially for teams whose reviews tend to begin with relationships and end with someone who's already started writing. For more from the show, check out
Why AI Won't Replace Manual QA Anytime Soon, which examines a different kind of quality gate in the proposal process.
What is DEV?
Software and web development from the side that has to ship it and then live with it. Architecture decisions with a cost attached, scoping, technical debt, hiring and vendor selection, and the AI tooling question every engineering team is now answering whether they planned to or not.
Each episode takes one decision — rewrite or refactor, framework choice, build versus buy, how to scope a fixed-bid project honestly — and works through the tradeoffs, including the ones that only show up in year two. Written for engineering leads, technical founders and the people who fund them. Five or six minutes, no hand-waving.
Topics include rewrite versus refactor, build versus buy, scoping fixed-bid work honestly, technical debt you should keep, framework and platform choices, hiring and vendor selection, code review culture, and where AI tooling actually helps.
Produced by DEV.co, web and software development. Full details, services and further reading at https://dev.co