A proposal performance dashboard is a one-page view of the numbers that show what a proposal team produces and wins: win rate, pipeline coverage, cost per win, capacity utilization, and pursuit time. It exists for one reason. Without numbers, a proposal team looks like a cost center, and cost centers lose budget arguments. The dashboard turns the team into a measurable line on the firm's growth.
Why Proposal Teams Lose the Budget Argument
Walk into most A/E firms and the proposal function is invisible on the books. There's no revenue line for it. There's a labor cost, a software cost, and a stack of deadlines. When the proposal team asks for another coordinator, a better tool, or relief from the Saturday crunch, the principal hears a department asking to spend more, with nothing on the other side of the ledger.
That's not a fair read of the work, but it's an accurate read of the information available. Proposal work runs 3 to 8 percent of revenue at a typical AEC firm, according to SMPS, and almost none of it is measured. The team knows it's drowning. The team knows which pursuits it had to skip. But "we're slammed" is an anecdote, and anecdotes lose to numbers every time leadership has to choose where the next dollar goes.
This is the exact gap a proposal performance dashboard closes. It doesn't make the team work harder. It makes the work legible to the people who control the budget. When you can show that the team responded to every pursuit that passed go/no-go, won at a stable rate, and is now turning away qualified work for lack of hours, the conversation stops being about cost and starts being about lost pipeline. That reframe is the whole point.
It also names the problem behind the proposal team that keeps burning out even though the firm bought AI. Overtime and turnover are usually symptoms of a capacity ceiling nobody has measured. You can't ask for help against a number that doesn't exist.
The Five Metrics That Prove a Proposal Team's Value
You don't need fifteen metrics. You need five that a principal can read in thirty seconds and that each map to a decision. Here's the set.
| Metric | What it answers | How to calculate | What to watch |
|---|---|---|---|
| Win rate | Are we winning the work we chase? | Pursuits won / pursuits submitted (track by count and by fee) | Your own trend over time, not just an absolute number |
| Pipeline coverage ratio | Do we have enough in play to hit the revenue target? | Total fee value of active pursuits / revenue target | Coverage of roughly 3x or higher, adjusted for win rate |
| Proposal cost per win | What does it cost us to land one job? | Total proposal labor and production cost / pursuits won | Trend over time; rising cost per win is an early warning |
| Capacity utilization | How much qualified work are we able to respond to? | Pursuits submitted / qualified pursuits that passed go/no-go | The gap between what came in and what you could answer |
| Pursuit time | How long does a submittal take us? | Median days (or labor hours) per submittal | Should hold steady or drop as volume grows |
A few notes on each, because the definition matters more than the chart.
Win rate is the headline, but it's the most misread number in the building. Track it two ways: by count (how many of the proposals you submitted you won) and by fee value (the dollars won versus the dollars chased). A 40 percent win rate on small pursuits and a 15 percent rate on large ones tell very different stories about where the team should spend its hours. Watch your own trend. A firm that improves its go/no-go discipline can move win rate 15 to 25 percent, according to APMP benchmarks, mostly by chasing fewer, better-fit pursuits rather than by writing better prose.
Pipeline coverage ratio is the metric principals understand instinctively, because it's the same logic as a sales pipeline. If you need 5 million dollars in new work and you win one in three pursuits, you need roughly 15 million dollars of active pursuits in play to get there. Coverage below that means the firm is going to miss the number no matter how good the proposals are. This metric reframes the proposal team as the front of the revenue engine, not the back office.
Proposal cost per win is the one that changes the budget conversation. Add up the labor hours and production cost across all pursuits in a period, then divide by the number you won. Rising cost per win is an early warning that the team is chasing the wrong work, rebuilding too much from scratch, or both. You don't need a perfect time-tracking system to start. A rough hours estimate per submittal is enough to show the trend.
Capacity utilization is the metric that justifies headcount. It's the share of qualified pursuits, the ones that already passed go/no-go, that the team was actually able to respond to. A 2026 benchmark of nearly 300 proposal professionals found 44 percent of firms can't respond to between 20 and 29 percent of the RFPs that come in. If your number looks like that, you're not short on talent. You're short on the hours to package it, and every skipped pursuit is work the firm was qualified to win and chose not to bid by default.
Pursuit time is the operational health check. Track the median days, or labor hours, per submittal. The same benchmark found 49 percent of firms take 6 to 10 days per pursuit, and much of that window goes to reformatting and coordination rather than thinking. If pursuit time holds steady or drops while submittal volume rises, the team is getting more efficient. If it climbs, you have a capacity problem worth fixing before it becomes a turnover problem.
How to Build the Dashboard From Data You Already Track
The dashboard itself is easy. A spreadsheet with five numbers and a small trend chart for each is enough. Nobody needs business-intelligence software to do this. The hard part isn't the chart. It's the pursuit log behind it.
-
Keep one pursuit log. Every opportunity the firm considered, in one place, with a row per pursuit. Not three spreadsheets and a shared calendar. One list is the foundation, and most firms don't have it.
-
Tag each pursuit with five fields. Status (pursuing, submitted, won, lost, no-go), client and agency, estimated fee value, the go/no-go decision, and a rough labor estimate. These five fields produce all five metrics. Capture them as the pursuit moves, not in a quarterly scramble.
-
Pull the five metrics on a fixed cadence. Monthly for the operational numbers, quarterly for the trend view. Calculate from the log. If a number takes more than a few minutes to produce, the log is missing a field.
-
Put it on one page. Five numbers, each with its current value and a small trend line. The audience is a principal who has ninety seconds, not an analyst. Resist the urge to add more.
-
Annotate the story. A number without context invites the wrong conclusion. One line under each metric: "Win rate up 6 points after we tightened go/no-go in Q1." The annotation is what turns the dashboard from a report into an argument.
The recurring failure point is step one and step two. The metrics are only as honest as the log behind them, and the log is where most firms struggle, because pursuit data lives in email threads, a shared calendar, and one person's memory. When a coordinator leaves, the history leaves with them.
This is part of what a proposal workspace is for. When pursuits, deadlines, and outcomes are tracked in one system alongside the staff and project content behind them, the raw inputs for the dashboard are recorded as a byproduct of doing the work, not as a separate logging chore. That's the layer RFPM.ai keeps in one place: the submittal count, the outcomes, the fee values, and the time per pursuit are already there when you go to build the dashboard, instead of being reconstructed from scattered files at quarter-end.
How to Use the Dashboard in the Budget Conversation
A dashboard you don't bring to the leadership meeting is a hobby. The value is in how you use it, and there are three moves that work.
Lead with the coverage gap, not the workload. Don't open with how busy the team is. Open with the revenue target and the pipeline coverage needed to hit it. If coverage is thin, the firm has a growth problem the proposal team is positioned to solve, and that's a very different ask than "we're tired."
Show cost per win as a trend, then explain it. If cost per win is rising, tie it to the cause: the team is rebuilding the same content on every pursuit, or chasing work outside the firm's real differentiators. Both have fixes that cost less than the trend line. A rising cost-per-win curve makes the case for the fix on its own.
Turn capacity utilization into lost pipeline. This is the strongest move. If the team responded to 75 percent of the qualified pursuits that came in, name the 25 percent it didn't, and put a fee value on it. "We turned away 4 million dollars of qualified pursuits last year because we ran out of hours" is the sentence that gets a coordinator approved or a tool funded. It connects directly to the time the team loses rebuilding content instead of writing, which is the cheapest capacity to recover.
The pattern across all three: tie every request to a number on the dashboard. Don't ask for a coordinator. Ask for the capacity to stop turning away 4 million dollars in pipeline. Don't ask for a tool. Ask to bring cost per win back down. The dashboard makes the proposal team fluent in the one language firm leadership already speaks, which is the language of revenue and return.
Frequently Asked Questions
What is a proposal performance dashboard?
A proposal performance dashboard is a one-page summary of the metrics that show what a proposal team produces and wins. The core set is win rate, pipeline coverage ratio, proposal cost per win, capacity utilization, and pursuit time. Its job is to make proposal work measurable to firm leadership, so budget and headcount decisions rest on numbers instead of anecdotes.
What metrics should a proposal team track?
Five are enough: win rate (by count and by fee value), pipeline coverage ratio (active pursuit value against the revenue target), proposal cost per win (total proposal cost divided by wins), capacity utilization (the share of qualified pursuits the team can actually respond to), and pursuit time (median days or hours per submittal). Each maps to a specific leadership decision, which is why the short list beats a long one.
How do I calculate proposal win rate?
Divide pursuits won by pursuits submitted over a set period. Track it two ways: by count and by total fee value, because a firm can win many small pursuits and lose the large ones, or the reverse. Exclude no-go decisions from the denominator. Win rate is most useful as a trend over time rather than as a single absolute number.
What is a good proposal win rate for an AEC firm?
It varies widely by work type, client, and whether the firm is the incumbent, so the honest answer is to watch your own trend rather than chase a benchmark. Many firms see higher rates on shortlisted, qualifications-based pursuits and much lower rates on cold or poorly qualified ones. Disciplined go/no-go decisions can lift win rate 15 to 25 percent, per APMP, mostly by improving which pursuits the firm chases.
How often should I update a proposal dashboard?
Update the operational numbers monthly and review the full trend view quarterly. Monthly keeps win rate, capacity, and pursuit time current enough to catch problems early. The quarterly view is what you bring to budget and planning conversations, because the trend over several months tells a clearer story than any single month.