Here's a scenario I've been putting to engineering leaders lately. The client writes some of the RFP with AI, you write parts of your response with AI, and they score it with AI. So who gets the work?
Most rooms get there quickly. The work goes to the firm with the better relationship, the one whose people listened and understood what mattered to the people behind the project, not just its technical features. When every proposal reads well, the firm that out-listens its competitors wins.
That's what being the first call is about. AI can't take it from you, but you do have to earn it, and plenty of your competitors won't bother.
Knowing the project, not the client
I built my program around a frustration. I'd sit with sharp project managers and senior engineers, and they could tell me everything about a project: the traffic counts, the permitting hurdles, maintenance of traffic challenges, and right-of-way issues. Then I'd ask about the client. Who has to defend this project at the commission meeting? What would make it a career win for the person who hired you?
Mostly, I got silence . . . and then more about right-of-way.
That's a contractor. A contractor is handed a scope and delivers it, often beautifully. Clients value good contractors, but they see them as interchangeable, so the next project goes to whoever's next in line, or to whoever happens to come to mind. Technical excellence gets you to the table, but it doesn't decide what happens once you're there.
What it means to be the first call
The first call is the one a client makes before there's an RFP, often before they've even pinned down what the problem is. They pick up the phone and say, "I've got something I'd like to think through with you."
That call gets earned one conversation at a time, and often not by the principal whose name is on the proposal. More often it's the project managers and technical leads the client talks with every week, the people in the middle of your firm, who either climb from contractor to advisor or stay stuck shuttling deliverables back and forth.
Advisors get brought in upstream, while the project is still taking shape and the scope is still soft. When the work does go out for bid, it often reads as if the advisor helped write it. [Funny how that happens.]
How you climb: DIG
If you lead a professional services firm, you probably know The Trusted Advisor by David Maister, Charles Green, and Robert Galford. It traces how a client relationship deepens, from being valued for a service to being trusted for your judgment, and for many firm leaders it's still the bible. The question I hear from them most is a practical one. What does a project manager actually do, conversation by conversation, to make that climb?
In The First Call, the short book I'm writing for consulting engineers, I call the method DIG: Discover, Interpret, Guide.
Discover is where consultative questioning and empathetic listening do their work. You ask open questions about the client's goals and the people they answer to, then listen past the technical issue to whatever's underneath it. If you think you know the answer, ask one more question to test it.
Interpret means making sense of what you heard. What does this client value most, and what's the real risk to them personally? Here an engineer's understanding of the work has to share the stage with judgment, curiosity, and empathy.
Guide earns you the advisor's seat. You bring a point of view and recommend a path, even when it isn't the one the client walked in expecting. Plenty of firms will answer the question the client asked; an advisor helps them ask a better one.
You won't learn this in a lecture any more than you learned to design that way. It takes practice and honest feedback on real client conversations.
The firm they call first
Every firm in your market can buy the same AI tools, but none of them can buy a project manager the client trusts enough to call first. Build that in your people, and you'll spend your time shaping work upstream while your competitors chase RFPs they were never positioned to win.