Should a quote ever go out without me looking at it?

Not while it carries a price. A quote is a priced offer with your name on it, and the cost of one wrong number is far higher than the two minutes it takes to approve a draft. What you can send unattended is everything around it: the acknowledgement that you have the job details, the appointment confirmation, and the follow-up messages once you have approved the wording once.

Do I need job management software before any of this works?

No, but you need one place where job details land. That can be a job management tool, a shared form, or a structured note you fill in before you leave site. The workflow needs to read something consistent. If the details live in three different places and half of them are in your head, fix that first, because no automation can assemble a quote out of a memory.

How many times should I chase a quote?

Twice, then stop and mark it. Day three and day seven covers most of the useful window, and a third and fourth message costs goodwill without adding much. If both go unanswered, a short call is worth more than another email, and knowing the quote is dead is worth more than pretending it is still live.

Quoting on the spot: automating quotes for trade jobs

Why does quoting cost more than the time it takes?

Because the expensive part is the delay, not the typing. A quote written on Thursday night for a job you looked at on Tuesday morning lands after the customer has already had two others and started forming an opinion about who is organised.

There is a second cost hiding behind the first. A quote you wrote after eleven at night is a quote you will not chase, because chasing it means going back through a pile you would rather not think about. So the work that took forty minutes to price sits in an inbox and quietly expires.

Most trades assume a quote that goes nowhere lost on price. Some do. A large share of them lost to nothing at all: the customer got busy, put it aside, and rang whoever followed up. That is the cheapest work in the business to win back, because you have already done the site visit and the pricing.

What part of a quote can a machine actually write?

Everything except the number and the judgement behind it. The line worth holding is that a workflow assembles and presents, and a person decides.

Safe to automate:

The header details. Customer, site address, contact, job reference, date, validity period. All of it already exists somewhere the moment you book the visit.
The scope description. Drafted from the notes, photos or voice memo you recorded on site, written up in your usual language rather than a template's.
Standard inclusions and exclusions. The ones you write out by hand every time for that job type: what is covered, what is not, access assumptions, what happens if something is found behind a wall.
Terms. Deposit, payment terms, warranty wording, how long the price holds.
Delivery and filing. Send it, save a copy against the job, record the date it went, and set the follow-up clock running.

Stays with you:

The price, always.
The risk read: the job that looks routine and is not, the customer who is going to be difficult, the site that will cost you a day in access.
Anything unusual enough that you would want to explain it on the phone.

The useful mental test is whether the step needs your professional read or just your presence. Assembly needs presence. Pricing needs judgement, and judgement does not get delegated to a tool because it is the thing you are actually being paid for.

What does the follow-up actually look like?

Short, specific and approved by you. The message that works asks a question the customer can answer in one line, rather than announcing that you are checking in.

The pattern that fits a small team:

Same day. The quote goes out, with the follow-ups already scheduled at the moment it sends rather than at the moment somebody remembers.
Day three. A drafted message sits in your approvals list. You read it, change a word if you want, send. It asks whether they got it and whether anything in the scope needs adjusting.
Day seven. A second draft, shorter, offering a start window rather than repeating the price. A date does more work than a discount.
Then stop. Mark the quote dead or ring them. Two messages is polite, four is noise.
Acceptance closes the loop. Once they say yes, the job gets created and the invoicing sequence takes over, which is a separate workflow with its own rules.

Keep every customer-facing message on draft-and-approve until the drafts have been right for a month. It is slower to build than fully automatic sending and much harder to embarrass yourself with, and it is worth knowing how the thing behaves when it breaks before anything sends on your behalf.

How do you tell whether it is worth building?

Run the count before you spend anything. Four numbers, all of which you can pull out of your job file or your sent items in an evening.

Quotes sent last month. The raw count.
How many got a single follow-up. Be honest, and count only ones where you actually sent something.
Your win rate on each group. Chased versus not chased. If you have never separated them, that is the number the exercise exists to produce.
Average job value. Total invoiced over a recent period divided by jobs. Use the median if one large job would distort it.

The gap between those two win rates, multiplied by the quotes you never chased, multiplied by average job value, is what the follow-up alone is worth in a year. Do it on paper with your own figures. Nobody can quote you an industry average that means anything for your business, and you should be wary of anyone who tries.

If the number is small, you have just saved yourself a build. If it is large, you now know what you are allowed to spend fixing it, which is the only sensible way to price any of this. The same arithmetic applies to the calls you never got to answer, and the two leaks usually turn out to be the same leak at different stages.

Where does this go wrong?

Four ways, in roughly the order they happen.

Pricing gets automated. Someone builds a rate card into the workflow so quotes can send themselves. It works until the job that needed a second look goes out at the standard rate, and one of those wipes out a year of saved evenings.

The details were never captured. The workflow can only assemble what it can read. If the measurements are on a photo of a scrap of paper and the access notes are in your head, you have an intake problem rather than a quoting problem, and the intake is what to fix first.

The follow-ups keep going after the customer said no. Nothing damages a small business faster than an automated chase for a job that was declined last Tuesday. Whatever you build, make sure a reply, a phone call or a status change stops the sequence.

It turns into a systems project. If a quote for this starts with replacing your job management tool, ask exactly why the tools you already pay for cannot be connected. The answer is sometimes legitimate. It is more often a sale. The full picture of where a trade business leaks time is in the wider list, and quoting is usually second on it rather than first.

What to do next

Pick last month's quotes out of your sent items and split them into chased and unchased. Count the wins in each pile. That single number tells you whether the chase is worth automating, and it takes about twenty minutes.

Then change one thing this week: capture the job details in the same structured place every time before you leave site. Everything else in this article depends on that one habit, and it is free. Once it holds for a month, the assembly and the follow-up are a small build rather than a project, and it is where Shift would start on a quoting problem before touching anything else. If you would rather see the whole process mapped and priced before choosing, that is what a Flow Map is for.