Between a new enquiry and the fee invoice, a small practice can automate six admin steps: capturing the enquiry in a structured form, scoring it for fit, drafting the fee proposal, filling the appointment letter from a template, raising stage-end invoices and drafting overdue reminders. The architect approves every document; the automation only drafts.
Design work, drawings and judgement calls stay with the architect: whether to take the job, what to promise and what to charge. What the tools remove is retyping. The same client name, site description, scope and fee figures appear in five documents, and each hand-off is where mistakes and delays creep in.
What is automated, and where the architect still signs
Read the table as a map. Each row starts from something that has already happened, does one clerical job, and stops at a person.
| Step | Starts when | What the tool does | The architect approves |
|---|---|---|---|
| 1. Enquiry | A form is submitted | Writes a row in a sheet and saves the answers | Nothing yet; it is only recorded |
| 2. Triage | A new row appears | Scores the project against your rubric and drafts a reply | Whether to take it, and the reply before it goes |
| 3. Fee proposal | You mark the enquiry "proposal" | Builds a draft from your stage template | Scope, fee and exclusions |
| 4. Appointment | The client accepts | Fills your letter, then cross-checks it against the proposal | The letter before it is sent for signature |
| 5. Invoice | You mark a stage "complete" | Creates a draft invoice in your accounts and tells you | The invoice before it is sent |
| 6. Reminder | An invoice becomes overdue | Drafts a reminder in the right tone | The wording before it goes |
Every automation in the chain ends in a draft: a Gmail draft, a draft invoice, or a document in a "To approve" folder. None has permission to send. That is the single control that makes "the architect approves every document" true rather than a hope. Zapier's Gmail connector offers Create Draft and Create Draft Reply alongside actions that send, such as Send Email and Reply to Email; use only the two draft actions. If you want a chatbot to answer fee and process questions on your website before the form, the tutorial on an AI chatbot for architects covers that front door.
Step 1: An enquiry form that captures what triage needs
Triage is only as good as the answers it reads, and a free-text email gives it little to work with. A short form fixes that. Aim for nine or ten fields, and mark only the first three as required, because every extra required field gives a busy person a reason to stop.
- Project type, as a pick-list: extension, new build, refurbishment, conversion, other.
- The project in their own words, as free text. This is what the AI will read most closely.
- Whether they own the site, and the general area, not the full address yet.
- Construction budget range, in bands, plus "not sure".
- Hoped-for start or decision date.
- Restrictions they already know about on the property or its surroundings, with "not sure" allowed.
- Existing drawings or photos, as a link. Google Forms' file-upload question makes respondents sign in with a Google account, which loses people, so ask for a link or let them reply to the confirmation email with attachments.
- Who decides: one person or several.
- How they heard about you, optional.
- A consent line: "You may use these details to reply to my enquiry."
Google Forms is free. Jotform's free Starter plan caps you at five active forms and 100 submissions a month, ample for a practice that receives a dozen or so enquiries. An enquiry form collects personal data, so put one line under it saying what you do with the answers, and decide how long you keep enquiries you decline. Each submission should land as a row in a sheet; the sheet is the practice's single list of live enquiries and the thing every later step reads.
Step 2: Score the project, draft the reply, you decide
Triage answers one question quickly: is this a project we should spend a call on? Write the rubric down once, in your own terms, so the AI applies your rules rather than guessing them. Score the project, never the person: the rubric below uses only project facts, and the prompt tells the model not to use anything personal about the enquirer.
| Criterion | 0 | 1 | 2 |
|---|---|---|---|
| Fit of project type | Not work we do | Adjacent | Core work |
| Budget against our floor | Below it | Unclear | At or above it |
| Timing | Impossible | Tight | Workable |
| Site inside the area we cover | No | Edge of it | Yes |
| Client readiness | No brief, no decision-maker | Partly ready | Owns the site, knows who decides |
A total of 8 to 10 means offer a discovery call, 5 to 7 means ask up to three questions first, and 4 or less means a polite decline with a referral. A red flag, such as an enquirer who is clearly collecting quotes without a budget, overrides the score and goes to you.
You are helping a small architecture practice screen enquiries. Score the PROJECT, not the person. Do not use the enquirer's name, background or anything personal in your reasoning.
Practice profile: [project types we take; construction budget floor; the start dates we can take; the area we cover, described without addresses].
Score each of these from 0 to 2: fit of project type; budget against our floor; timing; site inside our area; client readiness (owns the site, knows who decides, has a brief). For each, give one line of reasoning that quotes the enquiry. If information is missing, score 1 and say what is missing.
Then give: the total out of 10; the next step by my rule (8-10: offer a discovery call; 5-7: ask up to three questions; 0-4: decline politely and suggest [referral]); a draft reply for that step, under 120 words, signed [first name]; and any red flags for me to look at.
Enquiry: [paste the form answers]Take an illustrative enquiry: a single-storey rear extension plus a loft conversion on a 1930s house, a budget of $150,000 to $180,000, a hoped-for start on site next spring, the enquirers own the house, they are unsure about restrictions, they have no drawings and both partners decide. With a floor of $120,000 in your profile, a result looks like this.
Fit 2 ("rear extension and loft conversion" is core work). Budget 2 (the stated range is above our floor). Timing 1 (a spring start leaves about six months for design and approvals, which is tight). Area 2 (the stated area is inside ours). Readiness 1 (they own the house and both decide, but there is no brief or drawings and restrictions are unknown). Total 8: offer a discovery call. Red flags: none. Missing: whether any restrictions apply to the house or its surroundings.
Draft reply: "Hi [first name], thanks for getting in touch about the rear extension and loft conversion. It sounds like a project we would enjoy. The next step is a 30-minute call to understand what you want and what is possible on the site. Here is a link to choose a time. It would help to have photos of the rear and any existing drawings to hand."
The sheet row gets the score and the draft is saved as a Gmail draft, with a notification to you. You read the score before the draft, because the score is the decision. Two things go wrong here. A model scores generously when the enquiry is vague, which is why the prompt says to score 1 and name what is missing. And a score of 8 is not a promise: if your diary is full, the reply you approve may still be a decline. To add the AI step inside Zapier, the tutorial on adding AI steps to Zapier explains classify, summarise and draft steps and how they count towards your task allowance.
Step 3: A fee proposal built from your stage template
A fee proposal is mostly a template with a few judgements in it: the total fee, how it splits by stage, what is excluded, and what you assume about the client's decisions and access. The judgements stay yours. The prompt only assembles them into your structure and refuses to add anything. For the wider workflow around proposals and briefs, the tutorial on how architects use AI for fee proposals, briefs and paperwork goes further.
Here is the main worked example. For the extension and loft above you estimate 200 hours at an average of $93.00, so a total fee of $18,600.00. You split it across four stages, 20, 30, 30 and 20 per cent, which matches 40, 60, 60 and 40 hours.
| Stage | Covers | Share | Fee |
|---|---|---|---|
| 1 | Survey and concept design | 20% | $3,720.00 |
| 2 | Developed design and approval application | 30% | $5,580.00 |
| 3 | Technical design and tender package | 30% | $5,580.00 |
| 4 | Contractor selection and site stage | 20% | $3,720.00 |
| Total | 100% | $18,600.00 |
Draft a fee proposal from my template and the notes below. Use my template's headings exactly: [paste the headings].
Project: [description in my words]. Total fee: [figure]. Stage shares: [20 / 30 / 30 / 20]. Expenses: [what is included and what is charged separately]. Always include these exclusions: [approval fees, surveys, specialist consultants, site visits beyond [number], changes to the brief after a stage is signed off]. Assumptions: [site access; client decisions within [number] working days; and so on].
Rules: copy the fee and shares exactly and show each stage fee on its own line; add no services, guarantees or timescales I have not given you; flag anything in the enquiry that my template does not cover; end with a list of questions I should answer before sending.A good draft reproduces the table above, lists your exclusions and assumptions, and ends with questions such as "The client says restrictions are unknown: do you want a line saying that approval risk is outside this fee?" and "The loft may need structural input: is a structural engineer excluded or included?" Those closing questions are where the value lies, because they are the gaps you would otherwise find after sending. Two slips to catch: a promised programme ("design complete in eight weeks") that you never wrote, and a stage name that differs from the one in your template, which will break the letter check in step 4.
Do one sum before sending: stage fees add to the total (3,720 plus 5,580 plus 5,580 plus 3,720 is 18,600), and the total divided by your hours gives an average rate you recognise. If the draft is built in a document, Zapier's Google Docs connector has a Create Document From Template action that swaps placeholders such as client name and fee into your template, so the AI only has to supply the judgement-heavy sections.
Step 4: The appointment letter, filled and cross-checked
When the client accepts, the appointment letter repeats the proposal in contract form. Keep its legal clauses in your own template, or in the standard form your professional body publishes, and never ask an AI to rewrite them. Automation fills only the variables: client name, site description, scope, stage table, fee, payment terms, start date and contacts. The tutorial on telling clients about AI in contracts and proposals covers whether and how to say that AI helped prepare documents.
The AI earns its place as a proofreader, because the commonest error in this step is a figure or name that differs between two documents.
Compare the fee proposal and the appointment letter below. List every difference in client name, site description, stage names, stage fees, total fee, payment terms and dates. Show each as: Item / Proposal says / Letter says. Quote exact words. Do not rewrite or suggest wording. If there are no differences, say so. Do not invent clauses.
Proposal: [paste]
Letter: [paste]On the example, a typical catch is a stage 4 fee typed as $3,180.00 in the letter instead of $3,720.00. The stage fees in the letter then add to $18,060.00 while its headline fee says $18,600.00, a gap of $540.00 that would have turned up at the final invoice. The tool lists the stage 4 fee, the total and the mismatch between them. You fix the source and rerun it. Read the result yourself as well: the check can miss a difference or report one that is not there, so treat it as a second pair of eyes rather than a guarantee.
Step 5: Stage-end invoices created as drafts
Invoices need exact figures, so the invoice itself should come from a sheet, not from an AI step. Keep a fee tracker with one row per stage, copied from the signed letter.
| Project | Stage | Fee | Status | Planned end | Invoice raised |
|---|---|---|---|---|---|
| Rear extension and loft | 1 Survey and concept | $3,720.00 | Complete | 12 Nov | No |
| Rear extension and loft | 2 Developed design | $5,580.00 | In progress | 28 Jan | No |
When you change a stage to Complete and "Invoice raised" is No, a Zap creates a draft invoice from that row, writes Yes and the invoice number back to the sheet, and sends you a message: "Stage 1 complete: draft invoice ready to approve." Zapier's Xero connector has a Create Sales Invoice action with an optional status field; its page does not list the values or the default, so set the field and test with a dummy contact until the result is a draft, and leave its Send Sales Invoice by Email action out of the Zap. On QuickBooks Online, Create Invoice adds the invoice and a separate Send Invoice action emails it, so the Zap uses only the first. A line such as "Fee for stage 1, survey and concept design, as set out in our appointment letter" is a fixed description. The only place AI helps is the covering email, which can name the stage and the next one.
A second, simpler automation covers the case where nobody updates the sheet. A weekly scheduled Zap looks for stages whose planned end date has passed and whose status is not Complete, and sends you one message listing them: "Stage 2, rear extension and loft, planned end 28 Jan, still in progress. Mark complete and invoice, or move the date?" It creates nothing and only asks the question, which is how an invoice stuck behind a forgotten status change gets noticed. A stage often ends in practice when the client signs it off rather than on the planned date, so consider adding a "sign-off received" column and invoicing from that.
Step 6: Reminders for unpaid invoices, in three tones
Before building anything, check what your accounting package already does. QuickBooks Online lists invoice reminders on its invoicing page, and other packages have their own reminder settings, so a scheduled template is often enough. The tutorial on Xero invoice reminders with AI-drafted wording shows how far a built-in route goes. The Zap route adds the project name and stage to the wording and puts a person before the send, at the price of one more thing to maintain.
Zapier's Xero connector has an Overdue Sales Invoice trigger that fires when an invoice is overdue by a set number of days; QuickBooks Online's connector has a New Invoice Due trigger that fires when an invoice is due within a set number of days, which suits a nudge just before the date. One Zap per tone keeps each simple.
| Overdue by | Tone | What the draft does | Who acts |
|---|---|---|---|
| 3 days | Friendly | Checks the invoice arrived, links it, asks if there is a query | You glance and send |
| 10 days | Firm | States the amount and the days overdue, asks for a payment date | You read and send |
| 21 days | Formal | Short formal note, plus a task for you to phone first | You phone, then send |
The rules for the prompt are the important part: use only the invoice number, amount, due date and stage from the data; never mention stopping work, interest or fees, because those depend on your appointment terms and are your decision; never refer to anything the client has said unless it is in the data. A draft for the 10-day case reads: "Hi [first name], invoice 0042 for $3,720.00, covering stage 1, was due on [date] and is now 10 days overdue. Could you let me know when we can expect payment? If anything about the invoice is unclear, I am happy to talk it through."
What it costs and how many Zapier tasks it uses
| Item | Monthly cost (USD list) | Note |
|---|---|---|
| Enquiry form | $0 | Google Forms, or Jotform's free plan |
| Zapier Professional, 750 tasks | $19.99 annual, $29.99 monthly | The free plan allows two-step Zaps only and has no AI step |
| ChatGPT Plus or Claude Pro | About $20 | One login for the architect who approves |
| Accounting package | What you pay now | Invoice and reminder features vary by plan |
| New spend | About $40 to $50 | Check each vendor's page |
Zapier bills per task, and each successful action step counts. Say the practice gets 14 enquiries a month, drafts 5 proposals, makes 2 appointments, closes 4 stages and chases 4 invoices. Counting the updates, drafts, notifications and the weekly stage check, that is roughly 90 tasks without the AI steps. AI steps are charged by model tier, and Zapier's pricing page does not print how many tasks each uses, so this sum assumes five tasks per AI step, the highest rate Zapier had published. On that basis the roughly 29 AI steps add 145 tasks, for about 235 in total, well inside 750; even at double that rate the chain would fit. Check the count for the model you pick before relying on the sum.
Five ways it fails, and a ten-minute check each week
- Duplicates. A form submitted twice creates two rows and two drafts. Add a step that looks for an existing row with the same email before creating a new one.
- A stage marked complete by mistake. It creates a draft invoice for work not finished. The approval step catches it, which is why the invoice stays a draft.
- Template drift. Someone edits the proposal template and the headings no longer match the letter. Keep one master folder and change headings in both on the same day.
- Silent failure. Zapier pauses a Zap when 95 per cent of its runs have errored over seven days, and unless you have set up alerts, nobody notices the drafts have stopped. The tutorial on stopping automations breaking silently covers alerts that tell you.
- Invented scope. A model adds a service you do not offer. The "add nothing" rule and your read-through are the defence.
Once a week, spend ten minutes on this: open the drafts folder and clear anything older than three days; compare the enquiry sheet with your inbox for missing rows; compare the fee tracker with your accounts for any stage marked complete without an invoice; and read the last three AI scores to see whether they match what you would have said.
A month of running it: the time sums
The practice in this sum has four people: two architects, an assistant and a part-time administrator. The minutes below are illustrative, and the "after" figure includes your review time. Replace them with timings from your own week.
| Task | Minutes before | Minutes after | Times a month | Minutes saved |
|---|---|---|---|---|
| Enquiry triage and first reply | 15 | 5 | 14 | 140 |
| Fee proposal | 90 | 40 | 5 | 250 |
| Appointment letter | 45 | 15 | 2 | 60 |
| Stage-end invoice | 20 | 8 | 4 | 48 |
| Overdue reminder | 10 | 3 | 4 | 28 |
| Total | 526 |
That is about 8.8 hours a month. At the $93.00 average rate behind the fee example, it is roughly $815 of capacity, against $40 to $50 of software. The sums matter less than the two measures that show whether it works: days from enquiry to first reply, and days from a stage finishing to its invoice leaving. If the first stays at two days, the triage step is not running or not being read. If the second stays at two weeks, the approval step is the bottleneck, and the fix is a fixed time each week to approve drafts, not more automation.
Questions architects ask before automating practice admin
Can AI write the appointment letter's legal clauses?
Leave the clauses alone. Keep them in your own template, or in the standard form your professional body publishes, and let the tools fill only names, addresses, scope, fees and dates. Then use AI as a proofreader that compares the letter with the proposal. Legal wording should come from your standard terms or a solicitor, never from a fresh draft.
Is it safe to put client enquiries into ChatGPT or Claude?
Enquiries contain personal data and site details. Use a business plan, or a paid personal plan with the training switch off, send the tool only what triage needs, and keep drawings and title documents out of it. Say in one line under the form what you do with the answers, and ask your professional indemnity insurer how it views AI use.
Should the automation send emails to clients directly?
No. Build every step to end in a draft, and give no automation permission to send. A draft email, a draft invoice or a document in a to-approve folder keeps the architect's sign-off real. It is easier to switch on sending for one low-risk message later than to recall a wrong email from a client.
Can a practice run this chain without Zapier?
Yes, by hand at first. Paste each enquiry into ChatGPT or Claude with the triage prompt, keep the fee tracker in a sheet, and use your accounting package's own reminders. You lose the automatic drafts and the weekly stage check, but every prompt and template still works. Make is another automation service, billed in credits with a free allowance of 1,000 credits a month, so price both before you build.
Further reads
- AI Policy for Architects: A Ready-to-Use Checklist and Clauses — Write the AI policy your clients and insurer may ask for.
- Architect Meeting Minutes: Record, Summarise and Issue Same Day With AI — The next admin job after the appointment: same-day minutes.
- AI Consultant for Architects: What a First Engagement Costs — Seven consultant days priced deliverable by deliverable for a ten-person practice: audit, policy, one workflow, team session and a 30-day check.
- Architect Website: Project Descriptions and Service Pages Written With AI — A copy workflow for architects: project descriptions from verified facts, service pages by project type, honest area pages and an FAQ on fees and process.
- AI Tools and AI Development: The Complete 2026 Guide — the AI hub, including every tutorial in the AI-for-business series.
Sources: Zapier's pricing page and its Gmail, Google Docs, Xero and QuickBooks Online integration pages; Intuit's QuickBooks Online invoicing page; Jotform's pricing page; Google's Forms help page on question types; OpenAI's ChatGPT pricing page; read in late October 2026.