Winning Work5 min read

Your Pursuit Pipeline Is a Hiring Tool, Not a Scoreboard

Your backlog says you are covered. It cannot tell you who to hire. That is the job of a twelve-month pursuit pipeline view. Worth checking you have one.

Oswald B.Founder, RFPM.aiUpdated August 17, 2026

A pursuit pipeline view is a forward read of the work your firm expects to compete for, usually twelve months out, filtered by geography and market sector. Its job is not to track the proposals you have in flight. It is to tell you which capabilities need to be staffed before the RFPs arrive.

What a Pursuit Pipeline Is, and What It Is Not

Nearly every firm keeps a list of pursuits in motion: what is due, who is writing it, what stage it sits in. That list answers what the team is doing this month. A pipeline view answers what is coming, where, and in what sector, twelve months ahead of the list and before most of it has been advertised.

A proposal log is a workload instrument. A pipeline view is a hiring instrument. If the log is your only forward view, every staffing decision reacts to a deadline that already exists.

Why Backlog Is the Wrong Instrument for a Hiring Decision

The number most principals reach for instead is backlog, and it looks reassuring. In the ACEC Research Institute's Q2 2026 Engineering Business Sentiment Survey of 583 firm executives, median backlog held at 11 months and 49% of firms reported a year or more. But backlog is rear-facing. It tells you what you already sold, not which capability you will be asked to prove twelve months from now.

The cost shows up in the same survey. Thirty-three percent of firms turned down work in the prior six months for lack of staff, down from 51% in Q4 2024. The pressure has eased, but one firm in three still passed on work it wanted, and a specialized senior hire is a months-long search at best. The decision that would have prevented it needed making long before the RFP appeared. Meanwhile 64% expect hiring to increase over the next twelve months, and most are deciding that on the instrument pointing backward.

How to Read a Twelve-Month Pipeline for Shape

A business development leader with four decades in the industry walked me through his routine when I asked what he actually looked at each month. He filters the pipeline twelve months out by geography and market sector, sorts by value, and reads it for shape rather than for individual pursuits, since most of those change or disappear. He wants to see which sectors are thickening, which regions are going quiet, and whether the total is growing against last quarter.

Then he does the thing that makes it a hiring tool. If aviation work is stacking up in a region twelve months out, that is a signal to have aviation people in place, because you do not staff aviation work after you win it. The resumes have to exist before you submit, and the person has to exist before the resume does.

None of that requires the tooling a 3,000-person firm has. It requires that someone own the view:

  1. Write the pipeline down twelve months out. Capital improvement plans, state TIPs, bond measures, and agency procurement forecasts are public. The work is compiling them, not finding them.
  2. Tag by geography and market sector, not by client name. Client lists tell you about relationships. Sector and geography tags reveal shape.
  3. Read it quarterly, not weekly. Weekly reading turns it back into a proposal log. Watch that volume concentrated in one funding program is not a thickening sector, which is its own blind spot.
  4. Bring one question to every reading: what will we be asked to prove twelve months from now that we cannot prove today?

That last question is the whole exercise, and it runs upstream of go/no-go and capacity math, which decide what to chase and how much of it your people can support. It sometimes returns the more useful answer, which is that the shape does not justify a hire and the firm should be more selective instead. The same ACEC survey found 83% of firms still declining work are applying stricter evaluation criteria.

What Breaks When the Work Actually Arrives

The pipeline view creates a demand, and the demand lands on your records. Twelve months out you decide the firm needs to be credible in aviation. Twelve months later an RFP arrives and someone has to answer, quickly, who here has aviation experience and what you have delivered in that sector.

If that answer lives in a shared drive, a few individual memories, and whatever the last aviation proposal happened to say, the pipeline view has told you to prepare for something you cannot document on demand. This is the gap RFPM.ai is built for: staff and project history kept as searchable records rather than finished documents, so the question is answerable in an afternoon. A person still decides which staff and projects belong in the submittal.

That is separate from what a proposal team measures about itself. A proposal performance dashboard looks inward at hit rates to justify resourcing. A pipeline view looks outward to decide what the firm should become.

Frequently Asked Questions

What is a pursuit pipeline in an AEC firm?

A pursuit pipeline is a forward-looking list of the opportunities a firm expects to compete for, typically extending twelve months or more and organized by geography, market sector, and estimated value. It differs from a proposal log, which tracks submittals currently in progress and answers a workload question rather than a planning one.

How far out should an AEC pipeline look?

Twelve months is the common working horizon for staffing decisions, because that is roughly the range at which hiring, teaming, and qualification-building can still change what a firm is able to pursue. Individual pursuits are unreliable that far out, so the view is read for sector and regional shape rather than for specific opportunities.

Where do you find pursuit opportunities twelve months out?

Public agencies publish most of it. Capital improvement plans, state transportation improvement programs, approved bond measures, board agendas, and agency procurement forecasts all describe funded work well before any solicitation is advertised. The effort is in compiling these into one view by sector and geography, not in locating them.

What is the difference between a pipeline view and a go/no-go process?

A go/no-go process evaluates a specific opportunity that has already appeared and decides whether to pursue it. A pipeline view runs earlier and broader, reading the shape of expected work across sectors and regions to decide what the firm should be staffed and qualified to pursue at all. One filters; the other positions.

RFPM.ai automates proposal resumes and project sheets for engineering and construction firms. See how it works →