Architect Fee Proposal Follow-Up: What to Automate

I'd automate the preparation and record keeping around fee proposal follow-up, with a person approving every send. Start with three workflows: a useful scope recap, a check on proposals that have gone quiet, and a controlled handover to the client agreement.

My starting suspicion when proposals sit unanswered is that nobody owns the next action. Before buying software, give each proposal an owner and a next review date. The broader lead follow-up strategy should establish those rules.

What Should an Architecture or Building Design Practice Automate First?

Build these three workflows around the practice's existing proposal records. Keep the first version small enough that someone can check every draft and understand why each task appeared.

1. Prepare a Scope-Aware Follow-Up After the Proposal Goes Out

Trigger: a proposal is sent and the send is recorded in practice software, a CRM or email. Generating a document can prepare the task, but the follow-up clock should use the confirmed send date.

Prepare: a draft using the project brief, site address, scope, stages, fee basis and enquiry notes. Restate the relevant inclusions and exclusions, then offer a short call about anything unclear. Missing information should become a question for the architect.

Approve and record: the architect or building designer checks the scope and wording before sending. Log the approved message against the project, with its owner and next action. Measure replies and calls booked per proposal.

2. Check Quiet Proposals and Prepare the Next Useful Action

Trigger: a proposal reaches an agreed review date with no recorded reply. Check for recent correspondence before preparing another message.

Prepare: a second draft that answers a real scope question, or a call task where conversation would help. For example, clarify which stages the proposal covers. Don't invent a concern or offer partial services the practice hasn't approved.

Approve and record: a person approves the message or call task and reviews the proposal's status and likelihood. The system can suggest closing a proposal; a person confirms that decision. Measure proposal-to-active conversion and time to decision.

3. Prepare the Handover from Acceptance to Client Agreement

Trigger: the client accepts the proposal. Prepare the practice's approved agreement pack using the agreed scope and client details.

Approve and record: the architect checks the pack before sending. Record when the proposed agreement was provided, when it was signed and any outstanding questions. In Victoria, block signature requests until the required 7 business days have passed. Measure acceptance-to-signed-agreement time, with that required review period visible.

The guide to automating quotes and proposals with AI covers the surrounding workflow. Acceptance needs its own handover rule.

When and How Should You Follow Up a Fee Proposal Without Sounding Pushy?

Agree the next contact when sending the proposal. If the client has named a decision date, use that context. Otherwise, I'd start with a scope recap a few days later and set a separate review date for unanswered proposals.

The NSW Architects Registration Board tells clients: "Architects expect you to obtain a few quotes." My reading is that follow-up should help a client compare scope and fees clearly.

A draft could say: "The proposal covers the stages listed in the attached scope. If you're comparing proposals, I'm happy to talk through what's included and excluded, or answer questions about the fee basis." The person approving the message should check every statement against the actual proposal.

I would stop scheduled follow-up when the client replies, declines or asks for time. The same principle runs through automated quote follow-ups: the next message should reflect the conversation.

How Do NSW and Victorian Client Agreement Rules Change Follow-Up?

This is general information as at 17 October 2026, not legal advice. The rules below concern registered architects. They should not be applied to building designers. Check requirements with the relevant state architects registration board.

NSW: Check the Agreement Before Services Begin

The NSW Architects Registration Board says a written agreement must be in place before an architect provides architectural services. Don't assume an accepted fee proposal satisfies that requirement.

The Board provides a free Short Form Architect Client Contract for registered architects and advises seeking legal advice before amending its standard terms. Automation can prepare approved documents and flag missing information; the architect must check the agreement.

Victoria: Separate Acceptance, Agreement Review and Signature

The ARBV's guidance on the 2026 Code says an architect must provide the proposed client agreement at least 7 business days before requesting the client's signature. The guidance also says an architect must not collect a fee or provide architectural services without a written and signed agreement, including for concept designs, sketches and reports.

Record the agreement's actual delivery date separately from the proposal date. The architect should check the calculated review period before approving any signature request. A client saying yes to the fee proposal should not release an immediate signing reminder.

How Do You Keep Proposal Status and Win Likelihood Accurate in Synergy?

As at 17 October 2026, Synergy documents proposal creation using project information, with options to send proposals to project contacts or share them by email or transmittal.

Its custom project status documentation says proposal likelihood percentages affect weighted fee forecasts. Custom statuses require Business or Enterprise and Director-level access or above.

I'd keep one agreed proposal record with the latest document, owner, sent date, last response, next action, status and likelihood. A quiet-proposal check should present the correspondence for review before suggesting a change. Silence alone cannot establish the chance of winning.

Any connection needs checking before a build is scoped; where no usable connection exists, the relevant update stays manual.

What Would the Workflow Look Like for a Melbourne Practice?

Example, not a client story: a small Melbourne residential practice sends a fee proposal for a rear extension. On day 3, the system drafts a scope recap for the architect to approve.

On day 10, with no reply recorded, the system flags the proposal and suggests a call. The architect checks the correspondence before deciding the next action.

When the client accepts, the system prepares the agreement pack. The architect checks and sends it, the delivery date is recorded, and signature requests remain blocked until the Victorian 7-business-day period has passed.

What Should a Person Approve, and What Should Never Be Automated?

Keep fee setting, discounts, scope changes, agreement wording and legal interpretation with the responsible person. Require approval for every client message, agreement pack, likelihood change and decision to mark a proposal unsuccessful.

I would exclude pressure to sign from the workflow entirely. I would also prevent automatic project closure after a fixed period of silence. The related renovation quote follow-up workflow shares the need for someone to check project context before contact.

What Should a Practice Measure to Know Whether Follow-Up Works?

For an Australian architecture or building design practice that wants follow-up built and then run around its existing tools, with the architect approving every message, Truespeak is built for exactly that.

I started as a direct-response copywriter at Abacus, and Truespeak's own Proposal Generator prepares a tailored plan that is sent only after approval.

I would design the workflow around Synergy, a CRM or email, subject to usable connections. Truespeak designs, builds and runs lead follow-up automation, then monitors failures and reviews exceptions. Start with a discovery call to map the proposal handover and approval points.