Most bid teams do not have a pipeline. They have a folder of PDFs, a deadline spreadsheet, and a standing argument about which tender everyone is supposed to be working on. The symptom is always the same: the team is busy every week and surprised every quarter.
A bid pipeline makes the funnel explicit. Every opportunity sits in exactly one stage, moves forward only by meeting criteria, and exits with a recorded outcome. Once that structure exists, the numbers it produces (conversion rates, win rate, coverage) start answering the questions the folder of PDFs never could. Coverage, win rate and the stage names are in the glossary.
The three qualification gates
Every bid you prepare costs real money before a single mark is scored: estimating hours, document fees, and a bond. So the first job of a pipeline is to help you bid less, on better tenders. Three gates do most of the filtering:
- Fit. Is this scope what you deliver, or adjacent to it? Does the buyer award to firms your size, or do its bid tables show the same three large incumbents every time? Do you meet the eligibility conditions as written?
- Capacity. If you won it, could you deliver it alongside the current book? And can you afford to pursue it: a serious proposal costs something like 60 hours of estimating and writing.
- Bond affordability. A 5 percent bid bond on a 3M tender parks 150k of cash or credit line for months, win or lose. A tender whose bond you cannot carry is not an opportunity, whatever the margin looks like.
A tender that passes all three gates is qualified. One that fails any gate exits now, cheaply, instead of at the deadline, expensively.
Bid or no bid, as a discipline
Gates filter what you could bid. The bid or no bid decision picks what you will bid, and it only works as a discipline: a short scheduled meeting, a simple score, and a recorded reason either way.
Score each qualified tender on fit, winnability (bidder density, incumbency, and your relationship with the buyer) and economics (expected margin at the price the benchmarks lesson says would win). Set a threshold and hold it. A written reason for every no bid, revisited quarterly, is how a team learns what its wins have in common.
The hardest part is cultural. Declining a biddable tender feels like losing, so undisciplined teams bid everything and dilute their estimating hours across proposals they were never going to win. Killing a weak bid early is the highest-return decision a bid team makes.
Stage design: six stages, each with an exit rule
Stages only mean something if moving forward requires evidence. A working design has four stages on the line and two exits off it:
- IdentifiedDeadline and bond known
- QualifiedThree gates, an owner
- SubmittedReceipt confirmed
- WonPrice and reason recorded
- LostDistance from the winner
- No bidReason recorded, never deleted
01Identified. The tender exists, the deadline and bond are known, a source link is attached.
02Qualified. It passed the three gates and survived bid or no bid. An owner is assigned. The labour lives here: costed, priced against the category benchmarks, documents drafted, bond arranged.
03Submitted. Delivered before the deadline, receipt confirmed.
04Won. A terminal outcome with a reason recorded, and the winning price: that is next year's benchmark data.
05Lost. Also terminal, also with a reason. Record your distance from the winning price; losing by 2 percent and losing by 20 percent call for different fixes.
06No bid. A terminal outcome, never a deletion.
This is where a spreadsheet starts to strain: six stages, owners, deadlines, bond amounts, and outcome reasons across dozens of live tenders. In Ishara, chosen tenders go straight from the tenders table into a bid-team pipeline, where stage-entry requirements enforce the exit rules above and every won or lost outcome is recorded on the deal.
Win-rate math and pipeline coverage
Once outcomes accumulate, the pipeline produces the number that sizes everything else: your win rate. If you win 1 submission in 4, a revenue target needs 4x that value in submissions. That multiple is your pipeline coverage, and running below it is how quarters get quietly lost months in advance.
Sizing the funnel for a $12M year
Your target is $12M in new contract value next year. The average award in your categories runs about 1.5M, so the target is 8 wins.
Your pipeline history gives three conversion rates: identified to qualified 40 percent, qualified to submitted 50 percent, and submitted to won 25 percent.
Chain them backwards: 8 wins divided by 0.25 is 32 submissions. 32 divided by 0.50 is 64 qualified. 64 divided by 0.40 is 160 identified. The funnel must swallow about 13 identified tenders a month to hit the target.
Now the checks. Coverage: 32 submissions at 1.5M is 48M of submitted value against a 12M target, exactly the 4x your 25 percent win rate demands. Capacity: 32 proposals at roughly 60 hours each is about 1,900 hours, most of one full-time estimator. If you cannot staff 32 bids, the levers are a higher win rate through better selection, or a smaller target.
Measure conversion rates from your own recorded outcomes, and re-run the arithmetic quarterly, because win rates move with category mix. The bid pipeline calculator runs this chain for any target, rates, and average award size.
The funnel does not end at Won
The day you win a contract, two clocks start. The first is delivery. The second is the recompete: your new contract has an end date, and that end date is a future tender with you as the incumbent.
Create the recompete as an identified opportunity the week you win, dated 6 to 12 months before expiry, the window the recompete timing lesson mapped. Between now and then, incumbency defence is mostly delivery made visible: documented performance, renewed certifications, and attention to the buyer's other awards, because shifts in its supplier mix show up in award data before they show up in meetings.
And remember the symmetry: every contract you won is sitting on a competitor's radar with the same expiry date. The difference between an incumbent that holds and one that gets displaced is usually which side treated the recompete as a pipeline entry from day one.
That closes the course. You know how these procurement systems work, how to read a bid table, when expiring contracts create openings, how to price against history, and how to run the whole flow as a funnel with math attached. The pipeline is the piece that compounds: every recorded outcome makes the next gate call, price, and coverage estimate a little less like guessing.