Search for ServiceTitan integrations and you'll find a crowded ecosystem: AI receptionists that answer every call, middleware that syncs your data anywhere, inventory tools, marketing attribution, payment processors. It's a mature marketplace solving a mature set of problems.
Almost all of it shares one assumption: the revenue opportunity already exists somewhere in your system. A call came in. A lead was created. An estimate was written. The tools fight over capturing, routing, and converting demand that has already announced itself.
The revenue that never announces itself
There's a category of revenue no integration in that landscape touches: work your technicians observe on site and never write down.
A tech replacing a capacitor notices the contactor is pitted. A plumber clearing a drain sees a water heater past its service life. An electrician swapping a panel spots aluminum branch wiring. None of it is on the work order. The tech mentions it to the homeowner, maybe, on the way out. Nothing enters ServiceTitan. No estimate, no follow-up, no record it was ever seen.
Call-answering AI can't capture this; there was no call. Estimating tools can't price it; nobody opened an estimate. It dies in the gap between what a technician noticed and what anyone typed.
What revenue recovery means as a category
Revenue recovery is the discipline of capturing observed-but-unquoted work and moving it through review into your FSM as a real estimate. The mechanics that make it work:
Capture has to cost the technician almost nothing. A voice memo, not a form. If it takes typing, it doesn't happen.
Structuring has to be automatic. Transcription plus extraction into priced, urgency-ranked recommendations.
Review has to be human. An operator approves, defers, or declines every item before it becomes customer-facing. Your FSM stays the system of record; recovered work lands as draft estimates inside it, not in a side system.
Attribution has to be visible. When a recovered item converts to won work, the technician who spotted it gets named credit. Attribution is what keeps techs recording memos after week two.
Where Mentat stands with ServiceTitan
Honesty over positioning: Mentat runs this loop on Jobber, where our founding cohort is onboarding now. ServiceTitan is where we're headed, and it's the platform this category arguably matters most for, because ServiceTitan shops run the technician headcounts where unquoted observations compound fastest. We are selecting design partners for the ServiceTitan integration specifically: if you operate ServiceTitan locations and want to shape how revenue recovery works on that platform, we want to talk.
FAQ
Is this the same as an AI receptionist? No. Call capture works on inbound demand. Revenue recovery works on what technicians see in the field, where no call exists.
Is this an estimating tool? No. Estimating tools help price work someone already decided to quote. Revenue recovery surfaces work nobody was going to quote at all.
Does it replace the FSM? Never. The FSM remains the system of record; recovered work arrives as draft estimates inside it.
What does Mentat integrate with today? Jobber, with our founding cohort onboarding now. Signup is at mentathq.com. ServiceTitan is our strategic target, and design partner selection is open for the ServiceTitan integration only.