6 min read
Lahav Meiri, licensed renovation contractor · Published 3 August 2026
The first meeting with an architect looks like you describing your project. It's actually both of you assessing each other. While you're talking, they're working out whether your budget matches what you're asking for, whether the two of you agree, and whether this is a project they can take on. Knowing that changes how you use the hour.
Almost everything written about this is written by architects, about their own consultation. This is written from the other side of the table.
One thing worth knowing before you start: the last section is what they'll ask you. That's the part that decides how far the meeting gets.
Most first meetings follow the same shape, whether they last forty minutes or two hours.
Who lives there, how you live, what your days look like. It feels like small talk. It isn't - it's the raw material for everything that follows.
What you're hoping to do, roughly. This is usually shorter than people expect, because a good architect will start interrupting with questions.
Often within the first twenty minutes. Some people are surprised by this and read it as pushy. It isn't - there's no point designing something that can't be built.
Many practices do the first meeting at the property. If yours does, that's a good sign - a lot becomes visible standing on the ground that never comes through in photos.
Phases, what's included, what isn't, how they charge. This is where you find out what you're actually buying.
Nobody says this out loud, but that's what the meeting is for.
They ask about you before they ask about the house
This is the part nobody writes about, because the people writing are the ones doing it.
Not whether it's big. Whether it matches what you're describing. An experienced architect knows within minutes if there's a gap, and how they handle that tells you a lot about them.
If there are two of you, they're noticing who talks, who defers, and where you contradict each other. They've seen what happens when that surfaces in month six.
Projects don't stall because clients are difficult. They stall because decisions don't come back. Someone who can't answer basic questions about their own life is going to be slow on the ones that matter.
The site, the planning constraints, the timeline. Sometimes the honest answer is no, and a good architect will say so.
Good practices turn work down. You're being evaluated too, and arriving prepared is the strongest thing you can do about that.
You're being evaluated too
Some practices give the first meeting away. Others charge for it, sometimes several hundred dollars, and deliver notes, a feasibility read, and a proposal at the end.
Both are legitimate, and the difference isn't greed.
Under the AIA's standard owner-architect agreement, an architect's basic services begin at schematic design. Everything before that - the first consultation, defining what you're building, working out whether it's viable - sits outside them.
A free consultation is a firm absorbing that cost as a way of winning work. A paid one is a firm treating it as work, which it is.
What matters is what you get. Ask before you book: is there a fee, and what do I leave with? A paid meeting that produces a written assessment of your site and budget can be the best money you spend. A free one that produces a brochure is worth what you paid.
A free one that produces a brochure is worth what you paid
Every article on this says "bring inspiration images." Bring them. Just know they're the least useful thing in your bag.
Bring first:
Written down. This is the most useful thing you can hand over and almost nobody does.
Including land, fees, and a contingency. Saying a number out loud is uncomfortable and it saves the entire meeting.
Survey, plot plan, deed restrictions, what the neighbours built. Even a photo of all four boundaries helps.
Not a list of twenty. Five, in order.
Bring second:
A saved kitchen tells them nothing. "I saved this because of the light" tells them something.
It isn't wasted - it shows what you're picturing. But hand it over as information, not as a brief, or you'll get a version of your own drawing back instead of what an architect would have done with the problem.
These are the questions that come up in almost every first meeting. They're harder than they sound, and the meeting goes as far as your answers do.
Not the house you want. The one you're in.
Specific failures, not general dissatisfaction.
The real one. Including everything.
Two lists, not one.
It changes almost every recommendation they'll make.
A deadline you haven't mentioned changes what's possible.
If there are two of you, they will ask some version of this. Having an answer is better than discovering one in the room.
Those are the questions. Nestbrief works through them with you before you're in the room.
See how it works →An architect can only design from what you give them. Arrive with the questions above already answered and the first meeting starts on the work. Arrive without them and it becomes the meeting where you work them out - which is a fine meeting, just an expensive way to have that conversation.
Nestbrief asks you these questions one at a time, at home, at your own pace. When you say you want a bigger kitchen, it asks what for. When you're not sure, it helps you think it through instead of moving on. Nothing to prepare, nothing to fill in - you just talk.
This is what comes out of it:
One conversation, and you walk in with something to hand over.