Why great delivery does not automatically create growth

Most technical services firms are built on an unspoken assumption: do excellent work, and the work will speak for itself. Referrals will come, clients will return, and our reputation will travel. And for a while, it does. Good work begets more good work, and a firm grows to twenty people, then fifty, then well past a hundred, carried by delivery quality and the relationships a few senior people have built over years.

Then growth seems to lose momentum. The work is as good as it has ever been, arguably even better as the team is more capable. But the order book stagnates or feels thinner, and new work still depends on the same handful of people and the same handful of relationships. When those people are busy delivering, which is most of the time, business development is on hold. Nobody decided this; it just happens. The issue is not that the firm has stopped being good; it has simply reached a stage where informal growth mechanisms no longer carry the same load.

The usual response is that the firm needs to "do more BD": more proposals, more networking, a better website, someone to chase leads. This does bring relief, but not a long-term solution, because it treats a structural gap as an effort problem.

What makes the firm valuable also makes growth hard

Here is the part that is easy to miss. In a technical services firm, the thing that makes you valuable is the same thing that makes growth hard. Clients do not buy a product they can trial and return. They hand you a problem they cannot fully see, and they trust you to make decisions that carry real consequences. They open themselves up in a way someone trying a new tool never does. That trust is genuinely earned, usually in the field, under pressure, over time, and it is the whole foundation of the relationship.

But trust on its own is reactive; it lives between specific people, and it waits to be called on. It does not decide which sectors you want to grow into. It does not get you into the right conversations before a need becomes a tender. It does not make sure the next project is already taking shape while the current one is still running. That is a different kind of work: identifying, shaping, and pursuing the right opportunities on purpose, in line with where the firm has decided to go. It is business development in the real sense. Yet it is rarely framed for technical services, rarely grounded in a clear strategy, and rarely treated as a discipline of its own.

BD has no settled discipline for technical services

There is a deeper reason this catches good companies off guard. Almost every other function in a business has a settled body of knowledge to lean on. Finance has accounting; HR, legal, engineering, each has its own discipline, its own training, its own accumulated craft. Business development has plenty of generic advice, but far less practical discipline that fits this technical services context. Most of what is written about BD was built for selling products or repeatable offerings, where the buyer's risk is low and the sale is a transaction. Technical services is the opposite: high-trust, advisory, consequential. The models do not transfer, so firms improvise; success varies and improvisation does not easily scale past the founders.

None of this is a failure of talent or effort; it is the absence of a system. The growth that delivery and founder-led relationships can carry has a ceiling. At some point, what helped the firm grow informally needs to become a more deliberate management practice. Capable firms reach it without ever doing anything wrong. In fact, it is a growth milestone.

Crossing it takes a light, deliberate BD system: one that turns the firm's strategy into a steady pipeline of the right opportunities, runs as a rhythm that survives a busy delivery month, does not depend on a single person's network, and fits how technical people actually work rather than forcing them into sales behaviour that feels false.

That is the work I have built BDF Partners around: how business development, strategy, and foresight come together for technical and professional services firms. The next piece starts with what business development actually is, and what a firm's growth rests on.