If your app is under 4 stars, your AI roadmap is a distraction

Most field-service SaaS roadmaps I see this year have an AI line on them. So I went looking for proof that AI is what customers want.

In September I read 691 reviews of seven field-service platforms: every one- and two-star review I could reach on Capterra, G2 and Software Advice (224 of them), plus 467 positive ones. I tagged each review by what it was about. Then I pulled App Store ratings for twelve technician-facing apps, since the person in the field rarely writes a review on G2.

AI came up nine times in 691 reviews. That's 1.3% of the angry reviews and 1.3% of the happy ones. As far as these customers are concerned, AI has nothing to do with how they feel about the product.

And of the three negative reviews that mentioned AI, two were complaints about it. One two-star reviewer put it plainly: "it should not be the primary focus until the basics are ironed out first."

The two-star gap

The category leader averages 4.5 on G2 and Capterra. Its technician app sits at 2.94 in the App Store, across 1,650 ratings.

That's one product with two ratings. The 4.5 comes from an owner or office manager at a desk, using the web version, who signed the contract. The 2.94 comes from a tech on a phone with one bar of signal, who never chose the software and can't leave it. Vendors build for whoever signs, so the product wears out from the field end first.

Nine of the twelve technician apps I checked are under 4 stars.

App Store ratings, 12 technician-facing field-service apps

Ratings as shown in the Apple App Store on September 15, 2026. Highlighted bars are under 4 stars.

What each side complains about

On the buyer sites, owners are angriest about the company behind the software. Price and contracts show up in 43.8% of negative reviews, and more of those are about leaving than about price: cancellations that drag on for months, cards still getting charged after the account is closed. The most common specific complaint is onboarding, at 21.9%. Bad training and a messy data import, or a product that didn't match the demo. Only about a fifth of angry buyer reviews say the software itself breaks.

In the App Store, where techs write, crashes are the number one complaint at 21.4%. Slowness comes in at 11.9% and offline problems at 4.8%, against almost nothing on the buyer sites. Nobody at a desk loses signal halfway through an invoice.

Lost data is rare (7.1% of negative buyer reviews), and it's the angriest complaint by far. Those are the reviews with dollar figures in them: thousands of dollars of invoices gone, or thousands of customer records lost in an import.

The vocabulary tells you something too. Nobody writes "mobile experience" or "technical debt." Owners write about lost work, wasted hours and what it costs to get out. One owner on a trade forum priced a login bug in payroll, because every tech is on the clock while the app makes them log in again.

Your G2 score is the office's opinion. Your App Store score is the field's. If that second number is under 4, your techs are telling you something.

What a contractor wants from your software

The list is short:

It opens fast and doesn't crash. A tech standing at a customer's door won't wait on a spinner.
It never loses their data. Job notes, photos, signatures, the invoice. If they typed it in a dead zone, it should still be there when they get signal back.
A new tech can figure it out on day one without a training video.
It gets the job done faster than the clipboard did, and sends them home earlier.
And on a good day, they might even enjoy using it.

Look, that's a low bar. Plenty of apps in this space still trip over it, and no AI feature makes up for an app that crashes on the job.

Put a number on each of those

Every item on that list maps to something your team can measure. If nobody can hand you these numbers, start there.

Crash-free sessions. Crashlytics, Sentry, and both app store consoles report it. Ask for the 90-day trend, split by iOS and Android.
Lost-work tickets. Have support tag every ticket where a customer lost data. The target is zero, and each one deserves a real postmortem.
Time to first job. How long from the day a new tech gets invited to their first completed job without calling the office?
Time to close out a job, from arriving on site to invoice sent. It should drop release over release.
Your App Store rating, tracked separately from G2. The average moves slowly. The newest reviews tell you what the last release broke.

Why AI can't cover for a shaky app

AI features run on the same data your app collects. If job notes vanish during a sync, the AI summary of that job is built on half the story. A customer who catches one wrong summary stops trusting all of them.

New features also add weight to an app that's already struggling. Each AI feature shipped on top of a crashing app is one more thing for customers to hit, and one more thing your team supports instead of fixing the crash.

AI can also land badly with the people in the field. The biggest vendor thread of the year on r/HVAC, at roughly 205 upvotes, was a technician warning other techs that a major vendor was rolling out AI that records and scores them on the job. Crews read that as surveillance. A crew that distrusts the app finds reasons not to open it.

And the tech in the driveway is grading you on one question: did the invoice save?

Plenty of companies live with a bad app

Customers complain for years and stay, because switching costs more than suffering. The category leader runs a 2.94 app and it's doing fine.

One two-star reviewer said the only reason they stay with their vendor is that it holds years of their data and switching is hard. That's loyalty with a hostage. It lasts right up until a competitor makes the move easy.

The math changes when the app starts showing up in the P&L: support tickets climbing every quarter, or customers who name the app when they cancel. I've been on that side of it.

How we took an app from 2.5 stars to 4.8

I helped take a field-service app from 2.5 stars to 4.8. Customers didn't like the old one, and they said so in every review.

The old app was built in Ionic, one of the frameworks that promise you can write a mobile app once and run it everywhere, so you never have to build real native apps. In practice it made the app hard to work on, and the app looked and ran slow and clunky on the phones techs carry. The team decided a full rewrite as native iOS and Android apps was the only real fix.

Write-once-run-anywhere is tempting, since one codebase sounds cheaper than two. For the app a tech depends on all day in the field, it's rarely worth it.

A rewrite is still a big bet, and the research shows how it goes wrong. The bottom four apps in my App Store sample all recently shipped a ground-up rewrite or changed owners. One announced an end-of-support date and moved customers onto a replacement that wasn't ready. It sits at 1.46 and hasn't recovered.

Ours paid off. It took about a year with a team of six, and this was before AI coding tools.

We interviewed customers before writing a line of code and kept interviewing them the whole way through. They got early builds to test long before anything was polished, so the feedback arrived while it was still cheap to act on.

Real design time went into how the app felt to use.

We built it to run offline with zero data loss. Every job saves to the phone first and syncs when the signal comes back. Losing a job in a dead zone is what drives 1-star reviews, so we treated it as the one thing that could never happen.

And the old app stayed up while customers moved over. We tracked adoption and how users rated the new app, and we retired the old one only after the new app covered every feature and most customers had already switched. Nobody got pushed onto something that wasn't ready.

It became the company's biggest differentiator. It helped win new customers and kept existing ones from leaving, and customers brought up the mobile app constantly as the reason they stayed or the reason they switched.

If you're planning a rewrite, decide how the old app retires before you start, and tie it to usage instead of a date on the calendar.

Read your own 1-star reviews this week

This takes an afternoon and costs nothing.

Pull the last 90 days of reviews from the App Store and Google Play, and separately from G2 and Capterra. Give each one a tag for what it's about: crash, slow, offline, lost data, onboarding, contract or billing, support, missing feature, AI. Then count.

If crashes and lost data top the app store list, you've got next quarter's roadmap. If onboarding and contracts top the buyer list, that's a company problem, and AI won't fix it either. If customers like the app and they're asking it to do more for them, that's your green light for AI.

Read a few at your next leadership meeting, too. A tech's lost day of work hits differently when someone in the room has to say it out loud.

Where AI fits once the app works

AI has real uses in field service. A few that fit naturally:

Turning a tech's voice memo into clean job notes, so nobody types on a phone screen in work gloves.
Drafting the estimate or invoice from photos and the job history.
Smarter scheduling and routing for the office.
A quick summary of the customer's history before the tech knocks on the door.

The one owner in my research who asked for AI wanted an AI receptionist. He has no time to train and oversee a person, and he said he'd pay a premium to skip it. That's the kind of AI customers buy: it takes a job off the owner's plate. AI that watches the crew adds a new worry instead.

Every one of those uses depends on an app that captures data reliably. Ship them once the app works.

So, when did you last read your own 1-star reviews?

About the data. The 691 reviews cover ServiceTitan, Jobber, Housecall Pro, Service Fusion, Service Autopilot, Workiz and FieldPulse, collected September 24, 2026 from Capterra, G2 and Software Advice and deduplicated across sites. Reviews were tagged by keyword, so the counts measure mentions, and one review can carry several tags. 178 of the 224 negative reviews come from Capterra, which runs vendor-sponsored review campaigns; that probably inflates price and support complaints and understates crashes. The technician figures come from 84 negative App Store reviews. Trade-forum findings come from r/HVAC, LawnSite, HVAC-Talk and ContractorTalk.