Projects are won before the RFP exists. Outbound reaches developers, owners and general contractors while a project is still a permit application or a press release, so your firm is in the conversation before the shortlist is drawn.
Hi Elena,
The planning board agenda for the Rockville site shows a five-storey lab and office building with a parking structure, which I gather went through on the second reading last month.
We were the structural and MEP engineer on a lab building of similar size in Frederick that finished last year. The vibration criteria on the upper floors drove the framing, and we kept the floor plate flat enough that the tenant fit-out went in without changes.
If the consultant team is not yet fixed, would twenty minutes next week be worth your time?
[Your name]
Design firms win work through principals who have known a client for a decade, through repeat clients who bring the next building, and through RFPs that arrive after the owner has already decided who they want. Public work runs on qualifications and SF330s, private work runs on who the developer had lunch with. Both reward the firm that was in the room early, and neither gives a principal who is also stamping drawings any time to get into new rooms.
When engineering firms try outbound themselves it is usually a marketing coordinator sending a capabilities PDF to a list of general contractors, or a principal who means to follow up after the conference and never does. Developers and owners delete capabilities decks unread. Run properly, the email lands while the project is a planning submission or a bond approval, names the project, cites one comparable building you delivered, and asks for twenty minutes before the design team is fixed.
Engineering buyers care about comparable projects. Every email we write here names one, so the reader can picture your firm on their site.
We build the list from projects, not from firm directories. Planning and zoning agendas, permit applications, bond measures, capital improvement plans and groundbreaking coverage tell us who is about to need a design team and for what. We take the development manager, project executive or capital planning lead who chooses consultants, not the front desk, and we exclude any client, teaming partner or project you tell us to.
Before writing, our copywriters read the project: the site plan on the planning agenda, the square footage and use in the permit, the bond language that funds it, the architect if one is named, and what the same owner built last time. That tells them the stage the project is at and which of your past buildings the reader will recognise as comparable, the only proof an owner trusts.
Engineering emails fail when they list services. Ours name the project, its stage and one building you delivered that is like it, with a detail a technical reader will believe: a structural system, an energy target, a schedule held. No capabilities statements, no awards and no adjectives about your team. The ask is a short call before the consultant list is set, not a request to join a vendor database.
We send Tuesday to Thursday mornings in the prospect's time zone, from dedicated domains we warm for three to four weeks, so nothing touches your firm's own domain. Timing follows the approval calendar: planning commission dates, fiscal year budget adoption for public owners, November bond elections and the quarter after a groundbreaking. Follow-ups a few days apart add a second comparable, and the sequence stops the moment anyone replies.
Replies come to you and to the portal, sorted into interested, not now and out of office. An interested developer usually asks for a project list or a meeting with the principal, so the principal who would lead the work answers within a day, not a marketing coordinator. Not now often means the RFQ comes later, so we note the date. Every two weeks we review which project types reply.
It names the project, the approval it just cleared and the building type, so the reader knows within a sentence that the sender read the agenda. The proof is one comparable building with one technical detail, vibration criteria, that a development director will recognise as real. It leaves out the firm's founding year, its awards and its service list, none of which get Elena to reply.
Not with the scoring, but with what happens before it. Public owners write RFQs with firms in mind, and a programme manager who has already had a call with your principal about a comparable project reads your SF330 differently. We target the capital planning and public works leads before the RFQ is issued, and we leave the procurement office alone.
Almost none until a reply lands. We build the list, research the projects and write in the principal's name, and the principal sees the email only at approval and when a developer answers. What we do ask is that the principal who would lead the work takes the call, because developers reply to engineers, not to business development staff.
They reply to firms that clearly know their project. A development director with a building in planning is already assembling a consultant list, and an email that names the building and a comparable one you delivered is a shortcut, not an interruption. The emails that fail are the ones that describe your firm instead of their site, so we do not send those.