The pursuit that nobody ever decided to keep chasing
The most expensive losses are not the bids you decided to make and lost. They are the pursuits that drifted forward for months because no one ever stopped to ask whether they were still worth it. A pursuit gets opened, work happens, the RFP drops, a proposal team scrambles, and a thin bid goes out the door — not because anyone chose to invest that effort, but because nobody chose to stop. Gate reviews exist to make those choices on purpose.
A gate review is a scheduled decision point along the capture and proposal lifecycle where leadership looks hard at a pursuit and makes one of three calls: keep going, stop now, or fix specific gaps before deciding. The value is not in the meeting itself but in the forcing function: a pursuit cannot advance to the next phase without someone deciding it should. That single discipline separates organizations that invest their proposal capacity well from those that spread it across every opportunity that walks in.
Why one bid/no-bid call is not enough
Many teams run a single bid/no-bid decision when the RFP arrives and treat that as the gate. It is a gate, but it is the last one and the least useful, because by the time the RFP drops you have already spent most of your capture effort. A no-go at that point saves you the proposal cost but wastes everything that came before.
Gate reviews spread the decision across the whole lifecycle, so the question "is this still worth pursuing?" gets asked early, when the answer is cheap to act on, and again as the picture sharpens. A typical set of gates: a qualification gate when the opportunity is first identified, a pursuit gate once early capture confirms it is real and winnable, a bid/no-bid gate at RFP release, and a final pricing and submission gate before the proposal goes out. Each gate has more information than the last and a higher cost of being wrong.
What every gate decides
The gates differ in detail but each answers the same underlying questions, with progressively better evidence. Can we win this — do we have the discriminators and past performance the customer will reward? Should we win it — does the work fit our strategy and clear a margin floor once you run the price-to-win analysis? Can we deliver it — do we have the capacity, the team, and any teaming partners the gaps require?
The discipline that makes gates work is honest scoring against criteria set in advance, the same way a good qualification framework forces honesty in ordinary sales. The point of a gate is to be able to say no, which means the criteria have to be real enough that a weak pursuit actually fails them. A gate that always returns "go" is theater.
The fix-and-recheck option
The most useful gate outcome is often neither go nor no-go but "address these specific gaps and come back." A pursuit might be winnable except for a missing past-performance reference, an unclear customer relationship, or a capability gap that a partner could close. Killing it outright loses a real opportunity; waving it through pretends the gap is not there.
The third option turns the gate into a working tool: it produces a short list of must-fix items with owners and deadlines before the pursuit can advance. That keeps standards high without throwing away salvageable pursuits, and it gives the capture team a concrete to-do list instead of a vague "keep working it." Each fix-and-recheck item is exactly the kind of owned, dated commitment that a task is built to carry.
Make the gates real, not ceremonial
Gate reviews fail in two predictable ways. The first is the rubber-stamp gate, where the review happens but no pursuit is ever stopped because killing work feels like admitting waste. The cure is to track gate decisions over time and look at the kill rate: if nothing ever fails a gate, the gate is not doing its job, and you can see that in a win/loss analysis that shows effort spread thin across pursuits you never realistically could win.
The second failure is the gate nobody prepares for, where the review devolves into recollection because the pursuit’s status, customer intelligence, and open risks are not written down anywhere current. A gate review is only as good as the picture in front of it, which is the whole argument for managing pursuits in one system rather than in scattered notes and memory.
Where the CRM fits
Gate reviews need two things a CRM provides naturally: a current picture of every pursuit and a record of decisions over time. When each pursuit is a record in Hitt CRM with its logged capture history, its open risks, and its stage reflecting which gate it has cleared, the review walks in with the facts already assembled instead of reconstructing them. Fix-and-recheck items become assignable tasks with owners and due dates, automations flag pursuits sitting too long without advancing to the next gate, and a pipeline report across all active pursuits shows leadership exactly where the portfolio sits — how much effort is committed, where it is stalled, and which bids cleared the gate that matters. The gate stops being a meeting people dread and becomes a decision the data is ready to support.
The one-sentence version
Long pursuits fail quietly when no one ever stops to ask whether they are still worth chasing, so put deliberate gate reviews along the capture lifecycle — qualification, pursuit, bid/no-bid, and final pricing — each one an honest go, no-go, or fix-and-recheck decision against criteria set in advance, and you will invest your proposal capacity in the bids you can actually win instead of drifting into the ones you cannot.