The inspection went fine. You walked the basement, pointed out where water was coming in along the east wall, wrote up two options, emailed the proposal, and told the homeowner you'd check back in a week. Then week one passed. Week two passed. Now it's day nineteen and you're staring at your pipeline wondering whether they went with another contractor, whether the email landed in spam, or whether they're waiting on a bonus check. You have no idea which, and you have no clean way to find out without feeling like you're pestering them.
That gap between "estimate delivered" and "yes or no" is where a waterproofing opportunity can stall. Sometimes the customer chose another bid. Sometimes the project moved. But sometimes nobody owned the next step and nobody put a date on it, so neither side knew what would happen next.
What the system is
An estimate follow-up system is a written, repeatable process that takes a basement-waterproofing proposal from the moment you hand it over to a recorded decision, using a fixed sequence of contacts, a plain-language scope sheet the customer can actually compare against other bids, one named owner for every next action, and a loss-reason log you review monthly. It is not a script for pressuring people. It is a schedule of helpful, dated touches that makes it easy for a homeowner to say yes, easy to say no, and easy for you to learn from either answer.
A waterproofing customer may be comparing scopes, talking with another decision-maker, or waiting for a financing or scheduling answer. A follow-up system records the actual constraint instead of treating every silence as rejection.
The proposal handoff
Most follow-up problems start at handoff, not at touch three. If the proposal goes out as a nine-page PDF with no conversation attached, the customer files it mentally under "later" and you have nothing to anchor a follow-up to.
Do the handoff live whenever you can, by phone or in person, even if you email the document afterward. During that conversation, cover four things and nothing else:
- What you observed, in one or two sentences, separated from what the customer reported. "You reported water after heavy rain on the garage side. During the visit I observed the downspout discharge location shown in these photos; the proposal states exactly which condition our scope addresses."
- What the proposal includes, read off the scope sheet, not the contract boilerplate.
- What happens next, with a date. "I'll call you Thursday the 14th to answer questions. If you need more time, that's fine, just tell me and I'll set a date that works."
- What you did not find, if relevant. If the inspection didn't turn up a condition the customer is worried about, say so plainly and point them to the right professional rather than guessing.
Keep your language accurate and bounded: separate what the customer reported from what you observed, describe what your proposed work addresses, and state what it does not address. If moisture concerns come up outside your scope, the EPA's mold and moisture resources are a neutral starting reference rather than a reason to make promises about what may be behind a wall. Don't diagnose from a follow-up call.
End the handoff by confirming the next contact date out loud and writing it down before you hang up or leave. A follow-up sequence without a confirmed first date is just a wish.
The scope comparison sheet
Homeowners comparing waterproofing bids are usually comparing prices on work that isn't the same work. One bid includes exterior excavation, one proposes interior drain tile, one adds a battery backup, and none of them explain the difference in language a civilian can parse. The customer defaults to price, or freezes entirely.
A scope comparison sheet fixes this without criticizing competitors. It's a one-page document, built from your own proposal, that lists the line items in plain language with a "why it's here" note for each. You are not asking the customer to rank other bids. You are giving them a checklist they can carry to any bid and ask any contractor, including you, the same questions.
A simple format:
| Line item | What it does, in plain words | Questions to ask any bidder |
|---|---|---|
| Perimeter drain system | Catches water entering at the floor-wall joint and carries it to the sump | Where does the pipe sit relative to the footing? What is the pitch? |
| Sump pump, primary | Moves collected water out and away from the house | What discharge distance? Where does the water end up? |
| Battery backup pump | Keeps water moving during a power outage | How long does the battery run? Who services it? |
| Downspout extensions | Carries roof water farther from the foundation so it doesn't recycle back in | How many feet? Any grading work included? |
| Wall treatment | Handles water that comes through the wall itself, if that's part of your finding | What exactly was observed on my walls? What does this address and not address? |
Notice the third column. It hands the customer questions instead of conclusions. That does two things: it positions you as the contractor teaching them how to buy, and it surfaces real differences between bids early, before a competitor's low number wins on confusion.
Keep the sheet to one page. If it runs long, you've drifted back into proposal language, which is the thing the customer already couldn't read.
Ownership and dated next actions
Every open estimate needs three fields filled in the day it goes out, and they need to live somewhere you actually look — your CRM, a spreadsheet, or a whiteboard, as long as it's one place:
- Owner: one named person, not "the office." If you're a two-person shop, it's a name.
- Next action: a verb and an object. "Call re: scope questions," not "follow up."
- Next action date: a calendar date the customer has heard about, when possible.
Copyable field list for each open estimate:
Estimate ID: ______
Customer / address: ______
Date delivered: ______
Delivery method: in person / phone / email only
Scope sheet sent: Y / N
Owner: ______
Next action: ______
Next action date: ______
Customer's stated
timeline or constraint: ______
Decision date or
loss reason: ______The constraint field earns its keep. If the customer says "we're waiting on our tax refund" or "my husband travels until the 20th," write it down. Your follow-up schedule should bend around real constraints, and referencing them later ("you'd mentioned your husband was back on the 20th — is this a good week to revisit?") is the difference between a follow-up and an interruption.
Review the open-estimate list every Monday. Anything with no next action date gets one in that meeting or it gets closed out. An estimate with no date is a leak in the pipeline you can't see.
The five-touch sequence
The example below uses five touches across roughly four to six weeks. That is a starting structure, not a claim about the right decision window for every project. Adjust the number, spacing, and channel to what the customer requested and to the communication rules that apply to your business. Each scheduled touch should have a distinct purpose.
| Touch | Timing | Channel | Purpose |
|---|---|---|---|
| 1 | 2–3 days after handoff | Send the scope comparison sheet and a written recap of what you found. Low effort for them to read, easy to forward to a spouse. | |
| 2 | Day 6–8 | Phone | Answer questions. Ask directly: "What questions do you have about the proposal?" Silence on this call is information. |
| 3 | Day 13–15 | Phone or text | Offer one useful thing: a truthful scheduling update, a reference customer who agreed to be contacted, or the answer to a question raised at the inspection. |
| 4 | Day 20–24 | Make it easy to close the loop either way: "If you've decided to go another direction, no problem — just reply and let me know so I can stop checking in." | |
| 5 | Day 30–40 | Phone | Final check-in. If no answer and no response, leave one message, then move the estimate to the loss-reason log as "no response" and stop. |
Two rules keep this from feeling like pressure. First, every touch has to give something — information, an answer, or a truthful scheduling fact — not just ask for an answer. Second, the later touch explicitly offers an exit. A clear "no" lets you close the record cleanly instead of keeping an indefinite maybe in the pipeline.
If a customer gives you a shorter decision window, compress the spacing rather than adding more touches. The sequence is a planning example, not an industry cadence; use the customer's requested timeline and your own communication policy.
Handling silence
Silence has causes, and each one wants a different response. Before you assume disinterest, work the list:
- Wrong contact info. The email bounced or the number on the estimate form was a landline nobody answers. Check this before touch two, not after touch five.
- Decision partner missing. The person you met with isn't the only decision-maker. Touch one's email recap exists partly so it can be forwarded. Ask at handoff: "Who else should see this?"
- Stated constraint still running. If they told you they were waiting on money or travel, silence during that window is expected. Honor it and resume after.
- They already chose someone and don't want an awkward call. This is why touch four offers the exit in writing. Written exits get replies that phone calls don't.
- Genuine interest, stalled project. The scope sheet and the recorded constraint give you a useful place to resume if the customer asks to revisit the work.
When silence runs through the final scheduled touch, stop active contact. Move the record to a dormant list only if the customer consented to future contact, and give it a company-chosen re-check date or event. One short, relevant re-check is different from leaving the person in an endless sales sequence.
Recording loss reasons
Every estimate that ends — won or lost — gets a decision date and, if lost, a reason from a short fixed list. Free-text loss reasons are useless at review time because everyone writes something different. Use a closed list:
- Price — chose a lower bid for comparable scope
- Scope mismatch — wanted work you don't offer or a different approach
- Timing — deferred the project entirely
- No response — silence through touch five
- Trust or fit — went with a referral or a name they knew
- Other — one line required, reviewed monthly
Review the log monthly. Count each reason and look for the one that moves. "Price" clustering might mean your proposals bury the value of items customers don't understand — which is a scope-sheet problem, not a pricing problem. "No response" clustering usually means handoffs are happening by email only, with no live conversation and no confirmed next date. "Scope mismatch" clustering tells you which jobs to stop estimating, which saves you drive time you'll never bill for.
If you want to connect this to the money side, the Water Job Margin Calculator helps you check whether the jobs you are winning actually carry the margin you estimated. A follow-up system that wins the wrong jobs at the wrong price is just a faster route to thin margins.
A worked example
Here's the system on one job. All numbers are examples, not benchmarks.
Job: Estimate #0417, the Alvarez house. Inspection found water at the floor-wall joint on the north wall after heavy rain, plus a downspout discharging right against the foundation. Two options proposed: interior perimeter system with battery backup ($6,800 example price) or the same system plus exterior grading and downspout work ($8,100 example price). Scope comparison sheet prepared for the interior option.
Handoff: Delivered in person Saturday the 2nd. Mrs. Alvarez said she and her husband would talk it over; he works nights, so evenings were flagged as the contact window. Next action: call Tuesday the 5th, evening. Owner: you.
Touch 1, day 3: Email with the scope sheet and a three-sentence recap. Confirmed receipt — no bounce.
Touch 2, day 6: Evening call. Mr. Alvarez answered. One real question: whether the battery backup was necessary given their neighborhood loses power "maybe twice a year." You explained what it covers and what removal would change about the proposal. No decision. Next action: call the 12th.
Touch 3, day 13: Call. Mrs. Alvarez said they were waiting to hear back on a home equity line. Constraint recorded. You offered: "When you hear back, call me and I'll hold a spot on the calendar for the week after." Next action: call the 19th.
Touch 4, day 21: No answer on the 19th, so the email went out with the exit line. Reply came the next morning: approved for the HELOC, ready to book the interior option.
Outcome: Won, $6,800, booked for the 29th. Total follow-up effort: two answered calls, one email thread, three calendar entries. Total elapsed time from estimate to signature: 20 days.
Now the counter-example, same system: Estimate #0419, sent by email only, no live handoff, no confirmed date. Touch 1 bounced — the customer had typed their email wrong on the intake form and nobody checked. Touches 2 through 5 hit a phone number that rang to voicemail. Closed at day 40 as "no response." The loss-reason review flagged two no-response closes in one month, both from email-only handoffs, and the intake form got a read-back step added. That's the system paying for itself on the jobs you don't win.
Questions owners ask
How many touches is too many?
There is no universal number. Stop when the customer asks, when your disclosed sequence ends, or when you no longer have a relevant reason to contact them. If you can't name what a touch gives the customer — an answer, a document, or a truthful scheduling fact — cut it.
Should I text or call?
Match the channel the customer asked you to use, and follow applicable consent and communication rules. If all their communication has been email, stay in email unless they request something else. When you leave a message, give a specific reason and a clear way to close the loop.
Can I ask for a review when a job closes?
Yes, but keep it honest and transparent. The FTC's guidance for marketers on soliciting and paying for online reviews makes the operating principle clear: don't condition anything on the review being positive, don't buy reviews, and don't hide incentives. Ask every finished customer the same way, and let the reviews say what they say.
What if the customer asks about mold during follow-up?
Answer with what you observed and nothing more. Point them to accurate, neutral information — the EPA's mold and moisture pages are a solid reference — and to qualified professionals for anything that needs testing or diagnosis. Promising outcomes about conditions you can't see from where you stand is how good contractors end up in bad disputes.
Sources and operating boundaries
Primary sources referenced in this article:
- FTC guide to soliciting and paying for online reviews — used here for the principle that review requests and any incentives must be handled honestly and transparently. This article does not state legal conclusions; for questions about your specific review practices, consult qualified counsel.
- U.S. EPA mold and moisture resources — used to reinforce that moisture and mold concerns deserve accurate, bounded communication rather than remote promises or diagnosis.
This article describes a sales-process worksheet for owner-operated contractors. It does not replace a structural engineer's assessment, a licensed contractor's site-specific diagnosis of foundations, drainage, or water entry, professional mold assessment or remediation guidance, or advice from your accountant or attorney on contracts, pricing, or review practices. Nothing here constitutes an emergency service; if a customer reports active water intrusion or a safety concern, direct them to qualified professionals.
If you want help assembling the sequence itself, the Estimate Follow-Up Builder walks through the touch structure step by step, and the local marketing foundation checklist covers the upstream work of getting estimate requests in the door. The Growth Pack follow-up plan lays out the full sequence in one place for teams that want a starting draft to edit rather than a blank page.