Stop Writing Proposals Like You're Still Trying to Get the Meeting

If your federal proposal reads like a capabilities briefing, your capture failed.

That's the uncomfortable truth nobody wants to hear on day one of a pursuit. But it's the single biggest reason firms with strong past performance, solid technical teams, and real market presence keep losing work they should be winning.

They're writing pitches instead of proposals. And pitches don't win federal contracts.

What's the difference between a pitch and a proposal in government contracting?

A pitch is what you send when the buyer doesn't know you yet. You're introducing yourself. Establishing credibility. Making the case for why you deserve a seat at the table. It's heavy on company background, team bios, and capability claims because the reader needs all of that context to decide whether you're worth considering.

A federal proposal is the opposite. By the time you're submitting, the customer should already knows you exist. You made it through market research. You showed up at the industry day. You responded to the RFI.  

So why are you still introducing yourself on page three?

A proposal converts trust into a contract. That's its only job. It confirms what the evaluator already believes about you, gives them the language and proof points to advocate for your score in the evaluation room, and answers the specific questions the solicitation asked in the order it asked them.

When you confuse those two functions, you waste your best real estate on positioning work that should have happened months earlier.

The five symptoms of a proposal that's actually a pitch

After reviewing thousands of federal proposals across defense, civilian, and AEC opportunities, the pattern is consistent. Proposals that weren't supported by real capture work share the same tells.

Symptom one: the executive summary is a company overview. You can read the first two pages and still not know what the firm is proposing, who the customer is, or why this pursuit is different from any other opportunity on their website. The executive summary should open with a specific statement about how you're going to solve this customer's specific problem, with specific proof. Not a paragraph about your founding year.

Symptom two: the technical approach reads like a textbook. Generic methodology. Best-practice language. Phases and milestones lifted from every other proposal the team has submitted. No reference to the specific constraints this customer mentioned at industry day, the pain points that came up in market research, or the program office's known priorities.

Symptom three: past performance is a greatest-hits album. Eight contracts listed, each one described the same way. No connective tissue showing why those specific projects matter for this specific pursuit. The evaluator has to do the work of figuring out why you're qualified — and evaluators don't do that work. They score what's in front of them.

Symptom four: there are no win themes. Or the win themes exist on a slide somewhere but don't show up in the actual document. A win theme is a specific, evidence-backed reason the customer should pick you over your competitors. If your proposal doesn't have three or four of them woven through every section, you're competing on compliance alone.

Symptom five: the cover letter could go to any customer. "We are pleased to submit this proposal for [contract name]." If you can find-and-replace the customer name and submit the same letter to a different agency, you wrote a pitch.

What federal capture management is actually supposed to produce

Capture — real capture, not the paperwork version — produces three things that show up in your proposal whether you designed it to or not.

Customer insight. Not surface-level stuff like "the agency values innovation." Specific, actionable insight about what this program office is trying to achieve, what's keeping leadership up at night, what's failed before, who the real decision-makers are, and what language they use to describe their own priorities. When this insight shows up in your proposal, it's unmistakable. The customer reads it and thinks: they get it. They get us.

Relationships. Evaluators who recognize your name. Program managers who've heard you speak at conferences. Contracting officers who remember your response to the RFI. You don't mention any of this in the proposal directly, but it's the reason your proposal starts with a warmer reception than your competitors'.

Positioning. A clear, defensible point of view on why you're the right firm for this work. Not "we have experience in this space" — everyone does. Something specific enough that a competitor couldn't say it too. Positioning is what turns your past performance from a list into an argument.

When capture produces those three things, the proposal practically writes itself. When it doesn't, the proposal has to compensate, and the compensation always shows. It shows up as length. As generic language. As an executive summary that introduces instead of confirms.

What actually changes when capture did its job

The proposal gets shorter. Tighter. More confident.

The executive summary opens with the customer's problem, states the firm's specific approach to solving it, and gives three proof points that map directly to the evaluation criteria. No windup. No company background. That stuff lives in the management section where it belongs, and even there it's framed around why this team specifically is built for this specific work.

The technical approach references the work capture did. It doesn't name-drop the customer's staff, but it reflects what they care about. It addresses the risks the customer actually worries about — the ones that came up in industry day, the ones program leadership has mentioned in public remarks, the ones your competitors are going to sidestep because they didn't do the upstream work.

Past performance becomes surgical. Three or four projects instead of eight. Each one chosen because it maps directly to a stated evaluation factor, with specific outcomes that prove the point. Relevance, recency, and complexity all handled with intention, not coincidence.

The management approach demonstrates understanding of the customer's operating environment. Staffing plans reflect their actual contracting rhythms. Transition plans acknowledge the incumbent's strengths honestly. Risk mitigation addresses risks the customer has actually articulated, not generic risks pulled from a template.

This is what evaluators mean when they use the word "tailored." A tailored proposal isn't a proposal with the customer's logo swapped in. It's a proposal that could only have been written for this customer, by a team that actually understood the pursuit.

The gut-check test for your next proposal

Before you submit, do this exercise. Read the first five pages of your proposal as if you were an evaluator who'd never heard of your firm. Count how many pages go by before you encounter something the evaluator couldn't have gotten from your website.

If the answer is more than two, you weren't writing a proposal. You were writing a pitch.

Then read the executive summary in isolation. If your firm's name were blanked out, could a reader tell you were the author? Or could this executive summary have come from any firm responding to this solicitation?

The uncomfortable answer is almost always the second one. That's the gap between pitch writing and proposal writing. And closing that gap is what separates firms with flat win rates from firms whose win rates are climbing.

The Summit Win System™ view

Within the Summit Win System™, this is what happens when the Propose peak carries weight that should have been distributed across Plan, Position, and Persuade. The proposal becomes the venue where positioning, relationships, and strategy all get invented on the fly — which is the least efficient and least effective place to do that work.

When the first four peaks are doing their jobs, Propose gets to be what it's actually designed for: a disciplined, strategic closing document. Not a pitch.