How to automate quote follow-ups without buying an expensive CRM

Most quotes go quiet because nobody has time to chase them, not because the customer said no. You can fix that with a spreadsheet, the email account you already use and a low-cost automation tool, without paying for a full CRM.

Start with a list, not a platform

Automation only works if there is one reliable record of what has been quoted. For most small businesses that is a spreadsheet with a row per quote. Keep the columns few and plain:

• Customer name and email address
• Job or quote reference
• Amount
• Date sent
• Status (open, won, lost)
• Owner (the person responsible for the follow-up)
• Date of last follow-up

The status and last follow-up columns do the heavy lifting. Every rule you build later asks the same question: is this quote still open, and has anyone touched it recently? If the spreadsheet is patchy, the automation will be too, so fix the habit of logging quotes before you fix anything else.

Pick a tool you already pay for

You probably have what you need. If you run Microsoft 365, Microsoft publishes a tutorial on sending weekly reminder emails from spreadsheet data. It uses an Office Script for Excel together with a Power Automate flow, and the same pattern works for a quotes sheet. If you run Google Workspace, Google's Apps Script lets you send mail from a sheet, and its MailApp reference includes a call that reports your remaining daily email quota. That is a useful reminder that free and bundled tools have sending limits, so check them before you rely on a script.

If you would rather not write scripts, a no-code connector is the other route. Zapier publishes several quote templates. One detects sent quote emails in Gmail and creates follow-up records in Zapier Tables, so the list builds itself. Another watches quote rows in Google Sheets and sends templated reminder emails as a quote nears expiry. Check current pricing and task limits on the vendor's site before you commit, because they change.

Remind your team first, then the customer

There are two kinds of follow-up automation, and they carry different risk.

The first is an internal nudge. A rule checks the sheet each morning and emails the quote owner a short list: these quotes were sent three days ago and have no reply. The person then writes a real message. Zapier has a template along these lines that sends a follow-up reminder to the sales rep when a new quote arrives. Nothing goes to the customer without a human deciding to send it, so a bad row of data cannot embarrass you.

The second is a customer-facing email sent automatically. This saves more time, but it needs cleaner data and careful wording. A sensible approach is to begin with the internal nudge, watch it for a few weeks, and only then automate the customer email for simple, low-value quotes.

Whichever you choose, keep the sequence short and stop it the moment the status changes. A common pattern is a light check-in a couple of days after sending, a second touch a few days later, and a final note before the quote expires. Treat those timings as a starting point and adjust to how long your customers usually take to decide. Australian small business advisers publish similar short sequences, for example this three-message quote follow-up guide, which also cites survey data suggesting nearly half of tradies never follow up a quote. That is vendor content, so read it as a prompt to check your own numbers rather than as settled research.

Keep the emails inside the spam rules

Automated email to customers in Australia is regulated. The ACMA explains that the spam rules apply to commercial electronic messages, meaning those that offer, advertise or promote goods or services. A plain reply to a customer who asked for a quote is a different thing from a promotional blast, but a follow-up that pushes a discount or promotes other services can look commercial. Check your own wording against the ACMA's guidance rather than assuming.

The regulator's email and SMS unsubscribe fact sheet sets out the rules and notes that you may have to produce evidence of consent if asked. The ACMA has also flagged that it sees businesses with inadequate consent and unsubscribe processes in automated messages sent to new and prospective customers. Its research on small and medium businesses found some owners believed the rules applied only to larger firms. Being small does not exempt you. Build in three habits: identify your business clearly in every message, include a working way to opt out, and keep a note of why you are allowed to contact each person.

Build it in an afternoon, then review it monthly

A practical first version looks like this:

1. Create the quotes sheet and agree who fills it in.
2. Add a rule that flags quotes with no reply after a set number of days.
3. Send the flag to the quote owner as an email or chat message.
4. Add a status change that stops all reminders when a quote is won or lost.
5. Once that runs cleanly, consider automating the customer email.

Then review monthly. Look at how many quotes were chased, how many were won and where the process broke. If the automation sends a reminder for a job that was already won, the fix is almost always in the data, not the tool.

Send us your situation

If you want a second opinion on which tools suit your setup, send an enquiry through the 21Labs contact form. Describe how quotes are sent and tracked today, and we will tell you what we would automate first.

Sources

• Create follow-up records and send reminder emails to prospects (Zapier)
• Send 7-day quote expiration emails to prospective customers (Zapier)
• Send follow-up reminder email to sales rep for new quotes (Zapier)
• Tutorial: Send weekly email reminders based on spreadsheet data - Office Scripts (Microsoft Learn)
• Class MailApp | Apps Script (Google for Developers)
• Dealing with spam (ACMA)
• Email and SMS unsubscribe rules fact sheet (ACMA)
• Telemarketing and e-marketing (ACMA)
• Small and medium-sized businesses: marketing messages and unsubscribe rules (ACMA)
• Win 30% More Jobs: The Quote Follow-Up System (ServiceScale)