Turning RealGreen condition codes into an automated upsell machine

We've written the general case before, the revenue hiding in your technicians' job notes, and the math holds for any system. This one is the nuts-and-bolts version for companies on RealGreen: how to set the codes up, the taxonomy that works, how to get techs logging, and how to measure whether the machine is actually making money.

Why RealGreen shops start with an advantage

Condition codes are native to Service Assistant: your techs already have a device in their hands at every stop, and the code lands on the visit record attached to the customer and the property. There's no new app to deploy and no new habit more complicated than a couple of taps. The gap at most companies isn't capture; it's that the codes go nowhere. They print on a route sheet or an invoice, and that's the end of the story. The whole opportunity is in what happens after the tap.

Setting up codes automation can actually use

Details vary a little by version and configuration, but the principles don't:

• Keep the list to 5–8 codes. Many RealGreen instances have accumulated dozens over the years. Techs scroll past long lists; prune ruthlessly.
• One code, one meaning, one service. "LAWN-ISSUES" is unusable. "GRUBS" maps cleanly to a grub application at a knowable price.
• Name them for the observation, not the sale. Techs log what they see. "PATCHY-TURF" gets tapped; "SELL-AERATION" feels like being turned into a salesman and quietly doesn't.
• Make them part of visit close-out. The tech confirms the application, then answers one implicit question: anything worth flagging? Ten seconds.
• Confirm they sync. If you're automating, codes need to flow out of RealGreen nightly, see the replication pattern, not live only on printed route sheets.

The taxonomy that works

For a fertilization-first company, five codes cover most of the money (prices illustrative, use your matrix):

• PATCHY-TURF → aeration + overseeding. The workhorse: $300–$400 average ticket, best flagged spring and late summer for the fall push.
• GRUBS → grub control, $120–$180. Time-sensitive: same-day quoting matters most here, because the evidence is dying in the customer's yard.
• WEEDS-BEDS → bed weed control program. Easy add-on for customers who already trust you with the turf.
• TREE-SHRUB → tree & shrub program, often 5–6 visits at $60–$90 each, recurring revenue, not a one-off.
• SPRINKLER-ISSUE → irrigation inspection/repair, whether you self-perform or partner.

Add one or two for your specific menu (mosquito, perimeter pest), but hold the line on list length. Every code you add makes every other code slightly less likely to get logged.

Getting techs to log them

We covered the incentives playbook in the general article: two taps max, a $5–15 spiff per flag that converts, a leaderboard, and reading the revenue number back to the crew monthly. The RealGreen-specific addition: audit in the system. Pull flags per tech per 100 visits quarterly. A tech at 0% isn't looking; a tech at 40% with no conversions is spraying flags for the spiff. Both are coaching conversations, not software problems.

The automated quote flow

Here's the full path from tap to booked job, the way our RealGreen automations run it:

1. Overnight sync pulls yesterday's condition codes out of RealGreen into the marketing platform (replicated data, so API limits never throttle it).
2. Code → service match. PATCHY-TURF resolves to your aeration/overseed offering.
3. Measure and price. The property is measured via DeepLawn and run through your pricing matrix, the customer's real price for their real lawn, not "starting at."
4. The quote goes out by text and email, branded, framed as the tech's observation: "Miguel noticed some thinning turf during Tuesday's visit. Here's what fall aeration and overseeding would run for your lawn." Good/better/best, accept-and-pay in two taps, the same engine as our instant quotes.
5. Follow-up runs ~21 days until it books or declines, and the outcome writes back to RealGreen.

The customer gets the quote while the truck tracks are still visible on the lawn. That timing is the difference between "your technician noticed this today" and a postcard.

Measuring flag-to-close

Four numbers on one weekly report tell you everything:

• Flag rate = flags ÷ visits. Healthy is roughly 5–12%. Lower means techs aren't looking; much higher means codes are getting spammed.
• Quote rate = quotes sent ÷ flags. If automated, this should be ~100% within 24 hours. If it's not, the plumbing is broken.
• Close rate = booked ÷ quoted. 20–30% is a realistic target for warm, evidence-based offers to existing customers.
• Revenue per flag = close rate × average ticket. At 25% × $340, every flag is worth ~$85, which reframes tech adoption nicely: each tap is an $85 lottery ticket that hits one time in four.

Worked season (illustrative): 1,200 customers × 6 visits = 7,200 visits; 8% flag rate = 576 flags; 576 quotes; 25% close = 144 jobs; at $340 that's ~$49,000, plus the tree & shrub and grub programs that renew next year.

When a number is low, it tells you which lever to pull

The beauty of four metrics is that each failure mode has an address:

• Flag rate under 5%? A field problem. Ride along, re-brief the crew, check that the code list is short and visible at close-out, and make sure the spiff is actually being paid.
• Quote rate under ~95%? A plumbing problem. Codes aren't syncing, a mapping is broken, or properties are failing to measure. This should be fixed the week you see it: every unquoted flag is a tech's effort thrown away.
• Close rate under 15%? A sales problem: pricing out of line for the market, weak framing (lead with the tech's observation, not the discount), or follow-up ending too early. Test one change at a time.
• All three healthy but revenue flat? A mix problem: techs are flagging only the small-ticket codes. Coach toward the recurring-program flags like tree & shrub, where one close is worth six visits a year.

The takeaway: RealGreen already captures the observation. The upsell machine is everything downstream (mapping, measuring, pricing, sending, and following up) and none of it should require a human in the office.

Set it up this week

1. Prune your condition-code list to the five that map to priced services.
2. Confirm codes sync out of RealGreen nightly.
3. Load your pricing matrix so quotes price themselves.
4. Brief the crew: two taps at close-out, spiff on conversion.
5. Stand up the weekly flag → quote → close → revenue report.