Evidence note: Use this review to build a shortlist. We publish a numerical score or final recommendation only after the product completes the same hands-on scenarios and exception tests used for its peers.
The short verdict
ServiceM8 is a strong shortlist candidate for small field-service businesses that want published prices, broad essentials on every plan, and unlimited users once they leave the solo Free plan. Its clean pricing model is based on monthly job credits rather than paid seats, but device strategy is part of the product decision: the vendor recommends iPhones for primary field technicians and positions Android Lite around core field tasks.
Who it fits
Solo operators and small-to-midsize service teams that use iPhone or iPad in the field and prefer to scale paid access by job volume rather than user count.
Watch closely: Paid plans remove the user cap but retain monthly job-credit levels; Android Lite covers core work but omits management and advanced iOS functions.
Pricing and plan gates
Official US pricing lists Free at $0 for 1 user and 30 jobs/month; Starter at $29 for 50 jobs; Growing at $79 for 150; Premium at $149 for 500; and Premium Plus at $349 for 1,500+ jobs. Paid plans list unlimited users, and prices are in USD.
Evaluation access: 14-day trial with full feature access and no credit card required, according to the US pricing page.
- Model average and peak new-job credits, including quotes that consume a job credit when created.
- Assign every office and field role to iOS, Android Lite, desktop, or online dashboard before the trial.
- Price higher-tier add-ons such as Forms, Inbox, job costing, markup billing, and Knowledge only when operationally required.
- Confirm country-specific payments, phone, messaging, accounting, tax, and partner support before purchase.
Strengths and constraints
The strongest documented signals
- Published USD pricing and clear job-credit limits
- Unlimited users on every paid plan
- Scheduling, quotes, invoices, online booking, payments, recurring work, communication, and accounting integrations across the plan ladder
- Offline access is listed across plans, with synchronization when connectivity returns
The constraints to price and test
- The Free plan is limited to one user and 30 new jobs per month
- Higher job volume or certain advanced add-ons requires a higher tier
- ServiceM8 recommends iPhones for primary field technicians
- Android Lite omits management access, field payments, other staff schedules, advanced imaging, proposals, deposits, asset management, and other iOS capabilities
What we tested directly
These checks used a controlled ServiceTech Signal QA account, synthetic customer data, and no real customer payment.
Existing-client reuse
Native client search reused one saved client across two jobs while the Clients register remained at one head-office record. This proves the observed desktop matching path, not automatic duplicate prevention in every intake channel.
Client Sites hierarchy
A subordinate test site was saved beneath the head office as a reusable site record. A live job-to-site assignment, site-level field history, and native-device visibility were not demonstrated.
Urgent scheduling and reschedule
Two synthetic urgent jobs were added without removing existing commitments, and one booking moved across days. The current schedule saved, but the observed diary did not preserve the prior time as a reconstructable change event.
Simple recurring job
Completing one synthetic weekly job created the next Work Order one week later with the same staff and time plus a parent diary link. The successor did not retain the original reference or description, and no agreement entitlement or recurring billing lifecycle was tested.
Unsent invoice state
One synthetic EUR 95 invoice remained unsent and unpaid while its total, zero tax, balance due, diary link, client balance, and Pending Approval state reconciled across the observed desktop surfaces. No payment, refund, payout, or accounting sync occurred.
Weak-signal field workflow
No supported iOS or Android test device was available. Browser simulation was not treated as proof of offline cache, queued writes, reconnect behavior, conflict resolution, field payments, or final document generation.
What we still need to test
- Repeat the recorded workflow on the actual mix of iPhones, iPads, Android devices, and office computers.
- Complete a controlled offline field sequence and reconcile every queued update after connectivity returns.
- Add a second authorized test user and verify role restrictions, reassignment, and schedule-change evidence.
- Reconcile a changed invoice, two payment directions, a correction, and recovery through a QuickBooks Online sandbox.
- Generate and reconcile the full backup plus representative CSV exports before approving migration or cancellation.
Evidence sources
- ServiceM8 US pricing and feature comparison ↗
- ServiceM8 Lite for Android scope and limitations ↗
- ServiceM8 QuickBooks Online sync behavior ↗
- ServiceM8 Simple Recurring Jobs behavior ↗
- ServiceM8 Partial/Progress Invoicing setup ↗
- ServiceM8 credit-note boundary ↗
- ServiceM8 Automation overview and status surfaces ↗
- ServiceM8 Quote Follow Up eligibility and stop rules ↗
- ServiceM8 Customer Feedback automation eligibility ↗
- ServiceM8 Two-Way SMS replies and unsubscribe ↗
- ServiceM8 Phone country availability ↗
- ServiceM8 duplicate-client merge path ↗
- ServiceM8 security-role matrix ↗
- ServiceM8 account-activity retention and scope ↗
- ServiceM8 full-account backup boundary ↗
- ServiceM8 Advanced Reporting export coverage ↗
- ServiceM8 cancellation and deletion behavior ↗
- ServiceM8 post-cancellation read-only boundary ↗
Editorial record
Who reviewed this page and what happens next.
Commercial relationships cannot change the evidence state, fit statement, caveats, or conclusion.
- Research and review
- Andre Ribeiro
- Published
- Last material review
- Next scheduled review
- Evidence scope
- US pricing evidence; worldwide readership and country availability checks
- Evidence state
- Direct S01 through S08 / Recorded
Testing methodologyEditorial standardsCorrections and update log