Field service software without a mobile app — yes, it exists. Here's why every other platform forces one.

What the 1-star reviews actually say

The #1 complaint isn't features. It's apps that don't work.

Most service-trade-software marketing talks about feature gaps. Look at the actual 1-star reviews across ServiceTitan, Jobber, Housecall Pro, FieldEdge, Workiz, and Service Fusion — and the dominant complaint isn't "missing features." It's catastrophic in-field reliability collapse. The thing they sold as the centerpiece of their product is the thing breaking on real job sites.

What "reliability collapse" actually looks like

• Apps that won't open on the first job of the morning — the tech force-quits, re-launches three times, gives up, calls dispatch
• Back buttons broken for months (Service Fusion BBB complaints document this for 3+ months at a stretch)
• Sticky keyboards (FieldEdge reviews repeatedly describe keyboard input failing during invoice entry)
• Photo uploads that silently fail on weak job-site connectivity — the photo SHOWS as uploaded, but it's not, and the customer's closeout packet ships without it
• "Update required to continue" popups at 7:01am when the tech is trying to start his first call
• Background battery drain that turns a 100%-charge phone into 12% by lunch
• GPS that pings the office every 30 seconds because the app refuses to respect the user's location-permission settings

The owner's marketing pitch was "real-time dispatcher visibility." What actually arrives at the dispatcher screen is fiction — because the tech in the field can't open the app, or did, but it crashed, or did, and the data didn't sync. The dispatcher is making decisions on a screen that hasn't matched reality since Tuesday.

The 30-40% failure rate is real — and it's adoption, not technology

Industry data: roughly 30–40% of FSM platform rollouts fail because the crew refuses to adopt the mobile app. This isn't a marketing-friendly story so the vendors don't talk about it, but it's the dominant single failure mode of FSM implementations. Senior techs over 50 flatly will not download anything for work. Younger techs download it, use it for two weeks, then quietly stop. The data quality collapses. The dispatcher screen lies. The owner's $30K/year subscription is paying for a system whose central premise no longer holds.

OpsLight's wedge is that we accept this reality and design around it. We removed the failure mode entirely. The crew never installs anything. The owner's data quality is determined by the owner's intake channels (voicemail, SMS, email, form) classified by Claude — not by whether the techs entered job notes correctly on a 4.7-inch screen in a customer's basement.

How OpsLight replaces every app function with something simpler

The thing the app was supposed to do — and what we use instead.

1. Crew clock-in/out → SMS

Tech texts IN J-1248 on arrival, OUT J-1248 done, billed 4 hr, needs follow-up filter on departure. Claude parses, timestamps, writes to the Sheet. Owner sees crew positions in the 7am Game Plan email. No app install, no login, no tapping through screens with cold hands in winter.

2. Dispatcher screen → Daily Game Plan email

Every legacy FSM platform's centerpiece is the dispatcher screen. The whole product is built around it. OpsLight inverts: instead of one big screen the dispatcher stares at all day, the owner gets a Game Plan email at 7am — active jobs ranked by start time, crew assignments, urgent intake from overnight, week-ahead view. Print it. Forward it. Run the morning meeting off it.

3. Job photos → text attachments to company number

Tech texts the company number with a photo. Claude reads the message, attaches the photo to the right project record. No "upload via app" failure mode. The MMS infrastructure has been running reliably for 20+ years; the app version of this stops working when AT&T pushes an OS update Tuesday morning.

4. Customer signature on invoice → email + Stripe link

Closeout packet emails to the customer with a Stripe payment link. Customer pays or e-signs from their own phone using infrastructure they already trust. No "have the customer install our app." No "customer can't figure out how to sign on the tech's phone."

5. Owner real-time dashboard → owner's existing inbox + Sheet

The Game Plan email lands in the inbox the owner already lives in. Urgent intakes trigger SMS to the owner's phone using their existing texting app (not ours). The Google Sheet that IS the database can be opened on any phone or laptop browser. The owner doesn't install anything either. We didn't add a new tool — we organized the ones already in their day.

6. Route optimization → Google Maps link inside the Game Plan

Legacy FSM platforms charge for "route optimization" as a feature module. For a 1-15 person shop, the owner is the dispatcher and route planning happens in their head. The Game Plan email includes a Google Maps link with stops auto-ordered by start time and zip — open it once at 6:45am, share it to the crew's group text. Same result, zero per-seat feature tax. No CRM. No work-order management module. The Sheet IS the work-order log; QuickBooks integration is a one-click CSV export at month-end. E-signatures go through the customer's email, not an app upload.

7. "Offline mode" → SMS, which has always worked offline

FSM platforms advertise "offline mode with auto-sync" as a feature. The reality: an app that works offline still needs to be open, logged in, and not crashed. SMS works whether the phone has 1 bar, no signal until later, or the tech put it in the truck. The SMS retry mechanism predates the app store by 20 years. We didn't have to build offline mode — we picked a transport that already had it.

Common questions

What operators ask about the no-app commitment.