Your team tracks plenty of opportunities. Why does it still spend proposal money on the wrong ones?
Quick answer
Usually because opportunities enter the pipeline without being checked. Then they stay there, because no one is asked to take them out. Checking them (qualification) works when it happens early and uses the same criteria every time. It also helps to keep a quick screen apart from the formal bid/no-bid decision.
For an established contractor, finding opportunities is rarely the hard part. The hard part is deciding which ones deserve capture time, and dropping the rest while that is still cheap. That’s where business development (BD) teams lose the most time.
The problem isn’t finding opportunities
SAM.gov, agency forecasts, ordering portals, teaming partners and paid databases turn up more leads than any business development (BD) team can work. The hard step comes one stage later. You have to decide which leads deserve capture time, and say no to the rest early, while no still costs little.
When that step is weak, the signs are familiar. The pipeline report grows every quarter, but the number of proposals the company can staff stays flat. Capture managers carry more opportunities than they can shape. Proposal teams get pulled onto bids that were never realistic. Then a strong opportunity shows up, and the people who should work it are already busy.
1. A large pipeline doesn’t mean a healthy pipeline
Pipeline value is easy to add and hard to remove. An opportunity goes in when someone spots it. It rarely comes out before the award is announced. In between, it carries a value that may include every option year. It also carries a chance of winning (Pwin) that someone set once and never checked again. The usual reasons a pipeline looks too big:
- Ceiling values counted as revenue. A contract’s ceiling, or a base period plus every option, isn’t what one winner should expect to bill. This is common with an indefinite delivery, indefinite quantity contract (IDIQ).
- Odds that never move. A Pwin entered at the sources sought stage often stays the same after the request for proposals (RFP) comes out, even when the scoring rules favor someone else.
- Opportunities nobody is working. If no capture manager owns it and no one has talked with the customer, it’s a lead. It shouldn’t be counted as a pursuit.
- Duplicates and placeholders. The same need gets entered from a forecast, a sources sought and a draft RFP. Or a recompete is listed years before anyone knows anything about it.
None of this is dishonest. It’s what happens when adding an opportunity is free and removing one means someone has to admit a loss. A pipeline built this way is a list of everything the company has noticed. It shouldn’t be read as a forecast. The companion piece, why your pipeline looks healthy but isn’t, covers how to review one.
2. Why qualification is harder than it looks
Most teams with experience can name the things they check before they bid. The trouble is that each one needs a different kind of proof, and much of it isn’t in the notice.
| Factor | The real question | Where the evidence comes from |
|---|---|---|
| Capability alignment | Can we do this work, at this scale, with people we have or can hire in time? | The statement of work, labor categories, your staffing plan |
| Past performance | Do we have recent, relevant references the evaluators will accept? | Your contract history and CPARS, against the solicitation’s relevance and recency rules |
| Contract vehicle | Can we bid at all, as a prime or through a partner? | The notice and the vehicle’s list of holders |
| Eligibility | Does the set-aside, the size standard for the assigned NAICS code, or a clearance requirement fit us? | The notice and your SAM.gov record |
| Customer relationship | Have we talked with this program office, and does it know our work? | Call notes, industry days, prior work |
| Incumbent position | Who has the work now, and how is it going? | USAspending.gov, the old contract number in the notice, what the customer says |
| Acquisition strategy | How will they buy and evaluate: lowest price technically acceptable or tradeoff, which vehicle, orals or not? | The draft RFP, industry day material, the forecast entry |
You can usually check the first four from documents in an hour. The last three take talks, research and judgment, and that’s where most poor pursuits go wrong. A team can do the work, hold the vehicle and meet the set-aside, and still be a weak bidder. That happens when the customer likes the current contractor and the scoring leans on past work the team doesn’t have.
Check eligibility with care too. Whether you count as small depends on the industry code (NAICS code) the contracting officer gives the contract. A growing company can be small under one code and not small under another. Check the code on the notice, not the one you usually use. Our guides to contract vehicles and researching the incumbent go deeper on two of these factors.
3. The hidden cost of pursuing the wrong opportunities
Few companies track the full cost of a proposal on its own line, so it’s easy to guess too low. It includes:
- Proposal labor: the proposal manager, writers, pricing and contracts staff, and the people who review drafts.
- Technical time: the experts who design the solution, pulled off paid work or other bids.
- Leadership time: review meetings, pricing calls, teaming deals and final sign-off.
- Partner goodwill: teaming partners commit their own people and references. They remember which primes bid long shots.
- The bid you couldn’t staff: while the team works a weak pursuit, a better RFP may come out with no one free to work it.
The last cost is the largest and the hardest to see. In the short term, you can only write so many proposals. So every weak pursuit you don’t drop uses up one of a few good proposals. Our bid cost calculator helps put a number on the direct part.
4. Why BD teams need to evaluate opportunities earlier
By the time a final RFP comes out, most of what decides the contest is set: the need, the scoring rules and how the agency will buy. The Federal Acquisition Regulation (FAR) encourages talks with industry from the moment a need is first spotted. That can mean industry events, one-on-one meetings, draft RFPs and requests for information. Once the solicitation is out, all talks go through the contracting officer. Any specific facts given to one possible bidder must be made public (FAR 15.201). Early is when you can still shape the work.
Earlier review draws on sources most BD teams know but don’t always work in a steady way:
- Agency procurement forecasts. Agencies publish forecasts of planned contracts, and acquisition.gov links them in one place. Entries are estimates and change often. But they show what’s coming before a notice appears.
- Recompetes. USAspending.gov shows current contracts and how long they run. A contract nearing its last option year is a recompete you can plan for.
- Sources sought notices and requests for information. These are market research. Agencies use them in part to decide whether small businesses can meet the need. A strong answer is an early chance to shape the set-aside and the need itself.
- Agency buying habits. Look at how an office bought similar work before, which vehicles it uses and who won. That tells you more about the next award than the notice will.
Planning capture early doesn’t mean you commit early. It means you have enough facts to make the bid/no-bid decision when the RFP arrives. You don’t start research the day it drops. See procurement forecasts and sources sought for how to work each source.
5. Building a repeatable qualification process
Using the same checks every time matters more than the exact checks. When each capture manager judges opportunities a different way, you can’t compare pipelines across accounts. Then leaders end up checking everything again at review meetings.
Screening and the bid/no-bid decision are different steps
Screening and the bid/no-bid decision
| Screening | Bid/no-bid decision | |
|---|---|---|
| When | As soon as an opportunity appears, and again when it changes | Before committing proposal resources, usually once a draft or final RFP is out |
| Who | BD or the capture manager | The people who fund the proposal, with capture’s evidence |
| Effort | Minutes to an hour | Hours of preparation and a scheduled review |
| Question | Is this worth a closer look? | Should we spend proposal resources to win this? |
| Result | Plan capture, keep watching, or drop it | Bid, no-bid, or bid with conditions, recorded with reasons |
Sources: FAR 15.201. Checked Oct 22, 2026. A common practice, not a rule. Fit the steps to your own capture process.
Screening is fast and frequent. Its job is to drop poor fits before anyone spends time on them, and to flag the ones worth a capture plan. A bid/no-bid decision is slower and formal. It commits proposal money and people. So the people who will pay for the proposal should make it, with the capture manager’s evidence in front of them. Many groups add one or two checkpoints between the two. The idea stays the same: match the effort of each decision to the cost of getting it wrong.
Eight factors, assessed the same way every time
| Factor | Questions to answer | A weak signal |
|---|---|---|
| Strategic alignment | Is this customer and this work in our growth plan? Would winning help the next pursuit? | We’d bid it mainly because it’s large |
| Technical capability fit | Do we cover the core work ourselves? What would a partner have to provide? | The core work depends on a partner we haven’t signed |
| Eligibility | Set-aside, size under the assigned NAICS code, vehicle access, clearances, certifications | “We think we’re small under that code” |
| Past performance | Do our references meet the solicitation’s relevance and recency tests? | Our references are adjacent, not similar |
| Competitive positioning | Who is the incumbent, how is it performing, and why would the customer choose us? | We can’t say why the customer would switch |
| Customer relationships | Have we met the program office and the contracting officer? Do they know our work? | Our first conversation would be at industry day |
| Resource availability | Who would lead capture and the proposal? What else is due that month? | The proposal manager is already on two bids |
| Probability of winning | Taking everything above together, what is an honest Pwin, and what would raise it? | The number hasn’t changed since the opportunity was entered |
Rate each factor on a short scale, with written evidence. Record missing facts as unknown, never as a pass. An unknown should become a task: a call to make, a document to read, a partner to ask. If you can’t settle it before the decision date, the decision-makers should see it as a risk.
The chance of winning comes last, and it should follow from the other seven. A Pwin with no evidence behind it is a guess. Once a guess sits in a pipeline report, it soon starts to look like data. For the formal decision itself, use our bid/no-bid checklist.
6. Where software helps, and where it stops
Much of the time a BD team spends on this is gathering facts. That means finding notices, reading them, checking codes and dates, and noticing when something changed. Software is good at that part.
- Finding and matching: comparing new notices with your industry codes, skills and target agencies every day, with the reason each one matched.
- Fit and eligibility checks: setting the notice’s set-aside, industry code and work location beside your profile, with gaps and unknowns marked.
- Summaries and requirements: pulling dates, scoring factors and “shall” statements into a list a person reviews.
- Change alerts: spotting amendments, new deadlines and follow-on notices on the opportunities you track.
- Sorting and decision prep: ordering opportunities by deadline and fit, and gathering the evidence for a decision in one place.
Language models can speed up reading and summing up, and they keep getting better. They’re also wrong in ways that are hard to spot. So a person needs to check anything they pull from a solicitation against the source. AI does not know who the customer trusts, how the current contractor is really doing, or what a program manager said in a private meeting. No tool reliably predicts awards or replaces a capture manager with experience.
A useful rule: let software gather the facts, and keep the decisions with people. A tool should show what it found and why, mark what it doesn’t know, and leave the call to your team.
7. Better qualification leads to better resource allocation
The payoff shows up in where your people spend their time. Dropping weak opportunities early lets capture managers work fewer pursuits more deeply. Proposal teams get fewer bids, with more support for each. Leaders get a pipeline they can plan staffing around.
It also makes losses more useful. When you record every bid/no-bid decision with its evidence and reasons, you can trace a loss back to its cause. It may have been a bad pick, a weak position or a weak proposal. Over a year, those records show which of your checks predict wins and which don’t. A debriefing adds the agency’s side.
We won’t claim that better checks raise win rates by a set amount, and you should be wary of anyone who does. What it does change is how many proposals you write for work you had little chance of winning.
The goal isn’t more opportunities
Growth in federal work comes from winning work that fits, and doing it well enough to keep it. A BD team that finds more opportunities but checks them the same old way will mostly write more proposals. A team that checks earlier and the same way every time writes fewer. Each one has an owner, a plan and a reason to exist.
Common questions
How do federal contractors qualify contract opportunities?
They check each opportunity against the same list every time. The list covers fit with the company’s plans, technical skill, eligibility, past work, where they stand against rivals, ties with the customer, free staff, and a chance of winning based on evidence. A quick screen drops poor fits early. Then a formal bid/no-bid decision spends proposal time and money only on the ones that pass.
What makes a government contracting pipeline healthy?
Every opportunity in it has an owner, a realistic value, a chance of winning based on evidence, and a next step with a date. Opportunities nobody is working are removed or moved to a watch list. That way the pipeline shows work the company can really staff and win.
How do BD teams prioritize federal contract opportunities?
By fit and timing together. Fit is how well an opportunity matches the company’s plans, skills and past work, and how strong its ties with the customer are. Timing is when the decision and the proposal work land next to other commitments. Strong fits found early usually come first, because there is time to shape them.
What factors should influence a bid/no-bid decision?
Start with whether you can bid at all, including access to the contract vehicle. Then look at technical fit, relevant past work, the current contractor and likely rivals, and your ties with the customer. Add how proposals will be scored, whether your price can compete, which staff are free, and what winning is worth to your plans. Anything still unknown should go to the decision-makers as a risk.
How can AI help government contracting business development teams?
Mostly with gathering facts, not judging them. It can find and match notices, sum up solicitations, list requirements and flag changes. It can’t reliably predict awards or replace a capture manager’s judgment. So a person should check what it pulls out and make the decisions.
How FedPath helps
FedPath takes on the repetitive first pass. Opportunity Watch compares new SAM.gov notices with your skills and shows why each one matched. Fit Analysis lists the matches, possible gaps and unknowns for one opportunity, using rules you can trace. The Go/No-Go assessment records your team’s decision, who made it and why. You spend less time on opportunities that don’t fit your business, and more time on the ones that do.