No, The Grass Isn’t Greener in Other GovCon BD Shops
There’s a persistent belief in government contracting that somewhere out there is a perfectly functioning business development organization. A shop with a clean pipeline, airtight capture discipline, flawless win rates, and complete executive alignment. When revenue dips or bids are lost, it’s easy to assume the problem is internal and that other companies must have figured it out. Let me dispel the myth. Other companies have not figured it out.
After years of working with various organizations, including small businesses, mid-tier contractors, larger integrators, academic institutions, and government agencies, I’ve observed a consistent pattern. Every organization tends to believe that its business development (BD) challenges are unique, and many present an inaccurate portrayal of their BD teams. In reality, most organizations face similar structural challenges, albeit presented in different ways.
One common myth that I frequently encounter is the belief that increasing volume can solve growth problems. This is simply not true. The “spray and pray” approach, which involves submitting more Requests for Information (RFIs) and proposals, and entering more Indefinite Delivery/Indefinite Quantity (IDIQ) contracts, generates activity but lacks a defined strategy. Federal agencies do not award contracts based on enthusiasm or the number of submissions. They award contracts based on factors such as relevant past performance, a clear understanding of the mission, the advantage of incumbency, familiarity with the customer, and credible technical expertise. When companies pursue every opportunity that seems “close enough,” they dilute their positioning, stretch their capture resources, and exhaust their proposal teams. Submitting more bids does not necessarily lead to more wins; in fact, it often results in more losses. (See my recent article on Shiny Object Syndrome – SOS for more on this).
The second myth is that having a mature process alone guarantees success. Many companies respond to inconsistent results by establishing increasingly rigid capture frameworks. If you can’t figure out why you lost a recent proposal, I can assure you that adding a fourteenth-stage gate, increasing the amount of mandatory documentation, and/or requiring executive approval for every action in the CRM won’t help. While this approach may seem disciplined on paper, the reality is that federal contracting is way more dynamic. Funding can shift, requirements can merge or change, and policy changes can significantly alter priorities before ever being announced. Acquisition strategies can (and often do) evolve unexpectedly during the opportunity lifecycle. And the government isn’t known for being the best at updating that information in real time. If your capture process is unable to adapt to these realities, it becomes an exercise in performative compliance (compliance theater, perhaps) rather than strategic enablement. While discipline is important, excessive rigidity is not; it will inevitably become a burden even for the best teams.
Another uncomfortable truth is that most BD shops are far less institutional than they appear from the outside or advertise. Big companies still struggle to rein in their processes, and corporate knowledge is often trapped in individuals rather than embedded in systems. When a senior capture lead leaves, the context they created leaves with them. This prompts the next person to question why a similar opportunity was passed on, what competitive intelligence influenced prior pricing, and which discriminator resonated in the last industry engagement. CRM entries (should) capture data, but they don’t capture judgment or personal decision-making processes. Many organizations are still patching together institutional memory through email chains, slide decks, and verbal history. The perception of a polished growth engine often masks fragile knowledge-retention processes. Think about this next time you walk into a conversation with a legacy prime expecting it to be a top-tier organizational capture/BD process shop.
Perhaps the most pervasive issue, however, is structural misalignment around responsibility. In many organizations, BD is treated as singularly accountable for revenue growth. Pipeline thin? That’s a BD problem. Win rate down? Another BD problem. Recompete lost? Clearly, BD should have positioned better. This perspective blatantly ignores reality. BD can’t operate in isolation, nor should it. The BD team can’t invent strong past performance if delivery falters (never mind that many do, especially with the rise of AI tools that smooth over rough edges and hallucinate). BD can’t craft credible solutions without technical subject matter experts engaging early (no, asking them to plug information into ChatGPT and hope for the best output doesn’t count as subject matter expertise). BD can’t correct misaligned pricing strategies without input from the finance discipline. BD can’t build authentic customer intimacy while SMEs remain billable and absent from engagement.
Federal growth is an enterprise function. It requires coordinated behavior across leadership, technical teams, operations, finance, and contracts. When that coordination is weak, outcomes suffer. Assigning full responsibility to BD may simplify internal narratives, but it does not solve the underlying problem.
The belief that “another company has it figured out” often reflects internal frustration more than external reality. Every BD shop has dysfunction. Some chase too much. Some overanalyze and miss windows. Some obsess over process. Some operate reactively. Some hoard institutional knowledge. Some pretend their CRM is a strategy. The dysfunction varies, but it exists everywhere.
The federal market itself compounds the challenge. Acquisition cycles are long and uncertain. Funding profiles shift with appropriations and continuing resolutions. Executive Orders and policy reforms can redirect agency priorities within months. Workforce reductions affect procurement timelines and oversight capacity. Vehicles consolidate, increasing competition density. Compliance burdens expand. In that environment, no BD organization operates under stable, predictable conditions.
The companies that consistently win are not those with mythical perfection. They are those with alignment. They focus on defined agencies rather than everything everywhere. They make deliberate bid/no-bid decisions. They involve technical leadership early and visibly. They document lessons learned beyond superficial checklists. They distribute ownership of growth across the enterprise rather than concentrating it in one department.
The grass is not greener in other BD shops. It is simply managed differently.
For executives, the takeaway is straightforward: growth is not a department. It is a culture supported by process, accountability, and cross-functional engagement. Hiring a stronger BD lead will not compensate for weak delivery, absent technical participation, or unfocused strategy. Sustainable growth requires enterprise discipline.
Until organizations internalize that reality, BD professionals will continue to look over the fence, convinced that someone somewhere else has solved the equation. They will move, only to discover that the challenges look and feel remarkably familiar.