Services · ServiceM8 partner
Most ServiceM8 partners can implement the platform. We do that, and we also publish add-ons on the ServiceM8 directory, which means we understand where the platform ends and where you need code. Implementation, training, integration, and custom development from one team. Perth-based, working with field-services businesses Australia-wide.
What CCP does
Most ServiceM8 work falls into one of four buckets. We do all four under one engagement, so you are not stitching together an implementation consultant, a trainer, an integration developer, and a third party who builds your add-on.
New to ServiceM8, or finally moving off paper, spreadsheets, or whichever job-management system stopped fitting. We configure the platform around how your business actually works: job categories, forms, templates, badges, scheduling rules, security roles, and the integrations into accounting. You 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. We run targeted sessions for each, in person around Perth or online for everyone else. Recordings included so new hires get the same training six months from now.
Xero, MYOB, Microsoft 365, your CRM, your supplier portals, your dispatch and routing tools. Most are standard. The ones that are not, we build. Either way, the result is data flowing where it needs to, without manual re-entry.
When ServiceM8 does not cover something, we build the add-on. That can be a private add-on just for you, or a published add-on on the ServiceM8 directory if it makes sense to share the build cost across other operators. The Servicing Manager add-on below is one of ours.
The platform underneath
ServiceM8 is the job-management platform we build on. It is Australian, built for trades and field services, and used by operators in over 30 countries. More at www.servicem8.com.
Product images supplied by ServiceM8 Pty Ltd. ServiceM8 is a trademark of ServiceM8 Pty Ltd.
Proof of capability
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 completed jobs should have advanced a schedule but didn't. Customers kept asking. So we built it, published it on the ServiceM8 add-on directory, and run it for businesses that have outgrown 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. You can see at a glance who is overdue, what equipment is involved, and which schedules are linked to a contract instead of charged 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.
AWS Sydney. All add-on data stays in Australia. Backed by point-in-time recovery so we can recover from accidental loss.
Every record is keyed against your ServiceM8 account UUID. We publish a privacy policy specific to the add-on covering exactly what it accesses and stores.
Other tools jam state into ServiceM8 custom fields and then run into the platform's length limits and stripped characters. We do not. The add-on uses its own database.
What we recommend
ServiceM8 is more capable than it looks. A lot of what customers come to us asking to build can be solved with a form template, a job category, a badge rule, or a two-line setting we already know about. We will tell you that before we quote you for code.
A custom add-on is the right answer when:
If your situation isn't one of those, we will say so and configure what ServiceM8 already has. That is faster, cheaper, and doesn't leave you depending on a third party to patch your add-on when the API changes.
How it works
Scoping call.
30 to 45 minutes. We ask what you are trying to do, where ServiceM8 currently helps, where it currently doesn't, and what tools you are juggling around it. No deck. Nothing to sign.
Written recommendation.
Within a week, you get back a one-page recommendation. What we would configure in ServiceM8 itself. What, if anything, we would build. What we would integrate. An indicative range for each piece of work and the order we would do it in.
Configure and train.
We do the implementation work, configure the platform, run training for the team, and migrate any existing data. You sign off each milestone before we move on.
Build the custom pieces, if any.
Where custom code is part of the engagement, we build it after the core platform is configured. That way we know exactly what the add-on needs to do, instead of guessing during a workshop.
Common questions
The qualifier
Seven questions, one moment of your time. We'd rather tell you now than three months in.
