Consider a model of a hypothetical 20-person structural engineering firm with a $4 million net revenue target and $6 million in active pursuits. On paper, next year is covered 1.5 times over: $6 million divided by $4 million. In practice, that number treats a new lead the same as a shortlisted pursuit with a long-standing client.
Why the raw pipeline number misleads
A raw pipeline total rewards volume, not winnable work. Adding a $2.5 million long-shot lead swells the report while moving expected revenue only a couple hundred thousand.
Engineering firms win about 44.2% of the proposals they submit. Nobody can staff against a headline that counts every pursuit at face value.
Weighted pipeline replaces that headline with expected value: multiply each pursuit's fee by its probability of closing, then sum. Use stage-based defaults of 10% for new leads, 30% for qualified leads, and 60% for sent proposals, then adjust them as your own results justify.
What weighting does to the $6 million
Run the hypothetical firm's book through these assumptions. The amounts below are model inputs, and their weighted values are calculated outputs:
- $2.5 million municipal water project, new lead at 10%: $250,000
- $1.5 million higher-ed structural package, proposal submitted at 40%: $600,000
- $1.2 million industrial expansion for a repeat client, shortlisted at 65%: $780,000
- $800,000 in assorted early-stage leads averaging 25%: $200,000
The weighted pipeline, the sum of the four weighted outputs, is $1.83 million and less than a third of the raw total. That is the number a principal can staff against.
Sort by expected value and the ranking inverts. The $1.2 million repeat-client pursuit moves to the top, while the $2.5 million municipal lead contributes the least expected revenue.
Assigning probabilities without fooling yourself
The math only works if the percentages are honest. Subjective go/no-go workshops get scored to reach the answer the room wants, and one survey found every responding firm had a process while only 31% followed it consistently.
Calibration against your own history removes the argument:
- Pull closed pursuits, including wins and losses
- For each stage, divide eventual wins by the pursuits that reached that stage; the result is the stage's cumulative close probability
- Segment repeat clients from cold pursuits; relationship-based opportunities convert several times more often
- Anchor proposal-stage probability at your firm's actual win rate, then adjust for pursuit-specific factors
The firm won 8 of its last 20 proposals, so the 40% rate anchors its proposal stage. One firm lifted its hit rate from 37% to 68% through consistent go/no-go tracking.
When to override the baseline
These signals justify moving a pursuit off the baseline:
- Incumbency on the client's prior work
- Pre-positioning before the RFP dropped
- A named champion inside the client organization
- Fee competitiveness against the likely shortlist
Absent one of those, the default stands. Write the reason beside every override.
Slipping start dates: the second weight
Win probability is half the correction. The other half is when work starts. Architecture firms saw average backlog slip to 6.3 months in mid-2026 while billings stayed weak, and one similar-size firm reported nearly 40% of contracted projects on hold or paused.
Undated pursuits are worth less to a staffing plan than contracted work with known start months. When a project pauses, milestones shift and revenue recognition defers while payroll continues. Engineering firms carried median backlog near 11 months in Q2 2026.
Weight pursuits by probability and activation lag, the delay before billing begins. A high-probability $25,000 study starting next month outranks a low-probability public project with a long delay. Date every weighted dollar by expected start month. In the model, doing so removes the $250,000 municipal line from the plan year, leaving $1.58 million of the $1.83 million weighted pipeline inside it.
Working backward to the pipeline you need
Start from the revenue gap: the revenue target minus contracted backlog that will bill during the year. In the model, the firm's signed contracts produce $2.2 million, leaving a $1.8 million gap.
At the model's 40% proposal win rate, the firm needs $4.5 million of correctly dated proposal-stage fees, producing $1.8 million of weighted expected value. That is a 2.5× coverage multiple on the gap. Arithmetically, 3× coverage corresponds to a 33% win rate and only works when the pipeline sits at proposal stage.
This firm has $1.58 million of dated weighted pipeline against a $1.8 million revenue gap, leaving a $220,000 hole. Dated weighted pipeline must at least equal the revenue gap. Proposal activity leads revenue by 12 to 24 months, so the shortfall appears early enough to fix.
What the weighted view changes on hiring and pursuits
That $220,000 gap dictates different moves than the $6 million headline. A dated, weighted pipeline turns three judgment calls into arithmetic:
- Hiring. Don't add staff against raw pipeline. Utilization benchmarks set a 75-85% band for technical staff, with top-quartile firms running 92-94%, while utilization consistently under 70% points to unfilled capacity. Workbench sped up staffing 8x and cut unbilled fees by 75% after moving off spreadsheets.
- Pursuits. A large pursuit can eat six figures of marketing time and expense. The 10% municipal lead is where that money dies. Senior hours belong on the shortlisted repeat client and fast-start work, even when someone must tell a principal to stand down.
- Forecasting. Keep active work, signed backlog, and weighted pipeline as separate layers. Move value between them only when contracts sign.
Together, those rules keep hiring and pursuit spending tied to demand the firm can realistically schedule and bill.
Stop staffing against an inflated pipeline
In this scenario, a $6 million headline conceals a $220,000 revenue hole. Staffing and pursuit decisions need dated, weighted demand.
Used with this workflow, Monograph's Pipeline tracks opportunity status, fees, timing, and staffing signals to support revenue and capacity forecasting. The firm can see whether it needs a senior designer in April or more pipeline by June.
Find the gap before it becomes a missed revenue target. Book a demo.
Frequently Asked Questions
What if we do not have enough historical pursuit data?
Start with illustrative stage assumptions: 10% for new leads, 30% for qualified leads, and 60% for sent proposals.
Document every adjustment and begin tracking wins and losses now.
Once enough pursuits have closed, replace the assumptions with your cumulative close probability at each stage.
How do we stop principals from inflating win probabilities?
Set a baseline from actual conversion history and require a written reason for every override.
Incumbency, pre-positioning, a named client champion, and fee competitiveness can support an adjustment. Repeat-client opportunities should be calibrated separately because relationship-based work converts more often.
Without a supporting signal, the stage baseline stands. A familiar client does not make every project a sure win.
How often should probabilities and start dates be updated?
Update a pursuit whenever its stage, client signals, or expected start changes.
A shortlist, delayed RFP, paused project, or revised design start can materially change the forecast.
Compare closed outcomes with your assumptions regularly so the percentages continue to reflect how your firm wins work.