Building & Paying a Sales Team

Introduction

Growing an architecture or engineering firm past founder-led selling takes more than a few rainmakers. You need a real business development engine. That means you stop relying on the principal to chase every lead, attend every lunch, and carry every proposal. Instead, you build a team that can find work, qualify the right projects, and move prospects through a repeatable pursuit process.

For firms in this industry, sales is not about pushing a product. It is about earning trust for complex, high-value services. Clients are buying design judgment, code knowledge, coordination skill, and the ability to keep a project moving without surprises. That is why your business development people must understand project types, fee structures, client pain, and the risks that keep owners awake at night.

Recruiting the Right Talent

The best business development hires in this field are not always the loudest. They are the ones who can speak with owners, developers, contractors, and public-sector clients in a calm, credible way. You want people who understand how architecture and engineering projects actually get won: through relationships, pre-positioning, specification influence, and trust built long before the RFP drops.

A strong hire might come from a competitor, a construction-related service, or even from inside your own firm. For example, a project manager with great client instincts may outperform a polished outside salesperson because they know how a design team thinks and can talk honestly about scope, schedule, and risk. During interviews, ask how they would approach a school district, a hospital owner, or a developer with a tight pro forma. Look for people who can connect business goals to project outcomes, not just people who "sell."

Training and Development

Once hired, your business development team needs a real onboarding path. They must learn your firm’s service lines, ideal client types, fee philosophy, project delivery methods, and the handoff process from pursuit to project kickoff. Without this, they will chase bad leads, overpromise timelines, or bring in projects that clog the studio and kill margin.

A good training program should cover how to qualify opportunities, how to read a request for proposal, how to build a pursuit plan, and how to present the firm’s value without sounding generic. New hires should sit in on interviews, review fee proposals, and listen to project closeout meetings so they understand what creates profitable work and what creates chaos.

For example, a 30-day onboarding plan might include shadowing senior principals on three pursuits, learning how to use the CRM, studying win/loss history, and practicing short pursuits presentations for healthcare, civic, or commercial clients. By the end, they should know the difference between a good project and a shiny disaster.

Compensation Plans

Compensation in this industry has to reward both wins and the right kind of wins. If you only pay for booked revenue, you may end up with low-fee, high-drama projects that damage the firm. If you pay too much fixed salary, you get comfortable people who talk a lot and close little.

A better plan ties incentives to qualified wins, gross margin, and project fit. For example, a business developer could earn a bonus when they help win a project above a minimum fee threshold, with a bigger payout if the project stays on budget and client satisfaction stays strong after kickoff. That keeps them focused on value, not just volume.

You can also reward team behavior. In many firms, the principal, project manager, and pursuit lead all play a role in winning work. Build a structure that recognizes that shared effort, so your best technical people stay engaged instead of feeling like sales is "someone else’s job."

Overcoming Challenges

When architecture and engineering firms shift from founder sales to a team approach, the first problem is usually inconsistency. Some people know how to pursue work, others do not. One principal may win through relationships while another sends weak proposals and hopes for the best. That creates uneven results and internal frustration.

The fix is a standard pursuit system. Create a playbook for go/no-go decisions, client research, interview prep, proposal review, and follow-up. Use the same steps on every pursuit so the team knows what good looks like. Build scripts for common objections too, such as fee pressure, schedule concerns, or "we are talking to three other firms." This helps new business developers and technical leaders present a unified message.

Conclusion

Building and paying a sales team in an architecture or engineering firm is really about building trust at scale. The goal is not just to bring in more work. It is to bring in the right work, through the right people, with a process that your firm can repeat. When you recruit well, train deeply, and pay for profitable wins, your business development engine becomes a real asset instead of a founder dependency.