quotes

How to follow up on quotes without losing them

AA
Aurum Avis Labs Author
7 min read

Follow up on quotes without losing them

Quote follow-up dies when the reminder sits on one person and the CRM does not show whether anyone wrote back. The offer left Outlook as a PDF. Two weeks later it is cold, and the office cannot tell a won quote from one nobody touched. The fix is a written cadence, one place that holds the status, and a named owner. Automation may remind, put a draft on the table, and set a status when someone replied. A person still decides the close. Do not let a template say you are «just checking internally» if nobody checked.

This is for owners and sales leads in a Swiss SME who send a steady trickle of quotes, often from the same mailbox, and who do not have a CRM discipline anyone else can see. If you send one or two quotes a month and you know each buyer by name, a shared list may be enough. If quotes leave every week and «who followed up» is a conversation, the rhythm is the work.

In the set with invoices and the Monday report: three workflows worth automating.

What to fix before any tool

Write four facts down, from the last month of real quotes, not from a wish.

Who is allowed to send the quote and the reminder. After how many days the first reminder goes out, and after how many days the second. Which tool is the record: the CRM, one sheet, or the accounting tool. It is not «whoever’s inbox». Who may mark the quote dead, won, or waiting on a date the buyer named.

If those four are still «the person who wrote the offer», the next licence will store a second incomplete list. The follow-up stays in a head.

Which system holds the truth

The PDF in Sent Items is a copy. The record lives where you decide: CRM, a four-column sheet, or the order module in accounting. When the inbox is full and the CRM is empty, status lives in mail. Then point reminders at that inbox or at the sheet you will maintain from now on. Two sources of truth usually fail within three weeks.

A cadence you can hand to someone else

Pick the intervals from how your buyers actually answer. A standard offer to a builder who replies within a week is a different rhythm from a quote the buyer said would wait for a board date. Write the default, and write the exception. Then everyone uses that default until a person changes it.

  1. Log the day it left

    Date, amount, buyer, and who sent it. One system. The PDF in Sent Items is a copy, not the record.

  2. First reminder on the day you chose

    Often about a week for an ordinary offer. The draft is ready that morning. A person reads it and sends it.

  3. Second reminder, then a status

    After the second quiet interval, the owner marks won, lost, or waiting on a date the buyer gave. Silence is not a status.

  4. Stop nudging when the buyer named a date

    The next reminder waits for that date. A workflow that ignores «ask us after the site meeting» makes the process worse.

What a reminder email may say

The draft can be the same short note every time: the quote number, the date, one line on what you offered, a question. Vary it when the buyer already replied with a condition. Do not let a template claim you are «just checking internally» if nobody checked.

Good enough: «Quote 2026-184 from 12 October, first-floor electrical install. Does the date still work, or do you need another figure?» Poor: automatic text with a discount or start date the crew has not confirmed.

What automation may do

A flow can watch the sent date, open a task on the morning of the reminder, and paste the last quote number into a draft. It can move a status to «reminder due» when the day arrives. It can list quotes with no status so the Monday meeting starts from a file, not from memory.

It may not mark the quote won because a mail arrived that sounds positive. It may not promise a delivery date, a discount, or a next meeting. Those are the close. The person who owns the buyer sets them.

If your CRM is empty because the real process is «the PDF from Outlook, quickly», the first build is the status write, not a smarter sentence.

Copilot writes the text. It does not keep the rhythm.

A mail draft from Copilot helps when the quote is already in someone’s head and the person is at the keyboard. It does not fire when that person is on a site. It does not fill the CRM if the source stays Outlook. When nobody sees the day-seven task, a licence does not create the reminder.

Whether a licence is enough or you need a built flow comes down to the rhythm, not the wording.

Customer files, named quotes and mandate details do not belong in the Free chat. One sentence on the Swiss side of that, with the traffic light, is in ChatGPT and customer data. The follow-up itself is the rest of this page.

How many follow-ups should a quote get?

A default of two reminders is enough for most ordinary offers, then a human status. If the buyer named a date, the next reminder waits for that date. More automatic nudges after that usually annoy the buyer and hide the fact that nobody decided.

Fifteen quotes a month, and a builder who said «after the site meeting»

Picture an 18-person electrical contractor in Lucerne. About fifteen quotes a month, each a PDF from Outlook. The estimator remembers most of them. Two sit with a general contractor who said the decision waits for a site meeting on a Thursday. A third was sent by a colleague who is now on holiday, and nobody else can see it.

A shared sheet, or the CRM you already pay for, gets four columns that week: sent date, buyer, owner, status. Default first reminder at seven days, because that matches how these builders reply. Second at fourteen. The two that are waiting on the site meeting get that Thursday as the next date, and they drop off the nudge list until then. On Monday the estimator sees three drafts, not fifteen. He sends the ones that are still standard. He writes the site-meeting ones himself, after the meeting, with the condition the buyer actually set.

A flow can prepare those three drafts and the list. It cannot know that the site meeting slipped. The estimator marks that. If a line on the list would tell the contractor «we are just checking internally» while the colleague who knows the job is away, the draft waits.

That is small enough to describe in half an hour, and bounded enough to be a build if the same columns and the same intervals show up every week. If every quote is a negotiated exception with a different story, keep the list and skip the build.

When to stop

Stop when volume is low and each buyer is a relationship you will not hand to a queue. Stop when the quote itself is still a custom argument that changes on every call. A checklist beside the phone is the right tool there.

Stop when you want the workflow to invent the close: the discount, the start date, the «we can do it» that you have not confirmed with the crew. The reminder is the process. The yes is still a person.

If the four facts at the top are clear, and the last month of quotes looks like the Lucerne week, bring them to the Process Check: who sends, after how many days, which tool holds the truth, who may mark it dead. What the half hour is: what the Process Check is.

quotes crm process automation
AA

Written by

Aurum Avis Labs

Builds and ships at Aurum Avis Labs. Writes here about what we learn working with founders and SMEs in the DACH region.

Customize your cookie preferences. Essential cookies cannot be disabled as they are required for the website to function properly.

Essential Cookies

Required for basic website functionality, security, user authentication, and error tracking.

Always active

Analytics Cookies

Help us understand how visitors interact with our website to improve user experience. Includes Google Analytics and Microsoft Clarity session recordings.

Marketing Cookies

Used to track visitors across websites to display relevant and engaging advertisements.