The whole renewal season booked before the rush—without working last year's list at the kitchen table

Yes — that is the normal starting point. During setup, Deptly builds the season's list from last season's completed jobs, wherever they live, and reconciles the duplicates and the moved-aways. From then on the list is maintained as its own asset: every name carries a status, and nobody silently falls off between seasons.

No. You set the season's rates — including any increase — and Deptly offers exactly that. Many owners approve a standard adjustment once and it applies across the list. A customer who pushes back on price gets a consistent answer within your rules or comes to you; nothing is ever discounted to close a booking.

Early outreach is most of the answer: when the offer goes out weeks ahead, bookings spread across the window instead of piling into the last one. Deptly groups confirmed jobs into crew days by neighborhood, runs a standby list for cancellations, and flags overflow early enough that adding a Saturday crew is a decision you make in advance — not a scramble.

You set the rule before the season — for example, a hard-freeze forecast pulls remaining winterizations forward. When the forecast hits, Deptly proposes the re-sequenced schedule, you approve it, and every affected customer hears their new day from your business before they see the weather report. The replies — gate codes, out-of-town questions — get handled without you.

Verified closure is the whole design: every name from last season ends the window in exactly one state — completed, booked, declined with a logged reason, or explicitly deferred by you. There is no 'assumed they'd call.' You watch the unbooked names shrink week by week, and the final list is a record you can stand behind if a dispute ever comes.

It never prices them. Your tech reports what they found, you set the number, and Deptly sends the quote the same day — while the customer still cares — then follows it until it is approved or declined. Found-repair quotes that never go out are one of the quietest leaks in seasonal work; this closes that loop without touching your pricing judgment.

Yes. Terms go out on your schedule, routine questions get answered from your contract notes, and signatures and deposits are collected by your deadline — with a weekly list of who is signed, wavering, or quiet. Once the season starts, storm-day activations and service records are a different workflow; that side lives with our tree, snow and weather-responsive services page.

It works under your business name, in your voice, in whichever channel each customer prefers — phone included, nobody is forced to text. In practice, the ten-year customer's complaint was never about who called; it was that nobody did, until a competitor's postcard landed. Being asked early, by name, with last year's service referenced, reads as the good kind of organized.

Scope is priced to the work, so it can flex with the calendar. Renewal pushes are naturally batch-shaped: heavy in the weeks before each window, light between. Many seasonal businesses run outreach windows plus a small steady layer — payment follow-up, review requests, list upkeep — rather than a flat year-round scope.

A straightforward first workflow can often launch in days; complex integrations and regulated work may require more time. A single-season renewal push — one list, one service, your prices — is about as straightforward as first workflows get, which is why it is a common starting point ahead of a fall or spring window.

Small crews leak the most renewal revenue, because the person who should be working the list is on the blower. You start with one workflow — one season, one service, one list — and expand only if it earns it. If the fall push books itself while you finish cleanups, that answers the question better than any pitch.

It depends on scope: how many seasonal pushes, how many names, which channels and systems, and how much oversight you want. Most seasonal businesses start with a single workflow pilot — one renewal window, run end to end — and decide from there. The pricing page explains the models, and a short call gets you a scoped recommendation.