ServiceM8 is the friendly one: a public API, real documentation, an add-on marketplace, and a price small trade businesses can love. The reviews still carry wishes, and they’re specific: the field app is Apple-only (“the Android does NOT work for this,” as one reviewer put it after buying five Android phones), there’s nowhere to record “where did you find us?” and report on it monthly, the invoice and quote documents resist customization, and follow-up depends on memory. On a platform this open, every one of those is a build. Five of them, pictured.
The Android companion ServiceM8 never shipped
The public API means the field view doesn’t have to live inside the Apple-only app. A web companion runs on any phone the crew already carries: today’s jobs, checklists, photo capture, all syncing straight back to ServiceM8. The office changes nothing; the Android crew stops borrowing iPhones.
Finally answer “where did you find us?”
One reviewer’s exact frustration: they ask every customer the question and have nowhere to put the answer that produces a monthly report. One added field at booking, captured to a layer you own, and advertising decisions get made on revenue instead of vibes.
Quotes and invoices in your own layout
Reviewers call the documents clunky, and documents are what customers actually see. Generated from the ServiceM8 job through the API, the quote becomes your layout, your language, your photos, one click.
Quotes that follow themselves up
A quote with no reply after five days is the most valuable trigger in a trade business. An automation watches for the silence and queues your follow-up, in your wording, stopping the moment they book or decline. Nothing depends on anyone remembering.
Your history, mirrored to storage you own
Years of jobs, photos, and invoices deserve a copy that lives on your side: a nightly mirror through the public API, organized by year and client, durable on its own schedule, whatever your subscription does next. Owning your data is a habit, and this is the cheapest place to start it.
The common thread
ServiceM8’s openness makes these the small end of the shelf, with timelines in days. The platform keeps doing what it’s good at, and the gaps stop being gaps. If the Android one made your shoulders drop, you’re who it was pictured for.
Have a project like this in mind?
Describe it in a sentence or two and I’ll tell you what it would run, how long it would take, and whether it’s worth building at all. No pressure either way.