Every pursuit process has to answer a structural question before it answers any strategic one: how many times should the firm formally stop and decide whether to keep going? One gate keeps things fast. Four gates catch problems early and often. The right answer depends on your deal flow, your pursuit costs, and—more than most firms realize—on how much each gate costs to operate. This article works through the trade-offs, and then examines what changes when the operating cost of a gate approaches zero.
What a gate is actually for
A gate is a checkpoint where spending stops until someone with authority decides it should continue. The economics are simple: the cost of pursuing a project rises steeply over time—a quick screen costs an hour, a fee proposal costs days, a full estimate on a large pursuit can cost tens of thousands of dollars—while the cost of killing it stays near zero. The earlier a doomed pursuit dies, the cheaper the funeral. Gates exist to force that death early, before sunk cost and team enthusiasm make "no" politically expensive.
The catch is that each gate is also a coordination event. Scorecards go out, responses come back or don't, someone merges and chases and packages, an executive decides. Multiply that ceremony by every gate on every pursuit, and the overhead becomes the argument against the very discipline the gates provide.
One gate: fast, and all-or-nothing
A single-gate process asks every question at once: one scorecard, one review round, one decision. For firms with modest deal flow and inexpensive pursuits, this can be enough, and its speed is a real virtue.
Its weakness is uniformity. Every opportunity—the obvious decline, the obvious yes, the genuinely hard call—receives the same full evaluation, which means either the evaluation is thorough and the obvious cases waste everyone's time, or it's light and the hard cases get less scrutiny than they need. Single-gate firms tend to drift toward the light version, and the process quietly becomes a formality that ratifies whatever BD already decided.
Two gates: the common sweet spot
Most firms that sustain a gated process settle on two. Gate 1 is a cheap screen—often the BD lead alone, scoring client, fit, and competition in fifteen minutes—that exists to kill clear mismatches before anyone else spends attention on them. Gate 2 is the full multi-role review: risk, operations, preconstruction, and BD scoring in parallel, with the composite and narratives going to an executive for the real go/no-go.
The shape works because it matches effort to information. The screen catches the pursuits that never deserved a meeting, so the expensive gate runs only on candidates worth its cost. Reviewers take Gate 2 seriously precisely because they aren't asked to run it on everything. The two-gate flow diagrammed on the Bex Risk product page is this pattern: a solo scorecard, a go/no-go, a four-role parallel review, a final decision package.
Three gates and beyond
Larger pursuits justify more checkpoints because their cost curve has more distinct cliffs. A design-build pursuit might gate before the initial screen, again before committing to the SOQ, again before the full proposal effort, and once more before final pricing—each gate positioned just before a major spend. Joint-venture decisions, self-performed scopes, and unfamiliar markets similarly add review rounds with different participants: surety and counsel at one gate, JV partners at another.
The rule of thumb is that a gate belongs wherever the next increment of pursuit spending is large enough that you'd want the option to stop before committing it. What you should resist is adding gates to diffuse accountability—five gates where each reviewer assumes the previous one did the real scrutiny provide less protection than two gates taken seriously.
What belongs at each gate
However many gates you run, the assignment of questions matters. Early gates should carry the criteria that are cheap to answer and frequently fatal: client quality, geographic fit, competitive field, obvious capacity conflicts. Later gates carry what requires real work to assess—contract risk allocation, bond and schedule exposure, staffing plans, margin modeling. A useful test: if a criterion could have killed the pursuit at a cheaper gate, move it earlier. For what to score within each gate and how to weight it, see our companion piece on bid/no-bid scorecards.
When gates stop costing anything to run
All of the arithmetic above assumes each gate consumes coordinator hours—someone distributing workbooks, chasing reviewers, merging returns, and assembling decision packages. That assumption is why firms economize on gates in the first place.
Bex Risk removes it. Once your gates, participants, and scoring rules are configured, a pursuit kicked off by a single email flows through however many gates you've defined: Bex builds the workbooks, sends each reviewer a scorecard locked to their cells, scores returns by your weights, sends reminders, routes around out-of-office reviewers, escalates on timeout, and delivers one decision package per gate. The decision-maker replies "let's go" or "pass." Nobody merges anything. A live dashboard shows every active pursuit, its current gate, and who Bex is waiting on. The judgment remains entirely human at every checkpoint—reviewers score, executives decide, as we insist on in our humans-in-the-loop approach—but the ceremony runs itself.
That changes the sizing calculus. When a gate costs nothing to operate, the only question left is whether the checkpoint improves decisions, and firms can afford exactly as many gates as their pursuit economics warrant rather than as many as their coordinator can survive.
If you've been running fewer gates than you'd like because the overhead was the constraint, we should talk—the contact link is below. Bring your current process, however many gates it has, and we'll show you what it looks like when the coordination is free.