Every proposal you send has two costs: the obvious one (the connects or credits you spend) and the invisible one (the hours you will never bill). Most freelancers track neither — they just feel vaguely busy and vaguely underpaid. The proposal win rate turns that feeling into a dashboard: what percentage of your bids become clients, what each proposal is worth on average, and what your bidding habit costs in billable time every month.

Enter proposals sent and proposals won per month, your average project value, the hours each proposal takes (writing, research, calls), and your hourly rate. You get your win rate, revenue per proposal sent, proposals needed per client won, the monthly cost of proposal time at your rate, and a verdict benchmarked against the reported ~42.5% freelance win-rate average — plus a direct link to the client acquisition cost calculator, which turns these same inputs into your CAC.

Planning aid, not a judgment. Win rates vary wildly by platform, niche, and how aggressively you qualify prospects. A 20% win rate on perfectly qualified $10,000 projects beats a 60% win rate on $300 gigs — which is exactly why the calculator shows revenue per proposal alongside the raw percentage.

Key takeaways

  • Win rate = proposals won ÷ proposals sent. The reported freelance average is ~42.5% — treat it as a rough benchmark, not a target.
  • Revenue per proposal = (won × avg project value) ÷ sent. At the defaults (5 × $2,500 ÷ 20), each proposal is worth $625 whether it wins or not.
  • Proposals per client = sent ÷ won: at 25% win rate you write 4 proposals per client — every improvement here multiplies your pipeline.
  • Proposal time has a price: 20 proposals × 3 hours × $75/hr = $4,500/month of unbilled time at the defaults — usually the biggest acquisition cost.
  • Low win rate usually means poor qualification, not poor writing: bidding on everything is the most expensive strategy in freelancing.
  • Pair with the client acquisition cost calculator: win rate drives how many proposals each client costs you, which drives CAC.

Bids, applications, or quotes submitted in a typical month.

Of those sent, how many became paying clients.

Typical revenue per won project.

Writing, research, portfolio customization, discovery calls — be honest.

Used to price your unbilled proposal time.

Win rate—
Revenue per proposal sent—
Proposals needed per client—
Monthly proposal-time cost—
Verdict—

How it works

  1. Enter proposals sent and won per month — your honest trailing average, not your best month.
  2. Enter your average project value: typical revenue per won engagement.
  3. Enter hours per proposal honestly: writing, tailoring samples, research, and any discovery calls.
  4. Enter your hourly rate so the calculator can price your unbilled bidding time.
  5. Read the win rate and compare it with the reported ~42.5% freelance average — remembering that project value matters more than the percentage.
  6. Read revenue per proposal: the expected value of every bid you send. Compare it with the time cost per proposal (hours × rate) — the gap is your bidding margin.
  7. Read proposals-per-client and the verdict, then carry the numbers into the client acquisition cost calculator for the full CAC picture.

Worked example

Worked example — defaults:

  • Sent: 20/month | Won: 5 | Avg project: $2,500 | Hours/proposal: 3 | Rate: $75/hr
  • Win rate: 5 ÷ 20 = 25.0%
  • Revenue per proposal: (5 × $2,500) ÷ 20 = $625
  • Proposals per client: 20 ÷ 5 = 4.0
  • Monthly proposal-time cost: 20 × 3h × $75 = $4,500 of unbilled time, against $12,500 of revenue won
  • Verdict: below the ~42.5% average — the lever is qualification, not volume.

Second example — high-value qualifier: 8 sent, 3 won (37.5%), $8,000 projects, 4 hours each at $100/hr. Revenue per proposal = (3 × $8,000) ÷ 8 = $3,000; time cost = 8 × 4 × $100 = $3,200. Fewer, better bids: the win rate looks modest but each proposal is worth nearly 5× the default example. This is why revenue-per-proposal beats win-rate as the headline metric.

Third example — the volume trap: 60 sent, 6 won (10%), $800 projects, 1.5 hours each at $50/hr. Revenue per proposal = (6 × $800) ÷ 60 = $80; time cost = 60 × 1.5 × $50 = $4,500. Each proposal costs $75 of time to earn $80 of expected revenue — a $5 margin before platform fees. The verdict is brutal and correct: this freelancer is running a proposal-writing charity. Halving volume and doubling qualification would transform the business.

Frequently asked questions

What is a good freelance win rate?

Context beats benchmarks, but ~42.5% is the reported freelance average. Below 20% usually signals poor qualification (bidding on bad fits); 20–45% is the normal working range; above 60–70% usually signals underpricing rather than excellence. The metric that actually matters is revenue per proposal — a 25% win rate on $8,000 projects crushes a 60% win rate on $800 projects. Optimize the product of win rate and project value, not the percentage alone.

How do I raise my win rate without lowering prices?

Qualify harder, not bid harder. The highest-leverage moves: disqualify in the first message (budget, timeline, decision-maker), niche your positioning so fewer competitors apply, reuse templated sections for the 80% of proposals that repeats, and follow up once — a huge share of "lost" proposals were never read. Each point of win rate at the defaults is worth $500/month, so qualification work pays better than most client work.

What does each proposal really cost me?

Hours × your rate, plus any platform spend. At the defaults, 3 hours × $75 = $225 of unbilled time per proposal — against $625 of expected revenue. That $400 gap is your bidding margin, and it is thinner than most freelancers think. Track it monthly: if proposal-time cost ever approaches expected revenue from wins, your pipeline is running at cost and something structural must change (niche, prices, or qualification).

Should I count discovery calls in hours per proposal?

Yes — count everything the bid costs you. Writing, customizing samples, research, the "quick 15-minute chat" that takes 45, and follow-ups. Most freelancers undercount by half; the honest number is usually 2–5 hours for a serious proposal. Undercounting flatters your win rate economics and hides the true CAC — which is exactly why the input asks you to be honest.

My win rate is 80%. Should I celebrate?

Then raise your prices. An 80% win rate means the market is telling you, loudly and repeatedly, that you are cheap. Raise rates 15–20% and watch: if the win rate falls to 50% and revenue per proposal rises, you just gave yourself a raise with no extra work. The profit-maximizing win rate for most freelancers sits around 30–50% — high enough to keep the pipeline full, low enough to prove you are priced at the market's edge.

How does win rate connect to client acquisition cost?

Win rate is the denominator of CAC. CAC = (proposal spend + proposal hours × rate) ÷ clients won — and clients won = sent × win rate. Double your win rate and you halve your CAC without spending a dollar less. That is why the calculator links directly to the client acquisition cost calculator: win rate is usually the cheapest lever for lowering CAC, cheaper than cutting proposal spend.

Do proposal platforms (Upwork connects) change the math?

They add a cash cost per proposal on top of the time cost. Add your monthly connects/credits spend to the time cost for the full picture — the CAC calculator does this automatically. This also changes strategy: when each proposal costs real money, spraying bids becomes directly unprofitable and qualification becomes even more valuable. Price connects like ad spend: cost per proposal × proposals per client = cash CAC per client.

How many proposals should I send per month?

Enough to hit your revenue target at your win rate — no more. Work backwards: monthly revenue target ÷ (win rate × avg project value) = proposals needed. At a $10,000 target, 25% win rate, $2,500 projects: 10,000 ÷ (0.25 × 2,500) = 16 proposals. Sending 40 is not ambition, it is unpriced labor. Cap volume at the computed number and spend the freed hours on delivery quality and follow-up, which raise the win rate itself.

What if my projects vary wildly in size?

Segment the calculation. Run it separately for small projects and large ones — the win rates, hours, and values differ so much that a blended average lies. You will often find small-project bidding subsidizes large-project bidding or vice versa. Segmented numbers tell you which tier to push and which to prune; blended numbers tell you nothing.

Should I track win rate by lead source?

Absolutely — it is the highest-value cut of this data. Referrals might close at 70% with 1 hour of proposal time; cold platforms at 15% with 4 hours. The blended 25% hides a 10× difference in revenue per proposal-hour. Track sent/won by source for a quarter, then reallocate bidding time toward the sources with the best revenue per proposal-hour. Most freelancers discover one source subsidizes the rest.

How fast can I realistically improve win rate?

Qualification changes show up in 30–60 days; positioning changes in 3–6 months. Tightening disqualification (saying no faster) lifts the rate almost immediately because it removes the worst bids from the denominator. Niche repositioning, portfolio rebuilds, and testimonial gathering compound slower but lift both win rate and project value. Do both: qualify ruthlessly this week, reposition steadily this quarter.

Is a low win rate ever fine?

Yes — during deliberate experiments. Testing a new niche, a new platform, or much higher prices will crater your win rate temporarily, and that is the price of information. The rule: experiment with a bounded number of proposals (say 20), measure revenue per proposal, and decide. A permanently low win rate is not experimenting — it is a broken qualification process wearing a lab coat.

Last verified: 2026-09-25 Results are estimates for planning purposes only. Verify the figures independently before making financial decisions.