Lesson 8 of 15 · 6 min

Long estimate cycles in the pipeline

Track long roofing estimate cycles in the pipeline.

Read the lesson

Goal: Keep roofing deals alive through weeks of insurance waits without pestering the homeowner.

You need: Contacts → Deals, Pipeline stages in settings, and the Estimate Follow-Up Sales Sequence template.

Why this matters

A roof is not a same-day sale. After the inspection, the homeowner may wait for an adjuster, a claim decision, a second quote, or a spouse. Four to eight weeks is common. Some deals take months.

That long wait is where roofers lose deals. The estimate goes out. The follow-up ends after two weeks. Then nothing happens. When the claim is finally approved, the homeowner calls the roofer who stayed in touch.

The opposite mistake is just as bad. Some offices text the homeowner every few days. The homeowner is waiting on the insurance company, not the roofer. The texts feel like pressure, and the homeowner stops replying.

The answer is a pipeline that knows the difference. A deal waiting on insurance is not stalled. It is waiting. It needs a light, regular check-in from a person, not a sales sequence.

Size changes the setup:

  • Owner-operator. The owner sells and builds. A monthly task list keeps old deals from vanishing.
  • Fleet (Summit Roofing). Each estimator owns their deals. Saved filters show each person's waiting deals.
  • Multi-location. Use the same stage names everywhere, so reports compare.

A stage for waiting

The default pipeline stages are New, Qualified, Proposal, Negotiation, Won and Lost. Roofing needs one more: "Waiting on insurance."

In Proposal, the estimate is out and the follow-up sequence runs. In "Waiting on insurance," a claim or adjuster is pending. Messages only ask if there is news. In Negotiation, the claim is decided and a person agrees scope and price, then closes. At Won or Lost, the homeowner has decided and all follow-up stops.

Fig 1

Roofing pipeline with a waiting stage

  1. 1New and QualifiedLead in, inspection booked
  2. 2ProposalEstimate sent; the sequence runs
  3. 3Waiting on insuranceMessages only ask for news
  4. 4NegotiationClaim decided; a person closes
  5. 5Won or LostAll follow-up stops
Waiting gets its own stage, so it is not mistaken for stalled.

Two rules govern the waiting stage.

First, messages only ask if there is news. "Any word from your adjuster? We are ready when you are." They never discuss coverage, deductibles or what a policy pays. Those questions go to a person, always.

Fig 2

The one waiting-stage text

  1. noteDeal moved to Waiting on insurance
  2. Summit Roofing · 9:15 amHi Dana, any word from your adjuster? We are ready when you are. Just reply when you have news.
  3. Homeowner · 12:02 pmNot yet. Will my policy cover the whole roof?
  4. noteCoverage question: the estimator calls back. The text never answers it
The text asks only for news. A coverage question always goes to a person.

Second, the deal stays open. Day 30 of the follow-up is not a deadline. When the sequence ends, a person gets a monthly check-in task with a due date. The deal moves to Lost only when the homeowner says no.

Fig 3

When the sequence ends at day 30

  1. The Proposal sequence ends
  2. Did the homeowner say no?YesMove to Lost; record the reason in a custom fieldEnds hereNoKeep the deal open
  3. Is the claim decided?YesMove to Negotiation; a person closesNoMonthly check-in task with an owner and a date
  4. Check the Waiting on insurance filter every week
A deal moves to Lost only when the homeowner says no. Not when a sequence ends.

There is no date-field trigger and no wait-for-reply step in workflows. So the monthly check-in is a CRM task with a date. A person sets it, or the sequence's last step does.

Fig 4

Follow-up for a roof deal

  1. Day 1 to day 30Proposal sequence, with a stage check before each send
  2. Move to waitingOne news text and a 30-day task
  3. Every 30 daysEstimator check-in call; task date moved forward
  4. Claim decidedDeal moves to Negotiation
Automatic messages first, then a person on a regular date.

Build it in ServiceAgent

  1. Open Settings → Contacts & Pipeline → Pipeline stages. Add "Waiting on insurance" after Proposal.
  2. Open Workflows → Templates. Open the Estimate Follow-Up Sales Sequence.
  3. Before each send, add a Condition on the deal stage. Skip the send unless the stage is Proposal.
  4. Make the last step Create CRM Task. Set the Owner as the estimator, a due date 30 days out, and Priority MEDIUM.
  5. Build a second workflow: Event Trigger → Deal Updated. Add a Condition for "Waiting on insurance". Deal Updated fires on every edit. So add a second Condition: tags do not contain insurance-text-sent.
  6. In that workflow, send one short text that asks the homeowner to share news when they have it. Then add Update Contact with the tag insurance-text-sent.
  7. Then add Create CRM Task for a check-in call in 30 days.
  8. Open Contacts → Deals. Filter by Stage. Save the filter as "Waiting on insurance" in Saved Filters.
  9. Click Test on both workflows, then Publish.

Check in the client's account which event fires on a stage move: Deal Updated or Deal Status Changed. Use the one that fires.

Check it works: Move a test deal to "Waiting on insurance". Confirm one text and one task. Edit the deal again and confirm no second text goes out. Confirm the Proposal sequence skips its next send.

Worked example: Summit Roofing

Summit has 15 open roof deals. These are example inputs.

  • Average deal value: $12,000.
  • Open pipeline: 15 × $12,000 = $180,000.
  • 9 deals are in Proposal. 6 are waiting on insurance.

Before the change, deals with no reply after day 30 were marked Lost. Say 1 in 3 waiting deals went quiet that way. That is 6 ÷ 3 = 2 deals, or 2 × $12,000 = $24,000 marked lost while still alive.

Fig 5Example numbers

Summit's pipeline, example

$180KOpen pipeline: 15 deals at $12,000 each
6Waiting on insurance
$24K$24,000 marked lost too early before the change
Two quiet deals were worth $24,000 in this example.

After the change, those 2 deals keep a monthly task. If the estimator wins even one, that is $12,000.

The time cost is small. 6 waiting deals × 1 call a month × 5 minutes = 30 minutes a month for the estimator.

The credit cost is smaller. Each move to the waiting stage sends 1 text (2 credits) and runs once (1 credit). 6 deals use 18 credits.

What the estimator says on the check-in

The monthly call is short. It has three parts. Ask if there is news from the adjuster. Offer one useful thing, such as help reading the scope the adjuster sent. Set the next check-in date.

The estimator logs the call on the contact's Activity tab. Then they move the task date forward 30 days, so the next call is already set. If the claim is decided, the deal moves to Negotiation. If the homeowner chose another roofer, the deal moves to Lost. Record the reason in a custom field, because Lost has no reason field.

Reading the pipeline each week

Once a week, open the "Waiting on insurance" saved filter. Look for deals with no task, or a task more than a week overdue. Those are the deals that will be lost to silence.

Then open Contacts → Reports → Win Rate. Watch it month by month, and share it in the monthly report. A rising win rate on storm deals shows the waiting stage is working.

Common mistakes

  • Marking waiting deals lost after day 30. Fix: keep them open. Add a monthly check-in task with a person and a date.
  • Sales texts during an insurance wait. Fix: in the waiting stage, messages only ask if there is news.
  • The AI answering coverage questions. Fix: coverage, claims and deductibles always go to a person.
  • Restarting the whole sequence. Fix: one sequence per deal. After it ends, tasks take over.
  • No owner on the task. Fix: every task names one estimator and one due date.

Do this now

Add the waiting stage to a practice or client pipeline. Edit the follow-up template with a stage Condition before each send. Then build the waiting-stage workflow and test it with a dummy deal.

Practice the conversation

  1. Owner Half my estimates just sit there. The homeowner says they are waiting on insurance.
  2. Operator Then we give that its own stage. Waiting is not the same as stalled.
  3. Owner Do we keep texting them?
  4. Operator One text when the deal moves there. It asks them to share news when they have it.
  5. Owner And then?
  6. Operator Your estimator gets a check-in call task every month, with a date.
  7. Owner What if they ask whether insurance covers the whole roof?
  8. Operator A person answers that. The texts never talk about coverage.
  9. Owner When do we give up?
  10. Operator When the homeowner says no. Not when a sequence ends.

Quick check

  1. A roofing deal is in the waiting on insurance stage. The homeowner texts: "Will my policy cover the whole roof?" What should happen?
    • The AI explains what most policies cover
    • A person takes the question
    • The day 30 message goes out early
    • The deal is marked lost until the adjuster calls
  2. A roof deal passed day 30 of follow-up. The homeowner still waits on the adjuster. What do you do?
    • Mark it lost, because the sequence ended
    • Restart the day 1 to day 30 messages
    • Text the homeowner every week until they decide
    • Keep it open, with a monthly check-in task and a date
  3. A roofer has 12 deals in the waiting stage. Each gets a 5-minute check-in call a month. How much estimator time is that a month?
    • 12 minutes
    • 30 minutes
    • 60 minutes
    • 120 minutes

ServiceAgent UniversityLearn to run a service business on autopilot. Free courses, Blueprints and certification for Service Operators.

Learn

Get certified

Community