023 WHY CLIENTS DON'T TAKE ARCHITECTS SERIOUSLY

Clients don’t wake up in the morning and decide to disrespect architects.

They respond to the version of the architect that shows up.

In this deeply honest and reflective episode of The SILL TALKS Podcast, host Arc. Egbeiyon Leonard unpacks one of the most painful—and misunderstood—realities of architectural practice in Africa: why architects struggle to command respect from clients, despite their training, expertise, and responsibility.

This is not a client-bashing episode.
 It is not a motivational rant.
 And it is definitely not academic theory.

Instead, this episode is a calm but powerful examination of how architects often and unintentionally position themselves in ways that weaken authority, invite disrespect, and turn professional services into negotiable favours.

Through relatable Nigerian and African practice scenarios such as site meetings, unpaid redesigns, “let’s manage it” conversations, friendship-driven projects, and pricing battles, this episode exposes the patterns that shape client behaviour.

In this episode, you’ll hear:

• Why humility, when not balanced with authority, turns into silence
• How architects unknowingly train clients through flexibility and fear
• Why leading with drawings instead of decisions reduces professional value
• How pricing like a vendor invites negotiation instead of respect
• Why friendship without structure destroys authority
• How silence and conflict avoidance remove architects from leadership
• Why boundaries without consequences always collapse

Most importantly, this episode reframes the conversation from “clients don’t respect architects” to a far more powerful question:

What version of the architect have we been presenting—and what version do we now need to redesign?

If you’re an architect, designer, or creative professional practicing in Africa (or working with African clients), this episode will feel uncomfortably familiar—in the best possible way.

It’s a call to clarity.
 A call to structure.
 And a call to lead the process—not manage discomfort.

🎧 Listen closely. Reflect honestly. And redesign your professional authority.

Have a challenge in your practice, business, or professional journey that you’re currently navigating?

Send us a message at info@silldesigns.com
and share what you’re dealing with.
Your insight may shape a future episode or help us point you toward clarity, structure, and practical next steps.

Transcript

SILL TALKS PODCAST 

Why Clients Don’t Take Architects Seriously

This is Sill Talks Episode 23

Hello guys welcome to the Sill talks podcast, the platform dedicated to help architects and creatives build businesses that are profitable and sustainable, I am your host Egbeiyon Leonard.

One thing I know for sure is that;

Clients don’t wake up in the morning and say,
 “Today, I will disrespect an architect.”

Nobody plans it.

What clients do is respond to the version of the architect that shows up.

And that’s a difficult thing to admit — especially in Africa — because many of us were raised, personally and professionally, to be humble people.

We were taught to respect elders.
 Avoid confrontation.
 Manage situations.
 Not to offend anyone.
 Not to be overly confident. (you even here phrases like pride comes before a fall).

Those are good values to be honest.
 But nobody taught us how to balance humility with authority.

So we enter practice with good intentions…
 and weak positioning.

We rush to do drawings.
 We start work before contracts.
 We redesign again and again because “it’s just a small change.”
 We say, “Let’s manage it,” instead of saying, “Here’s how this works.”

And then — almost inevitably — the client says:

“Architect, calm down… it’s just a drawing.”

Just a drawing?

That “drawing” is the difference between a building standing for decades
 and one cracking after a few rainy seasons.

So how did something so important become so casual?

It didn’t happen overnight.

It happened through behaviour.

This episode is not about blaming clients.

Clients behave logically.
 They respond to boundaries, confidence, and clarity.

If there are no boundaries, they push.
 If leadership is unclear, someone else fills the gap.

And very often, architects — without meaning to — create that gap.

Let’s compare something uncomfortable.

Doctors don’t ask patients how much diagnosis should cost.
 Lawyers don’t say, “Pay me whenever you’re ready.”

But architects?

We say, “Let’s start first… we’ll sort it out later.”

And later never comes.

Later becomes unpaid fees.
 Later becomes endless redesigns.
 Later becomes frustration disguised as passion.

So the real question is not:

Why don’t clients take architects seriously?

The real question is:

What version of the architect have you been presenting?

In this episode, I am going to talk honestly — not academically — about why clients don’t take architects seriously, and how architects can begin to reclaim authority without becoming arrogant, rude, or disconnected from our culture.

This is not about shouting at clients.

It’s about leading the process. So Stay with me as I break it down.

To understand how we got here, we need to start with something that sounds positive — but has quietly cost many architects their authority.

Humility.

1 — Let’s talk about THE HUMILITY TRAP IN Our ARCHITECTURAL PRACTICE 

Most architects in Africa did not enter practice trying to be weak, unsure, or invisible.

In fact, many of us entered practice trying to be good people.

We were taught things like:
 “Respect your elders.”
 “Don’t argue too much.”
 “Be humble.”
 “Let your work speak for you.”

And those are not bad values.
 They are good values.

The problem is what happens when humility is never balanced with authority.

Because humility without authority slowly turns into silence.
 And silence, in professional spaces, is very expensive.

Let me paint a familiar picture.

You walk into a meeting.
 Maybe the client is older than you.
 Maybe they brought their uncle.
 Maybe there’s a contractor already seated, legs crossed, confident.

You greet everyone politely.
 You wait for permission to speak.
 You listen.
 You nod.

And when it’s finally your turn, you explain your point calmly… maybe too calmly.

Then someone cuts you.

“Architect, calm down.”
 “Don’t complicate it.”
 “We’ve done this before.”

And you retreat.

Not because you don’t know your job —
 but because you don’t want to look rude.
 You don’t want to offend.
 You don’t want to lose the job.

So you manage it.

That word… manage it.

In our noble profession, “let’s manage it” has ended more professional authority than many bad clients ever did.

Because “managing it” usually means:
 Letting things slide.
 Avoiding difficult conversations.
 Hoping respect will come later.

But respect does not come later.
 It comes at the beginning.

Here’s the uncomfortable truth.

Many clients don’t dominate architects because they are powerful.
 They dominate because the architect entered the room already shrinking.

And this is not weakness.
 This is conditioning.

Think about how many of us were trained in school.

You don’t challenge the lecturer.
 You don’t question too much.
 You don’t talk back.

Then you graduate…
 and suddenly you’re expected to lead rooms filled with money, ego, pressure, and fear.

Nobody teaches that transition.

So student humility enters professional spaces.

And clients can feel it.

In many meetings, the architect is the only professional who keeps apologising.

“Sorry for the delay.”
 “Sorry for asking.”
 “Sorry, just one thing.”

Have you noticed that?

The contractor doesn’t apologise for delay.
 The engineer doesn’t apologise for instruction.

But the architect apologises for existence.

And over time, the room responds accordingly.

This is where the humility trap lives.

Because humility starts as respect…
 but without structure, it turns into permission.

Permission for clients to:
 Push deadlines.
 Delay payments.
 Ignore advice.
 Treat drawings like favours.

And here’s the irony.

The architect is usually the person in the room carrying the most long-term responsibility.

If the building cracks, they remember you.
 If approval fails, they call you.
 If something goes wrong in ten years, your name is still on that drawing.

Yet in the moment, you’re treated like the quiet one.

Why?

Because authority is not assumed.
 It is demonstrated.

And in many African contexts, authority is not given to the most intelligent person in the room —
 it is given to the clearest.

Clarity beats politeness in professional settings.

Let me say that again.

Clarity beats politeness.

You can be respectful and firm.
 You can be humble and directive.
 You can be culturally grounded and professionally immovable.

But when humility makes you unclear, clients step into the vacuum.

And humans always fill vacuums.

That’s why you’ll hear things like:
 “I’ve already told the mason what to do.”
 “The engineer said it’s fine.”
 “Let’s not involve drawing for this one.”

They’re not trying to disrespect you.

They’re responding to the version of you that never clearly claimed leadership.

Many architects avoid authority because they confuse it with arrogance.

So they choose comfort over clarity.

And comfort is expensive.

Because the same client that calls you “nice” today
 will underpay you tomorrow.

This is not bitterness.
 It’s observation.

Authority does not mean shouting.
 It does not mean disrespect.
 It does not mean losing your culture.

Authority means:
 This is how the process works.
 This is where my responsibility begins and ends.
 This is the consequence of this decision.

That’s it.

And until architects learn to separate humility from silence,
 clients will continue to take advantage — not maliciously, but naturally.

Because human beings follow structure.
 They don’t follow intentions.

So before we talk about pricing…
 before we talk about drawings…
 before we talk about contracts…

We have to unlearn the idea that being taken seriously requires being aggressive.

No.

It requires being clear.

And here’s the transition.

Once humility removes authority, something else quietly starts to happen.

Architects begin to train clients — without knowing.

And that’s what we need to talk about next.

Because many clients behave the way they do
 not because they are difficult…

…but because they were taught.

2- so lets look at HOW ARCHITECTS TRAIN CLIENTS WITHOUT KNOWING 

Most architects think clients come into projects already difficult.
 Already disrespectful.
 Already unreasonable.

But in many cases…
 they weren’t.

They learned.

Clients are trained.

And very often, they are trained by the architect.

Not intentionally.
 Not maliciously.
 But consistently.

Every profession trains its clients.

Doctors train patients to wait.
 Lawyers train clients to respect process.
 Accountants train clients to submit documents on time.

Architects?

We often train clients that deadlines are flexible,
 payments can wait,
 scope is elastic,
 and drawings are negotiable.

And we do it quietly —
 through behaviour.

Let’s look at a familiar situation.

A client calls and says,
 “Architect, just do something small first. Let me see.”

You know that line.

“Just something small.”

So you open your laptop.
 You tell yourself,
 “It’s just a sketch.”
 “Let me show goodwill.”

You send something.

The client replies,
 “Okay… adjust this small thing.”

You adjust.

Then,
 “Can we try another option?”

Before you know it, you’ve redesigned the building three times.

No contract.
 No payment.
 Just vibes.

At that point, the client has learned something very important:

This architect will work first.

And once that lesson is learned, it sticks.

Pause there.

The client didn’t force you.
 They didn’t threaten you.
 You volunteered.

That’s how training happens.

Slowly.
 Politely.

Let’s go to site.

You notice something wrong.
 You mention it calmly.

The contractor shrugs,
 “Oga, it’s fine.”

The client says,
 “Architect, let’s manage it.”

And you manage it.

Next week, the same thing happens again.

Why?

Because last time… nothing happened.

No consequence.

So the system learned:
 Architect instructions are negotiable.

This isn’t wickedness.
 It’s pattern recognition.

Humans repeat what works.

Same thing with payment.

The client delays.
 You don’t want to disturb them.
 You keep working.

Weeks later, they pay — maybe half.

And what have they learned?

That work continues without payment.
 That there is no urgency.
 That payment is a favour, not a requirement.

So next time, they delay again.

Not because they hate you —
 but because the environment allows it.

And here’s the painful part.

Most architects do this because they’re afraid.

Afraid of losing the job.
 Afraid of being replaced.
 Afraid of being called difficult.

So they trade long-term authority
 for short-term comfort.

And clients sense that uncertainty.

That’s why you’ll hear things like:
 “Other architects don’t behave like this.”
 “My previous architect didn’t charge like this.”

Those are comparisons.

Clients compare environments —
 and they choose the one that favours them.

So if disrespect keeps repeating,
 at some point we must admit:

It may not be the client.

It may be the system.

And systems are designed.

Here’s the good news.

What is trained can be retrained.

But retraining requires discomfort.

Clear scope.
 Clear boundaries.
 Clear pauses when payment delays.

Yes, you may lose some clients.

But the clients who leave because of structure
 were never going to respect you anyway.

And once clients get used to flexibility,
 something else happens.

They stop seeing architects as decision-makers…
 and start seeing them as drawing providers.

Which takes us straight to the next section.

Because one of the biggest reasons architects are not taken seriously
 is that we present drawings…

instead of decisions.

.

3 — DRAWINGS VS DECISIONS 

Let’s talk about drawings for a moment.

Because this is where many architects unknowingly lose authority.

Most clients don’t disrespect architects intentionally.
 They simply think our job is to draw.

And if we’re honest, we help them arrive at that conclusion.

Think about how most projects begin.

“Architect, let me see something.”
 “Just send me a sketch.”
 “Let me see the plan first.”

And we rush.

We open our laptop.
 We start drawing before asking hard questions.
 Before defining the real problem.
 Before explaining consequences.

So the client sees drawings before they see thinking.

And once that happens, the client assumes:

This is what I’m paying for.

A file.
 A plan.
 A drawing.

That’s why later, when you explain that something won’t work,
 the client is confused.

They say,
 “But you already drew it.”

Here’s the difference.

Drawings feel light.
 Decisions feel heavy.

Drawings feel editable.
 Decisions feel final.

Clients respect weight.

They respect the person who says,
 “If you move this wall, here’s what it will cost you.”
 “If you ignore this, approval will delay.”
 “If we change this, the structure is affected.”

That is authority.

But when architects lead with drawings,
 they reduce themselves to operators.

That’s why clients send messages like:
 “Architect, just move this wall small.”
 “Shift the staircase.”
 “Change the toilet position.”

As if they’re rearranging furniture.

Because to them, it’s just lines.

They don’t see the structure.
 They don’t see the services.
 They don’t see the cost.

And they don’t see it because we didn’t position ourselves as decision-guides.

We positioned ourselves as drawing vendors.

And here’s the hard truth.

The person who controls decisions controls respect.

The person who only executes instructions is replaceable.

Architecture is not drawing.

Drawing is a tool.

Architecture is judgement.

Until clients experience your judgement before your drawings,
they will never fully take you seriously.

So this isn’t about drawing less.

It’s about leading with thinking.

Lead with questions.
 Lead with consequences.
 Lead with options and trade-offs.

Then let the drawing support the decision — not replace it.

And once architects are seen as drawing vendors,
 something else happens.

They start pricing like vendors.

And vendors are negotiated.

Let’s talk about pricing like vendors versus pricing like advisors.

4 — PRICING LIKE VENDORS OR AS ADVISORS 

I will start with pricing.

The moment many architects lose authority
 is the moment they price like vendors.

You hear questions like:
 “Architect, how much?”
 “What’s your budget for drawing?”
 “Can we adjust the fee small?”

And instead of leading the conversation,
 we follow it.

We ask,
 “What’s your budget?”

And once that happens, the frame is set.

The client is no longer asking,
 “What is this worth?”

They are asking,
 “How cheap can this be?”

And in our environment, once price becomes flexible,
 respect follows it down.

Doctors don’t ask patients how much diagnosis should cost.
 Lawyers don’t negotiate legal risk.

But architects?

We apologise for our fees.
 We discount before being asked.
 We “add it inside” the building cost.

So clients conclude something simple:

This service is optional.

And optional things are negotiated.

Here’s the truth.

Advisors anchor value before price.
 Vendors defend price after value.

When you explain what your work prevents —
 approval delays, structural mistakes, cost overruns —
 price becomes context, not argument.

But when price comes first,
 everything becomes a negotiation.

And clients will push — not because they’re wicked —
 but because the system allows it.

Once architects price like vendors,
 they are treated like vendors.

And vendors are replaceable.

Which is why this next issue matters deeply.

Because pricing problems are often tied to something even more dangerous.

Familiarity.

Friendship. or

Favours.

Let’s talk about that.

5 — FRIENDSHIP, FAVOURS & FAMILIARITY 

In our environment, friendships quietly destroys more professional authority than pricing ever could.

“My friend is the client.”
 “My uncle knows him.”
 “We go to the same church.”
 “Let’s just start, we’ll sort it out.”

And at the beginning, everything feels smooth.

No contract.
 No invoice pressure.
 Just trust.

Until money enters the conversation.

And money always enters the conversation.

That’s when things change.

Suddenly, boundaries feel awkward.
 Invoices feel rude.
 Follow-ups feel like begging.

And the architect starts managing emotions
 instead of managing the project.

And the truth is,

Friendship without structure is not kindness.
 It’s confusion.

Clients don’t disrespect architects because they are close to them.
 They disrespect architects because closeness replaced clarity.

Like I always say, Professional systems don’t destroy relationships.
 They protect them.

If your relationship cannot survive structure,
 it will not survive money.

And again,

The moment you remove structure in the name of friendship,
 you downgrade yourself from professional
 to favour.

And favours are not respected.
 They are consumed.

That’s why you’ll hear things like:
 “Architect, no stress now.”
 “We’ll balance you later.”
 “You know we’re family.”

But family does not replace process.

And once you accept favour positioning,
 it becomes difficult to reintroduce authority.

Which brings us to the next issue.

Because even when boundaries exist,
 many architects avoid something critical.

Speaking up.

So I will talk about silence, how we avoid conflict,
 and how it quietly erodes authority.

6 — SILENCE, CONFLICT AVOIDANCE & AUTHORITY

I will start with silence.

Many creatives think silence is professionalism.

They think:
 “If I keep quiet, I’m being mature.”
 “If I don’t argue, I’m being respectful.”
 “If I avoid conflict, the project will move smoothly.”

But silence does not protect authority.

Silence erodes it.

Think about site meetings.

You see something wrong.
 The setback is off.
 The reinforcement doesn’t match the drawing.
 The staircase feels wrong.

You notice it immediately.

But you hesitate.

You don’t want to embarrass anyone.
 You don’t want to slow things down.
 You don’t want to look like you’re “forming tough.”

So you say it softly…
 or you say it later…
 or you don’t say it at all.

And then someone else speaks louder.

The contractor explains.
 The engineer waves it off.
 The client says, “If they say it’s fine, then it’s fine.”

And just like that, your authority disappears from the room.

Not because you were wrong —
 but because you were quiet.

Here’s the hard truth.

In professional spaces, silence is not interpreted as wisdom.
 It is interpreted as uncertainty.

Clients don’t respect the person who sees risk but doesn’t name it.
 They respect the person who explains consequences clearly —
 even when it’s uncomfortable.

Avoiding conflict feels peaceful in the moment.
 But it creates bigger conflict later.

Because when things go wrong,
 silence offers no protection.

They will still remember your name.

Authority is not about being loud.
 It’s about being clear at the right moment.

And once silence becomes a habit,
 clients stop listening — even when you finally speak.

Which brings us to the final and most decisive issue.

Because even when architects speak,
 even when boundaries are set,
 respect still collapses if one thing is missing.

And that thing is Consequences.

7 — CONSEQUENCES: THE MISSING PIECE 

Consequences is where respect either becomes real…
 or remains theoretical.

Many architects set boundaries.
 They speak clearly.
 They explain process.

But nothing changes.

Why?

Because boundaries without consequences are just suggestions.

Think about payment.

The client delays.
 You remind them — politely.
 You explain — calmly.

But you keep working.

What has the system learnt?

That payment is optional.

Not because the client is bad —
 but because nothing happens when they delay.

Same thing with scope.

You agree on three options.
 The client asks for five more.
 You sigh… and do it.

No reset.
 No variation.
 No pause.

So the system learns:
 Scope is elastic.

And One simple fact is .

The first time a boundary is crossed and nothing happens,
 that boundary dies.

Clients don’t test boundaries because they are wicked.
 They test because humans test systems generally.

And systems only work when consequences are consistent.

Another point to note is that,

If work continues when payment stops,
 payment will always stop first.

If drawings are released before approval,
 approval will always come later.

If instructions are ignored without consequence,
 they will keep being ignored.

This is not personal.
 It’s structural.

Respect does not come from how well you explain your boundaries.
 It comes from what happens when those boundaries are crossed.

And this is where many architects struggle —
 because enforcing consequences feels uncomfortable.

It feels harsh.
 It feels confrontational.
 It feels like you’re risking the relationship.

But the irony is that.

A relationship that only survives when you abandon structure
 was never built on respect.

Consequences don’t destroy good clients.
 They filter out bad ones.

And once consequences enter the system,
 something interesting happens.

Clients adjust.

Because humans always adjust to systems that work.

And this brings us to the final reflection.

Because when you put all these pieces together —
 humility, training, drawings, pricing, friendship, silence, consequences —
 a pattern emerges.

And that pattern tells us one thing.

The problem is not architecture.

The problem is positioning.

— RECAP

Before we close, let’s a quick recap.

Because this episode covered a lot —
 and it deserves to be brought together properly.

If you listen carefully, everything we discussed points to one thing.

It was never just one problem.

It wasn’t just humility.
 It wasn’t just pricing.
 It wasn’t just drawings.
 It wasn’t just clients.

It was a pattern.

We talked about how humility — when not balanced with authority — turns into silence.
 How silence slowly trains clients to push.
 How flexible behaviour teaches clients that process is optional.
 How leading with drawings reduces architects to operators instead of decision-makers.
 How pricing like a vendor invites negotiation instead of respect.
 How friendship without structure turns professionals into favours.
 How avoiding conflict removes your voice from the room.
 And finally, how boundaries without consequences collapse completely.

Different issues —
 but the same root.

Positioning.

Clients don’t respond to intention.
 They respond to structure.

They don’t respond to how hard you work.
 They respond to what your system allows.

And over time, many architects — without meaning to —including myself
 have positioned themselves as helpful, flexible, and accommodating…
 but not authoritative.

So clients adjust.

Not because they’re wicked.
 Not because they hate architects.
 But because humans always adapt to the environment they’re in.

That’s the uncomfortable truth.

This episode is not a call to be aggressive.
 It’s not a call to shout at clients, or to misbehave
 It’s not a call to abandon our culture or humility.

It’s a call to be clear.

Clear about your role.
 Clear about your process.
 Clear about your value.
 Clear about your boundaries.
 and about your consequences.

Because respect in professional practice is not emotional.

It is structural.

You don’t gain respect by working harder.
 You gain respect by working clearer.

You don’t gain authority by explaining more.
 You gain authority by enforcing consistently.

And this is the shift that changes everything.

The moment you stop presenting yourself as a drawing provider
 and start showing up as a decision-maker,
 the room changes.

The moment you stop managing discomfort
 and start leading the process,
 clients adjust.

Not all clients  of course—
 but the right ones.

And the clients who leave because of clarity
 were never going to respect you anyway.

So let’s end where we began.

Clients don’t wake up and decide to disrespect architects.

They respond to the version of the architect that shows up.

And that means the real question was never:

“Why don’t clients take architects seriously?”

The real question is:

What version of the architect have you been presenting —
 and what version do you now need to redesign?

That redesign doesn’t start with clients.

It starts with us.

OUTRO

This is The SILL TALKS Podcast.
I’m Arc. Egbeiyon Leonard.

If this episode resonated with you, share it with another architect who needs to hear it.

Until next time —
 design with clarity,
 price with confidence,
 and lead the process.

See you in the next conversation.