How Do I Filter Out the Clients Who Will Ruin My Firm?

A quick reminder for every architect and firm principal: not every client is meant to work with you.

---

You have met this client before. They second-guess every decision, want to run the process themselves, and ask you to summarize and compare every option down to the hardware finish on a door pull. A typical project involves thousands of decisions. Taking on a client who wants to litigate every one of them is a bad business decision, even if you like them and genuinely want to help.

Before saying yes to a project, make the distinction consciously. Are you taking this on because it is a healthy move for your firm, or because you want to be helpful, even if it costs you your time, your fee, and your peace of mind for the next year or two.

Walking away is hard. It is also often the most profitable decision available to you. At minimum, learning to spot the wrong clients early lets you point them somewhere else before either of you has invested real time.

The red flags show up in the first call

A bad fit usually reveals itself before you have drawn a single line. Watch for these during the initial inquiry.

• An unrealistic budget for the scope described.
• An unrealistic timeline, especially one that assumes permitting and approvals will move faster than they ever do.
• A strong desire to run the process themselves, with you executing rather than advising.
• A request for the bare minimum: "just the construction documents," or "just the drawings," with no interest in programming, options, or a real design phase.

None of these make someone a bad person. The problem shows up when their expectations reveal that how they want to work is fundamentally opposed to how you work. As the architect, it is your job to guide the process. If they are not willing to be guided, that is the clearest signal available that they do not trust you or the process you are proposing.

What it costs you when you ignore them

When a client does not trust the process, it shows up fast, usually at the worst possible point in the schedule.

If a project needs to be de-risked early, through zoning research, a feasibility study, or an honest budget conversation before schematic design, a client who does not trust that step will skip it to save a few thousand dollars. They kick the can down the road.

Then the entitlement takes twice as long as planned, or the number the contractor returns bears no resemblance to what the client had in mind, and you are the one standing in the room when it happens. You will not get a referral out of that project. You may not even get a finished building for your portfolio. You will have spent a year or more of your firm's capacity on a pursuit that was decided the day you ignored the first red flag.

The inquiry call is an interview, not a pitch

The biggest mistake architects make in business development is treating every inquiry as a pitch to win. An inquiry is also your interview of them.

When you sign a contract with a client, you are agreeing to a relationship that will shape what your firm does for the next twelve to thirty-six months: entitlements, design development, construction documents, bidding, and a construction administration phase that puts you back in contact with them every week. That is a long time to spend with someone who does not trust your judgment.

You cannot expect a client to trust you by default. You have to give them a reason to, starting from the moment they reach out.

Trust is designed, not demanded

There are two places in your process where trust is either built or lost before the contract is even signed.

Answer the obvious questions before the call. Most firms answer the same handful of questions on every discovery call: what the process looks like, what a realistic budget range is for a project like theirs, what they need to have ready before starting, and what risks they have not thought about yet. Put that on a page. When a prospective client has already read it, the call stops being a logistics briefing and becomes a real conversation about their project, which is the conversation that actually tells you whether the fit is right.

Make the proposal itself do the convincing. A fee number and a bulleted scope of work do not build trust. They invite a client to negotiate the number, because the number is the only thing they can actually evaluate. A proposal that shows you understood the site, the budget constraints, and the approval risk, and that walks through your approach before it gets to the fee, gives a client something to trust before the work even starts. This is also where tracking how a proposal gets read becomes useful information, not just a vanity metric. If a prospective client spends nine minutes on the fee line and forty seconds on the approach section, you have learned something about how this relationship is going to go before you have signed anything.

The bottom line

You cannot force a client to trust you. You can build a firm that makes it easy for the right ones to.

The best clients are not the ones who agree with everything you say. They are the ones who understand why you are recommending what you are recommending, and trust that you are doing it to get them the best outcome, not the easiest one for you. The lesson is not to go find clients who already trust you. It is to build a process that gives the right ones every reason to.

Frequently Asked Questions

What is the clearest red flag in an initial client inquiry? A request to skip the parts of the process that exist to protect the budget and the schedule, like programming, feasibility, or an honest fee conversation. A client who wants to go straight to construction documents is telling you upfront that they do not see the value in what you actually do.

Should I turn down a client I like personally if the fit is wrong? Usually, yes. Liking someone does not change what a twelve-to-thirty-six-month engagement with a client who does not trust your process will do to your team's time and your firm's margin. The personal relationship is a reason to be honest with them about the mismatch, not a reason to ignore it.

How do I say no without losing the referral or the relationship? Be specific about the mismatch rather than vague. Tell them plainly that their timeline or budget does not match the scope, or that their expectations for involvement differ from how your firm delivers projects, and point them toward a firm or a delivery model that fits better. Clients respect specificity more than a soft decline, and it is the version of "no" most likely to produce a referral later for a project that actually fits.

Is this the same thing as a formal go/no-go process? Related, but earlier. A go/no-go framework is how you score a specific opportunity once you have real information about it. This is about what you notice on the first call, before you have enough information to score anything. Firms that do both catch different failures: one catches the wrong opportunity, the other catches the wrong relationship.