Fractional Business Development for Civil, Structural, and MEP Engineering Firms

Business development for engineering firms works differently than it does in most industries. The buyer usually publishes the criteria, scores the submittal against them, and in public work is often required to rank firms on qualifications before fee is discussed at all. Other technical industries are covered on the industries overview.

How do owners and agencies choose an engineering firm?

Engineering firms sell to two kinds of buyers, and both evaluate before anyone discusses fee. Public owners — cities, counties, water and sanitation districts, transit agencies, school districts — run a formal process. Developers, architects, and prime consultants run an informal version of the same one.

The public version is public on purpose. An agency advertises a request for qualifications, firms submit a statement of qualifications, and a selection committee scores each one against criteria printed in the solicitation. Typically three to five firms are shortlisted and interviewed, the committee ranks them, and fee is negotiated with the firm ranked first. Under qualifications-based selection, cost is not part of the score at all.

What earns points is narrower than it looks from outside: project experience of the same type, size, and jurisdiction; the named staff who will actually do the work; and evidence the firm understands this project rather than projects like it.

The part that decides the outcome usually happened months earlier. A project reaches a solicitation only after it has moved through a capital improvement plan, a funding decision, and scoping conversations with someone who already has a firm in mind. A strong submittal confirms a preference more often than it creates one.

Private work moves faster and skips the paperwork, but it runs on the same logic. A developer or an architect brings back the structural or MEP engineer whose drawings held up through plan check and who made the last project easier. That is a qualifications review too. It is simply held in one person’s memory.

So the leverage is rarely in the submittal itself. It is in whether the firm is already familiar to the people scoring it.

Where growth stalls in a civil, structural, or MEP practice

The constraint is almost never engineering. Licensure, portfolio, and repeat clients are already in place — growth is held up in four other places.

The people who win the work are the people billing the work. In a seller-doer practice, pursuit happens in whatever is left of a project manager’s week after deadlines, review comments, and client calls. So it expands when the backlog thins and disappears when it is full, which is precisely backwards: owner relationships are built over quarters, not in the month a firm needs them. Worse, those relationships sit personally with two or three senior principals and are written down nowhere the firm owns.

Every solicitation looks like an opportunity. Without a written standard for which pursuits to decline, the default answer is yes, and a go/no-go call made two days before a deadline is not a decision. It is momentum. The cost is billable hours spent on projects the firm was never positioned to win, and staff who stop believing a pursuit is worth their evening.

The submittal is assembled rather than written. In a compressed pursuit, the resumes come off the shelf a version out of date, project sheets describe scope instead of what the client got, and the sections a committee actually scores — understanding of this project, the approach, the named team — are the ones written last and fastest. The firm’s best evidence exists, but not in a form a pursuit can use.

Nobody asks why the firm lost. Debriefs go unrequested, committee scores are never collected, and a shortlist missed by one place is filed as bad luck. Without that record, the firm cannot say which client types it wins most often, what a pursuit costs in hours, or how many wins began with a relationship that predated the RFQ. The next pursuit then repeats the last one’s assumptions, including the wrong ones.

How does fractional business development work inside an engineering firm?

It begins with what leadership wants to be true a year out. For most engineering firms that comes down to three results: a larger share of pursuits won, on fewer attempts; a backlog that no longer rests on two principals’ relationships; and more repeat work — task orders, on-call assignments, later phases — from owners the firm already serves.

Every SignalCraft engagement runs on the same four stages. Here is what each one looks like when the buyer is a public agency or a prime consultant.

• Found. When an agency engineer or a developer’s project manager searches — in Google or in an AI answer — the firm’s disciplines, project types, and jurisdictions are what surfaces, not a services list that could belong to anyone.
• Trusted. What the firm puts in front of them is material an evaluator could score: project write-ups matched to the work it wants more of, current resumes for the people who would be named, and references who can speak to schedule, permitting, and how the firm behaved when the scope changed.
• Chosen. Pursuits are decided before they are written. That means written criteria for which solicitations the firm answers and which it declines, deliberate contact with priority owners while capital plans are still being set, and a submittal process that starts from the project rather than from the library.
• Measured. Leadership can see win rate by client type and project size, what each pursuit cost in staff hours, and how many wins began with a relationship that existed before the solicitation.

The tactical work is chosen last, once the diagnosis is clear: search and website pages that name disciplines, project types, and jurisdictions; a project and resume library kept current between pursuits; a CRM organized around owners and their capital programs; a debrief requested after every decision; and a monthly report a principal can read in five minutes.

The aim throughout is that the firm ends up operating this itself. A system that depends on an outside party is not much better than one that depends on a single principal.

Where this comes from

SignalCraft does not have an engineering firm as a client today.

What sits behind this page is Colin Bunyard’s work in industrial and infrastructure markets, where buyers move cautiously, procurement runs on a published calendar, and a working relationship tends to outweigh anything a firm says about itself. What carries across is the shape of the problem: capable organizations whose growth depends on a few senior relationships, long evaluation cycles, and decisions largely formed before a formal process opens.

The fair test is whether the description above matches how work actually arrives at your firm. Where it does not, your own record should win the argument.