A $38 air filter can turn into a $6,500 repair when nobody knows the skid steer ran 91 hours past service. That is the real test for cloud based fleet management software. Not dashboards. Not buzzwords. Can your operator see the hour meter, log the service, attach the receipt, and keep the machine out of the red before it costs you a week of work?
If you run 2 to 15 machines, your fleet problem is not the same as a national rental company. You probably have a skid steer, mini excavator, mower, compact tractor, trailer, plate compactor, maybe a dump truck. You also probably have one person who knows where the paper folder is, one guy who forgets to text the hours, and one machine that only gets attention when it starts smoking.
Good software should fix that. Bad software gives you another admin job.
This guide is for small contractors, landscapers, snow crews, dirt crews, and owner-operators who do their own maintenance. You will see what matters, what does not, and how to pick cloud based fleet management software that fits a small crew without paying for big-fleet overhead.
What a small crew actually needs
You do not need a control tower. You need a clean maintenance log that your crew will use when they are tired, wet, and standing next to a machine.
For a 2-15 machine crew, the important jobs are simple:
- Track service by engine hours, not guesses
- Know what is due soon and what is overdue
- Let any operator log hours and maintenance
- Keep photos of receipts, filters, leaks, cracks, and damage
- Work when the yard has weak signal
- Avoid per-user pricing that punishes you for adding operators
- Make history easy to find when you sell, trade, or diagnose a machine
That sounds basic. It is not. A lot of fleet tools were built for delivery vans, highway trucks, or enterprise maintenance shops. They assume you have a dispatcher, a fleet manager, a parts room, and someone paid to stare at software.
You may have none of that.
You need the machine to tell you what to do next. If the mini excavator needs hydraulic oil at 1,000 hours, the app should show that clearly. If the stand-on mower is 12 hours away from service, it should go yellow. If it is 19 hours overdue, it should go red and send an alert.
That is the difference between maintenance tracking and another digital notebook.
Why engine hours beat calendar reminders
Most small equipment does not wear out by the calendar. It wears out by use.
A skid steer that runs 42 hours in one muddy week needs attention faster than a backhoe that sat behind the shop for two months. A mower that runs every day in May is not on the same schedule as the same mower in January. Calendar reminders do not understand that.
Engine hours do.
Manufacturers write service intervals in hours for a reason. Oil change at 250 hours. Fuel filter at 500 hours. Hydraulic filter at 1,000 hours. Grease daily or every 10 hours depending on the machine. If your software only nags you every 90 days, it is guessing.
Here is a simple example.
You own a compact track loader. Oil and filter are due every 250 hours. The machine starts the month at 1,120 hours. It works 31 hours the first week, 18 the second, 44 the third, and 27 the fourth. That is 120 hours in a month. If your last service was 1,000 hours, you are now 10 hours away from the next oil service.
A calendar reminder set for every 3 months might stay quiet. An hour-based system flags it now.
That matters because small machines often work in bursts. Storm cleanup. Grading jobs. Spring mowing rush. Fall leaf work. Snow. You can burn through service intervals quickly, then park the machine. The meter is the truth.
If you want a baseline, use a written schedule like this equipment maintenance schedule and then track every task by actual meter hours.
The real cost of missing maintenance
Nobody likes maintenance because the cost is visible. Filters, oil, grease, downtime. The cost of skipping it hides until it gets ugly.
Say you have a mini excavator that bills at $95 per hour with operator. It needs a 500-hour service. Parts and fluids cost $220. Your time is 2.5 hours. Even if you value your own shop time at $50 per hour, the service costs about $345.
Now miss it badly.
Dirty hydraulic oil takes out a pump or contaminates a valve block. The repair is not just parts. It is hauling, diagnosis, shop delay, and a dead machine in the middle of a job. A small hydraulic repair can hit $2,000 to $4,000 fast. A bigger failure can go higher. Add two lost days at 8 billable hours per day and you just lost another $1,520 in revenue.
That $345 service was not expensive. The missed service was.
The same math applies to mowers. A zero-turn that misses oil, air filter, and blade spindle checks may limp through the week. Then it drops on Friday when you still have 18 lawns left. If those lawns average $55 each, that is $990 of work you now have to reschedule, rush, or give away to another crew.
For a small operator, downtime hurts twice. You lose the machine and you lose your own time trying to fix the mess.
Cloud based fleet management software is worth looking at when it prevents one avoidable failure, one lost receipt, or one argument about who last serviced the machine.
What cloud based really means for your crew
Cloud based does not mean fancy. It means the log is not trapped on one clipboard, one laptop, or one phone.
If you have three operators, all three should be able to see and update the same machine history. If the owner is buying filters at night, the owner should see current hours without calling around. If a machine is serviced in the field, the log should not wait until someone drives back to the office.
But cloud based tools can still fail in the real world. Job sites have bad signal. Metal buildings kill reception. Rural yards drop connection. If the app cannot handle weak service, operators stop using it.
Offline-first matters. That means the operator can log the hour meter, service note, receipt photo, or damage photo when there is no signal. The record syncs later when the phone reconnects. No double entry. No paper note stuffed into a cup holder.
For small crews, this is not a nice extra. It is how work actually happens.
The features that matter most
A long feature list is not the same as a useful tool. For small fleets, focus on the features that prevent lost money and lost time.
Engine-hour maintenance tracking
This is the core. Each machine needs its own meter reading and service intervals. The system should tell you what is due based on hours, not just dates.
Look for status that is easy to understand. Green means fine. Yellow means due soon. Red means overdue. Nobody should need training to understand that.
Fast logs from the field
If logging takes too long, it will not happen. Your operator should be able to pick the machine, enter the current hours, choose the task, add a note, and save.
A good log answers simple questions:
- What was done?
- At what hour meter reading?
- Who logged it?
- When was it logged?
- What proof or photo is attached?
Photos for receipts and damage
Photos are underrated. A receipt photo proves what oil, belt, filter, battery, or hose you bought. A damage photo shows the crack, leak, bent guard, worn tire, or broken lens before it becomes a debate.
This matters when multiple operators use the same machine. If the mower deck was cracked Monday morning, you want the photo in the log. If a hydraulic hose is starting to rub, a picture tells the story better than a note that says check hose soon.
Alerts that do not depend on memory
You are not going to remember every 250-hour, 500-hour, and 1,000-hour interval across 8 machines. Nobody does.
You need email and push alerts. You also need a simple status view so you can check the whole fleet in one minute. If three machines are green, two are yellow, and one is red, you know where to spend Saturday morning.
Simple machine-based pricing
Per-user pricing sounds fine until you add every person who touches equipment. Then you start sharing logins, which ruins accountability. Or you leave people out, which means they cannot log service when they actually do it.
For small crews, pricing per machine usually makes more sense. You pay for the equipment being tracked. Every operator can log without turning into another monthly fee.
You can see how EquipHours prices by machine on the pricing page. Free is $0 for up to 2 machines. Crew is $14.99 per month for up to 15 machines. Fleet is $39.99 per month for unlimited machines.
Comparison table: what to look for
Use this table when you compare options. Do not shop by the longest feature list. Shop by what your crew will actually use.
| Feature | Why it matters for 2-15 machines | What to watch out for |
|---|---|---|
| Engine-hour tracking | Matches how equipment service intervals are written | Calendar-only reminders that miss heavy-use weeks |
| Offline logging | Lets operators record work in yards, fields, and weak-signal sites | Apps that fail without service and create paper notes again |
| Receipt photos | Keeps proof of parts, fluids, filters, and purchases with the machine | Receipts stored in text threads or glove boxes |
| Damage photos | Documents leaks, cracks, dents, and wear before blame starts | No photo history tied to the machine |
| Green/yellow/red status | Makes priorities obvious without a meeting | Dashboards that look good but do not drive action |
| Email and push alerts | Catches overdue work before it becomes downtime | Alerts based only on calendar dates |
| Per-machine pricing | Lets every operator log without extra user fees | Per-user models that discourage adding the whole crew |
| Simple exportable history | Helps with resale, warranty discussions, and diagnostics | Locked-in notes that are hard to review later |
Per-user pricing versus per-machine pricing
This is where small crews get burned.
A per-user model charges based on people. That may work for an office software tool. It gets awkward for equipment maintenance. Your seasonal operator, mechanic friend, spouse, foreman, and part-time helper may all need to log hours or upload a photo. If each person affects price, you start limiting access.
That creates bad habits.
One login gets shared across the crew. Nobody knows who entered the wrong hour meter. The new guy cannot upload the damage photo because he does not have access. The owner gets three texts instead of one clean record. Maintenance history becomes a rumor again.
A per-vehicle model charges by vehicle or asset. That can work if every asset is counted fairly, but check how the vendor defines vehicles, equipment, attachments, trailers, and inactive units. You do not want to pay the same way for a trailer, a mower, and a truck if the system is not built for your mix.
A per-machine model is simple for equipment maintenance. You track the machines that need service. Operators are free to log because the machine is the thing creating the work.
For a 9-machine landscaping crew with 5 operators, this matters. You want all 5 people able to update mower hours, upload blade damage photos, and record oil changes. Paying per operator pushes you toward fewer users. Paying per machine pushes you toward better records.
When a spreadsheet is enough
You may not need software yet. If you own one machine and you are the only operator, a spreadsheet or notebook can work. Keep it clean. Record date, hours, service, parts, cost, and notes. Take photos and store them in a folder.
A free template can get you started. Use an equipment maintenance log template if you are not ready for an app.
But know where spreadsheets break.
They break when two people need to update the same machine. They break when the file lives on one computer. They break when receipts are separate from the entry. They break when nobody checks the sheet before the machine passes the next interval. They break when you are trying to read a tiny cell on a phone in the rain.
The tipping point is usually 3 to 5 machines or more than one operator. At that point, the cost of confusion beats the cost of a simple system.
A practical setup for a 2-15 machine crew
Do not overbuild your process. Start with the machines that can hurt you most if they fail.
For example, a small excavation crew might track:
- Compact track loader
- Mini excavator
- Dump trailer
- Plate compactor
- Skid steer attachment with hydraulic service needs
- Crew truck if you want it in the same maintenance view
A landscaping crew might track:
- Two zero-turn mowers
- Stand-on mower
- Compact tractor
- Skid steer
- Aerator
- Spray rig
- Trailer
Set up each machine with the correct service intervals from the manual. If you do not have the manual, look it up by model and serial number. Do not copy intervals from a different machine just because it is close.
Then enter the current hour meter. If the history is messy, do not wait until it is perfect. Start now. Put a note that says prior service history incomplete. From this point forward, keep it clean.
For each machine, create the must-track services first:
- Engine oil and filter
- Air filter inspection or replacement
- Fuel filter
- Hydraulic oil and filter
- Grease intervals
- Coolant checks
- Belts and hoses
- Blades, teeth, cutting edges, or wear parts
- Battery and electrical issues
- Tire or track condition
You can add more detail later. The first win is getting due and overdue service under control.
Example: the math on a 10-machine crew
Say you run 10 machines. You are busy 9 months of the year. Each machine averages 18 hours per month during the busy season. That is 1,620 machine hours per year across the fleet.
If the average service interval is 250 hours, you have about 6 service events per year just on that rough interval, plus daily greasing, blades, belts, filters, and repairs. In reality, you may log 40 to 80 maintenance events per year across the crew.
Now assume each missed or late service creates only 1 hour of avoidable downtime. That is conservative. If your loaded labor cost is $35 per hour and the machine could bill or produce $75 per hour, that lost hour can cost $110 in labor plus lost production.
If better tracking prevents 10 lost hours per year, that is $1,100 saved. If it prevents one bigger repair, the number jumps fast.
This is why the software decision should not be framed as another subscription. The real question is whether the system prevents enough mistakes to pay for itself.
For a 10-machine crew, EquipHours Crew is built to fit that range: up to 15 machines, unlimited operators, and hour-based tracking. The full feature set is listed on the features page.
Buying checklist for cloud based fleet management software
Use this checklist before you sign up for anything. If the tool cannot pass these questions, keep looking.
- Does it track service by engine hours, not only calendar dates?
- Can every operator log without buying extra seats?
- Can logs be created from a phone in the field?
- Does it work offline and sync later?
- Can you attach receipt photos to service entries?
- Can you attach damage photos to a machine record?
- Does it show due soon and overdue status clearly?
- Does it send email and push alerts?
- Can you set different intervals for different machines?
- Is pricing clear for your current machine count?
- Will pricing still make sense if you add 3 more machines?
- Can you start with imperfect history and improve from today forward?
- Is the app simple enough that your least techy operator will use it?
- Can you find past work fast when diagnosing a problem?
- Does the company understand equipment, not just vehicles?
Do not skip the operator test. Hand the app to the person who will actually log hours. If they cannot understand it in a few minutes, the system will fail no matter how good the dashboard looks.
Red flags to avoid
Some fleet software looks strong in a sales demo and weak in the mud.
Be careful with tools that focus more on maps than maintenance. GPS can be useful, but knowing where a machine is does not tell you whether the hydraulic filter is 40 hours overdue.
Watch for calendar-first maintenance. Dates help for inspections, registration, and seasonal work. They are not enough for engine service.
Avoid systems that make receipt storage an afterthought. If the proof is not attached to the log, you will end up searching email, texts, paper bags, and pickup consoles.
Be skeptical of software that requires one office person to keep everything updated. In a small crew, the person closest to the machine should be able to log the work.
And be careful with pricing that makes you choose who gets access. Maintenance records improve when everyone can contribute. They get worse when you lock the crew out.
What EquipHours is built to do
EquipHours is built for the small crew version of this problem. It is offline-first. It tracks service by engine hours. Each log entry can hold receipt and damage photos. Overdue status is shown green, yellow, and red. Alerts go out by email and push.
Pricing is per machine, never per seat. That means every operator can log for free. If you have up to 2 machines, the Free plan is $0. If you have up to 15 machines, Crew is $14.99 per month. If you have more, Fleet is $39.99 per month for unlimited machines.
No system will change filters for you. No app will grease a loader. But a good log makes the next right step obvious and keeps the proof in one place.
That is what cloud based fleet management software should do for a small contractor. Less guessing. Fewer missed intervals. Better records. More machines ready when you need them.
If you want a simple hour-based maintenance log for a small equipment fleet, start a free EquipHours account. Add one machine, enter the current hours, and see if your crew will actually use it.