Free alternative to ServiceM8 for small businesses in 2026
Compare ServiceM8’s one-user free plan and new-job bands with Lux Field’s free scheduling, documentation, invoices, and unlimited team access.
In this article
A service business can outgrow a free plan because it adds a colleague, because it takes on more jobs, or both. A useful alternative needs to address those changes together. Removing a user restriction is only part of the answer if the job allowance remains too small.
Lux Field is a free ServiceM8 alternative for teams that want unlimited jobs and users with the working features included. Visits, clients, estimates, invoices, and saved items are also unlimited. Tasks, notes, photos, service reports, and payment recording are part of the free product.
That combination lets the business organize the work, preserve what happened on site, and prepare customer documents without choosing a new job band as demand changes.
We publish this guide at Lux and focus on the included workflow described below. Product and plan details were checked against official sources on September 15, 2026. The business examples are illustrative.
ServiceM8 and Lux Field at a glance
| Working requirement | ServiceM8 | Lux Field |
|---|---|---|
| Free team access | 1 user | Unlimited users free |
| Free workload | 30 new jobs/month | Unlimited jobs |
| Entry paid workload | Starter: 50 new jobs/month | No monthly job band |
| Scheduling and documentation | Included tools remain subject to the job package | Visits, tasks, notes, photos, and reports included |
| Estimates and invoices | Available within the chosen plan | Free and unlimited |
The free user cap and the paid job bands both matter
ServiceM8 Free includes one user and 30 new jobs per month. Paid Starter raises the job allowance to 50 new jobs at $29 per month. Growing is $79 for 150 new jobs, and Premium is $149 for 500. The number being counted is new jobs, not individual appointments.
That unit should match the business's actual activity. A repair job requiring two visits is not automatically two new jobs. Conversely, a team completing many separate small jobs can reach a new-job band quickly even if each job takes only one visit.
Lux includes jobs and visits without quantity bands, along with unlimited users. The business can represent the work accurately without treating its record count as a subscription target. A quiet month and a busy month use the same included task, photo, report, estimate, and invoice routine.
A mobile repair team with a seasonal spike
Imagine a repair team that usually opens 45 new jobs per month but reaches 110 during its busy season. Some jobs are finished in one visit; others need a diagnosis and a return trip. The business wants to preserve the actual sequence rather than compressing every service call into a simplistic record.
The owner, a coordinator, and the technicians all need the relevant information. The coordinator needs to organize visits and prepare customer documents. Technicians need task instructions and a place for photos and notes. The owner needs enough context to understand the completed work and its invoice.
Lux Field includes that routine through both the ordinary and busy months. The seasonal increase changes the schedule, not a job-capacity subscription. The team can retain the visits, instructions, and documentation that make the job understandable, while continuing to prepare estimates and invoices for the work being delivered.
| Moment in the example | The Lux workflow | Why it helps |
|---|---|---|
| Ordinary month with 45 new jobs | Keep customer and job records organized | Establish a repeatable routine |
| Busy month with 110 new jobs | Continue using the same job workflow | No paid volume-band change |
| A repair needs a second visit | Keep the visit connected to its job | Preserve the sequence of service |
| The office closes the billing loop | Use the work notes, report, and invoice | Avoid reconstructing the job from separate messages |
New jobs and visits should remain separate in the plan
A single job may take one visit or several. The distinction affects both the working record and the subscription comparison. If a business opens 80 repair jobs and 20 of them need a second visit, it has 80 new jobs and 100 visits in that simple example. Those are useful numbers, but they are not interchangeable.
Lux Field includes both jobs and visits without quantity bands. The business can keep the overall service under a job and preserve the visits needed to deliver it. The record can follow the work instead of being compressed to suit a counting target.
This is especially important when another person handles the follow-up. The next technician needs the reason for the return, the relevant notes and photos, and the remaining task. The office needs to understand when the work is ready for its customer documents. A disconnected calendar entry is a weak substitute for that context.
| Work pattern | Job count | Visit count in the illustration |
|---|---|---|
| Forty straightforward repairs | 40 | 40 |
| Twenty repairs needing two attendances | 20 | 40 |
| Ten installations needing three attendances | 10 | 30 |
| Combined workload | 70 | 110 |
Seasonal demand should not weaken the record
During a busy period, teams are tempted to shorten notes, skip photos, or leave the office to fill in missing detail later. That can make the eventual billing and customer follow-up harder. The software arrangement should support the same useful routine when demand increases.
Lux includes tasks, notes, photos, service reports, estimates, and invoices alongside unlimited jobs, visits, and users. The team can keep the records it needs through a seasonal spike. The business still needs clear expectations about what to record, but it does not need a higher job package to maintain its normal volume of work.
A practical standard can stay simple: describe the task, record the material finding, add a relevant photo when it helps, and leave enough context for the next person. The goal is a useful handoff, not a long narrative for every visit. A short, specific note can be more valuable than a vague paragraph written hours later.
Evaluate the busiest plausible month, including return visits and extra office help. Check whether the customer record, visit sequence, and final invoice remain understandable. That is the working benefit of a free product with room for both the normal routine and the months when the business becomes busier.
What the free Lux Field workflow includes
Lux Field combines the working features and the capacity to use them. Jobs, visits, clients, saved items, estimates, invoices, and users are unlimited. Tasks, notes, photos, service reports, and payment recording are included in the free product. The team can evaluate the routine without selecting a paid feature or user tier.
| Part of the work | What Lux Field includes | Why it matters to the team |
|---|---|---|
| Clients | Unlimited clients | Keep the customer context available for the next job |
| Jobs | Unlimited jobs | Preserve the overall service record |
| Visits | Unlimited visits | Represent the actual sequence of work |
| Instructions | Tasks and notes | Give people concrete work and useful context |
| Documentation | Photos and service reports | Help the office and customer understand the service |
| Reusable services | Unlimited saved items | Start estimates and invoices from consistent information |
| Customer documents | Unlimited estimates and invoices | Explain proposed work and agreed charges |
| Payments | Payment recording | Keep received amounts and balances understandable |
| People | Unlimited users | Include the office, owner, and field staff |
The job and its visits have different purposes
The job holds the service context. A visit represents an attendance within that work. Keeping those ideas clear helps when a repair needs another trip or a service is completed in stages. The team should be able to understand the overall job without losing the detail of each visit.
A useful record answers why the person is attending, what needs doing, and what happened previously. The next visit should not depend on the last technician remembering every detail. Tasks and notes give the work structure, while relevant photos can make a finding easier for another person to understand.
Documentation should help the next person
The office and field staff use the same job information for different reasons. The technician needs instructions and a place to record the work. The office needs enough context to organize a follow-up or explain the service to the customer. A service report can communicate the completed work, while the invoice explains the charge.
Keep each record purposeful. A short, specific note can be more useful than a long vague one. A photo should add context. A task should describe something the technician can act on. Free access to these tools gives the business room to establish that working standard across the group.
Estimates, invoices, and saved items complete the routine
An estimate describes proposed work. An invoice describes the agreed amount being billed. Saved items provide reusable service information for those documents, while the client record keeps the customer details available. The person preparing the final document should review the actual scope, quantity, and amount.
The customer-facing documents should make sense alongside the job record. The business can use the service report to explain the work and the invoice to explain the charge, without relying on an unexplained total or a separate conversation to supply all the meaning.
Current device availability
Lux Field is available on the web. Apple App Store and Google Play releases are coming soon. Evaluate the current web workflow on the devices the team intends to use, including the screens used for visit details, notes, tasks, and customer documents. The free user arrangement applies to the product available now.
Keep completed work and received money clear
A completed visit does not automatically mean the customer has paid. The work record explains the service; the invoice and payment record explain the commercial position. Keeping those facts clear helps the office answer questions without confusing operational completion with settlement.
For an illustrative $900 invoice, a received payment of $300 leaves $600 outstanding. Recording the remaining $600 when it arrives brings the balance to zero. The amounts should be recorded against the correct invoice, especially when the customer has more than one job.
| Illustrative stage | Work or payment fact | What the team should understand |
|---|---|---|
| Service completed | The visit record explains what happened | Completion does not itself confirm payment |
| Invoice prepared | Agreed charge is $900 | The customer-facing amount is clear |
| First payment received | $300 recorded | $600 remains |
| Remaining payment received | Another $600 recorded | The invoice is settled |
Lux Field includes payment recording. Recording received money is different from processing a payment. External payment services have their own arrangements, separate from the free software workflow. The useful evaluation is whether the office can identify the correct invoice and explain its remaining balance from the record.
Plans and the conditions beside the price
Prices use USD and regular billing unless labeled otherwise. Local plans and availability can vary; taxes, introductory discounts, optional extras, and external payment fees are separate.
| Product and arrangement | Published price | Condition to plan around |
|---|---|---|
| ServiceM8 Free | $0 | 1 user; 30 new jobs/month |
| Starter | $29/month | 50 new jobs/month |
| Growing | $79/month | 150 new jobs/month |
| Premium | $149/month | 500 new jobs/month |
| Premium Plus | $349/month | 1,500 included jobs; $0.20/additional job |
| Lux Field | $0 | Unlimited jobs, visits, and users |
What changes with 10 or 20 people
| Team and workload | ServiceM8 | Lux Field |
|---|---|---|
| 10 users; 100 new jobs/month | Growing: $79/month | $0 |
| 20 users; 100 new jobs/month | Growing: $79/month | $0 |
ServiceM8's paid plans do not charge their subscription per user. These examples use the same Growing price for both team sizes because the workload is 100 new jobs. Starter's 50-job allowance would not fit that example, regardless of how many people can access it.
If the workload grows beyond the selected band, reevaluate the job package rather than multiplying a seat rate. Lux avoids that job-volume decision for its included workflow, while still allowing the entire group to participate.
The decision checks that matter for this alternative
- Count new jobs separately from visits when comparing ServiceM8 bands.
- Use a busy seasonal month, not only an average month.
- Include the office and owner in the free-plan access requirement.
- Evaluate Lux’s current web experience on the devices the team intends to use.
Evaluate a complete job with the people who will use it
The strongest trial example includes a customer, an estimate, a job with a follow-up visit, useful task instructions, and enough documentation for the office to prepare the final customer records. A calendar entry with a short title does not reveal whether the whole service routine fits.
- Start with realistic customer information. Use the details the office and technician actually need to identify the customer and understand the service.
- Describe the proposed work. Prepare an estimate using relevant saved items, then review the scope and amount.
- Organize the job and its visits. Include a return visit so the evaluation tests continuity across more than one attendance.
- Record useful work detail. Add tasks, notes, and a relevant photo, then ask someone who was not on site to interpret the record.
- Complete the office handoff. Prepare the appropriate service report and invoice, then review how received payments are recorded.
If the business adopts a new active workflow, preserve its earlier customer documents and outstanding balances before changing where new work is created. Pick a clear starting point, keep the required current customer information accurate, and review the first completed jobs together. This process does not assume an automatic import from the compared product.
The free alternative should support the work from beginning to end. The decision is stronger when the technician, coordinator, and administrator can all explain their part of the routine using the same records. Lux includes the users, capacity, and everyday tools needed to evaluate that working fit with the whole group.
When Lux Field is the right choice
Choose Lux Field when a one-user free account and monthly new-job bands no longer match the business. It includes the complete everyday routine—jobs, visits, tasks, photos, service reports, estimates, invoices, and users—without those allowances. That gives the team room to record its work properly throughout seasonal changes and growth.