The short version
- Companies routinely invest 40 or more hours of staff time on proposals they lose to requirements that were clearly listed in the brief and simply not addressed.
- The true cost of a lost bid goes far beyond the hours spent writing - it includes the contract value, anticipated follow-on work, and renewal revenue that will never arrive.
- Average RFP win rates sit between 20% and 35%, which means most proposals fail; the question is whether they fail on merit or on execution.
- Most teams have never calculated the return on improving their pre-submission process, because the maths feels abstract until you do it once.
- Once you run the numbers, a 10-minute structured review before submission is not a nice-to-have - the economics are not close.
Forty hours and a closed door
Picture a scenario that plays out hundreds of times a week across sales teams in the UK.
A software company has been shortlisted for a managed services contract. The contract value is £150,000 for year one, with a two-year renewal option. It is not the biggest deal the team has pursued, but it is significant. The sales manager clears capacity in the team’s diary. A senior account executive takes the lead on the response. A solutions architect joins scoping calls, contributes three technical sections, and reviews the commercial model. A proposal manager coordinates the timeline, chases inputs, and handles the final formatting.
Over three weeks, the team logs around 40 hours of combined effort. They go through four drafts. The sales manager reviews twice. The proposal goes in on deadline day. It looks professional. The executive summary is strong. The team feels good about it.
Six weeks later, the client calls. The contract is going elsewhere. The feedback, when it arrives, is a single paragraph: the proposal did not adequately address data residency requirements or the client’s business continuity obligations. Both requirements were listed explicitly in the RFP, weighted at 30% of the quality score. The proposal touched on both topics in passing, but did not answer the specific questions asked.
The team had assumed the answers were implied by their methodology section. They were not. The evaluators, working from a scoring guide, gave low marks to both criteria. The gap was enough to drop the total score below the threshold for award.
This is what submitting blind looks like. Not a weak solution. Not a poor team. A strong proposal with two holes in it that nobody noticed, because nobody checked the proposal against the RFP requirement by requirement before it left the building.
What 40 hours actually costs
The first instinct after a loss like this is to frame the damage in terms of time. That is right, but most teams significantly underestimate what that time is actually worth.
A loaded employment cost is not the salary figure on a contract. It includes employer National Insurance contributions (13.8% on earnings above £9,100), employer pension contributions (typically 3-5%), and a share of fixed overhead: office space, HR, IT, and management time. In practice, the true cost to an employer is typically 1.5 to 1.75 times the base salary, sometimes more in high-cost professional environments.
For a senior account executive on a £70,000 salary, that loaded cost runs to £105,000-122,000 per year, or roughly £50-59 per hour. A solutions architect at £85,000 costs the business closer to £60-75 per hour. A sales director reviewing and approving the final document at £120,000 base is costing the company £85-105 per hour while they are reading a proposal.
Now multiply those rates across the hours a competitive bid actually requires. A straightforward RFP response from a team that has done it before might come in at 30 hours of combined effort. A mid-complexity bid with multiple technical sections, commercial modelling, and management review sits at 40 hours. A complex, multi-lot or heavily weighted public sector opportunity can demand 60 or more hours of coordinated team time.
| Bid complexity | Hours | Mid-market firm (avg £50-65/hr) | Professional services (avg £75-100/hr) |
|---|---|---|---|
| Standard | 30 | £1,500-1,950 | £2,250-3,000 |
| Mid (our scenario) | 40 | £2,000-2,600 | £3,000-4,000 |
| Complex | 60+ | £3,000-3,900 | £4,500-6,000+ |
The scenario in this article, a 40-hour team effort at a technology firm with a mix of mid to senior contributors, lands somewhere between £2,500 and £4,000 in people cost alone. In a higher-salary professional services environment, bidding on a complex RFP with senior staff contributing meaningful time, that figure moves comfortably above £5,000 before anyone has accounted for anything beyond direct salary.
This is the floor. It does not include the time invested earlier in the sales cycle - the discovery calls, the site visits, the scoping conversations - that produced the information used in the proposal but are now sunk costs alongside it. Nor does it include the opportunity cost of what those same people could have been working on instead.
Every pound of it is gone the moment the client calls.
The number that actually matters
Even at the top of those ranges, the people cost of a lost proposal is not the number that should keep a sales manager up at night.
The number that matters is £150,000.
That is the year-one contract value the team was competing for. But even that understates the true loss, because most managed services contracts come with renewal options. If the client is satisfied at year one and renews for the two-year extension, the total contract value over three years is £450,000. Renewal rates for mid-market managed services contracts average around 70-80% for clients who are happy with delivery.
So the probability-weighted expected value of winning this contract was not £150,000. It was somewhere between £315,000 and £360,000, once you factor in the likely renewal at realistic rates.
The real cost of two unanswered requirements was not the proposal budget. It was the expected value of the contract - more than £300,000 of business that will now go to a competitor for the next three years.
That competitor did not necessarily have a better solution. They may well have had a weaker one. What they had was a proposal that answered every scored criterion clearly enough that evaluators could give them a high mark.
The part nobody puts in the spreadsheet
The numbers above are direct and visible. There are also indirect costs that most teams never calculate, because they do not appear on a single line in a sales report.
Pipeline displacement. The team spent three weeks of meaningful capacity on this proposal. That is three weeks when the same people were less available for other opportunities - qualification calls they did not make, conversations that did not happen, proposals that took longer because key contributors were stretched.
The post-loss overhead. After a significant loss, the debrief process itself consumes time. A sales manager will typically spend two to four hours reviewing what happened, discussing it with the team, updating notes in the CRM, and briefing leadership if the opportunity was material. That is more people time against the same deal after the outcome is already decided.
Selective bidding distortion. When a team loses a proposal they believed in, the natural response is caution on the next one. Bid-no-bid decisions start to skew conservative. Opportunities get passed because the team’s confidence in their own submissions has taken a knock. The revenue impact of this is impossible to measure precisely, but it is real and it compounds over time.
None of these costs appear in the post-mortem. All of them are part of the true cost of submitting blind.
If you build things for a living, the numbers are larger
The scenario above is grounded in an IT services sale. For someone managing tenders in a construction or engineering firm, the scale shifts significantly, and so does the pain.
A mid-size construction tender for a commercial fit-out or public infrastructure project might carry a contract value of £800,000 to £1.2 million. Tender preparation at that level can run to 80-120 hours across the full team - estimators working up the pricing, technical staff developing the methodology, a commercial manager handling the commercial model, and a contracts manager coordinating the whole document and writing the narrative sections.
The loaded people cost for a 100-hour tender effort, across that kind of mixed team, reaches £6,000-9,000. The expected contract value, probability-weighted at a realistic win rate, is measured in hundreds of thousands.
When a construction firm loses a tender because methodology and sustainability were weighted at 60% of the quality score and their submission did not answer those criteria specifically enough, the shape of the loss is identical to the IT scenario above. Just larger. And the tender documents made the weighting entirely clear. Award criteria in public sector tenders are a legal requirement to disclose - this information is always available.
The criteria were there. The answers were not.
Now run the other side of the calculation
Every number above assumes no structured pre-submission review took place. Now run the same maths with one change.
Before the proposal goes out, someone spends ten minutes uploading the RFP and the draft proposal to a review tool. The analysis comes back. Data residency and business continuity are flagged: both appear in the scoring guide at 30% combined weighting, and neither is specifically addressed in the current proposal. The team has two days left before the deadline. They write targeted responses to both criteria. The proposal goes out with those gaps closed.
Cost of the review: a fraction of a single person’s hourly rate. Minutes, not hours.
The counterfactual cost of skipping it: more than £300,000 in expected contract value.
This is not a complex ROI calculation, and it does not require precise numbers to be compelling. If a 10-minute check has even a 20% chance of catching a gap that would otherwise cost you a £150,000 contract, the expected value of that check is £30,000. Against the cost of running it, the return is not arguable.
Most improvements to a sales process require months of implementation, training, and behavioural change before they produce measurable results. A pre-submission proposal review requires none of those things. It requires ten minutes and documents the team already has.
What this actually changes
The argument in this article is not that your team writes bad proposals. Most do not.
The argument is that submitting blind - sending a proposal without a structured check against the RFP’s specific requirements and evaluation criteria - is a habit that carries enormous hidden cost, and that most teams maintain it not because they are careless, but because the alternative always seemed too time-consuming to be practical.
Asking a colleague to review a proposal before submission means asking for two hours of their time, and they have not read the RFP, so they cannot tell you what is missing - only how well the document reads. A proper requirement-by-requirement comparison means going back to the RFP, extracting every criterion, mapping each one to a section of the proposal, and scoring the coverage honestly. That process takes the better part of a day. Nobody has that time the day before a deadline.
The consequence is that proposals go out with gaps that are entirely avoidable. Not gaps in the quality of the solution. Gaps in the document - unanswered questions that evaluators record as absent because they cannot find a clear response, regardless of how strong the underlying offer is.
As covered in how your proposal is actually evaluated, evaluators do not read proposals searching for the best response. They work through a scoring guide, looking for specific answers to specific criteria in the order those criteria appear. A criterion with no clear response gets a low score or no score at all. The strength of your solution does not rescue you from an absent answer.
And as why experienced bid managers never submit on deadline day makes clear, the window to act on gaps is not the evening before submission. By then, the options are limited, the time is short, and adding material risks disrupting sections that are already in good shape. The review needs to happen when the team still has room to respond to what it finds.
The teams that consistently win a greater share of the proposals they submit tend to share one discipline: they know what is in the RFP, they know what their proposal currently addresses, and they close the gap between the two before anyone hits send. The cost of building that discipline into a process is minimal. The cost of not building it in is sitting in the numbers above.
