Landscaping CRM Software: What a Seat Costs in December

Most landscaping software comparisons treat the trade as a generic small service business with trucks. That misses the point. A landscaping company runs the same properties on a fixed rotation from April to November, sends the same two or three people to each one, bills most of them on a recurring schedule, and then goes quiet for the winter. The CRM question is shaped by that pattern, not by the features list. Pick the wrong meter and you pay a full year's worth of seats for two months of actual use.

Per plan vs. per user: what landscapers actually pay for

There are two shapes of price in this market. The first is the field-service tool, which charges per plan and includes a fixed number of users. The second is the generic CRM, which charges per user and lets you add seats one at a time. Landscaping companies with a small office and a fixed crew tend to do better on the per-plan shape. Landscaping companies that scale up mid-season, hire seasonal crew, or run multiple divisions tend to do better on per-user shapes, but only if they actually turn seats off in the off-season.

Here is the published pricing for both shapes, all checked in September 2026.

We make Asyntai, so read that row as a disclosure. The other rows are taken from each vendor's own pricing page on the dates in the sources block.

The Jobber and Housecall Pro figures are whole-plan prices with a user cap baked in. Zoho CRM and Pipedrive are per-user prices with no cap. The Asyntai row is included because the article needs to address the deflection side of the question, not because it competes with field-service routing. More on that below.

What each tool actually is, in one line

Jobber is a field-service platform built for trades like landscaping, cleaning and HVAC. It handles quoting, scheduling a route, invoicing the same property on a recurring schedule, and taking card payments on site. The price is per plan, not per user, and the user count is fixed inside the plan.

Housecall Pro is the closest direct competitor to Jobber. It targets the same trades, with stronger marketing automation and a larger payments ecosystem, and a slightly higher entry price. Like Jobber, it sells in plans with a user count, and it publishes extra-user pricing only on the higher tiers.

Zoho CRM is a general-purpose customer relationship management tool. It does not know what a mowing route is. Landscapers use it when they want a pipeline view of their sales process and are willing to configure the trade-specific bits themselves. It prices per user.

Pipedrive is also a general-purpose CRM, with a sales-pipeline shape similar to Zoho's but lighter to set up. Like Zoho, it prices per seat, and like Zoho it has no concept of a recurring property visit unless you build one.

The twelve-month arithmetic for a small crew

This is the part that actually decides which tool to pick. Pick the tool on the arithmetic, not on the demo.

A typical landscaping operation has one owner, one office person, and two crew leads. That is four people who need a login to the CRM at peak. The work runs from April through November, eight months of real use, with December through March being mostly quiet invoicing and snow contracts in some regions.

That is the per-plan answer. The plan includes the fifth seat for free, the price is the same in February as in July, and there is nothing to switch off in the off-season because the plan price is the plan price.

That is cheaper on paper, but only if you actually want four seats in February. The per-user shape gives you a lever the per-plan shape does not. If you turn off two seats for the four winter months, the math looks different.

The savings only appear if the tool lets you remove seats month to month and you remember to do it. Zoho's published price is per user per month billed annually, which is a single annual commitment per seat rather than a flexible monthly add. Removing seats partway through an annual commitment is a different conversation. The flexibility on paper is not the same as flexibility on the invoice.

The arithmetic when the crew grows in May

Landscaping companies routinely hire seasonal crew in April or May. The per-user tools charge for those seats from the day they are added. The per-plan tools charge a flat fee for the plan that already includes a fixed number of users, and then a known extra-user fee for anyone beyond that.

The same crew on Jobber Connect with the published extra-user fee looks like this.

The Jobber figure is the lower one, but the comparison is not about the dollar amount. It is about whether the published price matches what landscapers actually do. Jobber publishes $29 per extra user per month on every plan, which means a landscaper can add a seasonal crew member for May through October for a known cost. Housecall Pro publishes $100 per extra user on Essentials and $75 on Max, and Basic does not publish an extra-user price at all. Basic is for a one-person operation and stays a one-person operation.

What a CRM actually does for a landscaper

The plumbing list looks like this on every demo: contact records, a quote builder, a job schedule, an invoice, a payment link, and a recurring schedule for properties on a rotation. None of that is exotic. The interesting questions are about the recurring schedule and the route.

A landscaping company with eighty residential clients on a weekly or biweekly rotation needs three things the CRM has to do well.

1. Recurring jobs. The same property shows up automatically each week without someone retyping it. The CRM has to bill it on the same cadence without sending a fresh quote each visit.
2. Route view. The crew needs to see today's stops in driving order, not as a list sorted alphabetically by client name.
3. Property notes that survive the season. Gate code 4427, dog in the yard, mow the back twice in June because of the slope. The notes have to attach to the property, not to a single job, so the next visit in August picks them up.

The trade-specific tools handle these as built-in features. The general-purpose CRMs handle them as configuration that the landscaper builds. Whether that configuration cost is worth the lower per-seat price depends on how much the owner likes setting up software, which is not a number and not in any pricing page.

Per-plan vs. per-user, side by side

The two shapes have different personalities, and the personality matters more than the dollar figure for a landscaping operation.

The trade-specific tools win on the things a landscaper does every day. The general-purpose tools win on the things a landscaper does once a quarter, like a sales push into a new subdivision. Most operations need more of the everyday things, which is why most landscaping companies end up on Jobber or Housecall Pro rather than Zoho or Pipedrive. That is a pattern, not a recommendation.

Where a website chat fits

A landscaping website gets a small, predictable set of questions, mostly from people who have not booked yet. The list is short.

The first three rows are deflection candidates. The fourth is not, and trying to handle it on the website leads to mistakes. A chat agent that knows the difference between a new enquiry and an existing client, and routes the second one to the office, is the design that actually saves the office time rather than adding to it. See how an AI live chat agent handles that split.

Asyntai is an AI chat agent you put on the landscaping website to answer those first three rows automatically. The deflection maths is the second half of this article.

The deflection arithmetic across a mowing season

Assume, as the reader's own input, that the website gets 200 chats in a month across the season. Assume half of those are about service area, pricing and start date. Assume the chat agent answers those without the office being involved. Assume the other half routes to the office. The maths is then about how many chats a season that is, and what each handled chat is worth in office time.

At the Starter plan, $39 per month pays for 2,500 messages. At four messages a chat, that is about 600 chats a month, which is more than the 100 a month above, so the chat agent cost across the season is 8 months at the published price.

If the office currently spends a measurable amount of time per chat, the dollar saving comes out of that figure. The chat agent cost is a separate line. The two are not the same conversation and the article does not join them into a single number, because the time-per-chat figure is the reader's own number, not something the pricing pages publish.

What the website should answer before the phone rings

The landscaping website has a job before the CRM ever sees the lead. It has to answer the three deflection questions above in a way the visitor trusts. That means four things on the page.

• A service-area map or list. Postal codes, not "we serve the metro area". The chat agent and the website both point at the same map.
• A price band, with the variables that move it. Lot size, slope, gate access, frequency. A range is fine. A "call for a quote" with nothing else is not.
• A real start-date answer. Either "we are booking the week of May 6" or "we are fully booked for the season". Anything vague loses the lead.
• A way to book a slot or request a quote without a phone call. The form goes to the CRM. The chat hands off to the same place.

If the website has those four things, the chat agent can answer the deflection questions and the CRM sees a smaller, better-qualified pipeline. If the website does not have them, the chat agent is forwarding the same vague enquiries the phone used to take, and the deflection maths collapses.

The mistake most landscapers make

The mistake is buying a per-seat CRM for a four-person crew and paying for four seats in February. The published per-user price looks cheaper than the published per-plan price, and the comparison stops there. The per-plan tools, Jobber in particular, include the user count in the plan and run at the same price in every month of the year. The landscaper pays $99 a month for five seats through the winter and through the summer, and that is the whole bill. There is nothing to switch off and nothing to forget.

The mistake on the other side is buying a per-plan tool and then adding five seasonal crew members at the published extra-user fee without noticing what that fee is. Housecall Pro publishes $100 per extra user per month on Essentials, which is more than the base price of Zoho CRM Standard. A crew of ten on Housecall Pro Essentials is a different bill than a crew of five.

What changes the answer

Three numbers change which row of the maths is the right one for a given operation. None of them are in any pricing page.

Crew size. A solo operator lands on Jobber Core at $29 a month. A ten-person crew lands on Jobber Plus at $399 a month, plus nine extra users at $29 each, which is a different conversation than the same crew on Zoho or Pipedrive with seats turned off in winter.

Off-season behaviour. Some landscaping companies run snow and ice contracts from December to March. Those companies want every seat live in February. Companies that go fully quiet in winter want the opposite.

Sales process complexity. A landscaper who sells mostly to homeowners on a recurring schedule has light sales needs and a per-plan tool fits. A landscaper who bids on commercial contracts, runs multi-year bids, and tracks proposals needs a real pipeline view and the per-user CRMs earn their keep there.

What to do with this

Three concrete steps, in order.

First, count the actual seats you need in February, not the seats you need in July. The CRM choice is the February number, because the summer number is when the work pays for it.

Second, decide whether your website answers the three deflection questions above. If it does not, fix that first. No CRM, no chat agent, no automation fixes a website that does not say whether you serve a postal code.

Third, ask each vendor what the invoice actually is in month nine with your crew size, your off-season behaviour, and your seasonal hires. The published price is the start of the conversation, not the end of it.