ServiceM8

ServiceM8 is a cloud-based job management platform for trade contractors and mobile service businesses. It covers the complete job lifecycle: receiving enquiries, creating quotes, scheduling and dispatching staff, tracking job progress in the field, completing digital forms, capturing photos, invoicing, and accepting payments via Stripe.

The target market is small trade businesses with roughly 1 to 30 staff: electricians, plumbers, locksmiths, HVAC technicians, cleaners, pest control, and similar. Core features include job cards and history, a scheduling and dispatch board, GPS staff tracking, client CRM, digital forms and checklists, asset management, materials tracking, invoicing, SMS and email communications, an online customer booking portal, recurring jobs, and reporting.

ServiceM8 is iOS-native first. The full feature set is available on iPhone and iPad, with a web interface for office and admin work. An Android app exists but it's intentionally limited to basic job viewing and status updates for field technicians. Time tracking, most add-ons, and management functions are iOS-only. Companies with mixed device fleets will have an uneven experience.

ServiceM8 uses flat monthly pricing based on job volume, not per user. All plans include unlimited users, which is a genuine differentiator versus competitors that charge per seat.

There's a Free plan for evaluation, then tiers starting at $9/month for 15 jobs (Lite) up to $349/month for 1,500+ jobs (Premium Plus). The mid-range Growing plan at $79/month covers 150 jobs and unlocks the more useful features like digital forms, asset management, and proposals. No contracts, no setup fees, cancel any time.

The job-based pricing works well for businesses with predictable volumes. If you do many small, quick jobs you could find yourself pushing into higher tiers faster than expected. Some add-ons like Advanced Reporting carry extra monthly fees on top of the base plan.

Lock-in risk is moderate. Your core job data, client records, and invoice history are accessible via the API and CSV exports, so nothing is truly trapped. But leaving ServiceM8 requires meaningful effort.

The backup file can't be imported into another system, so migration means building custom extraction scripts or manually exporting data type by type. Digital forms, job templates, automation rules, and custom field configurations are platform-specific and would need rebuilding from scratch.

Photos and file attachments on jobs require separate handling to export at scale. And if your team switched to iPhones specifically for ServiceM8 (which the company actively encourages), moving to an Android-native competitor becomes a hardware conversation as well as a software one.

ServiceM8 was founded in 2009 by Kim Ford and his son Ben Ford in Darwin, Northern Territory. Kim had retired from corporate IT, bought a locksmith business, and found the existing field service software lacking. Ben built the first version and the product launched in 2010.

The company is entirely bootstrapped with no external funding. It's privately held, headquartered in Darwin, with about 24 staff spread across several countries. Despite its small size, it was recognised in Deloitte's Technology Fast 50 in 2020 with 248% revenue growth over three years. The platform has processed over 50 million jobs representing $50 billion in billings across 40+ countries.

ServiceM8 has won Xero's Small Business App of the Year twice, including in 2023. Kim Ford continues as CEO. Annual revenue is estimated at around $3.8 million USD, reflecting its intentional focus on the small-business market rather than enterprise clients.

Longevity outlook is solid. Fifteen years of profitable, independent operation with no reliance on investor capital means the risk of sudden shutdown is low. Being an attractive acquisition target for a larger field service platform is the main wildcard, though there are no signals of an imminent sale.

ServiceM8 has a REST API that's been available for years and covers the main data types: jobs, clients, contacts, staff, materials, forms, and more. It's reasonably mature and stable enough to build reliable integrations on.

Rate limits are adequate for small-business use cases but won't support aggressive real-time syncing. If you're dealing with a handful of jobs per day, you'll never notice. A larger operation trying to sync hundreds of records in real time will need to design their integration carefully.

Beyond the core REST API, there are specialised endpoints for messaging, document templates, custom fields, and a feed API for real-time event streams. Add-on developers can build serverless integrations that ServiceM8 hosts, with sample code available in several languages.

The accounting integrations with Xero, MYOB, and QuickBooks are properly maintained two-way syncs, not one-directional exports. These are the standout integrations and the ones most ServiceM8 users will care about. Zapier is also supported for connecting to the broader app ecosystem.

Webhooks are supported and cover the main object types. One quirk: webhook notifications tell you what changed but don't include the actual values, so your integration needs to make a follow-up request to fetch the updated data. This is a common pattern but adds a step compared to platforms that send the full payload. Testing webhooks requires a paid subscription as trial accounts can't create webhook subscriptions.

You can get your data out, but it takes some effort. A full account backup is downloadable once per day from the dashboard, covering jobs, clients, materials, and documents. However, this backup file is reference-only and can't be imported back into ServiceM8 or into another system.

For structured data, CSV and Excel exports are available for jobs, clients, materials, and reports. These are text-only though, so photos, videos, and PDFs attached to jobs aren't included.

The API is the most complete exit path. A developer can extract all major data types programmatically, but it's custom work rather than a one-click migration. Platform-specific configurations like digital forms, job templates, and automation rules would need to be rebuilt from scratch on any new platform.

The developer portal provides REST API documentation, authentication guides, webhook overviews, and sample code in a few languages. It's enough to get an integration running without too much guesswork, but it's not in the same league as platforms like Xero or HubSpot where the docs practically hold your hand.

The biggest friction point is the lack of a sandbox environment. You need a paid production account for full testing, including webhooks. This adds cost and complexity when you're just evaluating whether an integration is feasible.

There are no official client libraries, so you're working with raw HTTP requests or using third-party tools like Zapier or n8n as a starting point. The developer community is small and mostly supported by the ServiceM8 team rather than a broad ecosystem. Questions generally get answers on the developer forum, but don't expect the depth of community knowledge you'd find with larger platforms.