Last week, I had breakfast with one of my favorite school district clients. We were talking about interviews and what separates the teams that rise to the top from the ones that look good on paper but fail to make the same impression in the room.
They said something I need to share with anyone responsible for winning work: the team that demonstrates how it will work with the client scores best.
Not necessarily the team with the most polished presentation. Not always the team with the longest list of relevant projects or the strongest individual résumés. The team that helps the client experience what working together will actually feel like.
Then, over lunch, one of the state’s top owner’s representatives validated the very same idea. We were discussing a recently awarded project when they said, “Your superintendent won that project for you. He showed us what it would be like to work with him.”
Two conversations. Two highly experienced clients. The same conclusion.
The interview is not simply a presentation. It is a preview of the working relationship.
Qualifications get you shortlisted. Confidence gets you selected.
Most teams treat the interview as the moment when they need to convince the client that they are qualified. They spend weeks perfecting slides, rehearsing transitions, anticipating questions, and deciding who will cover each section. All of that matters, but it can create the illusion that confidence is something a team can manufacture once it enters the room.
It is not.
Interviews do not manufacture confidence. They reveal whether the preparation created it.
When a team truly understands the client, has spent meaningful time together, has wrestled with the work’s hardest challenges, and knows how each person will contribute, you can feel it. The answers are natural. The handoffs are smooth without appearing scripted. Team members listen to one another and build on each other’s ideas instead of waiting for their turn to speak. When someone receives an unexpected question, the others do not panic. They trust that person to respond, and they know when to add something useful.
When that preparation has not happened, you can feel that too. The presentation may be beautiful, but the team still feels like a collection of individuals. Everyone knows their assigned slides, yet they do not appear to know one another. Their answers are technically correct, but the client is left wondering how the team will respond when the work becomes difficult and there is no script.
Because the client is not only evaluating whether your team can do the work. They are imagining what it will feel like to do the work with you.
The real questions are rarely written on the page
A client may ask about schedule, cost, communication, risk, stakeholder engagement, technical challenges, or unforeseen conditions. Those are the questions on the page. Underneath them are much more human questions.
Will you tell us the truth when the news is not good? Will you listen before deciding what we need? Will you make our jobs easier or create more work for us? Will the people in this room actually be the people we see after the contract is signed? Can we trust your judgment when the answer is not obvious?
That is why I tell teams to answer the question underneath the question. The technical answer matters, but the client is also listening for evidence of judgment, chemistry, humility, candor, and trust.
If clients ask how you will manage a delayed decision, they do not only want to hear about your tracking system. They want to know whether you will identify the issue early, explain the consequences clearly, and help them make a decision without making them feel blamed.
If they ask about conflict, they do not need to hear another team claim that it communicates well. Every team says that. They are trying to determine whether you can disagree constructively, remain calm, and protect the work without damaging the relationship.
If they ask about the person who will lead the work every day, whether that person is a superintendent, architect, engineer, project manager, consultant, strategist, or account lead, they are not only evaluating technical qualifications. They are deciding whether this is the person they want beside them when the work becomes complicated, the schedule is slipping, and stakeholders are demanding answers.
Your résumé may get you into the room. Your behavior wins the work.
The owner’s representative did not tell me that our superintendent won because he had the longest résumé or the greatest number of similar projects. They said he showed them what it would be like to work with him.
That is a different kind of proof, and it is not limited to construction.
An architect can create confidence by showing how they listen to competing stakeholders and turn ambiguity into a clear design direction. An engineer can make the difference by explaining a complex technical issue in a way that helps the client make a better decision. A consultant can demonstrate that they will challenge assumptions without making the client feel challenged. A business leader can show that they understand not only the work being proposed, but also the pressure the client will face while delivering it.
In every industry, clients are trying to determine whether the people in front of them will make the work better, the decisions clearer, and the difficult moments easier to navigate.
Strong interview teams do not simply describe collaboration. They demonstrate it. They do not tell the client that they communicate well. The client watches them communicate well. They do not claim to value different perspectives. The client sees them invite another team member into the answer. They do not say they will listen. They listen during the interview, adjust their response, and remain curious.
The interview becomes a small sample of the working relationship.
Where most interview preparation falls short
Most teams do prepare. The problem is that they prepare for the presentation instead of preparing for the decision.
They review the solicitation. They divide the slides. They refine the graphics. They rehearse until everyone can deliver their assigned section within the allotted time. Then they walk into the interview believing that if they communicate their qualifications clearly enough, the client will choose them.
But qualifications are usually what got them shortlisted. The interview is where the client decides whether those qualifications belong to a team they can trust.
This is where even experienced teams miss the mark. The senior leader carries too much of the conversation because they are the strongest presenter. Technical experts provide more detail than the client needs. The people who will lead the work every day are given one slide and told to stick to the script. Everyone practices speaking, but no one practices listening, building on another person’s answer, or responding when the conversation moves somewhere unexpected.
The team leaves feeling that the interview went well because it covered everything it intended to cover.
The client leaves asking a very different question: Did we just meet the people we will actually be working with?
That may be why your highly qualified team keeps coming in second.
The Client Confidence Framework
Before anyone begins polishing slides, I take teams through what I call the Client Confidence Framework. It shifts interview preparation away from presenting qualifications and toward creating the confidence a client needs to choose you.
The framework asks four questions:
What is the client really deciding?
What does the client need to experience from us?
Who needs to make that confidence real?
How will we demonstrate it?
The questions are simple. Answering them honestly, building agreement around the answers, and translating them into an interview strategy is not.
The four questions are simple. Knowing how to answer them, align your team around them, and demonstrate the answers in the room is where most interview strategies fall apart. Paid subscribers can continue reading to learn how to apply the Client Confidence Framework.
