Pipeline velocity measures how many dollars of new work your pursuit pipeline produces per day. It's a standard B2B sales metric. Most A&E firms can't compute it because the underlying pursuit history doesn't exist:
Pipeline velocity = (open pursuits × average fee × win rate) ÷ average pursuit cycle length in days
Four inputs, one output: revenue per day. Getting the definitions right matters more than the arithmetic:
- Open pursuits: active pursuits that have passed your go/no-go screen, counted at a point in time, not every RFP a principal has heard about
- Average fee: mean design fee per awarded project over your recent wins (net service revenue, never construction cost)
- Win rate: awards divided by submittals over the same period, expressed as a decimal
- Cycle length: average days from RFP release to contract award for won pursuits over that period
Treat the four inputs the way you'd treat a load calc. Open pursuits is a current count, while average fee, win rate, and cycle length are historical measures. Those three historical inputs have to come from the same lookback period and follow the same segmentation rules, because pairing a three-year win rate with six months of fee data is mixing units, and the answer is meaningless.
A Worked Example: A Mid-Size Engineering Firm
Say your firm has 12 qualified pursuits, an average fee of $250,000, and a 44% win rate. That win rate is credible: survey data from 303 architecture, engineering, and construction firms puts engineering firms at a 44.2% hit rate. Assume a 120-day average cycle for won pursuits, measuring only the formal RFP-release-to-award window on a mixed public and private portfolio.
(12 × $250,000 × 0.44) ÷ 120 = $11,000 per day
Dollars per day feels foreign to principals who plan in months, so convert it. At the current pace, this pipeline produces roughly $330,000 in awarded fees per month, or about $4 million annualized.
The formula is multiplicative, so every input compounds. Compress that 120-day cycle to 90 days and velocity jumps to $14,667 per day. That is a 33% gain with no new pursuits and no change in win rate. That lever matters because A&E cycles run long: federal RFP-method procurements average about 13 months from RFP release to award, and private-sector work with a new client can take several years from first contact to contract.
Two Inputs Are Easy. Two Require History You Probably Don't Have
You can count your open pursuits in an afternoon. Average fee is already sitting in your executed contracts and your invoicing. The other two inputs, win rate by type and average cycle length, require pursuit history. A principal asks how long an RFP actually takes, opens the tracker, and finds a single Status column with no dates behind it. Half the marketing teams in SMPS's survey track opportunities in spreadsheets, and current-status-only trackers are where most firms stall.
A current-status-only spreadsheet stores the current stage of each pursuit. It does not preserve when the pursuit entered each stage, so you cannot compute how long pursuits actually take. Unless designed with required fields and governance, it does not enforce outcome fields by project type or sector, so you cannot compute win rate by segment. A purpose-built spreadsheet can retain that information, but you cannot rebuild the history retroactively; a firm that has tracked only current status has no path back to the data.
The benefits of replacing spreadsheet-based tracking extend beyond velocity analysis. After moving from Excel, Dynamic Engineering reported 25% profit growth, a 2x efficiency gain, and a 2x confidence boost.
Segmentation is not optional here. Repeat clients and referrals supply 75–85% of business at A&E firms. Monograph's 2026 Architecture & Engineering Business Benchmarks Report found engineering firms draw 18% of revenue from architect clients versus 6% at architecture firms, 3x the dependence on a single client type. That is concentration context, and it is why a blended win rate moves with your client mix even when your process holds steady. To compute the hard half of the formula, your pursuit record needs three things:
- A won/lost outcome, with a loss reason, recorded for every closed pursuit
- Structured fields for project type, client, and sector that you can query later
- A date on every stage change, so you can measure how long pursuits actually take
That record has to live in a system configured for disciplined pursuit tracking. Monograph's pipeline management tracks leads, ownership, next steps, opportunity status, proposals, and fee-based pipeline values. Teams can create, manage, and refine proposals in a shared system, and a lead remains connected to the opportunity record. Capacity-aware forecasting then shows how future work maps to staffing, timing, and revenue signals. That gives the firm a shared foundation for pursuit management and forecasting.
Build Weighted Pipeline First, Then Layer In Velocity
Velocity has a sibling metric. Weighted pipeline multiplies each pursuit's fee by its probability of closing and sums the results. That gives you a probability-adjusted snapshot of what your current portfolio is worth today. Take one of the pursuits from the worked example: a $250,000 fee at 50% probability contributes $125,000 to weighted pipeline today. As an open pursuit it also props up velocity while producing no actual revenue. If it sits in procurement for another eight months, stage aging exposes the individual stall; velocity shows the portfolio-level effect once cycle-time history changes.
The two answer different questions. Weighted pipeline tells you whether there is enough work on paper; velocity tells you whether that work is converting fast enough to hit near-term revenue. Principals who track only the weighted number usually discover the stall when a quarter closes short, too late to push a decision.
They are also sequential. Weighted pipeline only needs a win probability per pursuit, which a principal can assign today; velocity needs historical averages. Start weighted-pipeline discipline now, assign probabilities to every open pursuit, and add velocity once you have enough won/lost history to average.
The Four Levers, Once You Can See Them
Recomputed over consistent periods, velocity becomes a diagnostic. A drop from $11,000 to $9,000 per day has four possible causes, and the inputs tell you which one moved. Two are common. Fewer qualified pursuits points at business development capacity; a longer average cycle points at procurement or at your own proposal turnaround. Those conditions call for different remedies, and without recomputing the inputs you are guessing between them.
When revenue falls short, the formula tells you which input moved, and each input responds to a different action:
- More qualified pursuits: work existing relationships first; principals build more pipeline as relationship managers than as cold prospectors
- Larger average fees: build fees three ways (bottom-up, top-down from comparable projects, duration-based) and trust the number when the methods converge; a 5–10% increase holds with good clients
- Higher win rate: enforce go/no-go scoring; one tracked firm moved from 37% to 51% after systematically tracking proposals and the pursuit process
- Shorter cycles: run capture planning before the RFP drops and maintain a content library updated after every pursuit
The win-rate lever deserves the most scrutiny, because every proposal you write consumes senior staff hours you can't bill. Go/no-go scoring changes what you decide rather than how you staff, and it feeds the other three levers: pursuits you decline never inflate your qualified open-pursuit count or enter the completed pursuit history used for win rate and cycle length.
The velocity you compute a year from now depends entirely on the pursuit history you start recording this week. Pick a system, define your stages, then log the date on every stage change for the next RFP that crosses your desk.
Build a Pipeline Forecast You Can Trust
Principals and owners need dependable revenue forecasts, but the underlying record requires daily discipline. Operations leaders and project managers need clear pursuit stages, assigned owners, required outcomes, loss reasons, and dates they can maintain without rebuilding the tracker every quarter.
Monograph Pipeline keeps leads, owners, next steps, opportunity status, proposals, and fee-based pipeline values together in a system built around A&E work. It connects opportunity forecasts to existing project, financial, and staffing data so future work can be compared with real capacity, timing, and revenue signals.
Start the clock now. Define your stages, assign an owner to every pursuit, and record each change as it happens. Book a demo.
Frequently Asked Questions
How much pursuit history do we need before pipeline velocity is reliable?
Use enough closed pursuits to calculate meaningful historical averages, and keep average fee, win rate, and cycle length within the same lookback period and segmentation rules. Open pursuits remains a point-in-time count. Until you have that won/lost history, use weighted pipeline and begin recording outcomes and stage-change dates now.
What counts as an open pursuit?
Count active pursuits that have passed your go/no-go screen. Do not include every RFP or possible lead a principal has heard about, because unqualified opportunities inflate the result.
Should we calculate pipeline velocity separately by sector or project type?
Yes, when those segments have different fees, win rates, or pursuit cycles. Keep structured fields for project type, client, and sector so you can compare like with like instead of relying only on a blended firm-wide rate.
Can a principal-assigned probability replace historical win rate?
No. Assigned probability is enough for weighted pipeline, but velocity requires awards divided by submittals over a consistent historical period. Use the two metrics together rather than treating one as a substitute for the other.
Can a spreadsheet provide enough data for pipeline velocity?
A current-status spreadsheet cannot. You need a won/lost outcome, structured segment fields, and a date on every stage change; without that history, cycle length and segmented win rate cannot be rebuilt later.