Capture planning is the work of positioning your company to win a specific contract, ideally before the solicitation is released. Win themes are how that work shows up in the proposal: a few short, provable messages that tell evaluators why you are the better, safer choice. This chapter explains both in plain terms, with a capture plan outline you can copy and a worked example that turns an ordinary strength into a theme that scores.
Capture is not only for big defense contractors. A five-person IT firm in Westchester or a landscaper in Bergen County can run a lighter version in a few hours per opportunity. For spotting opportunities early, read procurement forecasts and early intelligence alongside this chapter.
What is capture planning?
Capture planning means finding an opportunity early, learning what the customer needs and fears, sizing up the competition, and shaping your solution, team and price so that you are already the strongest candidate when the RFP arrives. Proposal work starts when the RFP is released; capture starts earlier and hands the proposal its strategy.
- Stage 1: Identify
Spot the opportunity through forecasts, expiring contracts, budgets and alerts.
- Stage 2: Qualify
A first bid/no-bid gate: does it fit, and can you realistically win?
- Stage 3: Position
Learn the customer, study competitors, close gaps with partners or hires, draft themes.
- Stage 4: Prepare
Turn the capture plan into a proposal strategy and outline before release.
- Stage 5: Propose
Confirm the bid decision on the final RFP, then write, review and submit.
How early? For large federal or state programs, capture teams often start a year or more before the expected RFP. For a typical city, county or school district contract, a few weeks to a few months is realistic. If the RFP is already out, do a compressed version: one page on the customer, the competition and your themes, finished before writing starts.
How to find the customer's hot buttons
A hot button is a concern or goal that drives the customer's decision: fear of another failed transition, pressure to cut response times, an audit finding to fix, a new commissioner's priority. Hot buttons are often bigger than the written requirements, and proposals that name and answer them show evaluators you understand the job, not just the paperwork.
| Signal | Where to find it | Possible hot button |
|---|---|---|
| A factor with unusually high weight | Evaluation criteria | What the agency fears most, such as transition risk |
| The same phrase repeated through the scope | Scope of work, background section | A priority like 'resident experience' or 'data security' |
| Detailed penalties or service levels | Sample contract, performance standards | Problems with a previous vendor |
| Questions in an RFI or draft RFP | Pre-solicitation notices, industry days | What the agency has not decided and worries about |
| Audit findings, budget testimony, board minutes | Public meetings, audit reports, adopted budgets | Problems leadership has promised to fix |
Step 1: Read what the agency publishes
Strategic plans, budgets, audit reports and board minutes show what leadership is measured on. A school district that just failed a facilities audit cares about documentation more than price.
Step 2: Respond to RFIs and attend industry days
Federal rules encourage pre-solicitation exchanges such as requests for information, draft RFPs, industry conferences and one-on-one meetings. What the agency asks about reveals what it is unsure of.
Step 3: Talk to the customer before the RFP
Before release you can usually meet program staff to learn their challenges (not to lobby for a spec). Once the RFP is out, contact generally goes through the named contact only, and New York State's restricted period limits it to designated contacts. See relationship building within the rules.
Step 4: Listen to users, not just buyers
Facility managers, caseworkers and IT staff who live with the contract often describe the real problems most clearly. Conferences and public meetings are good places to listen.
Step 5: Use your debriefs
A debrief from a past bid with the same agency tells you what its evaluators valued. See how to get the most from a debrief.
Competitor and incumbent analysis
Evaluators compare proposals, so you need a realistic picture of who else will bid and what they will say. Start with the incumbent, then add firms holding similar contracts nearby, firms at the pre-proposal conference and likely teaming partners.
RFP Detector's public contractor profiles are a practical start for New York State work: each shows a contractor's state contract history, the agencies it serves and a Contractor Score. Add award notices, meeting minutes and what you hear at conferences. The competitor research tutorial walks through it.
| Factor (from the evaluation criteria) | Your firm | Incumbent | Competitor B |
|---|---|---|---|
| Technical approach | 4 | 3 | 4 |
| Relevant past performance | 3 | 5 | 4 |
| Key personnel | 4 | 3 | 3 |
| Transition risk | 4 | 5 (no transition) | 2 |
| Price position | 3 | 3 | 5 |
| Local presence and response | 5 | 3 | 2 |
The table tells a story. The incumbent is strong on past performance and has no transition risk, Competitor B will likely be cheapest, and your edge is people and local response. Your themes must neutralize transition risk (a credible plan with named staff) and make local response matter to evaluators.
Discriminators: what only you can claim
A discriminator is a feature of your offer that the customer values, that competitors cannot match and that you can prove. Most 'strengths' fail the test: 'experienced', 'customer-focused' and 'committed to quality' are claims every bidder makes.
| Question | If the answer is no |
|---|---|
| Does the customer care (is it tied to a hot button or evaluation factor)? | It is just a feature. Mention it briefly or drop it. |
| Is it different from what likely competitors offer? | It is table stakes. Prove it, but do not lead with it. |
| Can you prove it with numbers, names, documents or references? | It is a claim. Find the proof or stop making it. |
Real discriminator
- Do: Our depot is 6 miles from the county complex, so technicians reach any building in under 30 minutes.
- Do: The proposed project manager led this agency's last system migration and knows its data structure.
- Do: We already hold the certification the RFP requires by month three, removing that schedule risk.
Weak claim
- Don't: We are a customer-focused company with years of experience.
- Don't: Our team is highly qualified and dedicated.
- Don't: We follow industry best practices.
How to write win themes: feature, benefit, proof
A win theme is a short statement that links a discriminator or strength to something the customer cares about, and backs it up. The standard formula taught across the proposal profession has three parts:
- Feature: what you offer (a tool, person, process, location or certification).
- Benefit: what the customer gains, in their terms: less risk, faster results, lower total cost, higher quality, fewer complaints.
- Proof: evidence the benefit is real: past-contract data, a reference, a certification, a named person’s record.
Lead with the benefit, because that is what evaluators care about, and keep the proof right beside it. A theme without proof is a wish; a feature without a benefit is a brochure. The two examples below are illustrative.
'Our firm uses a state-of-the-art maintenance management system to deliver excellent service.' A feature with adjectives: no benefit to the customer and no proof.
'You will see every work order from request to close-out in real time. Our maintenance management system gives your facilities staff a live dashboard and monthly reports; on our current contract with a comparable school district, open work orders fell by a third in six months (reference in Volume II).'
| Location | How to use the theme |
|---|---|
| Executive summary | State all three to five themes, each tied to a hot button (see executive summary structure) |
| Section openings | Open each major section with a one- or two-sentence theme statement |
| Graphics and captions | Let the action caption carry the theme: what the reader should conclude |
| Résumés and past performance | Show the person or project that makes the theme true |
| Price narrative | Explain how the theme lowers total cost or risk, where narratives are allowed |
Ghosting the competition, ethically
Ghosting means drawing attention to the risks of a competitor's likely approach, without naming the competitor, by explaining why your approach avoids them. Done well, it raises a question in the evaluator's mind that the other proposal then struggles to answer.
Ethical ghosting
- Do: 'Our staff already know your systems, so there is no learning curve on day one.' (ghosts a newcomer's transition risk)
- Do: 'Our price includes all after-hours calls, with no emergency surcharges.' (ghosts a low bidder who adds fees later)
- Do: 'Every call is answered by our own staff in Newark, never an outsourced call center.'
Over the line
- Don't: Naming a competitor, or hinting so heavily that the target is obvious
- Don't: Claiming a competitor failed when you cannot prove it
- Don't: Using anything from a competitor's proposal, pricing or internal documents
A good rule: if the incumbent's project manager read your ghost statement aloud in a debrief, you should not be embarrassed. Ghost the approach, never the people, and be careful with incumbents: the agency chose them, and evaluators may like their staff.
A capture plan outline you can copy
A capture plan does not need to be long. For a mid-sized state or local bid, two to four pages is enough. What matters is that every action has an owner and a date, and that you update the plan at each bid/no-bid gate.
Template
One-page capture plan
A compact capture plan for a single opportunity, from snapshot to actions. Feed its decision into the bid/no-bid scorecard.
When to use it
Use it for any best-value opportunity you plan to bid, ideally before the RFP is released. For a low-bid IFB, complete sections 1, 4, 6 and 7 only.
CAPTURE PLAN: [OPPORTUNITY_NAME] Agency or issuer: [AGENCY] Solicitation no. (if known): [NUMBER] Capture lead: [NAME] Last updated: [DATE] 1. OPPORTUNITY SNAPSHOT Scope in one sentence: [SCOPE_SUMMARY] Estimated value and term: [VALUE] / [TERM_AND_OPTIONS] Expected RFP release: [RELEASE_DATE] Expected award: [AWARD_DATE] Basis of award (if known): [BASIS_OF_AWARD] Set-aside or certification rules: [SET_ASIDE] Incumbent: [INCUMBENT] 2. CUSTOMER Decision makers and evaluators (roles): [ROLES] Goals this contract supports: [GOALS] Hot buttons, with evidence: - [HOT_BUTTON_1] (source: [EVIDENCE_1]) - [HOT_BUTTON_2] (source: [EVIDENCE_2]) - [HOT_BUTTON_3] (source: [EVIDENCE_3]) Our relationship today: [RELATIONSHIP] 3. COMPETITION (bidder / strengths / weaknesses / likely price position) - [COMPETITOR_1] - [COMPETITOR_2] - [COMPETITOR_3] 4. OUR POSITION Discriminators (valued, unique, provable): [DISCRIMINATORS] Gaps (past performance, staff, certifications, price): [GAPS] How we close the gaps: [GAP_ACTIONS] 5. WIN STRATEGY Win themes (feature, benefit, proof): - [THEME_1] - [THEME_2] - [THEME_3] Ghost themes (risks our approach avoids): [GHOST_THEMES] 6. TEAMING AND PRICE Partners and roles: [PARTNERS] Price strategy and target range: [PRICE_STRATEGY] 7. ACTIONS AND GATES - [ACTION_1] / owner: [OWNER_1] / due: [DUE_1] - [ACTION_2] / owner: [OWNER_2] / due: [DUE_2] Next bid/no-bid gate: [GATE_DATE] Our estimated probability of win: [PWIN]
Fields to fill in
- [BASIS_OF_AWARD]
- Lowest price, LPTA or best-value tradeoff; it decides how much of this plan you need
- [HOT_BUTTON_1]
- The customer's worry or goal in their words, with the document or meeting where you found it
- [COMPETITOR_1]
- Name, main strength, main weakness and whether they tend to bid low or high
- [DISCRIMINATORS]
- Only items that pass all three tests: the customer cares, competitors lack it, you can prove it
- [GAP_ACTIONS]
- Teaming partners, hires, certifications or references you will secure, with dates
- [PRICE_STRATEGY]
- Your target range and the assumptions behind it; see the pricing chapter
- [PWIN]
- An honest percentage estimate; revisit it at every gate
For teaming partners, see teaming agreements and joint ventures; for price strategy, see price to win.
Worked example: turning a strength into a win theme
Here is the whole process for an illustrative company (all details invented). Hudson Mechanical, a 40-person HVAC contractor in Yonkers, is bidding a best-value RFP for preventive and emergency HVAC maintenance across 22 Westchester County buildings. Technical approach is worth 40 points, past performance 25, price 25 and local participation 10.
Step 1: Start with the raw strength
The first draft says: 'Hudson Mechanical has a 24/7 dispatch center.' True, but every serious competitor will say the same.
Step 2: Tie it to a hot button
The RFP background mentions repeated heating outages last winter, the sample contract has a 2-hour emergency standard with penalties, and the county's budget testimony promised fewer no-heat days in senior centers. The hot button: no-heat emergencies in occupied buildings.
Step 3: Find the discriminator
The main competitors are based on Long Island and in New Jersey. Hudson's depot is 15 minutes from the county center, and its trucks carry boiler parts for the county's equipment models. Valued, unique and provable.
Step 4: Gather the proof
Twelve months of dispatch logs from a comparable public contract show an average emergency arrival of 52 minutes, with 97% of calls inside a 2-hour standard. That client's facilities director agrees to be a reference.
Step 5: Write the theme
'Heat restored faster in county buildings: our Yonkers depot and parts-stocked trucks put a technician on site in under an hour on average, half the County's 2-hour standard, as our 12-month dispatch record on a comparable public contract shows.'
Step 6: Add the ghost
In the technical approach: 'Because our technicians are based in Westchester, response times do not depend on bridge or parkway traffic.' No one is named; the evaluator draws the conclusion.
Step 7: Place it everywhere it counts
Executive summary (theme), technical approach opening (theme plus a response-time graphic), staffing plan (named technicians and locations), past performance (the reference) and the price narrative (no emergency surcharges).
Figure 2-3. Our Westchester depot puts a technician at any county building in under an hour on average, half the required response time, so occupied buildings are not left without heat.
Captions like this carry your themes to evaluators who skim. The next chapter covers graphics and action captions and how to build an outline that keeps every theme where evaluators will look for it.
Frequently asked questions
What is capture planning in government contracting?
Capture planning is the work of positioning your business to win a specific contract before and during the solicitation: learning the customer's needs and hot buttons, analyzing competitors, closing gaps in your team or experience, and developing win themes and a price strategy. It produces a capture plan that hands the proposal team its strategy when the RFP is released.
What is the difference between capture management and proposal management?
Capture management decides whether and how to win: customer insight, competitive position, teaming, solution and price strategy, mostly before the RFP. Proposal management turns that strategy into a compliant, persuasive document once the RFP is out: outline, schedule, writing, reviews and submission. In small firms one person often does both, but the jobs are different.
When should capture planning start?
As early as you can. For large federal or state programs, teams often start a year or more ahead of the expected RFP; for typical local contracts, weeks to a few months is realistic. If the RFP is already out, a one-page assessment of the customer, competitors and themes before writing still helps.
What is a win theme in a proposal?
A win theme is a short, memorable message that tells evaluators why to choose you. It links a feature of your offer to a benefit the customer cares about and backs it with proof. Win themes appear in the executive summary, section openings, graphic captions and the evidence sections. Most proposals need three to five.
What is the difference between a win theme and a discriminator?
A discriminator is the fact: something the customer values that competitors cannot match and you can prove, such as a nearby depot or a key person with directly relevant experience. A win theme is the message built on that fact, written in terms of the customer benefit and repeated through the proposal.
What does ghosting the competition mean?
Ghosting means highlighting the weaknesses or risks of a competitor's likely approach without naming the competitor, by showing how your approach avoids them, for example stressing a no-surcharge price where a rival is known to add fees. It must stay factual and must never rely on improperly obtained information.
Is capture planning worth it for a small business?
Yes, scaled to the opportunity. A small firm can capture a local contract in a few hours: read the agency's public documents, attend the pre-proposal conference, look up the incumbent, list hot buttons and draft three themes. That preparation also improves bid/no-bid decisions, so you spend proposal effort where you can win.
Complete handbook
Download the complete handbook (PDF)
All 8 chapters, templates and checklists, ready to print or share.
Put it into practice
Search open RFPs from federal, state, local, education, private and non-profit issuers, each with the RFP Detector Score.
Find RFPs