Drew’s Seasonal
Services

The Drew’s Seasonal Services build, step by step

Drew’s Seasonal Services is a one truck seasonal operator in Grande Prairie, Alberta: spring cleanups, aeration, hedges, haul away, snow when it comes. It is the fullest case study on our site because Drew took all three parts of the system, and because the numbers are his and he agreed to publish them.

Where Drew’s Seasonal Services started

Most of the work came through Facebook. Calls landed while Drew was on a machine and went to voicemail. Two different ad providers were spending his money on leads from cities hours away, roughly a thousand dollars a month for enquiries he could not drive to. Quotes went out at night when he got home, invoices went out whenever, and follow up depended on whether he remembered. None of that is unusual; it is the default state of a one person service business, and it is why Drew’s Seasonal Services was leaving money on the table every single week.

Step one: stop the leak in the ads

We consolidated Drew’s Seasonal Services to one ad provider and rebuilt the Meta campaigns around his actual service area, with creative that spoke to the homeowner’s problem rather than a list of services. The junk leads from out of town stopped. Local leads went to three to six a day on a total monthly spend under $1K, ads included.

Step two: answer every call

The AI Sales Agent went on Drew’s existing line. Missed calls forward to it in four seconds; texts and the website form land on the same number. It quotes from Drew’s real price book, offers real openings from his calendar, books the job, sends the deposit link and chases the quiet ones. For Drew’s Seasonal Services that meant the 2 pm call from a homeowner became a booked Thursday 9 am instead of a voicemail he returned at 8 pm to a customer who had already hired someone else.

Step three: Drew’s Seasonal Services runs the job from a phone

The custom field app is the part people ask about most. It is a small piece of software built around how Drew’s Seasonal Services actually works: today’s jobs in order, the customer’s notes and photos, one tap to mark complete. When a job is marked complete, the app invoices the customer automatically and the AI agent sends the payment link. The line on our homepage came from this: he marked the job complete on his phone, the agent invoiced her, and he was paid before he left the driveway.

The Drew’s Seasonal Services numbers

• First month revenue from about $2K to over $10K
• Three to six quality local leads a day
• Total monthly spend, ads and software included, under $1K
• Same day complete to paid on most jobs
• Zero missed calls on the line since the agent went live

What Drew’s Seasonal Services pays to run it

The AI Sales Agent is $297 a month with usage pass through at Twilio’s published rates; at Drew’s call volume that is a few dollars a day. The field app is on the $399 retainer, which includes the agent’s fee, so the software line is one number. Meta management is a flat $500 a month and his ad spend goes straight to Meta on his own card. Nothing is under contract; every part of it has been re earned every month since launch.

What we would do differently

Honestly, the order. We ran the ads rebuild and the agent in parallel because the junk lead spend was urgent, but on a fresh account we would put the agent on the line first and let the ads follow a week later, so that every lead from day one lands on a system that can catch it. That order is now the default for every business that looks like Drew’s Seasonal Services.

Why this case study matters for your trade

Nothing in the Drew’s Seasonal Services build is specific to landscaping. Swap the price book and the photos and it is a fencing company, a painter, a pest control route or a mobile mechanic. The system is the same three parts: answer it, run it, fill it. If you are a one truck or a three truck operator with the same leaks, fifteen minutes with a partner will tell you which part to fix first and what it costs.

Timeline

Week one was the intake and the ads rebuild. The AI Sales Agent went live on the line in week two after Drew approved the voice on recorded test calls. The field app shipped its first version in week five, on real jobs, and invoicing on complete was added in week seven once the job flow was proven. The numbers above are from the first full month after all three parts were live, and they have held since.

Questions people ask about this case study

Is Drew’s Seasonal Services a real business? Yes, in Grande Prairie, Alberta, and Drew agreed to be named and to publish his numbers. Did the revenue jump come from ads alone? No; the ads brought the leads, the agent booked them, and the app got them invoiced and paid, and none of the three would have produced the same month on its own. Would this work with one truck in a smaller town? That is exactly what it is: one truck, a mid sized northern Alberta town, and a seasonal trade.

What the customer sees

From the homeowner’s side it looks like a business that has its act together. The call is answered at 2 pm, the quote comes with two real times, the confirmation and the reminder arrive by text, the crew turns up when it said it would, and the invoice lands on the phone while the truck is still in the driveway. That is the entire competitive advantage of Drew’s Seasonal Services over the next landscaper in Grande Prairie, and it costs less per month than the junk leads used to. It is also why the reviews started arriving on their own: the job complete text asks for one, and a customer who just had a good experience says yes.