Field-Service Software Living on the Technician’s Phone

The software worth studying in this category does not live in an executive suite. It lives in the door pocket of a service van, gets dropped on gravel driveways, gets smeared with grease, and is opened twenty times a day by someone wearing work boots. Trade-press surveys put roughly seventy percent of field technicians running the entire workday off a mobile device as their primary tool. That is the operating environment, and it decides everything downstream: in that environment vertical software either becomes infrastructure or gets deleted.

The Cracked Screen on the Dash

The day is paced by work orders. When a technician arrives at a job, the app is the first thing they touch. If it takes five taps to log a diagnostic reading, or if it loses its connection in a basement, the technician stops using it. They revert to a grease pencil and a scrap of cardboard, and the dispatcher spends the afternoon trying to find them.

So the product that wins is the one that removes friction from the workday rather than the one that renders the prettiest chart. The directional numbers, which come from vendors and trade press rather than audited studies, run in one consistent direction: paper-based technicians burn something like six hours a week each on administrative work, and roughly seventy-three percent of technicians name paperwork as their leading daily frustration. Voice-to-form entry is reported to complete that paperwork about thirty-five percent faster. Run the arithmetic on a single technician and you get somewhere around two hours a week back, which the owner experiences as capacity rather than as a feature. Treat all of these figures as directional. They point the same way, which is the most you can ask of a vendor statistic.

The Retention Anomaly

Small-business software is a difficult market to hold. A SaaS-focused lender calls seventy-five to eighty percent gross revenue retention quite strong when you are selling to small businesses — fickle customers, owner-driven decisions, high underlying failure rates — against ninety percent and up when selling to banks and insurers. Median net revenue retention for the sub-$25,000-ACV segment sits around ninety-seven percent, which means the median company selling to small businesses shrinks inside its own base before it sells anything new.

Vertical field-service platforms report numbers that do not belong to that segment. ServiceTitan's S-1 discloses net dollar retention above one hundred and ten percent for each of the last ten fiscal quarters and gross retention above ninety-five percent over the same window. That disclosure is contested: at least one analyst argues that once the quarterly figure is annualized it normalizes closer to eighty-one and a half percent — and lower still, since the disclosed metric counts only customers who churn to zero and ignores partial downsells — a gap of roughly thirteen points that is entirely definitional, not a dispute about the business. They also call eighty-one and a half percent "entirely believable and altogether fine" for the trades, which it is.

Take the lower number and the claim narrows. Vertical SaaS gross retention averages around ninety-one percent, fintech-led vertical SaaS around ninety-six — so eighty-one and a half percent is not an anomaly against that cohort, it is ordinary. The anomaly is only against the small-business baseline of seventy-five to eighty percent, which is the right comparison for a base made of local plumbers and electrical contractors. The distance between the small-business baseline and the observed number is the depth of the switching cost, and it is worth knowing which methodology produced any retention figure before you admire it.

The Retraining Tax

The barrier is a coordination cost, not a technical one. If a contractor wants to move from one field-service tool to another, the license fee is the smallest line in the calculation. The user base is not three analysts at head office; it is every dispatcher and every technician, retrained simultaneously. That cost scales with headcount and turnover, not with seat price.

Work a hypothetical. A business with ten service vans has ten technicians and two dispatchers. Switching platforms means halting the schedule, bringing the crew off the road, and teaching twelve people a new system. Assume, for the sake of the arithmetic, sixty dollars an hour of billable revenue per technician and a single lost week: call it twenty-odd thousand dollars of foregone capacity, paid in cash, in one quarter, for a benefit that arrives later if it arrives. This analysis has no sourced figure for what that week actually costs across the industry, and the number moves with the trade and the region. The direction is what matters. The owner will tolerate a mediocre product, rising prices, and indifferent support for a long time before writing that cheque.

The Payments Pipeline

The stickiest field software processes the money as well as the calls. Once a trades business runs estimating, job costing, invoicing, payments, and payroll through one platform, the tool is holding how the business gets paid and how it pays people. Jobber syncs approved timesheets into QuickBooks Online and runs payroll through Gusto. ServiceTitan's core spans call tracking, scheduling, dispatch, estimating, job costing, inventory, and payroll integration.

The scale of that plumbing is the part institutions did notice. Roughly sixty-two billion dollars of gross transaction volume moved through ServiceTitan in the trailing twelve months, with the company capturing about one percent of that volume as revenue overall and something like a quarter of a percent on the payments-processing slice specifically. Both figures are analyst-derived from the S-1 rather than lifted from a headline number in it. Note the second engine hiding in there: because the take rate rides on the customer's transaction volume, vendor revenue grows without anyone raising a seat price. A pure per-seat scheduling tool has no equivalent.

Removing a system that sits between a business and its bank account is a different operation from swapping a CRM. The fear of a missed payroll run is a stronger barrier to exit than any contract term, because a contract can be breached and a payroll cannot be un-missed.

Sizing the Tail

None of the above is a secret. The bellwether went public in December 2024, grew revenue to roughly $961 million in FY2026, and is covered, owned, and priced by people whose job it is to price exactly this. The stickiness is real and it is already in the number. There is no capacity-constrained inefficiency in a multi-hundred-million-dollar-revenue software company that institutions can buy in size.

The tail is a different question, and a narrower one than it looks. Vertical benchmark data suggests the barrier requires density within a vertical rather than mere presence — a tool at five percent penetration of its niche does not carry the embedded switching costs of one at thirty or forty. That density requirement is the fence. It keeps large players out of the smallest, most fragmented niches, because winning them requires knowing the specific language of rotating-shift clinic staffing or single-trade dispatch and cannot be bought with advertising. Field adoption is not a channel you can scale by spending money on it.

Which is also the honest capacity read. The same smallness that keeps the institutions out caps what you can deploy and thins the buyer pool for the asset itself. There is no sourced answer to how small a high-retention niche tool can be and still support a purchase — that is an open empirical question, not a solved one, and anyone who tells you the number is estimating. At minimum, a framework which locates the edge precisely where the data runs out is a convenient one.

What the Habit Actually Proves

The benchmark literature marks a business-to-business tool as part of a regular workflow when daily actives run above twenty percent of monthly actives, and calls thirty percent and up strong stickiness. An app opened at every job, every day, sits at the top of that range by construction. The technician taps the same screen at every stop because the paycheck depends on it, and that repetition is the asset — not the feature list, not the dashboard, not the roadmap.

The weakness in the argument is that habit is measured after the fact. Retention data tells you a tool was hard to remove last year; it cannot tell you the price at which owning that fact stops being worth it. Muscle memory is very difficult to destroy and completely indifferent to what you paid for it.