EN | ES
Playbook · Quote follow-up

AI Quote Follow-Up Automation: A Playbook for Getting Priced Jobs Off the Fence

Nexus AgentWorks · August 26, 2026 · Also available in Español

You already paid for this job once. You drove there, walked the property, took measurements, checked material prices, and wrote the number down. Then you emailed the estimate — and heard nothing. Not a no, which at least closes a file, but silence: the single most common fate of a priced job in the trades and local services. This playbook covers how an AI agent takes over estimate and quote follow-up deterministically — answering questions, booking decision calls, and working a fixed reminder ladder — with the guardrails that make it safe to point automation at revenue you have not won yet.

A framing note before anything else: this is deliberately not another speed-to-lead topic. The moment described here happens after the customer contacted you, asked for a price, and received one. Nobody is chasing strangers. Every automated touch in this playbook is a response to a request the customer initiated — which matters both ethically and legally.

What this playbook covers

Why sent quotes die quietly

The pattern repeats across roofing, HVAC, painting, landscaping, plumbing, electrical, cleaning, fencing, and every other business that prices work before winning it. Customer asks for a quote. You produce one within days — sometimes hours of unpaid site time. The email goes out, life resumes, and the estimate sits. Third-party sales research routinely cited in the industry puts an average of roughly five follow-ups behind a closed sale (The Brevet Group), while separate widely quoted survey data says around four in ten salespeople give up after a single follow-up attempt (Marketing Donut). Whether or not either figure describes your market exactly, the gap they describe is familiar to anyone who has worked a quote board: buyers need several reminders, most sellers send zero or one.

The money side is just as well documented as third-party reporting. Harvard's Joint Center for Housing Studies (JCHS LIRA) projected U.S. home improvement and repair spending at roughly $518 billion for 2026 — the demand exists. And benchmark figures reported from HubSpot sales data put quote-to-job win rates dramatically higher for followed-up estimates than for untouched ones (figures reported via US Tech Automations' industry roundups). None of these are our numbers; we cite them to establish that the leak is real and measured by others. The pipeline arithmetic for an individual shop is simpler still: a dozen open estimates at typical job values, times whatever fraction would sign with one more professional touch, is usually five figures of sitting inventory. Model it for your own ticket sizes — treat any single result as a Simulated estimate until your own quote board confirms it.

Why this is different from lead-response speed

Much of the sales-automation content aimed at service businesses is about the first minutes: contact someone who just raised their hand anywhere on the internet before a competitor does. Estimate follow-up lives in a completely different regime:

What quote follow-up automation actually is

Estimate follow-up automation means: when a quote leaves your system, a defined sequence begins, runs on a clock instead of on memory, and ends at a defined point. That is the whole idea. The implementation detail that separates a useful agent from a nagging autoresponder is what happens between the scheduled touches — because customers reply, and their replies are not all the same thing.

In practice, replies to a sent quote fall into a small number of classes:

An agent earns its keep precisely where those classes get different treatment. Scheduling and clarification are mechanical — answer from documented scope notes, offer real calendar slots, book the crew window. Promised timing pauses the ladder until the promised date passes, exactly like the promise-handling logic in our document collection playbook. Comparison shopping, negotiation, and scope changes go to a human the same day, because repricing work is judgment, not syntax. In our planning models we assume the majority of quote replies are scheduling or clarification rather than objection — plausible, since a homeowner who was never interested rarely writes at all — but treat that split as a Simulated estimate and measure your own reply mix during a pilot.

The follow-up ladder, concretely

Deterministic means the model never decides when to follow up; a versioned config does. Day offsets below are defaults, tuned per trade and per estimate value:

Channel order follows customer preference recorded at intake: SMS-first for most homeowners, email for commercial facilities contacts. In our planning models, structured multi-touch ladders meaningfully reduce median days-to-decision versus unstructured manual follow-up — directionally supported by the third-party research above, but treat any specific magnitude as a Simulated estimate until your own pilot produces a baseline.

Guardrails in code, not in prompts

These are prospects who asked you for a price once — not subscribers to a drip list. The guardrail set reflects that relationship:

How it varies by trade

The ladder is the same; what changes is cadence length, ticket size sensitivity, and where the human line sits:

A worked week (simulated example)

Mechanics end-to-end for a hypothetical residential painting company mid-season. All quantities are illustrative patterns, not measured results:

The operating claim worth making here is modest: an owner who currently follows up inconsistently gains consistency, and consistency is what the cited research rewards. How many additional jobs that converts to per month depends on ticket size, seasonality, and how disciplined follow-up already was — we'd model it together in a pilot rather than promise it in a paragraph. Treat every magnitude above as a Simulated estimate until measured on your own quote board.

Measuring whether it works

The whole point of a deterministic ladder is that its output is measurable. Track four numbers, all derivable from the audit log your system already keeps:

A caution about before/after comparisons: seasonality confounds everything in trades. A spring pilot against winter quotes will flatter any intervention. Compare against the same season last year, or run geography-staggered rollouts if you have the volume for it.

Honest boundaries: where the cheap tool wins

Field-service platforms already ship native estimate follow-ups — Jobber, Housecall Pro, ServiceTitan, and similar tools can fire a couple of timed reminders off an estimate status. If you send a handful of quotes monthly, single-cadence reminders are probably sufficient, and layering an agent on top is over-engineering; we mean that sincerely. The step up to a conversational agent makes sense when volume or nuance breaks the template: enough quotes that replies arrive daily, reply types mixed enough that canned responses misfire, coverage hours wide enough (evenings, weekends) that the office misses them systematically, or lead qualification upstream (missed-call recovery, intake qualification) already feeding people into a quote board nobody has time to work. Map your situation row-by-row in the service fit finder if unsure.

A fit checklist

What this looks like in practice

We deploy this as our Quote Follow-Up configuration spanning the email/inbox agent (reply classification, ladder execution, tone gate) and, where shops want it, a voice layer that answers return calls about quotes after hours and books decision conversations into the calendar — mechanics shared with our scheduling playbook. In a simulated 14-day dry run against pilot fixture data — labeled simulated estimate, not results — the configuration classified quote replies, paused promised-timing ladders, routed negotiation attempts to humans, and booked qualified callbacks without improvising pricing. Pricing context lives in our cost guide; the money math trades against your own average ticket.

For adjacent money-leak playbooks see invoice follow-up and inbox triage: invoice follow-up playbook · shared inbox playbook. For the wider picture, start the complete AI agents guide.

Frequently asked questions

Will automated follow-ups annoy my quotes?

Four well-spaced, substantive touches that reference the actual scope read as competence, not spam — very different from daily "just checking in" blasts. The second (widely cited) part of the Marketing Donut statistic works in the customer's favor here: most competitors stopped after one message, so a professional structured cadence stands out gently. In planning assumptions most engaged quotes respond somewhere in the middle of the ladder rather than at the final touch (Simulated estimate; verify with your own cadence data). And any stop signal suppresses the sequence instantly.

Is this different from the saturated "speed to lead" stuff?

Yes, structurally. Speed-to-lead races to contact someone who just raised a hand anywhere. Estimate follow-up responds to someone who asked you for a price and received one — the relationship, expectation-setting, and consent posture are entirely different, and so is the automation problem: fewer unknowns, longer timelines, and much larger tickets. We cover speed-of-response elsewhere; this post is deliberately about the month afterward.

What software does this work with?

Common field-service setups — Jobber, Housecall Pro, ServiceTitan, Workiz and comparable FSMs — plus CRM pipelines and standalone proposal tools with status fields or scheduled exports. Minimum requirement: the agent must be able to read estimate status and contact details, and write back logs. It never alters the quote document itself.

Could it accidentally promise something wrong?

The failure mode is designed out structurally: the agent only answers from documented scope notes attached to that quote, quotes no numbers, negotiates nothing, and routes anything ambiguous to a human the same day. A question it cannot answer factually gets "let me have [owner] confirm that today," not a guess. Escalations carry the full thread so the human answers with context.

Does sending these follow-ups create compliance risk?

The posture is conservative by construction: every message responds to the customer's own quote request, includes sender identification, honors stop requests absolutely, respects quiet hours, and uses carriers-compliant SMS registration where applicable. Because the sequence is triggered by the customer's transactional request rather than marketing intent, and carries none of the urgency and discount language that trips spam filters, deliverability and regulatory exposure stay modest. This is general information, not legal advice; confirm specifics for your jurisdiction.

Text, email, or phone?

All three exist in the architecture but the default is SMS-first for residential customers and email-first for commercial contacts, with voice reserved for: inbound return calls about a quote, decision-call booking, and after-hours coverage. Blasting automated calls at prospects who asked for an emailed price would misread the relationship and we don't configure it that way. Channel preference recorded at intake governs.

Can it chase homeowner-insurance work differently?

Insurance-adjacent jobs (storm damage, water mitigation) add parties: adjusters, documentation requirements, deductible questions. The agent can track which documentation is outstanding — feeding the same mechanics as our document collection playbook — but deductible explanations and any coverage interpretation route to humans immediately. In planning assumptions insurance-involved quotes need roughly double the decision time of retail ones (Simulated estimate); tune ladders accordingly.

What does something like this cost?

We start every vertical with a fixed-price pilot rather than an air-drawn quote — current tiers on the pricing page, background math in the cost guide. For rough internal planning only: a pilot pays for itself quickly if consistent follow-up recovers even one or two mid-sized jobs per month, since single traded-job margins dwarf software pricing (Simulated estimate; the honest calculation depends on your ticket sizes and current follow-through discipline). FAQ-level answers live in the main FAQ.

Start small, measure honestly

Pick one trade or service line, run the ladder on all new quotes for two weeks with every escalation copied to you, and track three numbers daily: reply rate by touch, median days-to-decision, and quotes moved to a human conversation. Compare against the prior quarter's quote board. When the pattern holds, extend to other services one at a time — and let the files that silently expire keep doing so quietly, not expensively. Ready to see it live? Walk the workflow on the live demo or see how a pilot starts; if it fits, start here →.