Maintenance is not the same business as installation, and most software in this category was not built for it. An install crew sells a job, does the job, invoices the job, and moves on. A maintenance crew sells a season, shows up forty times, and gets paid on a schedule that has almost nothing to do with which day the mower actually ran.
That difference is why so many landscaping maintenance software evaluations go wrong. Operators demo tools on the things that are easy to demo — quote templates, invoice design, a nice calendar — and then discover in week three of the season that the recurrence engine fights them every time a customer says "can you skip next Tuesday."
We build Landscapey, a recurring-maintenance-first CRM, so treat this as an interested party writing about its own category. Everything below is either arithmetic you can check or a price read off a vendor's own live page on a stated date. Where we could not verify something, it says so.
Why maintenance contracts break generic field-service software
There are three structural mismatches, and every practical problem you will hit descends from one of them.
1. The unit of work is the recurrence, not the job
In a project tool, the job is the object: it has a start, an end, and an invoice. In maintenance, the object is a recurring agreement that spawns visits. A weekly mow for a residential client is one agreement and roughly 32 visits, and those visits need to exist as individual, movable rows — because reality moves them.
The test that separates the two: can you move one visit without moving the recurrence? If a customer asks you to come Thursday instead of Tuesday this week only, a real maintenance system moves that single visit and leaves the pattern alone, so next week regenerates on Tuesday as always. A calendar bolted onto a project tool will often either shift every future visit or force you to delete and rebuild the schedule. That single behaviour will cost you more admin hours over a season than any feature on the sales page will save you.
2. The schedule is a route, not a calendar
Sixteen stops on a Tuesday is not sixteen appointments. It is an ordered sequence where the drive between stops is a real, paid cost, and where the order determines whether the crew finishes at 3pm or 5:30pm. A tool that shows you the day as a list of times, rather than as a sequence you can re-order and optimise, is asking you to do the hard part in your head.
3. Billing is decoupled from the visit
This is the one that surprises people coming from install work. Under a flat-monthly maintenance agreement, the invoice does not care how many times you mowed in April. That is the whole point — it is why maintenance revenue is predictable. But it means your software has to hold two separate truths at once: what was serviced, and what was billed. Tools that generate an invoice per completed job cannot represent a maintenance contract without you working around them.
The route math, worked
Route density is the number most maintenance operators feel and few actually calculate. Here is the calculation, with every assumption stated so you can substitute your own.
Assumptions: two-person crew, eight-hour day, 16 stops, truck and trailer averaging 9 mpg. Fuel prices are the U.S. Energy Information Administration's Short-Term Energy Outlook (July 2026) forecast annual averages for 2026: regular gasoline $3.64/gal, on-highway diesel $4.61/gal. Labor is a reader input — the example uses $22/hour fully burdened, which you should replace with your own number.
Compare a tight route at 40 road miles a day against a scattered one at 70.
| Cost of 30 extra route miles per day | Tight route (40 mi) | Scattered route (70 mi) | Difference |
|---|---|---|---|
| Diesel burned (9 mpg) | 4.44 gal | 7.78 gal | 3.34 gal |
| Fuel cost at $4.61/gal | $20.49 | $35.86 | $15.37/day |
| Extra drive time at 25 mph average | — | +1.2 hours | +1.2 hours |
| Crew cost of that time (2 × $22/hr) | — | $52.80 | $52.80/day |
| Over a 160-day season | — | — | $2,459 fuel + $8,448 labor |
The labor cost of loose routing is roughly 3.4 times the fuel cost of it. That ratio is the useful finding, and it survives most changes to the assumptions, because fuel is cheap per mile and people are not.
There is a harsher way to read the same 1.2 hours. At 27 minutes a stop, it is two to three stops you did not make. At $50 a stop that is $100–$150 of revenue per crew per day, or $16,000–$24,000 across a season — on one crew. This is why route optimisation is not a nice-to-have in maintenance the way it is in install work, and it is worth knowing which tools charge extra for it (see the pricing table below).
If you want the margin context for those numbers, we worked a full profit and loss for a $400k operation in our landscaping profit margin breakdown.
Flat monthly or per visit? Run the cash flow first
This is the single biggest configuration decision in maintenance software, and most tools make you commit to it before you understand the consequences. Here is the comparison on one residential mowing agreement.
Assumptions: 32 weekly visits across an eight-month season, $50 per visit, so $1,600 of contract value either way. The only thing that changes is when the money arrives and who carries the weather risk.
| Per visit | Flat monthly (8 months) | Flat monthly (12 months) | |
|---|---|---|---|
| Monthly invoice in season | ~$200 (varies by weeks) | $200 | $133.33 |
| Monthly invoice off season | $0 | $0 | $133.33 |
| Cash in the four dead months | $0 | $0 | $533 |
| Three visits lost to rain, never made up | −$150 | $0 | $0 |
| Three extra visits you ended up doing | +$150 | −$150 of unpaid work | −$150 of unpaid work |
Two things fall out of that table that are worth saying plainly.
The 12-month spread is a payroll bridge, not a discount. Splitting the same $1,600 across twelve months puts $533 into the four months when nothing is growing. If you have ever borrowed to make February payroll, that column is the argument for the 12-month structure, and it costs the customer nothing.
Flat monthly moves weather risk onto you, and that is usually the right trade. Under per-visit billing a washed-out week is a direct revenue loss. Under flat monthly it is not — but the mirror image is that you must actually count visits, because three visits of overservice is $150 of free labor that no invoice will ever show you. A maintenance system should be reporting visits-delivered against visits-contracted. Many do not.
We covered the mechanics of setting these agreements up, including proration and mid-season starts, in how to bill recurring landscaping clients.
What a rained-out day actually costs — and what recovering it is worth
Every maintenance operator loses days. Almost no software helps you decide what to do about it, and the decision is arithmetic, not instinct.
Take the same 16-stop day, lost entirely to rain.
- If you skip it and you bill per visit: 16 × $50 = $800 of revenue gone, permanently. If you paid the crew anyway, that day also cost you 8 hours × 2 people × $22 = $352.
- If you absorb it forward across the four remaining days of the week: each day picks up 4 extra stops, which at 27 minutes a stop is about 1.8 extra hours per day. Paid at time-and-a-half ($33/hr) for two people, that is $118.80 a day, or $475 for the week.
$475 of overtime beats $800 of lost revenue. Absorbing the day forward is worth doing until the overtime bill approaches $800 — which, on these assumptions, it does not. And notice the answer inverts if you bill flat monthly: then skipping costs no revenue at all, so paying overtime to catch up is money spent purely on service quality and customer goodwill. Same weather, same crew, opposite correct answer, and the only thing that changed was the billing model.
That is the specific thing to test in a demo: ask the vendor to rain out a Tuesday and show you what happens. You want to see the day's stops move as individual visits, with the recurrence untouched, and you want the tool to tell you which of those clients are billed per visit — because those are the ones where skipping has a price.
What the tools cost, verified
Software pricing in this category is quoted loosely and changes often, so every figure below is read off the vendor's own live page on the date stated, not from a review aggregator. Annual rates are shown where a vendor publishes both.
| Tool | Published entry price | What we verified |
|---|---|---|
| Jobber | Core $29/mo billed annually, 1 user ($49 month to month) | Sold in team-size bands: Connect $99 (1 user) / $149 (5 users); Grow $149 (1 user); Plus from $399. Extra users $29/mo each. QuickBooks Online sync starts at Connect; job costing starts at Grow. Verified 2026-08-03. |
| Service Autopilot | Startup $49/mo | Route optimisation is not on Startup — it begins at Pro, $199/mo. Automations begin at Pro Plus, $499/mo. Elite is unpriced. Every published plan carries a sign-up fee whose amount is not disclosed. Verified 2026-08-01. |
| LMN (Granum) | Starter $297/mo | Starter includes 1 office/crew-lead licence and 5 crew licences; Professional $648/mo (3 office, 15 crew); Enterprise is quote-based. SMS messaging is an add-on: $75 setup plus $30/mo. No free tier is listed on the pricing page. Verified 2026-08-03. |
| Yardbook | Free core tier | Paid tiers were $34.99/mo (Business) and $49.99/mo (Enterprise, $599.88/yr) when we read the pricing page on 2026-07-29, with QuickBooks sync on Enterprise only. That pricing page now returns a 404 (checked 2026-08-03), so treat those figures as last-verified, not current. |
| Aspire, DynaScape Manage360 | Not published | Both are quote-based. Expect a sales call before a number. Checked 2026-08-03. |
| Landscapey | $19.99/mo flat (listed $29.99) | One plan, unlimited users, no per-seat fee, 14-day trial. Our own product. |
The pattern worth naming: maintenance capability is the most reliably up-sold thing in this category. Route optimisation — the one feature a 16-stop day genuinely depends on — sits four tiers-worth of money above Service Autopilot's headline price, at $199/mo instead of $49. The two platforms built hardest around maintenance and job-costing rigor, LMN and Aspire, start at $297/mo and "call us" respectively. Jobber is the honest counterexample at the bottom end: $29/mo billed annually is a real entry price, though the QuickBooks sync many operators consider mandatory sits at $99–$149.
None of that makes any of these the wrong tool. It means the headline price is not the number to plan against, and you should price the tier that contains the features maintenance actually needs. For a straight tool-by-tool comparison rather than a capability discussion, we keep a running roundup of the best landscape management software, and a line-by-line read of one vendor's plan chart in our Service Autopilot review.
A maintenance-specific evaluation checklist
Generic software checklists ask whether a tool has scheduling and invoicing. Every tool here has scheduling and invoicing. These are the eight questions that actually separate them for recurring work. Ask them in the demo, and ask for the answer to be shown rather than described.
- Move one visit, keep the pattern. Reschedule a single Tuesday visit to Thursday. Does next Tuesday still generate?
- Rain out a whole day. Can the day be absorbed forward, moved wholesale, or skipped — and does the tool warn you which affected clients are billed per visit?
- Pause and resume a contract. A client goes to Florida for six weeks. Can you pause without deleting, and does the schedule rebuild correctly on resume?
- Visits delivered versus contracted. On a flat-monthly agreement, can you see that you have done 35 visits against a 32-visit contract?
- Route order, not just route list. Can you re-sequence a day's stops and see the drive-time consequence before you commit?
- Two billing models side by side. Can flat-monthly and per-visit clients coexist on the same route without manual reconciliation?
- Season boundaries. What happens on the last visit of the season, and how much work is it to roll every agreement into next year?
- The real price. Which tier contains items 1–7, and what does that tier cost with your actual headcount?
Item eight is where most evaluations quietly fail. The demo is nearly always run on the tier that has everything.
Where Landscapey fits, and where it does not
Landscapey was built recurring-first, so items one through six of that checklist are the product's spine rather than features added later: jobs generate visits, visits move individually without touching the recurrence, a lost day can be absorbed forward or moved with a preview of every client's before-and-after, routes are optimised and re-orderable, and flat-monthly and per-visit clients sit on the same day without reconciliation. Pricing is one flat plan at $19.99/mo with unlimited users, because per-seat pricing punishes exactly the operators who add a second crew.
What it is not: there is no CAD or design takeoff, no GPS vehicle tracking, no chemical application program tracking of the depth Yardbook and Service Autopilot offer, and no multi-user crew accounts yet. If your business is design-build or heavily chemical, the honest answer is that one of the tools above fits you better today.
If you run maintenance contracts and the schedule is the thing that breaks, that is the case we are built for. See pricing or start a 14-day trial.
Frequently asked questions
What is landscaping maintenance software?
Software that manages recurring service agreements rather than one-off projects. The defining capabilities are a recurrence engine that generates individual visits, route-based scheduling, and billing that can be decoupled from the visit — typically flat monthly. Tools that only manage quote-to-job-to-invoice are project tools, however well they handle each step.
How is it different from landscaping estimating or design software?
Estimating and design tools optimise the sale: takeoffs, material lists, renderings, proposals. Maintenance software optimises delivery over months — who gets serviced, in what order, at what interval, and what gets billed regardless. Design-build companies usually need both, which is one reason platforms aimed at them cost more.
Should I bill maintenance flat monthly or per visit?
Flat monthly is generally better for you: predictable revenue, no weather risk, and if you spread it over twelve months it funds the off-season. On a $1,600 season that is about $533 of cash landing in the four dead months. The trade is that you carry the weather risk and must track visits delivered against visits contracted, or overservice quietly eats the margin. Per-visit is simpler and fairer-feeling to customers, but it hands your revenue to the forecast.
What happens to my schedule when a day is rained out?
That depends on your billing model, which is the point most software misses. On per-visit billing a skipped 16-stop day is roughly $800 of revenue gone, and absorbing it into the rest of the week costs about $475 in overtime on our worked assumptions — so recovering it pays. On flat monthly, skipping costs no revenue, so catching up is a service-quality decision rather than a financial one. Good maintenance software should let you preview both outcomes before you commit the change.
How much does landscaping maintenance software cost?
Published entry prices run from free (Yardbook's core tier) through $19.99–$49/mo for flat and entry-tier plans, up to $297/mo for LMN Starter, with Aspire and DynaScape quote-only. The more useful question is what the tier containing route optimisation and job costing costs: in Service Autopilot that is $199/mo, and in Jobber job costing starts at Grow. All figures verified on the vendors' own pages between 2026-07-29 and 2026-08-03.
Do I need route optimisation with only one crew?
Yes, and arguably more than a multi-crew operation does, because one crew has no slack. Our worked example puts 30 extra road miles a day at $15.37 in fuel and $52.80 in crew time — and, more painfully, at two to three stops you did not fit in, which is $100–$150 of revenue a day. On a single crew there is nowhere for that to go but your own hours.