Free alternative to Kickserv for small businesses in 2026
Compare Kickserv’s five-, ten-, and twenty-user packages with Lux Field’s free jobs, visits, documentation, invoices, and unlimited users.
In this article
The sixth person can be a meaningful software decision for a small service company. That person might be a new technician, an office administrator, or a partner helping with billing. Their role is ordinary, but a user-bundle boundary can make adding them a package change.
Lux Field is a free Kickserv alternative with unlimited users and the everyday job workflow included. Jobs, visits, clients, saved items, estimates, and invoices are unlimited. Tasks, notes, photos, service reports, and payment recording are included as well.
The benefit is being able to give the right people access without choosing which team-size package now fits the business. The work stays organized in the same free product as responsibilities change.
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.
Kickserv and Lux Field at a glance
| Working requirement | Kickserv | Lux Field |
|---|---|---|
| Entry team allowance | Start: 5 users | Unlimited users free |
| Mid-size group | Run: 10 users | No user band |
| Larger group | Scale: 20 users | No paid team package |
| Customer and job workflow | Included within the selected paid package | Clients, jobs, and visits included free |
| Documentation and billing | Package-specific tools | Tasks, notes, photos, reports, estimates, and invoices included |
The five-, ten-, and twenty-user bands shape the purchase
Kickserv Start includes five users for $60 per month. Run includes ten for $119, and Scale includes twenty for $199. These are package prices tied to the included group size, rather than a single per-person rate.
The boundary can arrive before the business feels large. Four technicians, an owner, and an administrator are six people. A five-user package does not fit all of them even if the administrator only helps a few hours each week. Likewise, the eleventh person changes which published bundle accommodates the team.
Lux includes unlimited users with its jobs, visits, documentation, estimates, and invoices. Access can follow responsibility rather than a package threshold. The business can include the office and field staff together without making the next person a subscription upgrade.
A growing service company adding an office administrator
Consider a company with four technicians and an owner. The owner has been organizing the schedule and preparing invoices after the field work is finished. The business hires an administrator to take responsibility for customer details, visits, and billing preparation.
That new role is intended to reduce the owner's administrative burden. It only works if the administrator can use the records directly. Keeping that person outside the system would preserve the very bottleneck the hire was meant to remove. Counting only the technicians would miss the access requirement.
Lux Field lets the business include the administrator without a seat charge. The field team can maintain tasks, notes, and photos while the office uses the same job context to organize visits and prepare customer documents. A sensible division of work does not need to wait until the business is ready to buy another user bundle. The benefit comes from keeping responsibilities and records aligned.
| Moment in the example | The Lux workflow | Why it helps |
|---|---|---|
| Administrator takes over scheduling | Use client, job, and visit records | Give the new role practical access |
| Technician receives instructions | Review the job tasks and notes | Keep the planned work clear |
| Work is completed on site | Preserve photos and service details | Make the office handoff useful |
| Administrator prepares billing | Use estimates, invoices, and payment records | Reduce dependence on the owner for routine updates |
The next hire may be an administrator, not another technician
Small businesses often hire office help to give the owner more time for customers and field work. That person needs access to the records they are expected to maintain. Otherwise the owner remains responsible for every software update, even after the business has paid someone to take on the task.
Lux Field includes unlimited users, allowing the administrator to participate in the customer, job, visit, and billing routine. Technicians can preserve the information the office needs through tasks, notes, and photos. The benefit is a practical transfer of responsibility, with the right records available to the person doing the work.
Before evaluating a user package, write down everyone involved. Include the owner, the coordinator, the administrator, and field staff. Do not count only simultaneous use. An administrator who prepares invoices in the evening and a technician who uses the records during the day are still different people with different access needs.
| Team example | People included | Total access requirement |
|---|---|---|
| Small crew with owner | 4 technicians + owner | 5 users |
| Same crew with office help | 4 technicians + owner + administrator | 6 users |
| Growing operation | 8 technicians + owner + coordinator | 10 users |
| Added billing support | 8 technicians + owner + coordinator + administrator | 11 users |
A clear handoff is more useful than another message
The office should not have to ask a technician to repeat everything after the visit. A useful job record gives the next person enough information to organize follow-up work or prepare the customer documents. That does not require a long essay. It requires the right facts in the right record.
Lux includes tasks, notes, photos, and service reports alongside jobs and visits. A technician can record the material finding, show a relevant detail, and leave the next action understandable. The office can use that context when checking the estimate or preparing the invoice.
Shared access works best with a clear working standard. Decide what information should be present before a job is handed to the office. For example, the agreed work should be recognizable, any return visit should have a reason, and the final service description should be clear enough for billing.
Test that routine with a colleague who did not attend the job. Ask them to explain the customer's next step and prepare the appropriate document. The exercise reveals whether the team has a dependable handoff, while Lux's free users ensure that participation itself is not restricted by a package boundary.
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 |
|---|---|---|
| Kickserv Start | $60/month | 5 users |
| Kickserv Run | $119/month | 10 users |
| Kickserv Scale | $199/month | 20 users |
| Lux Field | $0 | Unlimited users and all product features |
What changes with 10 or 20 people
| Team and workload | Kickserv | Lux Field |
|---|---|---|
| 10 total users | Run: $119/month | $0 |
| 20 total users | Scale: $199/month | $0 |
The difference between Run and Scale is $80 per month at the displayed monthly rates. The packages also differ in features, so that difference should not be described as a universal per-seat charge. Payment-volume discounts and annual savings are separate purchasing conditions.
For a business choosing software mainly to share the core service workflow, Lux removes the bundle decision. A ten-person and a twenty-person group can both use the included customer, job, visit, documentation, and invoicing routine for free.
The decision checks that matter for this alternative
- Count the sixth and eleventh person in the growth scenario.
- Include administrators and owners, not just field technicians.
- Compare the actual bundle price rather than inventing a per-seat rate.
- Test whether an office colleague can complete the handoff using the job record.
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 Kickserv alternative when team-size bundles are the constraint on sharing the work. It includes the records, tasks, documentation, estimates, and invoices the team needs, with unlimited users. The business can add people according to its workload without making every bundle boundary another software decision.