When Should an Architecture Practice Say No to a Project?

Nobody in architecture school teaches you to turn work down. You learn it later, usually after one project shows you what a yes really cost.

It rarely looks like a mistake at the start. The enquiry is warm. The site is interesting. The client has seen your work and wants something like it. There's a number on the table that feels fair, maybe even generous. Saying no to that feels ungrateful, and when the next enquiry isn't guaranteed, it can feel reckless.

So most studios decide on the fee. It's the first number you see and the easiest one to compare. If it clears a certain line, the answer is yes.

The trouble is that the fee tells you what you'll be paid, not what you'll spend. A good fee on a loose scope can earn you less than a modest fee on a tight one. The fee is fixed the day you sign. Everything that eats into it arrives later, one meeting at a time.

Scope is usually where it starts. Listen to how the brief is described in the first conversation. "We're flexible." "We'll figure it out as we go." "Just give us a few options." None of these say anything bad about the person saying them. Most clients genuinely don't know what they want yet, and helping them find out is part of the job. But each of those phrases describes work. Options are drawings. Figuring it out as you go is revisions. If the scope isn't written down before the fee is agreed, the fee is covering a project nobody has defined.

Then there's how decisions get made. This is where it's easy to slip into talking about difficult clients, and that's rarely fair or useful. What matters isn't whether someone is pleasant. It's the structure around them. How many people need to approve a drawing? A couple building their first home might need a week to agree on a window. A developer with three partners might need a month. Neither is wrong. But a project where every decision waits on four people moves at a different speed from one where it waits on one, and your fee doesn't know the difference.

A few other signals are worth noticing early. Do replies come back in days or in weeks? Is the conversation mostly about the design, or mostly about price? Has another architect already worked on this project? None of these decide anything on their own. Together, they tell you how the next eighteen months are likely to feel.

Capacity is the part studios think about least, because it doesn't show up in the enquiry at all. Ask a simple question: who in your team will actually do this work? Not the studio in general. The names. Now look at what those people are already doing. A new project doesn't arrive into empty time. It arrives into someone's week that's already full, and something else slows down to make room. Often that's an existing client, one who said yes to you months ago and is now waiting a little longer for drawings.

That's the real cost of a yes. Not just the hours on the new project, but the quiet delay it puts on the ones you've already promised.

Profitability brings all of this together, and it doesn't need a spreadsheet to start. Estimate the hours the project will take, honestly, including the site visits and the round of revisions you know will come. Multiply by what an hour of your team's time actually costs you. Put that number next to the fee. If the gap is thin before the first revision, it'll be negative by the third.

Most studios never do this sum before saying yes. Not because anyone's careless, but because the numbers live in different places, and nobody has time to put them side by side when an enquiry is warm and the client wants an answer by Friday.

Here's what changes when you do. The answer stops being yes or no. It becomes "yes, if."

Yes, if the scope is written down and revisions beyond two rounds are billed separately. Yes, if the fee is staged so early design work is paid before construction drawings start. Yes, if the start date moves three months so your team can finish what's already on their desks. Yes, if one person on the client side is named as the decision-maker.

Most clients respond well to this. It shows them you've taken their project seriously, and it gives them a clear picture of how working together will go. And if a condition can't be agreed, you've learned that before signing rather than after.

Sometimes, after all of this, the answer is still no. The fee can't stretch, the scope can't be pinned down, the team can't take it on without something else suffering. That's not a lack of ambition. It's the same judgment you use on a drawing: knowing what to leave out so the rest works.

Saying no to a project is really saying yes to the ones you already have. To the client who's waiting for drawings. To the team member who's been staying late for a month. To a practice that does fewer things, and does them well.

The hardest part is seeing the full cost before you commit, while the enquiry still feels exciting. That's the gap Projectsmate was built around: fee, hours and team capacity in one place, so the decision is clearer on a busy Tuesday afternoon.