If your practice uses AI for drafting, design support or meeting notes, check what has changed in the work itself. Faster individual tasks are useful, but the financial result depends on how the team uses the time saved and what the tools cost.
The reason isn’t the tool. AI for architecture firms has mostly meant adding tools on top of work that isn’t written down. The principal writes each proposal a little differently. New projects start a little differently every time. Drawing updates depend on whichever project architect is closest to the work that week. Builder questions during construction get answered the way the project architect feels like answering them that day. Pile AI on top of that and you save a few minutes per task. You don’t change how the practice runs.
This guide sets out five workflows to assess, how to standardise them before adding AI, which steps need human judgement, and how to measure operational and financial results.
The workflows below are suggestions, not measured industry benchmarks. Establish your own baseline and retain a change only when the evidence supports it. There is no assumed percentage saving or timetable for financial returns.
Before using client data: approve the tool and data use before connecting recordings, notes or client systems. Confirm lawful recording, confidentiality terms, required notices and consents, and vendor access, training, retention and overseas processing settings. Use only the minimum necessary data. The privacy and sign-off checks below apply to every workflow, including the examples.
The implementation framework
The order is the whole game. Write it down first. Automate second.
AI tools don’t make a messy workflow good. They make it messy faster. Writing things down is the step that has to come first. It is not optional clean-up you do later.
AI is a power tool. A power drill. A circular saw. A nail gun. Fast and strong. It can do in minutes what hand tools take hours to do. But without a blueprint, a power tool just builds a faster mess. AI is the same. Without a workflow written down underneath it, you just speed up whatever chaos was already there.
What “writing it down” actually means: take the workflow and break it into six to twelve steps. Each step has an input (what you start with) and an output (what you end with). Each step has one owner. The test: a brand new hire could run the workflow from the document without asking questions.
What “automate” actually means: once the workflow is written down, separate the pattern steps from the judgment steps. Pattern work looks like drafting, summarising, formatting, comparing, copying. Judgment work looks like design calls, client conversations, sign-off, picking which direction the project goes. AI takes the first pass on the pattern work. People review. Judgment stays human.
This is the practical version of a bigger argument. If you want the deeper version on why the order matters for every kind of services firm, we wrote that here. The rest of this post is what to actually do inside an architecture practice.
An architecture practice sells senior time, so the hours a workflow eats are the cost that matters. Getting the order right matters more than the number of tools.
The 5 workflows worth standardising first
These five workflows are candidates for review. Rank them using your own time records, frequency, complexity and risk; the order below is not an industry ranking.
Workflow 1: writing project proposals
What a proposal actually contains.
Strip away the cover page and every project proposal an architecture firm writes has five things in it:
- What the client wants to build.
- What stage they’re at and what they need from you.
- How you’d approach the project, broken into phases.
- Who from your team would work on it.
- The fee, the timeline, and what’s included or not.
Everything else is wrapper.
Where the time goes today.
Proposal work can involve reviewing meeting notes, selecting relevant past work, checking scope and preparing fees. Record the time spent on each step, including revisions and sign-off, before deciding which parts to standardise.
What standardising actually means here.
You write down three things:
- A library of every kind of project you do. Residential renovations, new builds, mixed-use, healthcare fit-outs, whatever your practice does. For each one: what stage you take it from and to, the team it needs, the typical fee range, the photos and past projects that prove you can do it.
- A standard fee structure. What each phase costs, how the fee scales with the size or complexity of the building, what your minimums are, what triggers extra fees.
- A standard proposal layout. The five sections above, with sub-templates for each section.
What an AI-assisted workflow could look like once those three are written down.
AI could prepare a draft of each step for the senior project architect to confirm:
- Pulls only approved, necessary notes from meetings and calls with the client (Otter, Fathom, or whatever tool the practice records on).
- Drafts the what they want to build and what stage they’re at sections straight from those notes.
- Matches the project to the right kind of project in your library, pulls the matching past projects and photos.
- Generates the fee from your standard pricing logic, sized to the project.
- Assembles the whole document in Word, Google Docs, or InDesign using your standard template.
Queue the proposal for senior review when the required inputs are complete. Check the draft and approve it before sending.
What stays human.
The responsible senior professional checks the proposed approach, scope, evidence and fees before sending the proposal. Allow time to verify source material and rewrite an unsuitable draft; review time depends on the proposal.
What to measure.
The aim is a consistent proposal that meets your quality standard. Measure the total preparation and review time against the baseline rather than assuming a percentage saving.
Workflow 2: starting a project with a new client
What starting a project actually contains.
Every new project, no matter the type, starts with the same five things:
- The kickoff call with the client.
- Collecting what you need from them (site survey, existing drawings, planning approvals, budget confirmation, key contacts on their side).
- The internal kickoff brief that gets your design team aligned on what they’re actually building.
- Setting up the project in your tools (project management software, file folders, drawing templates, billing setup).
- The first design milestone plan with dates, owners, and what gets shown to the client when.
Where the time goes today.
Gathering client information, access, source documents and approvals can create repeated follow-up work. Record the time spent gathering and checking inputs, and the elapsed time to kickoff, so you can identify the actual bottleneck.
What standardising actually means here.
You write down three things:
- A standard kickoff sequence. Every step from contract-signed to design-work-starting, with clear owners, message templates, and a checklist that has to be complete before the design team picks up the project.
- A standard intake list. Everything you need from every client at the start (site survey, existing drawings, planning approvals, budget, key contacts), in the same format every time.
- A standard internal kickoff brief. What your design team needs to know to start work, written the same way for every project.
What an AI-assisted workflow could look like once those three are written down.
AI could prepare a draft of each step for the senior project architect to confirm:
- Drafts the welcome messages from the proposal and the signed contract, spread across the first week, for the senior project architect to approve before they go.
- Generates the intake checklist sized to the specific project, and drafts the reminders to the client on what’s still missing.
- Drafts the internal kickoff brief from the proposal, the contract, and the recorded client meetings.
- Proposes the project setup in your project management tool (Monograph, Asana, ClickUp, or whatever you run on), the file folders, and a kickoff call slot on the senior project architect’s calendar, for a person to confirm.
- Drafts the first design milestone plan from the scope with proposed dates.
What stays human.
The senior project architect runs the kickoff call. They make the call on whether the client’s stated brief matches what came out of the first meetings, and they adjust the plan if it doesn’t.
What to measure.
The aim is a clear onboarding sequence with complete inputs, named owners and agreed deadlines. Check whether it reduces missed information, rework and the time to begin delivery.
Workflow 3: sending regular client updates
What a regular client update actually contains.
Every update an architecture firm sends has six things in it:
- What we delivered since the last update.
- What’s in progress and when it’ll be ready.
- What’s stuck and what we need to unstick it.
- What’s coming next period.
- The drawings or visuals showing the design progress.
- Anything we need from the client (decisions, sign-offs, info).
Where the time goes today.
Preparing updates means gathering project information, checking its accuracy and explaining what matters to the client. Measure that work across your actual reporting cadence; weekly and fortnightly updates create different workloads.
What standardising actually means here.
Two things:
- A single update template. Same six sections, same order, same format, every project.
- A list of where to pull drawing progress from per project type. What the design team puts into Revit, AutoCAD, or Bluebeam, and what the standard view looks like for the client.
What an AI-assisted workflow could look like once those two are written down.
AI drafts the update every period:
- Pulls activity from the project management tool, the drawing files, the team’s messaging tool, and the meeting notes.
- Drafts each of the six sections from that data.
- Pulls the latest drawing views or renders as the visuals.
- Flags risks where the timeline is slipping, items are stuck, or there’s a pattern of late client decisions.
- Formats the update and queues it for review, ready to go to the client on the same day every two weeks (or whatever cadence the practice picks).
The project architect reads and approves the draft before it goes out. Nothing is sent without that approval. Allow enough time to check the draft against its sources.
What stays human.
Client judgement and difficult conversations stay with the responsible professional. Record any time saved, then assess its effect on delivery capacity and allocated project costs. Total business profit still depends on revenue and actual expenses.
What to measure.
The aim is a consistent, accurate update on the agreed schedule, approved by the person responsible for the client. Compare total preparation and review time with the baseline.
Workflow 4: answering builder and contractor questions during construction
What a builder question actually contains.
During construction, the builder or contractor sends questions when something on site doesn’t match the drawings, or when they need a decision the drawings didn’t cover. Every question has the same five parts:
- What part of the building they’re asking about.
- What the drawings say.
- What they’re seeing on site or what they want to do.
- What they need from you to keep building.
- When they need it by.
Where the time goes today.
Construction questions vary in volume, complexity and risk. Measure the number received and the time spent finding information, checking drawings and preparing responses across your own projects.
What standardising actually means here.
Three things:
- A standard format for incoming questions. What you require from the builder before a question is “complete enough” to answer. Question-ready format means the architect can respond fast.
- A response template. Same structure for every answer. What the drawings say. What the answer is. What it changes about the spec or drawings. Any cost or time impact for the contract.
- A documented library of past answers. Tagged by part of the building (foundations, structure, services, finishes, joinery) so the practice can look up how a similar question was answered before.
What an AI-assisted workflow could look like once those three are written down.
AI prepares the first draft of every response:
- Pulls the question and matches it against past answers on this and earlier projects.
- Drafts the response structure and a proposed answer for the project architect, who pulls and quotes the relevant drawings.
- Flags anything that looks like a real design change, a cost impact, or a structural concern.
- Sends the draft to the project architect for review.
The project architect checks the draft against the drawings and relevant project records, resolves uncertainties and signs off. Allow enough time for that professional review; complexity and risk determine when a response is ready to issue.
What stays human.
Any answer that changes the design intent. Anything with a cost or timeline impact. Anything where the contractor is pushing back and a relationship conversation is needed. Anything touching structure goes to the structural engineer of record; anything touching safety is escalated under the project’s WHS arrangements. The project architect coordinates but does not decide outside their discipline.
What to measure.
Set response targets appropriate to the question and its risk. Measure retrieval and drafting time separately from the professional checks needed before a response can be issued.
Workflow 5: invoicing and getting paid
What an invoice actually contains.
Every invoice an architecture firm sends has five things in it:
- The phase or work done that period (phase-based, hourly, or both).
- Any pass-through costs (engineering consultants, planning fees, printing, renderings, models).
- The right amount per the contract, set out as a valid tax invoice (your ABN, the GST and the other details the ATO requires) if you are registered for GST.
- Sent to the right billing contact on the client’s side.
- A plain summary so the client knows what they’re paying for.
Where the time goes today.
At a billing milestone, the team gathers time and expense data, checks the agreement and approves the invoice. Measure the lag between completing billable work and issuing the invoice. Track the later invoice-to-payment interval separately.
What standardising actually means here.
Three things:
- A standard billing day. Choose billing dates or milestones that match the client agreement.
- Invoice templates per project type. Phase-based, hourly, or hybrid. Each with the same structure.
- A written review-and-send sequence. Admin knows what triggers each step. The principal knows when their sign-off is required and when it isn’t.
What an AI-assisted workflow could look like once those three are written down.
AI handles the invoicing cycle, with a person approving each run:
- Pulls time data from the time tracker or project management tool.
- Pulls pass-through costs from the accounting system (engineer invoices, planning fees, printing, renderings).
- Cross-references the contract for fee structure and rates.
- Drafts the invoice with line items plus a plain summary for the client.
- Queues the invoices for approval, then sends them to the billing contact on the standard billing day.
- Drafts follow-ups on overdue invoices on a written sequence (reminder at day 7, escalation at day 14, principal flagged at day 21), each approved before it goes.
What stays human.
Principal sign-off on anything where the scope went sideways, the amount looks unusual, or the client needs a real conversation instead of an email. If your books are kept up to date so accounts receivable (money clients owe you that hasn’t landed yet) is current, the team can see and follow up overdue invoices sooner.
What to measure.
Use an agreed billing schedule that matches the client contract, with accurate invoices and timely approval. Earlier invoicing can bring cash receipts forward, but it does not by itself make customers pay invoices faster or guarantee a reduction in debtor days.
Five workflows to assess
Set priorities using your own baseline
-
Project proposals
Principal/senior project architect time per proposal
Front-of-funnel Measure time -
New project kickoff
Senior project architect time per new project
Project start Measure time -
Regular client updates
Project architect time across every active project
Recurring Measure time -
Builder questions
Senior architect time on construction-phase responses
Construction Measure time -
Invoicing
Admin and senior review on every invoice cycle
Cash cycle Measure lag
What this looks like in the numbers
Evaluate capacity, profit and cash independently. An improvement in one does not guarantee an improvement in the others, and there is no verified quarter-by-quarter timetable.
Measure capacity. Compare total preparation, checking and rework hours before and after the change. Freed salaried hours create capacity; they do not reduce payroll expense by themselves.
Measure profit separately. Fewer hours charged to a project can improve its allocated margin while total salary costs stay unchanged. Business profit improves only if extra work generates revenue or actual costs fall, after allowing for AI subscriptions, setup, review and rework. See the Queensland Government guide to financial ratios for the distinction between profit and efficiency measures.
Measure billing and collection separately. Earlier invoicing can shorten the time from completing work to receiving cash, if payment timing otherwise stays the same. It does not by itself shorten the invoice-to-payment interval or guarantee lower debtor days. Track billing lag, payment terms, overdue balances and actual cash receipts.
There are knock-on effects most principals don’t price in until they show up. Project management tools that were holding non-standard work together come off the software line. Reporting tools whose output now generates upstream come off the software line. Workflow tools whose use got absorbed come off the software line. Check which subscriptions you can actually cancel before you count the saving.
Keep a record of the baseline, implementation costs and results. Client mix, staffing, pricing and payment behaviour all affect the outcome; use your own evidence to decide whether to expand the workflow.
Three outcomes to measure
Assess each outcome separately.
-
Capacity
Measure hours saved after checking and rework. Salary costs may stay unchanged.
-
Profit
Count extra revenue or actual cost reductions, less implementation and ongoing costs.
-
Cash
Track billing lag, collection time and cash receipts separately.
Implementation timeline
Start. Pick a workflow using time records and risk. Document the steps, inputs, outputs and owners before adding AI.
Pilot. Standardise the workflow with the team, then add AI to suitable drafting or formatting steps. Compare total cycle time, quality, review effort and cost with the baseline. Investigate poor results before expanding the pilot.
Extend. Move to another workflow only when the first pilot meets the targets you set. Reuse what worked, but measure the new workflow on its own terms.
Review financial results. Check whether saved time has led to additional revenue or lower actual costs. Include software, setup and review costs, and reconcile any claimed cash improvement to receipts.
Where AI backfires in an architecture firm
Three workflows that look automatable but where AI usually backfires.
Design and concept development. Design taste is the product. AI can help explore options, but it can’t lead. Handing design direction to AI risks work that converges with everyone else’s.
Drawing review and red-lining. This needs senior eyes even when drafting is AI-assisted. The drafting can be AI. The judgment on whether the drawing is right cannot.
Scope creep conversations. AI can flag when a project is going over scope. It can’t have the conversation with the client about it. That’s relationship work.
The pattern across all three: judgment-heavy, relationship-heavy, taste-heavy. AI in those workflows gives you faster output and worse outcomes.
Client data, confidentiality and sign-off
Two rules apply to every workflow above, before any tool goes near it.
A person approves everything that leaves the practice. AI drafts; it does not send. Proposals, client updates, builder responses and invoices all go out after a named person has read them. Anything that changes the drawings, the specification, the cost or the programme is a professional decision for the responsible registered architect. Anything touching structure goes to the structural engineer of record; anything touching safety is escalated under the project’s WHS arrangements. The architect coordinates but does not decide outside their discipline. Using AI to draft it does not move that responsibility.
Know where client information goes. Briefs, drawings, site photos, contracts and meeting recordings are your clients’ confidential information. Before you connect a tool, check its data terms: where the data is stored, who can see it, and whether your inputs are used to train its models (many business plans let you switch this off). Check your client contracts for confidentiality clauses. Tell clients, and get their agreement, before you record meetings; the rules on recording conversations differ between states and territories.
If your practice turns over more than $3 million a year, the Privacy Act also applies to the personal information you put into these tools; some smaller practices are covered too, for example if they trade in personal information, hold Commonwealth contracts or are related to a larger entity (see the OAIC small business guidance). The statutory tort for serious invasions of privacy, in force since 10 June 2025, has no small-business exemption, and from 10 December 2026 covered entities that use automated decision-making that significantly affects individuals must say so in their privacy policy.
Limit access to the people and systems that need it, set retention and deletion periods, and test with de-identified or synthetic data first. For entities covered by the Privacy Act, assess collection, notification, use and disclosure, overseas disclosure and security under APPs 3, 5, 6, 8 and 11. Some small businesses are covered despite turnover below $3 million. Human review does not replace these obligations. The OAIC recommends keeping personal and sensitive information out of publicly available generative-AI tools.
What to do this week
Three things you can start before Friday.
Pick the workflow. Look at last month’s senior timesheets. Where did the most senior hours go? That’s your first workflow.
Write it down. Six to twelve steps, inputs, outputs, owners. One afternoon.
Mark the steps. Pattern work gets a star. Judgment work gets a different mark. The starred steps are your AI list for next month.
Skip the tool conversation until you’ve done these three. The gains we see come from firms that write the workflow down before buying anything new. To see where your own numbers (margin, debtor days, cash) stand before you start, get your free financial health check.
AI implementation in an architecture firm isn’t a tool problem. It’s a discipline problem. In our experience, the firms pulling ahead are the ones that picked one boring, repeatable workflow at a time, wrote it down, decided which steps deserved a person, and let software handle the rest.
If you’ve never mapped your most-repeated workflow end to end, that’s the place to start. The real returns sit in the unglamorous work, the part that’s been running on senior memory for years.
Frequently asked questions
What’s the best AI tool for an architecture firm?
The honest answer is that tools matter much less than which workflow you point them at. A written-down workflow runs well on cheap tools. A messy workflow makes expensive tools look broken. Pick the workflow first, write it down, then choose the simplest tool that fits the pattern steps. Most firms overspend on tools and underspend on the writing-down work that makes those tools actually useful.
How do I get my team to actually use AI?
Resistance usually comes from teams that think AI is being added to watch them or replace them. The fix is operational. The person who runs the workflow today is the one who should write it down, not someone above them. They know where the friction lives and where the exceptions hide. Bring in outside help for the automation step if needed, but the writing-down has to come from the team that owns the workflow.
What can AI realistically do for an architecture firm right now?
Most useful for first drafts of structured documents (proposals, client updates, builder question responses, invoices), pulling and formatting data from connected tools, and drafting internal briefs from existing inputs. Least useful for taste, design judgement, client relationship calls or strategic priorities. Every output in either list is checked against its sources and approved by the responsible professional before it is used.
Won’t my clients feel cheated if they find out I used AI?
Clients buy outcomes, not methods. They care whether the building works, the design hit the mark, the project came in on time and budget. The risk isn’t using AI. It’s using it to do worse work faster, or putting their information somewhere they didn’t agree to. Be open about it where their data or your contract is involved, keep a person accountable for every document that goes out, and use it to free senior people up to do better work, more often.
How long until this shows up in my practice’s financial numbers?
There is no verified timetable for these outcomes. Measure hours saved after review and rework, then check whether they produce extra revenue or lower actual costs after implementation costs. Track billing lag and invoice collection separately: earlier invoicing alone does not mean customers pay invoices faster.
About this article
Written by Jordan Bevans. Published . General information for Australian businesses, not advice for your situation.
