The First Client Meeting: Questions to Ask, How to Qualify the Project, and What to Send Afterwards

The first client meeting is rarely just a conversation. It is the moment a prospective working relationship either takes shape or begins to unravel, and the outcome depends heavily on how prepared you are before you walk through the door.

Done well, it gives you the information you need to assess the project, build trust with the client, and position your practice as the right choice. Done poorly, it leads to vague fee proposals, misaligned expectations, and commissions that cost more to deliver than they earn.

This guide covers everything architects need to know about structuring the first client meeting – what to prepare in advance, how to ask the right questions, how to qualify the project afterwards, and what to send once the meeting is over.

What to Do Before the Meeting

Preparation separates a confident, credible architect from one who is simply showing up and hoping for the best. The more you know before the meeting, the sharper your questions will be and the more assured your presence.

Even thirty minutes of focused research can transform how a meeting flows. Clients notice when an architect has done their homework, and it immediately signals professionalism.

Research the Client and Site

Start with the site. Use planning portals to review any historical applications, permissions, or refusals. Check land registry data if ownership or boundary questions might be relevant. Look at aerial imagery and street views to get a sense of the context.

If the client is a company or developer, look them up. Review their previous projects, any public statements about their work, and their presence in the local market.

For private clients, a modest amount of background research is entirely appropriate – you are assessing whether this is a project worth pursuing.

Understanding the site constraints early means you can ask more targeted questions during the meeting rather than gathering basic information that was publicly available.

Prepare Your Own Materials

Bring a curated selection of practice work – a physical or digital portfolio showing projects of a similar type or scale to what is being discussed. A generic brochure is less useful than two or three well-chosen precedents from your own output.

Prepare a brief agenda for yourself, even if you do not share it directly with the client. Know which topics you need to cover and in what order. Have your list of questions ready, alongside a high-level overview of how your practice structures fees and appointments.

If the client has sent any brief materials in advance, read them carefully and note any gaps or ambiguities that need clarification during the meeting.

How to Structure the Meeting Itself

A first client meeting should feel like a conversation, not an interrogation. The best architects manage the flow instinctively – moving between listening, asking, and explaining without making the client feel like they are being processed.

Structure gives you control without making the meeting feel rigid. Aim for roughly sixty to ninety minutes, and have a clear sense of the three phases: opening, middle, and close.

Opening: Building Rapport and Setting Expectations

Begin by thanking the client for their time and briefly explaining what you hope to cover. Something simple and direct: “I’d like to hear about the project in your own words first, and then I’ll ask some more detailed questions about scope, budget, and timeline. By the end, we should both have a clearer sense of how we might work together.”

This sets expectations without being formulaic. It also reassures the client that the meeting has a purpose – which matters particularly for clients who have never worked with an architect before.

Keep the opening short. A few minutes of genuine rapport-building is valuable. Fifteen minutes of small talk is not.

Middle: Asking the Right Questions

The substantive phase of the meeting is where you gather the information you need to qualify the project. Resist the urge to talk about your practice at length here – your priority is listening.

Ask open questions that give the client room to describe their vision, their concerns, and their expectations. Follow up with more specific questions to extract the detail. If the client gives a vague answer, probe gently rather than moving on.

The detailed questions to ask are set out in the next section, but the general principle is to move from broad to specific: what they want, why they want it, how much they have to spend, and when they need it done.

Closing: Next Steps and Expectations

End the meeting by summarising the key points discussed and confirming what happens next. Be specific about what you will send and when: “I’ll put together a written summary of what we’ve covered today and follow it up with an outline fee proposal within the next week.”

Do not leave the meeting without confirming mutual interest. If you are not sure whether the project is right for your practice, it is fine to say that you need a short time to review what has been discussed before committing. Clients respect honesty more than false enthusiasm.

The Essential Questions to Ask a New Client

The questions you ask in a first meeting determine the quality of the information you leave with. Vague questions produce vague answers. Targeted questions produce the intelligence you need to write an accurate fee proposal and make an informed decision about whether to pursue the project.

Organise your questions by theme and work through them in a logical sequence, adapting based on what the client reveals as the conversation develops.

Questions About the Project Brief

Start by asking the client to describe the project in their own words, without prompting. What are they trying to achieve? What does success look like to them? What has prompted the project now?

Follow up with questions about scale and programme: How many rooms, floors, or units? What are the key spaces and how do they need to function? Are there any specific requirements around accessibility, sustainability, or material preferences?

Ask whether the client has any reference projects or images that capture what they have in mind. This is often revealing – not just in terms of aesthetic preferences, but in terms of the gap between what they are imagining and what their budget is likely to deliver.

Understanding how to develop a design brief properly from the outset will save significant time and prevent scope creep later in the project.

Questions About Budget

Budget is the question most architects feel uncomfortable asking, and it is the one that matters most. Ask it directly but sensitively, early in the substantive phase of the meeting.

A useful framing: “Do you have a budget in mind for the construction works? Even a ballpark figure helps me make sure we’re thinking about the project at the right scale from the start.”

If the client is reluctant to give a figure, offer a range and ask them to position themselves within it. If they have no budget at all and have not thought about it, that itself is useful information. Understanding how feasibility is assessed early on can help frame this conversation with clients who are not yet sure what is achievable.

Questions About the Timeline

Ask about the client’s expected programme. When do they want to be on site? When do they need to be in occupation? Are there any fixed external deadlines – a lease expiry, a funding condition, a school term, a business launch?

Probe for realism. Clients often underestimate how long the design and planning process takes. If they need planning permission and want to be on site in four months, you need to manage that expectation now, not after you have been appointed.

Understanding how the RIBA work stages map onto a project timeline is useful context to bring to this conversation – it allows you to explain the process clearly without lecturing.

Questions About Decision-Making and Stakeholders

One of the most important things to establish in a first meeting is who is actually making decisions. Ask directly: “Who will be the main point of contact on your side, and who else is involved in the decision-making?”

For private clients, this might mean a partner or spouse who is not present. For developers, it might mean a board or investment committee. For community organisations, it might mean a trustee body or steering group with competing priorities.

Understanding the decision-making structure early prevents the frustration of designs being approved and then reversed, or of key stakeholders appearing late in the process with fundamentally different requirements.

Questions About Previous Experience with Architects

Ask whether the client has worked with architects before. If they have, ask what went well and what did not. This is not idle curiosity – it is one of the most diagnostically useful questions you can ask.

A client who has had a difficult experience previously may carry expectations or anxieties that will shape the working relationship. A client who has worked well with architects before will have a more realistic sense of the process. Either way, the answer tells you something important about how to pitch the relationship.

How to Qualify the Project

Qualification is the process of deciding, after the meeting, whether this is a project your practice should take on. It is not a passive assessment – it requires deliberate judgement about viability, compatibility, and commercial sense.

Not every enquiry should become a commission. Saying no to the wrong project is as valuable as saying yes to the right one.

Is the Budget Realistic?

Cross-reference what the client has told you against your knowledge of current construction costs. A client who wants a four-bedroom house extension for £60,000 in a high-cost urban area is working with an unrealistic expectation. That gap needs to be addressed before you invest time in a fee proposal.

If there is a significant mismatch, consider whether the client is open to rescoping the project, whether the brief can be staged, or whether they are simply not yet ready to commission. Some clients need education before they are ready to proceed – others are in denial and will not be moved.

Is the Client the Right Fit?

Assess the client’s communication style, their openness to professional advice, and their clarity as a decision-maker. A client who contradicted themselves repeatedly during the meeting, who seemed dismissive of professional input, or who became evasive when budget came up is signalling something about how the working relationship will feel.

Consider also whether your practice has the right experience and capacity for the project. Taking on a project type you have never handled before is not necessarily wrong – but be honest with yourself about what that means for your risk and your resourcing.

Is the Project Commercially Viable for Your Practice?

Work out whether the fee you could reasonably charge for this project will cover your time adequately. For smaller projects in particular, it is easy to underestimate the overhead involved in client management, administration, and coordination relative to the actual design fee.

Understanding how small practices generate sustainable income from their project mix is useful context here – some projects are worth taking at a reduced margin for portfolio or relationship reasons, but that should be a conscious choice, not an accident.

Red Flags to Watch For

There are warning signs that experienced architects recognise quickly. A client who refuses to discuss budget at all. A client who has already dismissed two or three previous architects without clear reason. A client who insists they know exactly what they want and do not need your input on design. A client whose project appears to have no clear planning basis.

These are not automatic disqualifiers, but they warrant serious consideration. The cost of taking on a problematic client – in time, professional stress, and potential disputes – almost always outweighs the fee.

What to Send After the Meeting

The post-meeting follow-up is where many architects lose momentum. A well-structured, promptly delivered set of documents signals professionalism, reinforces the impression made in the meeting, and moves the project forward with clarity.

Aim to send your follow-up within two to three working days of the meeting. Leaving it longer risks the client’s energy dissipating or another practice stepping in.

The Follow-Up Email

Write a concise, professional email that thanks the client for their time, briefly confirms the key topics discussed, and outlines what you are sending with the email and what comes next.

Keep it warm but businesslike. This is not the place for a lengthy pitch – the meeting was the pitch. The email is confirmation that you listened, you are organised, and you are ready to move forward.

The Meeting Notes or Summary Document

Send a written summary of what was discussed – the project description, the stated budget, the timeline, the decision-makers, and any specific requirements or constraints noted during the conversation.

This document protects both parties. If there is a later dispute about what was agreed or understood at the outset, the meeting notes provide a written record. It also demonstrates to the client that you were paying careful attention throughout.

Keep the summary factual and clear. One to two pages is usually sufficient. It is not a brief – it is a record of the conversation that forms the basis for the brief to be developed.

The Initial Fee Proposal or Appointment Letter

If you have enough information to do so, send an initial fee proposal. This should outline the scope of services, the proposed stages of work, the basis of your fee (fixed, percentage, or time charge), and any exclusions or assumptions.

Understanding how architectural services are structured and communicated is essential here – a vague fee proposal creates ambiguity that will cause problems later. Be specific about what is and is not included.

If the project is not yet sufficiently defined for a full fee proposal, send a letter of intent or a preliminary scope document instead, and flag what additional information you need to refine it. Clarity at this stage protects everyone.

It is also worth considering how you approach fee negotiation if the client comes back with questions or pushback on your proposal – knowing your position in advance makes that conversation far easier to manage.

Supporting Materials to Include

Tailor your supporting materials to the client’s level of experience. An inexperienced private client may benefit from a one-page explainer on the design and planning process. An experienced developer may prefer a direct fee schedule without any accompanying narrative.

Relevant project case studies from your practice – particularly those with a similar brief or context to the proposed project – are always useful to include. Keep them concise: one page per project, with imagery, key information, and a one-line description of your role and the outcome.

Practical Guidance: Building a First Meeting Template

Creating a reusable framework for first client meetings is one of the most efficient things a small practice can do. It does not mean every meeting is identical – it means you always arrive prepared and never leave without the information you need.

Build a simple question checklist organised by the themes above: brief, budget, timeline, stakeholders, and previous experience. Alongside it, prepare a standard agenda template that you can adapt in the first five minutes of any meeting based on what the client has already shared with you.

Develop a post-meeting document set: a meeting notes template, a fee proposal structure, and a follow-up email template. These do not need to be elaborate – a well-designed one-page template is more useful than a twelve-page form that never gets filled in consistently.

Review and refine these templates after every significant first meeting. The questions that generated the most useful answers are the ones worth keeping. The questions that consistently produced vague or defensive responses may need reframing.

Case Studies: How Architects Have Navigated First Client Meetings

Case Study 1: Residential Extension – Inexperienced Private Client

A small residential practice in Bristol met with a couple looking to extend their Victorian terraced house. The clients arrived with magazine tear-sheets and a vague sense of wanting to “open things up” – but no firm budget.

Using structured questioning, the architect established early that the couple had mentally allocated £40,000 for a project that, based on the scope they described, was likely to cost three times that amount. Rather than writing a fee proposal based on the inflated brief, the architect wrote a clear summary letter noting the budget-scope gap and offering two options: a feasibility study to explore what was achievable within budget, or a revised brief based on a more realistic construction figure.

The clients chose the feasibility route. The project proceeded, rescoped appropriately, and completed successfully. The early honesty – delivered in writing – prevented a much more costly misalignment later.

Case Study 2: Commercial Fit-Out – Experienced Developer Client

A mid-sized practice met a repeat-developer client who arrived for the first meeting with a detailed room schedule, a fixed budget, and a planning reference number already in hand. The traditional discovery phase was largely redundant.

The architect adapted the meeting structure accordingly, spending the majority of the session on fee structure, programme, and the specific conditions of the planning consent that would affect the fit-out scope. The follow-up documents were streamlined: no meeting notes beyond a brief confirmation email, and a fee proposal sent within twenty-four hours.

Understanding the client’s existing experience allowed the practice to position itself as a delivery partner rather than a design guide – which was exactly the role the developer needed and exactly the tone that led to appointment.

Case Study 3: Community and Cultural Project – Committee-Led Client

A practice specialising in community buildings attended a first meeting for a new village hall project. The “client” turned out to be a committee of seven people, four of whom attended the meeting, each with different priorities and varying degrees of involvement in the fundraising process.

The architect opened by asking each committee member to briefly describe their primary concern for the project. This simple move produced a remarkably clear picture of where consensus existed and where tensions lay. It also allowed the architect to identify the committee chair as the primary decision-maker – a fact that was not immediately obvious from the group dynamic.

The follow-up summary was written directly to the chair, with a note that it had been shared with the full committee. This established the communication protocol from the outset and prevented the later confusion that often arises from multi-stakeholder clients with no agreed decision-making hierarchy.

Case Study 4: Self-Build Residential – Enthusiastic but Underprepared Client

A client arrived for a first meeting having already purchased a plot, found a builder on a recommendation, and watched several self-build television programmes. They were enthusiastic, engaged, and almost entirely unprepared for what the process involved.

The architect used the meeting to gently map the process – explaining the sequence from brief through planning to construction without overwhelming the client or undermining their enthusiasm. Crucially, the architect framed this as preparation for the questions that would follow, rather than as a lecture.

The follow-up pack included a simple one-page process overview alongside the fee proposal. The client later cited that document as the thing that gave them the confidence to proceed. The project was appointed and delivered successfully, with the client becoming a source of referrals for the practice.

Case Study 5: Failed Commission – A Lesson in Qualification

A sole practitioner took on a residential conversion project after a first meeting that produced several red flags: the client could not name a budget, had already parted ways with a previous architect without explanation, and was evasive when asked who else was involved in decisions.

The practitioner, eager for work and reassured by the client’s apparent enthusiasm, proceeded anyway. Four months later, after producing measured drawings, concept designs, and a planning pre-application document, the client withdrew from the project citing “a change in circumstances” – but not before requesting a revised design to address comments from a partner who had never been mentioned during the first meeting.

The practitioner recovered a partial fee but not the full cost of time invested. In retrospect, every early warning sign had been present at the first meeting. The lesson was not simply to ask better questions, but to act on the answers – and to recognise that walking away from a commission at the qualification stage is always cheaper than walking away from a project midway through.

Common Mistakes Architects Make in First Client Meetings

The most common error is talking too much. Architects are trained to explain, and many default to presenting their practice, their philosophy, and their process before they have heard anything substantial from the client. The meeting should be weighted towards listening, not presenting.

Failing to ask about budget is almost as common. Architects often avoid the question out of awkwardness, and then spend hours on a fee proposal based on a scope that the client’s budget cannot support. Ask early, ask directly, and frame it as being in the client’s interest.

Not clarifying decision-making structures is a frequent oversight that causes problems later. Assuming the person in the room is the sole decision-maker – without checking – leads to redesigns, reversals, and frustration that could have been avoided.

Sending nothing after the meeting, or sending a follow-up too late, is a missed opportunity. The follow-up documents are part of the first impression. A well-structured summary sent promptly signals that working with you will feel organised and professional.

Finally, ignoring your own instincts. Experienced architects often know in the meeting whether a project is right or not. The discipline is acting on that knowledge rather than proceeding out of optimism, obligation, or financial pressure.

Conclusion

The first client meeting deserves the same level of preparation and professional rigour as any design stage. It is the point at which a project is defined, a relationship is established, and a commercial decision is made – often without it being explicitly framed as any of those things.

Arriving prepared, asking the right questions, listening carefully, qualifying the project honestly, and following up with well-structured documents is not bureaucracy. It is the foundation of a working relationship built on clarity and mutual respect.

Architects who treat the first meeting as a formality tend to find themselves managing the consequences throughout the project. Those who treat it as one of the most important hours in the commission cycle tend to find that everything that follows runs more smoothly as a result.