There is a specific moment that decides whether a CRM works for a service business, and it does not happen in the office. It happens in a driveway, one-handed, on a phone with 14% battery, while a homeowner waits. If the software is good there, everything downstream works. If it is not, your team builds a shadow system of texts and photos and the CRM becomes a place where the office types things in later.
Kaizen runs in the phone browser — there is nothing to install and nothing to keep updated across twelve devices — but the design constraint is the same either way: the field is not a smaller desktop. It is a different job.
A missed call answers itself in 90 seconds — while she is still holding the phone.
Built on the truck, sent before you pull away, with the chase already scheduled.
Photos and notes land on the customer record, not in someone's camera roll.
Invoice, review request, and next spring's tune-up — all without a Monday to-do list.
Five things that decide whether crews use it
- 01The whole job is three taps from open
A technician standing at a door has a working memory of about one screen. If arriving at the customer record takes a search, two menus, and a tab, they will text the office instead. The jobs for today, the customer, and the last thing that happened to them should be the first screen, not a destination.
- 02It behaves when the signal does not
Basements, crawlspaces, mechanical rooms, the far side of a commercial building. Software that loses a note written in a dead zone gets abandoned after exactly one incident, and it never gets a second chance.
- 03Photos land on the record, not the camera roll
This is the difference between a photo and an asset. A picture of a bulging capacitor in someone's camera roll is a private observation. The same picture attached to the customer record is a quote the office can send by lunch, evidence in an insurance claim, and context for whoever takes the next call.
- 04A quote can be built and sent before you pull away
Every hour between the visit and the quote costs conversion. Building it on-site — with the photos already attached and the follow-up cadence arming itself — collapses that gap to zero and removes an evening of paperwork.
- 05You can take the money on site
Days-to-invoice is one of the largest and most fixable cash-flow drags in service work. Invoicing at completion, from the driveway, routinely collapses a two-week lag to same-day.
The knowledge problem nobody budgets for
The most valuable thing a technician produces on a visit is usually not the repair. It is an observation: the unit is fourteen years old, the panel is at capacity, the homeowner mentioned redoing the upstairs "next spring." That observation is worth thousands and it has a half-life of about four hours.
In most businesses it dies in a van. The tech means to mention it, the day gets long, and by Thursday it is gone. A field CRM that captures it in one tap — and sets the reminder for next March automatically — is not a convenience feature. It is a revenue system dressed as a notes field.
App store download versus browser-based
Both approaches ship real products; the trade-offs are just different, and it is worth knowing which one you are buying.
| Installed app | Browser-based | |
|---|---|---|
| Getting a new hire running | Store download, account, permissions | Send a link |
| Updates | Every device, on its own schedule | Everyone is on the current version |
| Deep hardware access | Stronger (background location, native camera) | Good, and improving |
| Works on the phone they already own | Depends on OS version | Any modern phone |
| Who it suits | Large fleets with managed devices | Teams of 3–20 on personal phones |
For a 3–20 person team where everyone uses their own phone and a seasonal hire starts on Monday, the ability to onboard someone with a link rather than a device-management policy is worth more than most native-only capabilities.
What "unified" means once it is mobile
The point of putting the CRM in the field is not that the field gets software. It is that there stops being a gap between what happened on site and what the business knows. The office sees the photo while the tech is still on the ladder. The customer's next call reaches someone who already knows about the fourteen-year-old unit. Next March's reminder fires without anyone having remembered to set it.
That is the whole promise, and it only holds if the phone is a first-class citizen rather than a stripped-down afterthought.
Common questions
Does Kaizen have a mobile app?
Kaizen runs in the phone browser, so there is nothing to install and every device is automatically on the current version. For a 3–20 person team on personal phones, that means a new hire is working from a link rather than a device-management policy.
What should a field technician be able to do from their phone?
See today's jobs and the full customer history, log notes and photos onto the record, build and send a quote on site, and take payment at completion. If any of those requires calling the office, the field will build a workaround and the record will go stale.
Why do crews stop using field software?
Almost always because it asked for more effort than a text message at the moment of use. Common causes: too many taps to reach the customer, data lost in a dead zone, and photo upload that fails silently. Watch one technician do one job and count how often they reach for their personal phone instead.
Is a browser-based CRM good enough for field work?
For most small and mid-size service teams, yes — and the onboarding and update story is materially better. Large fleets with managed devices and heavy background-location requirements are the case where an installed app still earns its cost.