The revenue hiding in your technicians' job notes

Your best salesperson is already on the truck. Every day, your technicians stand on properties and see exactly what each customer needs next: thin turf, grubs, a busted sprinkler zone, shrubs swallowing a window. Most of that knowledge dies in a job note nobody reads. Here's how to turn it into booked revenue.

Condition codes 101

A condition code is a standardized flag a tech logs during a visit: what did I see on this property? Instead of a free-text note like "back yard looking rough," the tech taps a code: THIN-TURF, GRUBS, WEEDS-HEAVY, SHRUB-TRIM, IRRIG-LEAK. Both RealGreen and Service Autopilot support condition codes natively; Jobber shops can accomplish the same with standardized checklists.

The magic is in the standardization. "Looking rough" is a diary entry. THIN-TURF is a data point, and because it always means the same thing, it can be mapped to a service you sell: aeration and overseeding. A code that maps to a service can trigger a quote. That's the whole trick.

The aeration math

Let's run a realistic mid-size fertilization company:

• 1,000 recurring customers × 6 visits a season = 6,000 property visits where a trained pair of eyes is standing on the lawn.
• Say techs flag thin or compacted turf on just 8% of visits (deduplicated to one flag per customer, call it ~400 customers).
• Average aeration + overseed ticket: $340.
• Every one of those 400 customers gets a same-day, priced quote, with automatic follow-up. A 25% close rate on warm, evidence-based offers to existing customers is conservative.

400 × 25% × $340 = $34,000 in incremental fall revenue: from work your techs were already doing, sold to customers you already have, on routes you already run. No ad spend. Run the same play with grub control, mosquito, tree & shrub, or irrigation repair and the number multiplies.

Why manual follow-up always dies

Most owners have tried some version of this: "techs, write it in the notes; office, call the customer." It works for about two weeks. Then April happens. The failure chain looks like this:

1. The note sits unread because the office is answering phones.
2. Reading it requires pricing the service: someone has to look up the lawn size and do the math.
3. Pricing it requires writing a quote. Writing it requires sending it. Sending it requires following up. Twice.
4. Multiply by 30–50 flags a week, and the whole thing quietly stops. The notes keep coming; the revenue doesn't.

The problem isn't discipline. It's that you've built a five-step human relay race during your busiest season. Relay races drop batons.

The automated flow

Here's the same play with zero office steps, the way our marketing automations run it:

1. Tech taps a code in RealGreen or Service Autopilot before leaving the property. Two taps, ten seconds.
2. The platform catches it through the integration and matches the code to the mapped service: THIN-TURF → aeration & overseeding.
3. The property is measured and priced automatically against your exact pricing matrix. Not "starting at": the customer's actual price for their actual lawn.
4. A branded quote lands on the customer's phone the same day: "Miguel noticed some thinning turf in your back yard today. Here's what fall aeration and overseeding would run for your lawn." Accept and pay in two taps; the booking syncs back to your CRM.
5. Follow-up runs for weeks automatically until it books or the customer declines. (The cadence matters: see our speed-to-quote article.)

Same-day timing is half the power here. The quote arrives while the customer can still see the truck tracks on the lawn. "Your technician noticed this today" converts in a way no postcard ever will.

Getting techs to actually log codes

The system only eats what the techs feed it. Four things that work:

• Make it two taps. A short pick-list of 5–8 codes, not a 40-item scroll. If logging takes longer than closing the truck door, it won't happen.
• Pay on conversion. A $5–15 spiff per flag that turns into a booked job aligns everyone. You're paying commission on found money, happily.
• Leaderboard it. Flags logged, flags converted, revenue generated per tech, on the wall or in the weekly huddle. Techs are competitive; use it.
• Close the loop. Tell the crew "your codes produced $9,200 last month." When techs see the pipeline they created, logging stops feeling like paperwork and starts feeling like selling, because it is.

One guardrail: audit for quality quarterly. If a tech's flags never convert, ride along and recalibrate what "thin turf" means. Codes are a diagnosis; you want doctors, not alarm buttons.

The takeaway: your techs already find the work. A code-to-quote automation is just plumbing that connects what they see to what the customer buys: same day, at full price, with zero office labor.

Start this month

1. Pick your top 5 upsell services and assign each a condition code.
2. Map each code to a priced service in your system.
3. Train the crew in one 15-minute huddle: two taps, before you leave the property.
4. Automate the quote-and-follow-up leg, or accept that a human has to own it daily, in season.
5. Report flags → quotes → booked revenue weekly. What gets reported gets logged.