How Architects Can Qualify Enquiries Before a Meeting

I reckon the first meeting is the most expensive free thing a small practice gives away. Before booking one, collect the project basics, prepare a one-page brief and have the architect approve the next reply. My starting point is client intake software for qualifying enquiries, with clear limits on what happens before an agreement.

Which Three Enquiry Workflows Should a Small Practice Automate First?

I would build these in order. First establish what the practice needs to know, then carry those answers into the meeting and proposal. Treat the following as a proposed design, with measures to track from launch.

1. Enquiry Questionnaire and Triage

   Trigger: An enquiry arrives through the website, inbox or a listing platform. The system prepares a reply linking to a short questionnaire, then summarises the answers against the practice's criteria: project type, location, budget band, timing and services.

   Approval: The architect or practice manager approves every reply. The architect approves every decline or referral. Missing information becomes a question, and a budget mismatch becomes a review flag.

   Record: Save the original enquiry, answers, reviewer and decision in the CRM or spreadsheet. Measure: Time to first reply, the share of enquiries reaching a meeting, and meetings leading to a fee proposal.

2. Pre-Meeting Brief Pack

   Trigger: A meeting is booked. The system prepares one page covering the client's project, stated budget, stage, decision makers, unresolved questions and documents to request, such as an existing survey.

   Approval: The architect reads and checks the pack before the meeting. Label client statements clearly: “Owner reports possible heritage restrictions” carries a different meaning from a verified finding. Include no design or feasibility opinion.

   Record: Attach the checked brief to the contact. Measure: Meeting length and questions still open afterwards. I would look for better prepared conversations before trying to shorten every meeting.

3. Fee Proposal and Agreement Follow-Up

   Trigger: The architect decides to propose. The system prepares the covering correspondence, permitted agreement fields and follow-up drafts using the architect's approved scope and fees.

   Approval: The architect approves the proposal, agreement and each follow-up. Nothing is sent or signed automatically. Include a timing check for the applicable state rules before requesting a signature.

   Record: Save the approved version, sent date, follow-ups and outcome. Measure: Proposal acceptance rate and days from first enquiry to signed agreement. Follow-up stops when the prospect declines.

What Should an Architecture Enquiry Form or Client Questionnaire Ask Before the First Meeting?

I would use short choices where possible and leave room for uncertainty. A prospective client should be able to say “I don't know” without inventing an answer.

• Project: New house, extension, alteration, multi-unit development or commercial fit-out; what the client wants to achieve.
• Site: Address, suburb, ownership or purchase stage, and any heritage or overlay issues the client already knows about.
• Stage: Early idea, site purchased, survey available or application already lodged.
• Budget: Construction budget band, with fees, GST and landscaping included or excluded.
• Timing: Desired start and completion, plus any fixed deadline and its reason.
• Services: Full service, development application, documentation or help defining the scope.
• People: Contact details, decision makers and how the client found the practice.

For the form structure, see what a client intake form should include. Ask only for details the practice will use and explain their purpose. The OAIC's Australian Privacy Principles reference covers collection and collection notices, with higher standards for sensitive information. This is general information, not a determination of the practice's legal obligations.

How Do You Screen Architecture Enquiries by Budget Without Turning Good Clients Away?

Ask for a band, then establish what the client has counted. “Construction only” and “everything including fees and landscaping” need different follow-up questions.

I would have the system flag uncertainty or a mismatch against the practice's own criteria. The architect can then ask about priorities, flexibility or staging before deciding whether a meeting makes sense. A blank budget field should prompt clarification.

What Can an Architect Discuss Before a Written Client Agreement Is in Place in NSW and Victoria?

As at 17 October 2026, the distinction matters. Build the approval rules around the practice's jurisdiction.

Victoria's guidance covers architectural work even when no fee is charged. A free concept sketch still needs a signed agreement. ARBV also says an architect cannot collect a fee without a signed client agreement, so a paid feasibility session needs that step first.

For NSW practices using the Short Form Architect Client Contract, the system could prefill the customisable covering letter and services schedule for review. Keep the standard terms unchanged. Truespeak gives no legal advice; use the relevant Board's guidance to check the engagement process.

What Would a Qualified Enquiry Look Like in Practice?

Worked example, not a client story: A homeowner enquires about a rear extension in Marrickville. The questionnaire records that the homeowner owns the site, wants another living area, has a budget band excluding professional fees, and is unsure about heritage restrictions.

The system drafts a reply asking about timing and available documents. The architect approves it. Once a meeting is booked, the brief carries those answers forward and highlights the heritage question as unverified. The system gives no opinion on approval prospects or what could fit on the site.

If the architect decides to propose, the approved scope feeds the agreement draft. Each reply and agreement stays subject to approval.

What Should Architects Not Automate When Qualifying Clients?

I would keep sketches, site feasibility opinions, planning interpretations, fee commitments and final suitability decisions with the architect. The same applies to promises about approvals or completion dates.

Do not let AI infer missing facts, turn client comments into verified findings or reject an enquiry on budget alone. The related granny flat enquiry qualification guide discusses the same preparation and approval pattern.

Does the Same Approach Work for Building Designers?

I would use the same questionnaire, brief and follow-up structure for building designers. The architect agreement rules above apply to registered architects; they do not establish building designers' obligations. Check the rules for the particular service and jurisdiction before setting the gates.

Where Does Truespeak Fit?

I'm Sonny Hovsepian, Truespeak's Sydney-based founder, and clients work directly with me after more than 20 years in commercial roles, including e-commerce leadership at Optus and Samsung. For an Australian practice that wants enquiry automation designed, built and run around its existing tools, with the architect approving every reply, decline and agreement, Truespeak is built for exactly that.

I would design this around the existing inbox, form and CRM through client intake automation. A step stays manual where a tool has no usable connection. After launch, Truespeak monitors the system, fixes failures, reviews exceptions and improves rules.

The closest related construction page is AI automation for home builders. To discuss the practice's enquiry process, start with a discovery call.