Your BD Process Is Not Broken. You Just Do Not Have One

About This Series: BD, Proposals, and Building the Function That Wins - Post 6 of 11

There is a version of business development in AEC that everyone in the industry recognizes. A principal has a relationship with a client. They hear about an opportunity, usually late. They tell the marketing coordinator to "pull something together." The proposal lead, who is already running two other pursuits, gets brought in ten days before the deadline to produce something that was never strategically framed. The team submits something adequate. They usually do not win.

Then they do it again.

This is not a people problem. In most of the firms I have seen operating this way, the individual contributors, the marketing coordinators, the proposal managers, the BD leads, are talented and hardworking. The problem is that they are working inside a function that was never architected as a system. It was assembled from habits.

A BD function that works looks structurally different from this, at every stage.

At the pipeline stage, it means a CRM that is actually used, trusted, and maintained. Not a database that one person updates reluctantly. A live system that reflects the real state of relationships, pursuit stages, and client intelligence, that everyone on the BD and principal team accesses and contributes to. Salesforce, HubSpot, Cosential, the platform matters less than the discipline. The discipline is: if it is not in the system, it does not exist.

At the pursuit identification stage, it means early conversations, well before an RFP materializes, that include the right people. Not just the principal who has the relationship, but the marketing and BD lead who will frame the pursuit strategy, and representatives from the project team who will ultimately execute the work. These conversations are where you build the competitive intelligence, identify relationship gaps, and decide whether to actively develop the opportunity or pass.

At the go/no-go stage, it means structured criteria and ego-removed analysis. This has been covered in this series, but the system point is this: the go/no-go process only works if it is a real process with real criteria, not a meeting that ratifies decisions already made informally.

At the proposal stage, it means the marketing and proposal lead is driving the narrative from the beginning, not executing someone else's outline. The proposal lead's job is to translate pursuit strategy into client-centered communication. They cannot do that job well if they are handed a strategy at the last minute.

At the pursuit review stage, it means regular, honest pipeline reviews. Not reviews where everyone reports good news. Reviews where the team asks, with genuine curiosity: what pursuits are we overconfident about? What client relationships are weaker than we think? What are we pursuing that we should qualify out of?

The reason all of this matters is not just efficiency. It is that the system is what makes authentic relationship building possible. When you are not scrambling, you can actually be present in client conversations. You can follow up when you said you would. You can bring relevant value to a client at a moment when they need it, not just when you need something from them. The structure creates the space for the human quality of the work.

Bernstein's argument about AEC's fragmentation applies inside firms too. Most BD functions are disaggregated, with relationship intelligence in individual heads, pursuit strategy in hallway conversations, and proposal production disconnected from business strategy. The firms that are winning consistently have integrated those pieces. Not perfectly, but intentionally.