Quote follow-up: buy a tool, or build it?

What actually happens

Nobody decided to let this happen.

The pattern is always the same. The quote gets sent on Tuesday. The owner means to check in on Friday. Friday is a fire. The following Tuesday it feels too late to chase without seeming desperate, so it does not get chased, and the quote quietly becomes a no.

Nobody decided to lose that job. There was no moment where somebody weighed it up and let it go. It fell through a gap in a process that was never designed, which is a different problem from being bad at sales and it has a different fix.

Work out your own number

What is this costing you?

Before deciding anything, work out your own number. Do not take mine, and do not take a vendor's.

1
Count the quotes you sent last month.
2
Count how many you followed up more than once. Be honest; the gap between those two numbers is the workflow.
3
Take your average job value and your rough close rate on quotes you do chase properly.

One extra job a month from quotes you already sent, at your own average value, is the entire budget for this conversation. If that number turns out to be small, this is not your first build and you should stop reading here — that is a real outcome and it is the one the Fit Check is most likely to give you.

The honest version

Buy a tool, or build it?

Buy the tool if

Your quotes all look broadly alike and come out of one system.
You are happy for the follow-up to be a generic 'just checking in' on a fixed timer.
You have nowhere else the follow-up needs to write to — no scheduling, no job record, no ops handoff.
You would rather pay a monthly fee than own anything.

Build it if

The quote lives in one place, the customer history in another, and the job record in a third, and the follow-up needs to know all three.
A generic chase would embarrass you, because what to say depends on what was quoted.
The follow-up should stop automatically when something else happens — the customer calls, the job gets booked, the work is cancelled — and no off-the-shelf timer knows about those events.
You have already bought a tool for this, and it is not being used, which usually means the tool asked your team to change how they work rather than fitting how they already work.

The first list is common and it is a genuinely good outcome. If you land there, buy the tool, spend an afternoon setting it up, and keep your money. I would rather tell you that than sell you a build you did not need — and if you want a second opinion on which list you are in, that is a free 20-minute call, not a project.

If it is the second one

What a build actually has to do

Part 1

It knows what was quoted

The chase references the actual job, not a generic nudge. That is the difference between a follow-up that reads as attentive and one that reads as automated, and it is mostly a plumbing problem — getting the quote detail to the place that writes the message.

Part 2

It stops on its own

When the customer replies, books, or cancels, the sequence ends. Follow-up that keeps chasing after a yes is worse than no follow-up, and it is the single most common way a bought tool damages a relationship.

Part 3

It drafts, you send — at first

The sensible starting setting. You read each one for a couple of weeks, you see the pattern, and then you decide whether it graduates to sending on its own. That decision is yours and it is per-workflow.

When to leave this alone

Do not build this yet if…

If you send a handful of quotes a month, or you already chase every single one properly, leave this alone. Automating a workflow you are already good at buys you nothing and gives you a system to maintain.

The part most people worry about

Nothing gets authority by accident.

Every workflow I build has a setting for how much it is allowed to do on its own, and you pick it per workflow rather than once for the whole business.

Setting one

It drafts, you send

The system does the assembling and the remembering. A person reads it and presses the button. Where most work should start, and where a lot of it should stay.

Setting two

It runs, you get told

It acts on the rules you agreed and reports what it did. Suitable once a workflow has proven itself and the cost of a wrong move is small.

Setting three

It runs, you can stop it

Fully hands-off with a switch you own and a record of every action. Appropriate for high-volume, low-judgement work, and not much else.

Straight answers

Questions this one always raises

Will this make my business sound like a robot?

It will if it is built badly, and that is the main risk with this particular workflow. The guard is that the chase carries real detail from the actual quote and stops the moment the customer does anything. If a build cannot clear that bar with your systems, I will tell you, because a follow-up that feels automated costs you more than the job it was chasing.

We use a CRM already. Does it not do this?

Often partly. Most CRMs will send a message on a timer; far fewer will stop cleanly on the events that matter or reference what was actually quoted. Worth checking properly before spending anything: if yours does it, use it. If it half-does it, the honest question is whether the gap is worth closing, and that is what the Map answers.

Where this comes up

Most common in these areas

Not a rule, just where I see it most. I work across south and east King County.

Auburn, WA Renton, WA Issaquah, WA Other workflows

Start at the bottom of the staircase

Sixty seconds, and you will know whether this is worth another minute.

No account, no calendar, no waiting for a reply. Run the Fit Check and you get the read on your own screen. If it says the work is worth mapping, the next step is a free 20-minute call. If it says leave it alone, you have lost a minute and I have lost a customer I should not have had.

Run the 60-second Fit Check Skip it, book the 20-minute call

Or just write to me: bryan@perseidechocreations.com · or call 425-243-3473