A landscaping company runs on a few things that are hard to see from the office: how fast a new lead gets a site walk, how accurately the estimator prices labor hours, and whether crews spend the day mowing or driving. In Colorado the calendar compresses all of it. Spring start-ups, the April lead rush, summer maintenance, fall cleanups and irrigation blowouts, then snow removal contracts that run on a completely different rhythm.
InTheory works as your fractional AI and technology lead. We would start with one expensive recurring workflow, such as estimates sitting in a drafts folder or maintenance renewals that slip every February, and fix it inside the software you already pay for where possible. Aspire, LMN, Jobber or Service Autopilot usually have more capability than gets used. People still approve every price, every contract and anything sent to a property manager or homeowner.
Between March and May, enquiries arrive faster than the owner or sales lead can call back. Web forms, Google Business Profile messages, voicemails and HOA referrals land in different places. By the time someone returns the call, the homeowner has booked whoever showed up first. Response time in that window decides a large share of the year's design-build and enhancement work.
Most estimating knowledge lives in the head of the owner or a senior estimator: production rates for sod, rock and edging, how long a crew really takes on a sloped lot, what to add for haul-off. When that person is on site or on vacation, bids stall or go out inconsistent, and margins vary from job to job.
A week of maintenance routes can fall apart with one rain day, a broken mower or two laborers who do not show. Re-sequencing by phone and text eats the account manager's morning. In winter, the same team has to switch to snow triggers, per-push tracking and site logs that the summer system was never set up for.
Many companies grow from ten people to thirty each spring, sometimes with H-2B workers who arrive on a fixed date. Applications, I-9s, safety training, equipment sign-outs and Spanish-language onboarding all happen in the same three weeks the phones are busiest. Small gaps here show up later as turnover, damaged equipment and crews that start the season short.
We fix one at a time, starting with the one that costs you most. Each page shows the steps, the tools, what stays human and what we would measure.
Acknowledge every web form, call and message within minutes during the spring rush, ask the questions your estimator needs (property type, scope, photos, timeline), and book the site walk without waiting for the owner to get back to the truck.
See the workflow →Turn site walk notes, measurements and photos into a draft estimate using your own production rates and material costs in Aspire or LMN, so the estimator reviews and adjusts instead of building every line from scratch.
See the workflow →Follow up on every open design-build, enhancement and maintenance proposal on a consistent schedule, with messages that reference the actual scope. Stop letting good bids go quiet because the season got busy.
See the workflow →Build maintenance routes and enhancement schedules with fewer phone calls, re-sequence quickly after rain days or equipment problems, and give crew leads a clear daily plan on their phones.
See the workflow →Send maintenance and snow removal renewals on time each winter, flag accounts with complaints or overbudget hours, and give account managers a short list of properties to visit before contracts lapse.
See the workflow →Send invoices when work is completed, follow up politely on aging balances, and handle monthly property manager billing and snow event invoicing without the office manager chasing each one by hand.
See the workflow →Ask homeowners for a review after a finished install or a clean spring cleanup, and ask property managers for referrals at the right moment, instead of remembering to do it in October.
See the workflow →Screen seasonal applicants faster, send bilingual onboarding paperwork and safety training before day one, and track equipment training and licenses so new crew members are productive in their first week.
See the workflow →How we deliver this: AI automation for small business or fractional CTO leadership, scoped in writing and run over 90 days. See pricing or the sample scope.
We start with what you already pay for. New tools have to earn their place.
Landscaping data is mostly customer contact details, property addresses, gate codes, photos and payment information. Gate codes and alarm details deserve the same care as passwords: limit who sees them and keep them out of AI prompts. Card data should stay inside your payment processor. If you employ H-2B or other seasonal workers, I-9 and immigration documents need restricted access and proper retention. Colorado's SB 26-189 (effective January 1, 2027) is worth tracking in general terms if AI tools ever influence hiring decisions.
General information, not legal advice.
Defaults are illustrative for landscaping companies (new maintenance or install clients per month). Change them to your numbers.
a month in staff time, before any lost sales
Illustration only, not a forecast or guarantee. Recovered staff time becomes a cash saving only if spending actually declines or the time goes into paid work. Tool costs are an assumption; we replace every number here with yours before recommending a scope.
Usually not. Most of the gains we would look for come from using features you already pay for, connecting your field software to your phone system or website, and adding AI drafting in narrow places like estimate notes or follow-up messages. Replacing a field service platform mid-season is disruptive and expensive. Sometimes the right recommendation is a settings change and better training, not a new tool.
For many companies it is spring lead response or estimate follow-up, because the cost of a slow reply is easy to see and easy to measure. Others start with maintenance renewals, because a few lost commercial accounts can wipe out a season's growth. In the first 30 days we would pick one, set a baseline and agree what success looks like before building anything.
We would plan around it. Diagnosis and design work best in late fall and winter, when the owner has time to think and the team can test changes before the spring rush. A change to dispatch or lead handling should be live and tested by early March. We avoid launching new systems in the middle of May, when nobody has time to learn them.
It can help with the administrative side: logging events from crew check-ins, matching pushes and salt applications to each contract's terms, drafting event invoices and flagging sites where documentation is thin. It should not decide when to send a crew. That remains a judgment call made by someone watching the forecast and the trigger depth written into each contract.
Plans run $2,500, $5,000 or $7,000 per month for an initial 90-day engagement, with a written scope before kickoff. Software and any major custom build are budgeted separately. For a company doing a few million in revenue, the question is whether one fixed workflow, such as faster lead response or on-time renewals, pays back the fee. We would model that with your numbers first.
In 30 minutes we look at one recurring workflow, what it costs you today and whether there is a credible case to improve it. If there is not, we will say so.
30 minutes with Phil or Martin. No technical brief, no pitch deck. Phil or Martin replies personally, usually within one business day.