Set up around your jobs, your forms and your accounting, with your staff trained on it. Where the platform runs out, we write the add-on. We publish one on the ServiceM8 directory ourselves, so we know where configuration stops and code starts. Perth-based, working with field-services businesses Australia-wide.
One engagement, one team
You are not stitching together an implementation consultant, a trainer, an integration developer and a separate shop for the add-on. All four sit in one engagement, with one team accountable for the lot.
The platform underneath
ServiceM8 is the job-management platform underneath all of this. Australian-built, made for trades and field services, and used by operators in over 30 countries. More at www.servicem8.com.
New to ServiceM8, or moving off paper, spreadsheets, or a job-management system that stopped fitting. You get job categories, forms, templates, badges, scheduling rules and security roles built around your actual work, plus the link into your accounting. Go live with a system you understand, not one you have to reverse-engineer later.
Field staff learn differently to office staff, and both learn differently to the owner. Each group gets its own session, in person around Perth or online everywhere else. Recordings come with it, so a new hire six months from now gets the same training.
Xero, MYOB, Microsoft 365, your customer database, supplier portals, dispatch and routing tools. Most connect with what is already there. The ones that do not, we build. Either way your data lands where it belongs, with nobody re-typing it.
When ServiceM8 does not cover something, we build the add-on. It can be private, installable only on your account. Or published on the ServiceM8 directory, where it makes sense to share the build cost with other operators who want the same thing. Servicing Manager below is one of ours.
Product images supplied by ServiceM8 Pty Ltd. ServiceM8 is a trademark of ServiceM8 Pty Ltd.
Recurring maintenance work
ServiceM8 is excellent at one-off jobs. Recurring service contracts and maintenance plans are harder. Who is due, who is overdue, who is up for billing, and which finished jobs should have advanced a schedule and did not. Customers kept asking for it. We built it, published it on the ServiceM8 add-on directory, and run it for businesses that outgrew the spreadsheet.
The dashboard
Two questions, answered at a glance. What service work is due in the next four weeks. What contracts are up for billing in the next two. Click into either to bulk-create jobs or bulk-bill the lot.
Schedules across every customer
Every recurring schedule on your account, filterable and sortable. One screen shows who is overdue, what equipment is involved, and which schedules bill to a contract instead of per visit.
Inside the ServiceM8 customer card
A read-only servicing summary inside every customer record in ServiceM8. Your staff see the same information without leaving the workflow they already know.
Amazon Web Services in Sydney. All add-on data stays in Australia. Point-in-time recovery sits behind it, so a record deleted by accident can be restored.
Every record is keyed to your ServiceM8 account UUID, so no other business can reach your data. The add-on has its own privacy policy covering what it reads and stores.
Other tools cram their own data into ServiceM8 custom fields, then hit the platform's length limits and stripped characters. Ours keeps its data in its own database.
Configuration first
ServiceM8 is more capable than it looks. A lot of what people ask us to build turns out to be a form template, a job category, a badge rule or a setting. You hear that from us before you get a quote for code.
A custom add-on is the right answer when:
If none of those fit, we configure what ServiceM8 already has and tell you so. Faster, cheaper, and no third party to chase when the platform changes underneath you.
How it works
Scoping call.
30 to 45 minutes. We ask what you are trying to do, where ServiceM8 helps today, where it does not, and what tools you juggle around it. No deck. Nothing to sign.
Written recommendation.
Within a week you get a one-page recommendation. What to configure in ServiceM8 itself, what to integrate, and what, if anything, needs building. An indicative price range for each piece, and the order we would do them in.
Configure and train.
We configure the platform, migrate your existing data and train the team. You sign off each milestone before we move to the next one.
Build the custom pieces, if any.
Custom code comes last, after the core platform is configured. By then the add-on's job is obvious, instead of something guessed at in a workshop.
Common questions
The qualifier
Seven questions, one moment of your time. We'd rather tell you now than three months in.
