How to follow up enquiries and quotes without losing them

This guide from AR Labs is for owners and office staff at small service businesses (trades, studios, makers and consultancies) who want to stop losing enquiries and sent quotes. An enquiry comes in by Instagram message while you are on a job; a quote goes out on Tuesday and nobody chases it; a prospect says "we'll get back to you" and you never find out what happened. The guide sets up one list of everything open, a next action and an owner on each item, and a short routine that keeps the list honest. It starts with a spreadsheet or the CRM you already have, and says where automation helps once the routine works.

It rests on owners' posts in public business forums and on the vendors' own pages, applied through our general method for mapping a business process before automating it. We have not built a follow-up system for a business of this kind.

Why enquiries and quotes get lost

Owners in UK, US and Australian business forums describe reaching a point where enquiries and open quotes outgrow what one person can remember. One custom-furniture maker described enquiries rising from roughly 10 or 15 a week to 35 or 40, arriving across several channels, with messages buried and follow-ups forgotten. A solo consultant described a lead spreadsheet that stopped working once it held about 150 leads. Others ask when to chase a quote after the prospect goes quiet, or whether to chase a client again for information after several attempts or proceed without it. A small team described website leads landing in a general inbox and waiting too long before anyone passed them to the right person.

Underneath, the failures are few:

• No single list. Enquiries live in email, text, social messages, voicemail and a notebook, and nobody can see them together.
• No next action. An enquiry or quote is "open" but nobody has written down what happens next, or when.
• No owner. Everyone assumes someone else replied.
• No ending. Dead items are never closed, so the live ones are hidden among them.

Speed matters for some businesses more than others. A former HVAC owner described returning calls in the evening and finding that about half the callers had already booked another firm.

flowchart TD
  E["Enquiries: email, text, social, calls"] --> I["Separate inboxes and notes"]
  I --> R["Owner replies when noticed"]
  R --> Q["Quote sent"]
  Q --> M["Follow-up kept in owner's memory"]
  M --> W{"Owner remembers to chase?"}
  W -->|"yes"| C["Chased, often late"]
  W -->|"no"| L["Lost without a reason recorded"]

The common current flow: state lives in several inboxes and one person's memory.

What existing tools already do

Ordinary software covers most of this. CRM systems (customer relationship management software, such as HubSpot or Pipedrive) are built around a pipeline of deals moving through stages (Pipedrive pipeline management). HubSpot's sales plans, for example, list pipelines, email sequences, routing of leads from forms, and reporting (HubSpot sales pricing and features). Job-management software for trades commonly tracks quotes alongside jobs. Shared inboxes let a team see who has answered what. Software still depends on the habit around it: HubSpot's own sales blog notes that manual logging is done inconsistently when teams are under quota pressure, and that follow-up speed varies when it depends on someone remembering (HubSpot blog).

Many owners asking about this in public forums are looking for exactly these tools, but the fields and the review matter more than the product. A tool helps once there is an agreed routine: what every item must contain, who owns it, and when the list is reviewed. The steps below set that routine up first, so it works in a spreadsheet or in whatever CRM you choose.

Where the current flow above ends in an item lost without a reason, the routine ends with every item decided. Seven stops run from listing the channels to measuring what the list shows, and three decisions, marked with flags, stay with a person: setting each follow-up date, closing each item with a reason, and the weekly review.

Step 1: List every channel enquiries arrive through

What to do. Write down every place an enquiry can arrive: each email address, phone line and voicemail, website form, social media inbox, marketplace or directory, and walk-ins. Note who checks each and how often.

Why. An unlisted channel cannot feed your list, and a channel nobody is named to check is where enquiries wait unseen.

Example. A kitchen fitter might list the main email, the website form (which emails a different address), a mobile used for texts and WhatsApp, Facebook and Instagram messages, and a trade directory's messages, and notice that nobody is responsible for the directory.

• Every channel listed
• A named person checks each one
• Rarely checked channels redirected or closed

Step 2: Create one list with a small number of fields

What to do. Make one list of open enquiries and quotes, in a spreadsheet or your CRM. Each item needs: who it is, what they want, the stage (new, replied, quote sent, waiting on them, won, lost), the next action, its date, and its owner.

Why. One list makes the open work visible, and the next action, date and owner turn a vague "open" into something someone will do on a known day. The list holds people's names and contact details, so keep only what you need to follow up, store it where only your team can see it, and follow the data-protection and marketing rules where you operate: chasing a quote someone asked for is different from adding them to a mailing list without their consent.

Example. "Homeowner, 12 Park Lane | fitted wardrobe, two bedrooms | quote sent | call to ask if she has questions | Thursday | office manager."

• One list, in one place
• Stages defined and few
• Every item has a next action, a date and an owner
• List kept private to the team, holding only what follow-up needs

Step 3: Get every new enquiry onto the list the same day

What to do. Decide how each channel's enquiries reach the list. At first that can be a person copying them over at set points in the day. Send each new enquiry a reply that tells them what happens next and when.

Why. An enquiry not on the list exists only for whoever saw it. A clear reply buys time and sets an expectation you can meet.

Example. At lunchtime and at the end of the day, the office manager checks every channel and adds new enquiries. Each gets a reply: "Thanks, we'll call you tomorrow morning to talk through what you need."

• Each channel's route onto the list defined
• Set times to sweep the channels
• Every new enquiry gets a reply naming the next step

Step 4: Set a follow-up routine for sent quotes

What to do. Decide a standard sequence after a quote is sent: for example, a check that it arrived, a call to answer questions, and a final message. Write a short template for each, and put the next step on the list with its date as soon as the quote goes out.

Why. Prospects often go quiet for ordinary reasons: the quote is waiting on a partner, a budget, or a decision they have not made. A planned sequence means the chase happens whether or not anyone remembers. A person sends each message, so it can respond to what the prospect said last, which a scheduled message cannot.

Example. Day of sending: "Quote sent; here is what happens if you go ahead." A few working days later: a call. If still quiet: "We're holding this price until the end of the month; let us know if you'd like to talk it through, or if you've decided to go another way."

• Standard follow-up sequence written
• Templates for each message
• Next follow-up added to the list when a quote is sent

Step 5: Close items with a reason

What to do. When an item ends, mark it won or lost and record why: chose a competitor, price, timing, no response after the full sequence, not something we do. For "not now" answers, set a future next action instead of closing.

Why. Closing dead items keeps the live ones visible. Reasons tell you, over time, whether you are losing on price, speed or fit.

Example. "Lost: went with a cheaper quote." "Not now: asked us to get back in touch in March," with a next action dated in March.

• Every ended item marked won or lost
• Reason recorded
• "Not now" items given a future date

Step 6: Review the list on a fixed day

What to do. Once a week, the owner and anyone who handles enquiries go through the list: anything overdue, anything without a next action, anything without an owner. Fix each one there and then.

Why. A list without a review becomes another inbox. The review is where the owner makes the judgement calls: whether to chase again, offer a concession, or let it go.

flowchart TD
  E["Enquiries from every listed channel"] --> L["One list: next action, date, owner"]
  L --> A["Reply naming the next step"]
  A --> Q["Quote sent; follow-up dated"]
  Q --> F["Owner of item sends follow-up from template"]
  F --> D{"Person decides: chase, concede, or close"}
  D -->|"chase"| F
  D -->|"close"| C["Won or lost, with reason"]
  D -->|"not now"| N["Future next action dated"]
  L --> W{"Weekly review: overdue or unowned items"}
  W --> L

The target flow. Diamonds are decisions made by people; the list and the routine carry the memory.

• Weekly review in the calendar
• Overdue, unowned and action-less items fixed in the review
• Judgement calls made by the owner, not by default

Step 7: Automate the routine you already follow

What to do. Once the routine has run by hand for a while, automate the parts that are pure copying and reminding: website forms that create list items, reminders when a next action is due, a report of overdue items before the weekly review. Use your CRM's built-in features first.

Why. Automating a routine that works saves effort; automating one that does not yet exist produces reminders nobody acts on.

Example. The website form now creates a CRM deal at stage "new". When a quote is marked sent, the CRM creates a follow-up task for its owner. On Monday morning the owner gets a list of overdue items.

• Routine has worked by hand first
• Copying and reminders automated with built-in features
• Messages to prospects still sent by a person

Step 8: Measure what the list tells you

What to do. Look at three things: how long new enquiries wait for a first reply, how many items are overdue at each review, and the reasons for lost work.

Why. These numbers show whether the system is working and where to act next; the number of follow-ups sent says much less. If replies are slow, the problem is the channels; if quotes are lost on price, it is not a follow-up problem at all.

• Time to first reply checked
• Overdue items counted at each review
• Lost reasons reviewed

Choosing how far to go

Approach	What it involves	Good fit when	Limits
By hand	A spreadsheet list, channel sweeps, templates, a weekly review	Up to a modest number of open items; one or two people	Depends on the sweep and review happening
Configure an existing tool	Stages, owners, tasks and reminders in a CRM or job-management system	The spreadsheet has grown unwieldy, or several people share the work	Software reminds; it does not decide or write the right reply
Connect tools	Forms and inboxes creating list items automatically; quote status triggering tasks	Enquiries are copied by hand from several channels	Each connection needs testing and an owner
Build custom	A system that reads incoming messages, drafts a list item and a suggested reply for a person to approve	Volume is high and channels are many, after the routine works	Most cost; drafts must be reviewed before anything reaches a customer

AR Labs offers this kind of discovery and design work to owner-run businesses; more about us is on the about page.