The Proposal Gap: Why Strong Contractors Lose Work They Should Win
Most commercial contractors who lose a shortlist interview weren't less qualified than the contractor who won.
They were less prepared for how the decision actually gets made.
That's what I call The Proposal Gap—the distance between what your team puts into a proposal and what a selection committee actually uses to choose a winner. It's one of the most expensive problems in commercial construction, and almost nobody talks about it directly because it's easier to blame price.
How Selection Committees Actually Make Decisions
Here’s what typically happens: Contractors build proposals around what they want to say. Selection committees evaluate proposals based on criteria they defined before your submission arrived. Those criteria are usually weighted, and they include risk mitigation, project approach, team qualifications, schedule methodology, relevant experience, and occasionally price, but rarely price alone, and almost never price first. (If price is the top priority, I invite you to read my blog about the three types of RFPs you should ALWAYS walk away from.)
AGC's Best Value Selection guidelines make this explicit: evaluation committees establish weighted scoring criteria at the outset, and only those criteria are considered in scoring. Your capabilities brochure language, your mission statement, your company history—none of it scores unless it directly answers a weighted criterion. Contractors write about themselves. Evaluators score against a rubric. The gap between those two things is lost revenue.
The 4 Most Common Proposal Gap Mistakes
1. Leading with company history instead of project understanding
The first thing most proposals say is some version of: "Founded in [year], [Company] has been delivering quality construction for [X] years." Evaluators don't score company founding dates. They score demonstrated understanding of their specific project, their specific risks, and their specific constraints. A proposal that opens with your risk analysis for their project outscores a capabilities statement every time because it answers a weighted criterion before the evaluator has to go looking for it.
2. Burying the differentiator
Most contractors have something genuinely distinctive: a specific process, a relevant project history, a team member with rare expertise. It usually shows up on page 11 of a 14-page proposal. Selection committees don't always read page 11. Research consistently shows evaluators spend the most time on executive summaries, project approach sections, and team qualifications. If your differentiator isn't surfaced in the first third of the document, there's a real chance it's not factoring into the score.
3. Proposal vs. shortlist presentation
Contractors who build a strong written proposal often walk into the shortlist interview and essentially re-read the proposal to the room. The shortlist interview is a separate evaluation event with different dynamics. The committee has already read your proposal. Instead, they're looking for confidence, chemistry, and clarity under pressure. The contractors who win shortlist interviews at high rates treat the written proposal and the oral presentation as two distinct sales moments, each designed for how that format gets evaluated.
4. No debrief loop
Most contractors who lose a pursuit move directly to the next one. Without a debrief loop, every proposal starts from the same baseline. With one, your proposals improve compounding. Each loss makes the next submission smarter. If your company submits 15 proposals a year and closes 4, a debrief process that moves your win rate from 27% to 40% is two additional projects annually. At a $3M average contract value, that's $6M in revenue from a habit that costs nothing but a 20-minute phone call.
What Closing The Proposal Gap Actually Looks Like
Closing The Proposal Gap isn't about writing longer proposals or spending more on graphic design. It comes down to three specific shifts:
Shift 1: Read the RFP as a scoring rubric, not a project description.
Every weighted criterion in an RFP is a question your proposal needs to answer explicitly. Map your responses directly to those criteria. Don't make evaluators connect the dots.
Shift 2: Write for the person who skims, not the person who reads.
Most evaluators are reviewing multiple proposals under time pressure. Headers, callout boxes, and executive summaries aren't design preferences, they're how your key points survive the skim. If your differentiator can't be seen in a 90-second scan, it might as well not be there.
Shift 3: Treat the shortlist interview as a separate pursuit.
Assign a prep owner. Run a rehearsal. Anticipate the three hardest questions the committee will ask and prepare specific, confident answers. Bring the actual project team so evaluators can see the people who will run their project. Check out my blog for more tips on how to prepare your team for the shortlist interview.
The Proposal Gap Is a System Problem, Not a Writing Problem
The contractors who close The Proposal Gap fastest aren't the ones who hire better writers or graphic designers. They're the ones who build a repeatable pursuit process—a consistent way to evaluate RFPs, structure responses, prep for interviews, and debrief after every outcome. That's a system. Systems are buildable, and once they're built, they compound.
