A maintenance tech finishes a spring checkout and drops into the crawlspace to look at the return. There are two things down there worth money. The condensate line is draining into the dirt under the house. The return was never sealed after somebody else's install, and it has been pulling crawlspace air into the system ever since.

Neither one is on the work order. On the way out they mention the condensate line to the homeowner, because that is the one that turns into a real problem first. Then the truck gets loaded and the next call is across town.

Nothing happens after that. No estimate. No follow-up. No note anyone will ever read. The observation was correct, the work was real, and the customer would very likely have bought it. It just never became anything.

That is not a rare day. On most visits a good tech sees something outside the scope of the call, and on most of those visits nothing comes of it. Owners tend to read that as a people problem. It is worth looking harder, because it is not one.

Why do technicians leave revenue on the table?

Because the observation has nowhere to go.

Start with what is actually true about the tech in that crawlspace. They saw the problem. They understood it. They cared enough to tell the homeowner. Nobody was hiding anything, nobody was too shy to bring it up, nobody was indifferent to the company's numbers. They did the hard part, which is knowing what they were looking at.

What did not happen is the part where it becomes a document. Between noticing work and someone quoting work sits a stretch of unpaid, unstructured effort that lands entirely on the busiest person in the company. Remember it. Describe it well enough for an office person to use. Price it, or find someone who can. Type it somewhere a human being will actually see it and act on it. That stretch is where the money goes.

Call it a motivation problem and every fix you try will aim at the wrong target. It is a capture problem.

What happens in the last ten minutes of a visit?

The end of a visit is the worst possible moment to ask a technician for anything.

Tools are going back in the truck. The homeowner is in the doorway with a question about filters. Dispatch has already pushed the next call and it is across town and the morning job ran long, so everybody is behind. Hands are dirty. The phone is in a pocket.

Now ask for a write-up on work nobody requested. That means reconstructing what they saw in language somebody else can use. Guessing at a price, or leaving it blank and hoping the office chases it. Typing all of it on a phone screen in a driveway. And doing it while knowing the most likely outcome is that nothing happens, because that is what happened the last several times.

"Just put it in the notes" sounds like a small ask. From inside the truck it is not small, and techs are very good at telling the difference between work that pays off and work that disappears.

Why don't the usual fixes hold?

Most operators have already tried the obvious things. They tend to fail in the same place.

Sales training teaches the conversation. But the conversation was never the missing piece. The tech in that crawlspace already told the homeowner. What went missing was the record, and no amount of coaching on how to present an option creates one.

Spiffs and commission pay for the outcome, not for the noticing. The tech gets paid if the work sells, which means getting paid for something they do not control, long after the moment that produced it. Incentives work when the reward sits close to the behavior. Here it is far away and mostly in somebody else's hands.

A required recommendations field in the field service system moves the work to the worst moment of the day. So it gets filled the way every mandatory field on a deadline gets filled. "System OK." "Discussed with customer." Technically compliant. Commercially worthless.

Ride-alongs and coaching genuinely work, right up until you get out of the truck. They do not survive the month, they do not scale across branches, and the manager running them has a day job.

The pattern underneath every one of them is the same. Each asks the technician to carry more, and their hands are already full.

What makes upsell revenue so hard to capture in field service?

The fixes fail because the difficulty is structural. Several things are true about this business at once, and together they make the loss close to automatic.

An observation that was never written down cannot be managed. You cannot route it, assign it, follow up on it, or hold anybody accountable for it. It is not a weak lead in your pipeline. It is not in your pipeline.

A tradesperson spots the work. What they lack is a reason to write it down and a way to do it in ten seconds instead of ten minutes. The moment a job wraps, the next call is already waiting, and the thing they noticed goes unspoken. Not because they can't sell it. Because nothing makes capturing it worth the interruption.

The software is built around requested work. Work orders, dispatch, scheduling, invoicing: every one of those descends from a customer asking for something. An unrequested observation has no native home in that model, so it lives in a notes field or it lives nowhere.

And the loop runs too long. Notice something in March, watch it turn into revenue in May, if it turns into anything at all. Nothing in that teaches a technician that noticing is worth the trouble.

Why can't you see how big the problem is?

This is the part that lets it survive quarter after quarter.

You are watching ticket average and it is flat. Flat tells you the number did not move. It does not tell you whether your techs found nothing worth quoting or found plenty and none of it made it out of the driveway. Those two situations look identical on the report and are nothing alike in the business.

Every measurement you have is built out of records. The entire problem is the absence of a record. No report can show you a conversation in a doorway that ended when the truck pulled away. Compare branches and you may see spread worth asking about, and spread is a hint, not proof.

So let's be straight about this. Nobody can tell you what this costs your company. Not us, and not anyone waving a figure at you. The loss is unmeasured because it is uncaptured, and the only honest way to size it is to start capturing it and then look at what shows up. Anyone who hands you a number before that is guessing, and it is fair to ask them how they got it.

How do you capture the work techs notice but never sell?

Capture has to happen at the moment of observation, in the cheapest form the technician can produce. In practice that means speaking, because a tech will talk about a job when they will not type about it. Everything downstream of that, the structuring, the pricing, the write-up, has to be somebody else's job entirely. Get the split right and the observation survives the driveway. Get it wrong and you are back to asking the busiest person in the company to do office work with dirty hands.

One more thing has to be true, which is that credit for the find lands on the tech who made it. Revenue Recovery for Technician Estimates covers how that attribution works.

Where Mentat fits

This is the problem Mentat was built for. Mentat is field service revenue recovery software. It rides on top of the field service system a company already runs, and it is never the system of record: not a field service management system, not a CRM, not a replacement for anything you have. A technician records a short voice memo about what they saw. Mentat structures that memo, prices the work, and drafts the estimate straight back into that same system, where a person on your team reviews it and sends it. Every opportunity carries the name of the technician who spotted it. Today the loop runs against Jobber.

See also

FAQ

Why do technicians leave revenue on the table? Because the observation has nowhere to go. The technician sees the work and often mentions it to the customer, but turning it into a quote means reconstructing it, pricing it, and typing it up at the end of a visit when they are already behind. It is a capture problem, not a motivation problem.

Is this a training problem or a tools problem? Much closer to tools. Training teaches the conversation, and the conversation usually already happened. What is missing is a record of what the technician saw, and training does not produce one.

Why doesn't a required recommendations field in the field service system fix it? Because it puts the work on the technician at the worst moment of the day. Mandatory fields on a deadline get filled with whatever clears them. The field ends up compliant and empty of anything anyone can quote.

How do you capture upsell work a technician notices but never sells? Capture it at the moment they notice it, in the cheapest form they can produce, which is speaking rather than typing. Then make the structuring, pricing, and write-up somebody else's job, so nothing is added to their day.

Does capturing this mean pressuring technicians to sell? No, and it should not. Documenting a condition is not pitching it. The technician reports what they saw, and a person on your team decides what is worth quoting and what is not.