A landscaping CRM that captures the extras

A landscaping business does not usually fail at landscaping. It fails at the accounting that surrounds the landscaping, and almost always in one specific place.

The extras problem, in detail

A crew is at a property on its scheduled day. A branch came down in the wind and they clear it. An irrigation head is broken and they replace it. A bed that got away over the winter takes an extra forty minutes.

All of that is real work, done well, at the customer’s benefit. It is mentioned to the foreman, or it is not. It reaches the office in conversation, or it does not. The invoice goes out for the agreed amount.

Individually each instance is trivial, which is exactly why it persists. Across sixty properties, a season and several crews, it is a meaningful volume of completed work given away for nothing. No amount of effort on winning new customers replaces work you already did.

What capture has to look like to actually happen

The failure of most attempts to fix this is not the intention. It is the design.

If recording an extra requires opening a laptop, logging in, finding a property and filling a form, it will not happen. Crews are working, the truck is moving to the next stop, and the extra was fifteen minutes. The effort of recording it must be smaller than the thing being recorded.

In practice that means it happens at the property, on a phone, in under a minute: which property, what was done, roughly how long, and a photograph. The photograph does more than the words, because it settles any later question about whether the work occurred and what state things were in.

A weekly review of unbilled extras then takes the office ten minutes and recovers most of what was previously lost. This is the whole feature, and it is worth more than every other capability in a landscaping system combined.

Two businesses, one customer record

The landscaping hub makes the case that maintenance and installation are separate businesses. That does not mean separate systems.

A customer record should be shared, because a maintenance client is the most likely source of an installation enquiry and the shop should be able to see both histories in one place. What should differ is everything after the record: a route stop has a schedule, a crew and recurring billing, while an installation has a proposal, a decision period and a project timeline.

Shops that force one workflow onto both end up with maintenance drowning in project overhead, or with large installations managed as casually as a weekly mow. Neither is recoverable by adding features.

The long sales cycle on the project side

An installation enquiry behaves like the painting work described on the painting hub: the homeowner considers it for months, discusses it, changes the scope twice, and frequently goes quiet without deciding against you.

What the record needs there is small — what they asked about, when, what was proposed, and a date to raise it again. A homeowner who enquired about a renovation in March and hears from you in September is not being pestered; they are being remembered, and a good share of them have simply been busy.

Channels, and the crew’s personal phone

A predictable pattern in this trade is customers texting a crew member directly, because during the first job that was the only number anyone offered. It then becomes the channel for everything, including complaints, schedule changes and payment questions, none of which reach the office.

This is rarely fixable by asking the crew to stop. It is fixable by offering a better alternative — an office number that is genuinely answered, which for a small operation usually means answering coverage (the plumbers page covers the mechanics) rather than a person.

What to build first

Extras capture. Then the shared customer record. Then the project follow-up dates. Billing automation comes last, and only once the extras are reliably captured, because automating an incomplete invoice simply sends the wrong number faster.

What a property record should hold

Less than most systems offer and more than most companies keep.

The property, the schedule, who is assigned, what the agreed scope actually includes, and a running list of extras. That last item is the one everything else exists to support, and it should be the easiest thing in the system to add to.

Access details belong here too — gate codes, dogs, where the tap is, which neighbour complains about early starts. That information currently lives in a crew member’s head and leaves when they do, which is a quiet and recurring cost in this trade.

The scope conversation, written down

A surprising share of maintenance disputes come from a genuine disagreement about what was included, and both parties are usually remembering honestly.

Writing the agreed scope into the record at the start, in plain language, and referring to it when something falls outside, removes almost all of that. It also makes the extras conversation easier, because an extra is by definition something outside a scope that was written down rather than assumed.

The concrete page describes the same failure in a trade where the stakes per incident are higher, and the remedy is identical: a dated note, the same day.

What to look at weekly

Unbilled extras, and nothing else at first.

Ten minutes, once a week, covering what the crews recorded and what has not yet reached an invoice. That single habit recovers more than any other change available to a maintenance business, and it stops being effective the moment the interval stretches to a month, because the details stop being fresh enough to confirm.

The demos include a record you can push sample properties through, and starting a project begins with a season’s worth of unbilled extras.