Bid/no-bid is a decision, not a vibe

Tomorrow’s post is the long one — the pillar piece on the complete bid/no-bid scoring framework. 3,500 words. Five variables, weighting, the meeting structure, override discipline. This post is the preview. The honest argument the long version makes a lot of room for: most proposal teams make their bid/no-bid as a vibe, not a decision, and the cost is high.

What an implicit decision looks like

A meeting on a Tuesday at 11am. The capture lead presents the new RFP. The VP of Sales says, “I think we should go for this.” The proposal manager says, “OK, I’ll get the kickoff scheduled.” Everybody nods. The meeting is over in 8 minutes.

The team has now committed roughly 200 person-hours of senior engineering, sales engineering, and proposal-management time to a bid that nobody scored. There is no written rationale. There is no probability-of-win number. There is no opportunity-cost analysis. There is a “we should go for this,” which is the social-proof equivalent of a coin flip with momentum behind it.

Quilt’s research has the realistic high-end at 100 to 300 hours per RFP response. If your team’s average is 200 hours and your cost-loaded average hourly rate is $150, the implicit decision just bound $30,000 of your team’s time to a bid based on a vibe. Six bids of that quality per quarter is $180,000 a quarter spent on the wrong question (whether to bid) before the team has spent a minute on the right question (how to win).

Why implicit scoring is the default

Three reasons, in roughly the order they show up.

Bid decisions feel like sales decisions, and sales decisions are made fast. The cultural posture of most B2B vendors is “say yes to the customer.” A formal bid/no-bid feels like the opposite — a structured no being applied to revenue opportunities. The team that takes 30 minutes to score reads, in the moment, as the team that is putting up barriers to revenue. The team that says “we’re in” in 8 minutes reads as aligned and aggressive. The first team is correct; the second team is comfortable.

Implicit scoring lets everyone avoid the hard conversation. The capture lead has a probability-of-win read that is darker than the VP of Sales’s read. The proposal manager knows the SME calendar this month is full and the cost-to-produce is going to be heavier than the team is admitting. Both of them, in the implicit-scoring world, do not have to put a number on the table. Putting a number on the table forces the disagreement. Not putting a number on the table preserves the team’s surface harmony, at the cost of the team’s win rate.

Nobody is accountable for the win rate at the bid-portfolio level. The CFO tracks revenue. The VP of Sales tracks pipeline. The proposal manager tracks individual bid quality. Nobody, in most organizations, tracks “what fraction of our bids should we have no-bid” as a measurable line. Without that line, there is no signal pulling the team toward formal scoring.

What changes when you make it a decision

A bid/no-bid that is a decision has three shapes that an implicit one doesn’t.

Written scores, written rationales. Every variable scored on a written rubric. Every score backed by a one-sentence rationale that names the evidence. Six months later, when the team is debriefing a loss, the rationale tells you whether the bid/no-bid was a good decision badly executed or a bad decision that was executed cleanly.

A senior approver who has authority to say no. The Shipley method calls this the “bid decision gate.” The approver’s job is not to bless the proposed bid; it is to be the person who stops a bad bid from happening. If the approver always says yes, the gate is decorative. The Lohfeld read on where proposal processes break is consistent: bid/no-bids that fail to actually filter are one of the most-corrosive failure modes a proposal shop can carry.

A logged override when the rubric is wrong. The rubric will be wrong sometimes. Strategic-customer overrides, reference-value overrides, capture-intelligence overrides — these are real. But the override is logged with a category, an approver name, and a one-paragraph rationale. The override doesn’t dissolve the rubric; it documents the exception so the team can see, six bids later, whether the override category is being abused as a permission slip.

The meeting

Tomorrow’s pillar piece walks through the meeting structure in detail. The compressed version: 15 minutes. Three to four named roles. Scores written before the meeting; the meeting is for review and decision, not data gathering. Output is a written decision with a rationale paragraph that goes into the proposal record.

The 15 minutes are the cheapest 15 minutes in proposal management when measured by time saved on bids you would otherwise have written and lost.

The honest objection

A real objection I hear from teams considering this discipline: “We can’t afford to no-bid that often. Our pipeline is thin and we need the at-bats.” That is a real argument. It deserves a real answer.

The answer is not “score everything you bid anyway.” That doesn’t change the bid count; it just adds 15 minutes per opportunity to the work. The answer is to lower the floor. A team with thin pipeline operates the rubric at a +9 composite floor instead of +12. The same five variables, the same weighting, the same meeting, the same logged rationale — applied with a lower bar. The team still bids more, but it bids more deliberately, and the bids it skips are the catastrophic ones (wired-against-us, hostile terms, opportunity-cost-crippling).

The other answer: a thin-pipeline problem is a sales-and-marketing problem. The right response to a thin pipeline is more pipeline, not less discipline on the pipeline you have.

See you tomorrow

The pillar piece tomorrow has the full framework, the worked examples, the rubric template, the meeting walkthrough, and the override discipline. If you only read one bid/no-bid post this year, read that one. If you read two, the shorter rubric craft essay from July is the back-pocket version of the same framework, in a form you could bring to your next bid kickoff.