Key takeaways
- The first three automations for a paving company: proposal follow-up, a review request after the final walkthrough, and a late-winter reminder to past customers.
- Trigger each one from a status your team already sets: proposal sent, project complete, season opening.
- Personal means the surface, the address, the estimator's name and the real schedule, not a first-name merge field.
- Pause automations when weather moves the schedule, and never send "book now" when your crews are booked out.
Marketing automation for a paving company should start with three workflows: chasing every proposal until it is signed or declined, asking for a review once the job is done, and reminding past customers before the next season. Set those up in your CRM and they run all season without anyone in the office having to remember a text.
The first three automations
- Proposal follow-up. It starts when the estimator marks a proposal as sent and stops the moment it is signed or declined. Most paving proposals are lost to silence, not to a lower price, because the homeowner is comparing bids and the contractor who checks in looks like the one who will show up.
- A review request after the final walkthrough. It starts when the project is marked complete. The first message carries your crew's care instructions for the new surface. The review request follows a day or two later, sent to every customer, never only to the happy ones, because Google bans review gating (Maps content policy).
- A late-winter season reminder. It goes to past customers and to everyone who said "call me in spring". Sealcoating customers hear that it is time, concrete customers hear about patios and walkways, and commercial accounts get a note that you are building next year's schedule.
Here is an example proposal follow-up for a residential driveway. Tune the days to how long your customers usually take to decide.
| When | Channel | Example message |
|---|---|---|
| Proposal sent | Text and email | The proposal link, from the estimator by name |
| Day 2 | Text | "Any questions about the base work or the tear-out?" |
| Day 7 | Photos of a similar driveway you finished recently | |
| Day 14 | Text | The real next opening: "We're scheduling paving for the week of [date]." |
| Day 30 | Text | "Should I keep your estimate open, or did you go another way?" |
The last message matters. A clear "we went with someone else" is useful too, because it closes the lead and tells you something about your price or timing.
The first three automations
- Missed-call text-back When an inquiry goes unanswered
- Quote follow-up When a quote sits without a reply
- Review request When the work is finished
Keeping it personal
Automation stays personal when every message uses details from the estimate: the surface, the address, the estimator's name and the actual schedule. "Hi Pat, it's Sam from [Company]. Still thinking about the concrete driveway on [street]?" reads like a person because a person's details are in it.
- Send from a person, not "the team". Customers met the estimator at the site visit.
- Stop when a human replies. The moment a customer answers, the sequence pauses and the estimator takes over.
- Pause for weather. A cheerful "your project is coming up" on the morning a rain delay moved it reads as careless.
- Separate residential and commercial. A property manager comparing three bids for a lot repair does not want homeowner-style texts. Use email and a phone call, on their decision timeline.
Tools
Use your field service or construction CRM for job-side messages, and HighLevel or a similar marketing CRM for the sales and marketing side. Each tool should do the part it already does well.
Field service or construction CRM : Crew scheduling, work orders, arrival notices and invoices. Keep those messages here, because this is where the schedule lives.
HighLevel : The lead inbox, proposal follow-up, review requests, past-customer campaigns and reporting by source.
The connection between them : A direct integration or an automation that passes two statuses across: "proposal signed" and "project complete". These two moments start and stop most of what matters.
A registered texting number : Business texting needs A2P 10DLC registration through The Campaign Registry before you send at volume (The Campaign Registry).
Common mistakes
Most automation mistakes in paving come from forgetting the calendar.
- Selling into a full schedule. "Book now" in July, when your crews are booked weeks out, creates angry customers. Swap in honest wait times when the backlog grows.
- Selling in the dead of winter. A paving offer in a cold month nobody can pour in wastes the message. Save it for late winter, when people are planning.
- Chasing a signed customer. If "signed" never reaches HighLevel, a new customer gets "still thinking about it?" a week after paying a deposit.
- Asking for a review before the job is truly done. Wait until the final walkthrough and any punch-list items are finished.
- No owner. Someone has to read replies daily in season. An automation that sends but nobody answers is worse than none.
- Texting without consent or a working STOP (CTIA messaging principles).
The CRM page for paving companies covers the setup behind these automations, and the repeat customers guide goes further on the late-winter campaign.
How VETS Growth Marketing helps
We build the three automations in a CRM you own, connect them to the software your crews already use, and finish the work on a date before the season opens. Then we watch the replies and report in proposals signed, reviews earned and past customers rebooked. In a growth consultation we will look at last season's proposals and reviews and pick the automation to build first.
Sources
- Prohibited & restricted content (Maps user-generated content policy), Google Maps Help
- Messaging Principles and Best Practices, CTIA
- The Campaign Registry (A2P 10DLC brand and campaign registration), The Campaign Registry