Most freelancers price their time and call it a business plan. Fewer do the sales math: if you know your win rate and what a typical project is worth, you can work backward from a revenue goal to the one number that actually predicts whether you'll hit it — how many proposals you need in the pipeline. This calculator turns "I want to make $60,000" into "I need to send 80 proposals," so pipeline building stops being a vague anxiety and starts being a target you can plan a quarter around.
How it works
Three inputs drive the math. Your win rate is the share of proposals that turn into signed work — not leads, not conversations, proposals actually sent and actually won or lost. Your average project value is what a typical won project is worth, all-in. Your target revenue is whatever you're pricing your pipeline against, a quarter or a year.
From those, the calculator first works out the expected value of a single proposal: average project value multiplied by your win rate. A proposal isn't worth its full project value to your pipeline — it's worth that value discounted by the odds it actually closes. Dividing your target revenue by that expected value gives you proposals needed: the number of proposals, at your current win rate and pricing, required to reach the goal. Separately, dividing target revenue by average project value gives projects to win — the number of actual clients you need to land, independent of how many proposals it takes to get there.
Worked example
Say your win rate is 25%, your average project is worth $3,000, and you're targeting $60,000 in revenue.
- Expected value per proposal: $3,000 × 25% = $750
- Proposals needed: $60,000 ÷ $750 = 80 proposals
- Projects to win: $60,000 ÷ $3,000 = 20 projects
Eighty proposals to land twenty projects is a 1-in-4 hit rate, which checks out against a 25% win rate — the math is just making that ratio explicit instead of leaving it as a feeling. If you send five proposals a week, 80 proposals is roughly four months of steady outreach, which turns an abstract revenue goal into a concrete weekly habit.
How to interpret your result
Proposals needed is a pipeline target, not a guarantee — win rates are averages, and any given quarter can run hot or cold around that average by chance alone. Treat the number as the volume you need flowing through your pipeline to make the odds work in your favor over time, not a promise that proposal number 80 closes the deal.
It's also a diagnostic. If the proposals-needed number is higher than you can realistically send in your timeframe, you have exactly three levers, and "send more proposals" is the weakest one on its own. Raising your win rate — better-qualified leads, a tighter proposal, following up instead of ghosting your own pipeline — multiplies the value of every proposal you already send. Raising your average project value, by pricing higher or bundling more scope into each deal, does the same with fewer transactions. Sending more proposals without moving either number just means more unpaid time spent on rejections, and it's usually the last thing worth doing, not the first.
The other diagnostic use is tracking win rate honestly over time. If you don't know your real number, don't guess — pull your last 10 to 20 proposals and count what actually converted, including the ones that went quiet instead of getting a clean "no." A win rate built on only your clear wins and losses will flatter you and understate how many proposals you actually need.
Methodology & sources
The formula is expectedValuePerProposal = avgProjectValue × winRatePercent / 100; proposalsNeeded = ceil(targetRevenue / expectedValuePerProposal); projectsToWin = ceil(targetRevenue / avgProjectValue). Both proposal and project counts round up, since a fractional proposal or a fractional project doesn't get you paid — you need the next whole one to actually hit the target.
Win rate itself varies enormously by industry, deal size, and how proposals are sourced, so treat any external benchmark as a sanity check rather than a target to hit. HubSpot's sales statistics research puts the average sales win rate around 21%, which is a reasonable reference point if you have no history to pull from yet — but your own tracked win rate, once you have 10-20 proposals to measure it against, will always beat an industry average for planning your actual pipeline.