The seasonal shape of a landscaping backlog
Design-build and hardscape work has a booking window rather than a sales cycle. Homeowners think about their yard when they are looking at it, which means inquiry volume concentrates heavily in spring and early summer. Proposals written at the front of that window convert well. Proposals written at the back of it get pushed, because there is no crew capacity left and no appetite for a construction site in November.
The result is a backlog with a very specific composition: a cluster of late-season deferrals from design consultations that went well, plus a scatter of mid-season proposals that lost to budget or to a competitor with earlier availability. The first group is materially different from the second. The homeowner did not decline the design — they declined the timing.
That is also why the window for reactivation is narrow. Reaching a deferred design-build proposal in late winter or very early spring means you are talking to them before they start re-shopping. Reaching them in May means competing for the same crew slots as every fresh inquiry, at which point the advantage of having already done the design work largely evaporates.
Why maintenance and project records must stay separate
Recurring maintenance accounts and one-time project proposals share a CRM but almost nothing else. A maintenance customer has an ongoing relationship, a known property, and a service history — the natural conversation is about expanding scope or addressing something the crew has been noticing. A project prospect had a consultation and a proposal, and the natural conversation is about whether they still want the project.
Running both through the same sequence produces messages that are too generic for either. It also risks the specific failure of sending a maintenance customer something that reads as though you do not know they are already a customer, which is worse than sending nothing.
What to look at in the export
Landscaping exports vary more than most trades because the software landscape is fragmented. Whatever platform you use, these fields determine how a stalled record should be handled:
- Service type — design-build, hardscape, drainage, irrigation, lighting, and recurring maintenance each need their own sequence and their own timing.
- Proposal date and, critically, the month it was issued, because that reconstructs whether this was a deferral or a loss.
- Whether a design was produced and paid for, which is a much warmer record than a walkthrough estimate.
- Proposal amount, since a patio and a full backyard renovation sit at very different points in the household's decision process.
- Any recorded note about intended timing — "next spring" in a note field is the most actionable data in the whole export.
- Existing customer flag, so maintenance accounts are excluded from prospect sequences.
Upload the export and the free audit sorts open from resolved, flags what it cannot classify, and totals the open proposal value. That runs today. Everything downstream of it is still being built.
Reopening the design conversation
The most productive follow-up in this trade does not re-present the old proposal. It asks whether the project is still something they want to do this year and offers a site review — because the site has changed, the plant availability has changed, and the crew calendar for the coming season is a real constraint worth discussing before it fills.
SignalBack is designed to run that timed outreach ahead of your booking window once campaigns are enabled, so the deferred proposals get touched in February rather than remembered in June. Replies route to a person; scope, plant selection, and pricing are not things automation should attempt.
Sending, integrations, and billing are not built yet. Landscape companies can join early access for the campaign side, and use the audit now to see what last season actually left behind.