The wrong denominator hides the constraint
Most teams describe proposal load with a count: five RFPs this month, nine next month. The count is easy to report and almost useless on its own. A 40-question renewal completed from approved content is not the same unit of work as a net-new enterprise pursuit that needs solution design, pricing, legal review, references, resumes, and an executive narrative.
A useful capacity model starts with total contributor hours by pursuit. That includes time spent locating evidence, re-answering familiar questions, waiting in status meetings, resolving version conflicts, and reviewing material that should have been governed before the opportunity arrived.
Measure four layers of load
The fourth layer is why proposal operations belongs in a revenue conversation. QorusDocs' 2026 benchmark describes typical teams handling five to nine RFPs monthly, with responses often requiring six to twelve or more contributors. Loopio and APMP reported that RFPs influenced 37% of respondent revenue in their 2025 research. When that much revenue passes through a shared operating process, capacity is a control surface for growth.
- Core production: requirement analysis, response drafting, editing, production, and submission.
- Contributor drag: the time sales, technical, security, legal, finance, and delivery leaders spend away from their primary work.
- Rework: effort caused by stale answers, unclear ownership, contradictory versions, or late changes in solution strategy.
- Opportunity cost: qualified pursuits declined—or weak pursuits accepted—because the team could not see capacity and fit together.
Turn the baseline into a decision
For eight representative pursuits, record total team hours, number of unique contributors, time spent waiting, percentage of scored requirements supported by current evidence, and advancement or outcome. Segment renewals, expansion bids, and net-new pursuits rather than averaging them together.
Then calculate the loaded annual cost of the current response mix and the capacity tied up in avoidable effort. Do not claim that all rework will disappear. Use conservative scenarios—such as 15%, 20%, and 30% recovery—and decide which operating changes are justified even at the low case.
The executive question
The point is not to make every response faster. The point is to spend scarce expert attention on the pursuits where proof, fit, and economics justify it. A mature operating system may deliberately invest more time in a strong opportunity while declining a weak one earlier. That is better capacity management than celebrating a lower average response time.