Why government pursuits break a normal sales pipeline
A commercial deal moves in a recognizable arc: a lead shows up, you qualify it, you demo, you negotiate, you close — weeks, maybe a couple of months. Drop a government opportunity into that same shape and it snaps. A federal pursuit — a SBIR topic, an agency BAA, a subcontract on a prime's bid — can sit in your sights for a year or more before a single dollar moves, gated by funding cycles, solicitation release dates, and a proposal deadline you don't control. The buyer isn't one person with a budget; it's a contracting officer, a technical point of contact, a program manager, and sometimes a prime contractor standing between you and the agency. Treat that like a normal deal and your pipeline lies to you — it either shows a "90% close this month" opportunity that's really eighteen months out, or it quietly loses the pursuit you should have been nurturing all along.
The teams that win government work — especially the small SE and aerospace shops chasing SBIR/STTR and early subcontracts — succeed not because they have a fancier pipeline but because they track the right things: the pre-solicitation capture work, the relationships across a buying committee that doesn't behave like a commercial one, the teaming partners, and the unforgiving calendar. You don't need a six-figure capture-management suite to do that. You need a CRM you'll actually keep current, bent to the shape of the work.
Capture is the pipeline before the pipeline
In commercial sales, the pipeline starts when a lead appears. In GovCon, the most important work happens before anything is biddable — the phase capture managers call, simply, capture. It's the months of positioning before a solicitation drops: learning the agency's real problem, shaping requirements through legitimate pre-RFP engagement, identifying the incumbent, and deciding whether you'll bid at all. A pursuit you first hear about when the RFP hits the street is one you've probably already lost to whoever spent the prior year on capture.
So the first adjustment is to model capture as its own set of pipeline stages that sit ahead of "proposal." Something like: Identified → Qualifying → Capture/Positioning → Bid-No-Bid → Proposal → Submitted → Awarded/Lost. Each stage has an honest exit criterion the same way a healthy commercial pipeline does — you don't advance to Capture until you've confirmed the opportunity is real and funded, and you don't advance to Proposal until you've made a deliberate bid-no-bid decision. The discipline is identical to commercial pipeline stage design; only the stage names and the timescale change.
The bid-no-bid decision is your most valuable qualification
A small team's scarcest resource is proposal effort. A serious federal proposal can eat weeks of senior engineering time, and chasing the wrong ones is how shops burn out their best people on bids they were never positioned to win. That makes the bid-no-bid gate the single highest-leverage qualification decision you make — the GovCon equivalent of disqualifying early instead of hoping late.
Treat it as structured data, not a hallway conversation. On each pursuit, capture the answers that decide it: Is it funded, and is the money real? Do we have a genuine technical fit, or are we reaching? Who's the incumbent, and can we unseat them? Did we do real capture, or are we cold? What's our honest probability of win? Recording those answers on the opportunity record — the same way you'd capture MEDDIC fields on a commercial deal — turns "should we bid?" into a decision you can see and defend, instead of a gut call you'll second-guess at 2 a.m. the week the proposal is due.
A buying committee that doesn't behave like a commercial one
Government opportunities have stakeholders, but the roles are different and the rules are stricter. There's the contracting officer (CO) who owns the procurement mechanics, the technical point of contact or COR who owns the requirement, the program manager who owns the mission, and — during a blackout period after a solicitation drops — a hard wall on who you're even allowed to talk to. Map all of them as contacts tied to the pursuit, with their role noted, because the relationship you build with the technical POC during capture is exactly the relationship-first advantage a generic pipeline throws away by reducing a deal to one name and one number.
This is where logging every interaction stops being good hygiene and becomes a competitive necessity. A pursuit that spans a year will outlast someone's memory of who said what at an industry day eight months ago. When every call, every conference conversation, and every capability briefing lives on the pursuit's timeline, the proposal team a year later inherits the full context instead of reconstructing it from a half-remembered email thread.
Teaming partners are relationships you also have to manage
Few small shops win federal work alone. You're a sub on someone's prime, or you're a prime assembling subs, or you're hunting a teaming partner who brings the past performance you don't have yet. Those partners are a second relationship graph running alongside the agency one — and they decay if you only think about them when an RFP forces it. The prime who'll carry you onto their next bid is the one you stayed in genuine contact with, which is the same logic as building a referral pipeline: the warm path converts and the cold ask doesn't.
Track teaming partners as their own contacts and pursuits, note what each brings (a NAICS code, a clearance, a past-performance qualification, a relationship with the agency), and set follow-up tasks to stay in touch between solicitations rather than scrambling to assemble a team in the two weeks before a deadline.
The calendar is the part you cannot fumble
Everything in a government pursuit ladders up to dates you don't set: the solicitation release, the questions-due date, the proposal deadline, the period-of-performance start. Miss the proposal deadline by a minute and a year of capture evaporates — there is no "we'll take it next week." This is speed-to-lead discipline turned into a months-long countdown, and it's exactly where a CRM earns its keep over a spreadsheet.
The move is to turn every known date into a task with enough lead time to actually act — a task to draft the proposal outline three weeks before submission, a task to submit questions before the cutoff, a task to check for amendments weekly. And because these milestones repeat across every pursuit, an automation can materialize the standard set the moment an opportunity enters the Proposal stage, so the checklist a winning bid needs is dropped in front of you instead of living in someone's head.
Run it inside the CRM, not in a spreadsheet that goes stale
Most small GovCon shops track pursuits in a shared spreadsheet, and it works right up until the pursuit you cared about quietly fell off row 40 and nobody followed up. The reason to move off the spreadsheet is the same reason it matters everywhere: a spreadsheet holds data but does nothing with it, while a CRM acts.
In Hitt CRM, a government pursuit is a deal on a pipeline whose stages you can shape into a capture-through-award flow, with the CO, the technical POC, and your teaming partners as contacts on a shared timeline that survives the long cycle. Tags and contact properties let you mark agency, NAICS, set-aside type, and incumbent so a segment can answer "every active SBIR pursuit we haven't touched in 30 days" in one click. Automations fire the proposal-milestone tasks and the partner-touch reminders so deadlines don't depend on memory, and reports turn your pursuit history into a real bid-no-bid track record: your true win rate by agency, by set-aside, by whether you ran capture — the numbers that tell you which pursuits to chase next year and which to walk away from.
The one-sentence version
Government and SBIR pursuits run on a year-long, multi-stakeholder, deadline-locked cycle that a commercial pipeline mangles, so the win is to model capture as stages ahead of the proposal, make bid-no-bid a structured qualification decision, track the contracting officer and technical POC and your teaming partners as the long-lived relationships they are, and turn every immovable date into a CRM task an automation drops in front of you on time — all run through one system so a pursuit you've nurtured for a year doesn't die because it fell off a spreadsheet nobody refreshed.