Field service software marketing has collapsed three different products into one phrase: "turn voice into money." They are not the same product. They operate at different points in the job lifecycle, solve different problems, and produce different outcomes. Here is the clean distinction.
Voice-to-invoice: after the work
Voice-to-invoice tools operate at the end of a completed job. The technician describes work already performed, and the tool formats it into a bill. The revenue already exists; the tool accelerates collecting it. The problem it solves is paperwork speed. The measure of success is how fast an invoice goes out.
Voice-to-estimate: during the sale
Voice-to-estimate tools operate mid-visit, on work the customer already asked about. The technician dictates a quote instead of typing one. The opportunity already exists; the tool accelerates pricing it. The problem it solves is quoting speed. The measure of success is estimates delivered before the tech leaves the driveway.
Revenue recovery: before anything exists
Revenue recovery operates on work nobody asked about. A technician notices something on site: a component near failure, equipment past its service life, a code issue. It's not on the work order and no one requested a quote. The technician records a voice memo, the observation becomes a structured, priced recommendation, a human operator reviews it, and only then does it enter the field service platform as a draft estimate. The revenue did not exist anywhere in the system until the memo. The problem it solves is silent revenue loss. The measure of success is recovered revenue attributed to the technician who found it.
The one-sentence test
Ask where the money was before the technician spoke. If it was on a finished work order, you're looking at voice-to-invoice. If it was in a customer request, voice-to-estimate. If it was nowhere at all, revenue recovery.
Why the distinction matters when buying
A shop losing revenue to slow billing needs voice-to-invoice. A shop losing bids to slow quoting needs voice-to-estimate. A shop whose technicians see fixable problems every day that never become quotes needs revenue recovery, and neither of the other two categories will fix that, because both start from an opportunity that already exists.
Mentat is a revenue recovery platform. It rides on top of the FSM you already run, is never the system of record, and puts an operator review between every technician observation and anything customer-facing.
FAQ
Can one tool do all three? Some tools bundle invoicing and estimating. Revenue recovery is structurally different because it starts before any record exists, and requires a review-and-attribution loop the other two don't have.
Is revenue recovery just upselling? No. Upselling pitches additions to work being sold. Revenue recovery documents observed conditions, prices them, and routes them through human review into the FSM as drafts. Nothing is pitched automatically.
Does revenue recovery replace the FSM? No. It writes draft estimates into the FSM, which remains the system of record.