Free alternative to Jobber for small businesses in 2026
Compare Jobber’s user bundles and checklist tier with Lux Field’s free jobs, visits, tasks, photos, reports, estimates, invoices, and unlimited users.
In this article
A small service business can outgrow a one-user plan long before it becomes a large company. The owner needs to see the work, an administrator needs to organize it, and technicians need the customer details and instructions for the jobs they carry out. Those are different responsibilities, even when only a few people are involved.
Lux Field is a free Jobber alternative for teams that want the whole job-to-invoice routine without user packages. Jobs, visits, clients, saved items, estimates, invoices, and users are unlimited. Tasks, notes, photos, service reports, and payment recording are included.
The practical advantage is having those features available to the whole group at once. You can organize another visit, document completed work, and include another colleague without deciding which paid package now fits the team.
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.
Jobber and Lux Field at a glance
| Working requirement | Jobber | Lux Field |
|---|---|---|
| Entry team allowance | Core: 1 user | Unlimited users free |
| Structured job instructions | Checklists start in Connect | Tasks included free |
| Scheduling and customer records | Available within the paid user package | Jobs, visits, and clients included |
| Job documentation | Package-specific tools and access | Notes, photos, and service reports included |
| Estimates and invoices | Paid product workflow | Free and unlimited |
The one-user starting plan does not fit a working group
Jobber Core includes one user. Connect is offered in different user configurations, and checklists begin in Connect. A small company therefore needs to look beyond the starting price if both shared access and structured job instructions matter to its daily work.
The user restriction is especially significant for businesses with an owner, an office coordinator, and several technicians. The office is part of the workflow. Counting only the people in trucks understates how many people need access. A colleague who helps one day a week still needs a suitable way to work with the records.
Lux includes unlimited users with its tasks, job notes, photos, service reports, estimates, and invoices. You can design the routine around the people doing the work. The owner does not have to act as the sole operator of the system, and a new technician does not force the business to reconsider its invoicing and scheduling package.
A plumbing team with technicians and an office coordinator
Consider a plumbing business with eight technicians, an owner, and an office coordinator: ten people who need access. The coordinator organizes visits and prepares customer documents. Technicians need the address, the work instructions, and a place to record what happened. The owner needs the context to review the work and billing.
A repair may require a diagnosis visit followed by another visit when a part arrives. The business should preserve those visits under a clear job record rather than leaving the second trip in a message thread. Photos and notes help explain the work. Tasks make the instructions visible. The invoice needs to reflect the service that was actually completed.
Lux Field includes that routine for all ten people. If the business later grows to 18 technicians plus the same owner and coordinator, the subscription does not change for 20 users. Hiring changes the work schedule, not the software seat bill. That is particularly useful when growth arrives unevenly and the business wants to include new people without renegotiating access to its basic operating records.
| Moment in the example | The Lux workflow | Why it helps |
|---|---|---|
| Customer reports a fault | Save the client and organize the job | Give the office and technician a common record |
| Diagnosis needs a return visit | Keep each visit clear within the job | Preserve the sequence of work |
| Technician completes the repair | Use tasks, notes, and photos | Make completion understandable to the office |
| Office prepares the customer document | Use estimates, invoices, and a service report as needed | Connect the work record to the bill |
The office is part of the field team
A technician is often the most visible user of field-service software, but the office depends on the same records. Someone answers the initial call, confirms customer details, organizes the visit, and prepares the invoice. Excluding those people from the access calculation understates the working requirement.
Lux Field includes unlimited users, allowing the business to involve the people responsible for each stage. The owner can remain responsible for commercial decisions while the coordinator handles ordinary schedule and document work. Technicians can keep the job notes and photos useful for the office. The purpose of shared access is to keep the handoff direct.
That division of work becomes more valuable as the group grows. A new administrator should be able to take on a responsibility rather than becoming another person who sends the owner requests to update the software. A new technician should receive the same clear job context as the existing team. The included records should support that continuity.
| Role in the business | Why access matters | Work the record should support |
|---|---|---|
| Owner | Understands scope and commercial decisions | Review estimates, jobs, and invoices |
| Coordinator | Organizes the work | Maintain clients, jobs, and visits |
| Technician | Carries out the service | Review tasks and record notes/photos |
| Administrator | Completes the billing handoff | Prepare documents and record payments |
Return visits should preserve the job’s meaning
A return visit is more than another appointment on the calendar. It usually has a reason: a part was unavailable, the customer agreed additional work, or the service requires a separate completion stage. The next person needs to understand that reason without reconstructing the previous visit from messages.
Lux Field keeps jobs and visits as part of the included routine. Use the job to preserve the overall service context and the visits to keep the sequence clear. Tasks describe what needs doing. Notes explain findings or changes. Photos can make a detail understandable to someone who was not on site.
The record should answer what happened, what remains, and what the customer should receive. A service report can explain the completed work, while the invoice explains the charge. Those documents have different purposes and should be reviewed accordingly.
For a practical evaluation, use a job that needs an initial diagnosis and a later repair. Have someone who did not attend the first visit read the record before the second. They should be able to identify the customer, understand the task, and see why the team is returning. Then ask the office to prepare the final customer documents using that context. This tests the everyday value of the free workflow more thoroughly than a single appointment with a short title.
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 |
|---|---|---|
| Jobber Core, 1 user | $49/month without commitment | 1 user |
| Connect, 1 user | $139/month without commitment | Still a 1-user configuration |
| Connect, 5 users | $199/month without commitment | 5-user configuration |
| Connect, 10 users | $299/month without commitment | 10-user configuration |
| Lux Field | $0 | Unlimited users; all product features |
What changes with 10 or 20 people
| Team and workload | Jobber | Lux Field |
|---|---|---|
| 10 total users | Connect: $299/month without commitment | $0 |
| 20 total users | Request a quote; do not extrapolate a smaller package | $0 |
Jobber presents different billing arrangements. Core is $49 month-to-month, $39 per month with a one-year commitment, or $29 per month equivalent when billed annually. Those amounts should not be mixed. For Connect with ten users, the corresponding figures are $299, $259, and $229.
At the no-commitment monthly price, twelve payments for the ten-user Connect arrangement total $3,588. The annually billed equivalent totals $2,748 for the year. Lux's subscription remains $0 for the users and included field workflow. The comparison is about that working requirement, rather than a claim that every capability in Jobber has an identical counterpart.
The decision checks that matter for this alternative
- Count the owner and office staff as well as technicians.
- Evaluate the checklist or task requirement in the actual package being priced.
- Use a job with two visits, rather than testing only a single appointment.
- Compare one-year commitments and annual prepayment separately from flexible monthly billing.
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
Lux Field is a strong free Jobber alternative when small user bundles and paid feature tiers are restricting the whole team's workflow. It includes jobs, visits, tasks, notes, photos, service reports, estimates, invoices, and unlimited users together. The business can organize the work and let everyone participate without purchasing a larger team package as it grows.