Lexis Careers › Architecture › Unit 09 › Lesson 01

Three Minutes to Present

B2 The Client Conversation
About this lesson ▾

Every design decision you have defended so far was defended to a code official or a plan checker. This unit is about defending it to the person paying for it — a different audience, with a different kind of authority.

XP 0 Streak 0 First-try —
Lesson progress0%
01
Warm-up · 5 min

A meeting that went well, and one that did not

Think of two client meetings — one where you felt the conversation went well, and one where it did not.

  • What was the client actually worried about, in each case?
  • Did you find that out, or did you guess?
  • In the one that went badly — what did you say first?
Teacher note Listen for whether "went badly" means she lost the argument or lost the client’s trust. Those are different failures, and only one of them is what this unit fixes. A designer can be completely right about the code and still lose the room.
02
Input & Noticing · 10 min

The triangle you are always standing inside

The role structure printed on every set you have ever issued.

From your own title blocks

RoleControlsCannot do
OWNERApproves scope, budget and scheduleCannot approve what code forbids
LANDSCAPE DESIGNERProduces the design and the drawings — licence B-C27Cannot approve a price; can only propose one
LANDSCAPE CONTRACTORBuilds it and prices itOften in the room when the owner objects to that price

You are the only role that can see all three positions at once. The owner does not know what the contractor can build for the money; the contractor does not know what the owner will accept losing. When an owner objects to a cost in a meeting, they are very often objecting to a number they do not yet understand — and you are the only person in the room who can translate it.

That reframes what a "client conversation" is. It is not you defending a decision. It is you translating between two people who are not speaking the same language about the same number.

03
Focus on Form · 8 min

What / why / how much, in that order

The shape of a design presentation

MoveAnswersGoes wrong when…
WhatWhat is being proposed, in one sentenceBuried under detail first
WhyWhy this and not something simpler or cheaperAssumed rather than stated
How muchThe number, stated plainly, before they askLeft for them to ask

The third row is the one designers avoid. Leaving the cost for the client to ask about does not delay the objection — it just means it arrives as a question instead of as something you framed. Stating your own number, in your own words, before they ask is the single highest-leverage habit this unit teaches.

04
Diagnostic Practice · 12 min

What do you already control?

Lexical Matching

Match each role to what it actually controls. Click the role, then its power.

Approves scope, budget and schedule — but cannot approve what code forbids
Produces the design and can propose a price, but cannot approve one
Builds it and prices it — often present when the cost lands badly
Reducing cost while holding the design intent, rather than simply cutting scope
A placeholder budget line, not a fixed price — it can move
Teacher note If "allowance" is new, flag it now — it is the term that makes Lesson 5 possible, and confusing it with a fixed quote is the single most common misunderstanding a client conversation has to correct.
MCQ Reading

Choose the best answer.

1. An owner objects to a cost in a meeting. What are they usually actually doing?

2. Why state your own number before the client asks for it?

3. Which role in the triangle can see all three positions at once?

4. What is a design presentation that buries the cost until asked most likely to produce?

05
Baseline Performance · 15 min

Present a design in three minutes

Your Day One marker for this unit.

Task card

One of your own projects. Your teacher is the owner, meeting you for the first time.

Present the design in three minutes: what, why, how much. No slides, no notes.

  • State your own number before your teacher asks for it.
  • Three minutes. Your teacher will time it and stop you.
  • Keep it. Lesson 8 comes back to it.
Teacher note Do not coach the what/why/how much structure while she presents. Note whether the cost appears in her own words or has to be extracted by a question, and whether "why" is ever stated explicitly or only implied. Both are diagnostic, and most designers at this baseline do the second of each.
06
Feedback & Reflection · 5 min

Did the number come from you?

  1. Did you state the cost, or did your teacher have to ask for it?
  2. Did you state why this design, or only what it is?
  3. How long before you said a number at all?
07
Wrap-up · 5 min

Before the next lesson

Homework. Think of a real meeting where a client objected to a cost. Do not write it down — just be ready to describe, in one sentence, exactly what you said first.