Scheduling crews looks like a calendar and is not one. The difference between a calendar and a dispatch system is where the money goes, and it is worth understanding before you ask anyone for a price.
Key Takeaways
- A shared calendar you already pay for solves more than owners expect.
- The expensive parts are the phone in the van and the day changing.
- One developer, $3,000 to $12,000, covers a solid first version.
- Full dispatch with live updates and job history is $15,000 to $45,000.
Why It Is Not a Calendar
A calendar assumes the day goes as planned. Field work does not. The first job runs two hours long, a customer cancels, someone calls in sick, and an emergency comes in at eleven. A scheduling system is really a tool for handling the day changing, which is a different and harder problem than putting jobs into slots.
The second thing that makes it real is the phone in the van. The moment a technician updates a job from a driveway with one bar of signal, you have offline behaviour, sync conflicts and two people editing the same job. That is the part that separates a weekend tool from a real build.
What Drives the Price
The crew's phone. Viewing today's jobs is easy. Updating from the field, with photos, signatures and bad signal, is the expensive half.
Rebuilding the day. Drag a job and everything after it moves, the customer gets told, and the technician's phone updates. This is the feature owners ask for last and value most.
Job history that sticks. What was done, by whom, what parts, what the customer signed. Once you keep it, you have inherited real records.
The connection to invoicing. Most of the value of field scheduling is that the invoice goes out the same day. That connection is a small project on its own.
Realistic Ranges
| What you need | Band | Typical cost |
|---|---|---|
| A shared calendar and a group chat | Tools you have | Often already paid for |
| Jobs, crews, a day view, phone read-only | One developer | $3,000 to $12,000 |
| Field updates, photos, live reschedule, invoicing link | Small team | $15,000 to $45,000 |
A Concrete Version
A plumbing company with six vans wanted a full dispatch system. What the owner described as the problem, when I asked what actually went wrong last week, was that he did not know a job had finished until the technician called at the end of the day, so the next job went out late and the invoice went out two days later.
That is one screen with a button on it that says done, and a message to the office. We built that and the invoicing connection first, inside the one-developer band. The full dispatch board he originally asked for was never built, because after eight weeks he did not need it. The scheduling was never the problem. The silence between jobs was.
The Honest Counterpoint
There are strong field service products on the market that do all of this, and for many companies renting one beats building. Build when your work has a shape those products handle badly, such as multi-day jobs, unusual crew rules or equipment that has to be tracked with the job. If your work is ordinary dispatch, buy it, and spend the money you saved on the one thing that is not ordinary.
Frequently Asked Questions
Do my technicians need an app from the store?
Usually not. A web page saved to the home screen looks the same to them and avoids app store reviews for every change. Consider a real app only when you need the camera, location or reliable offline use.
What about tracking vans on a map?
Available and usually less valuable than it sounds. Owners ask for the map and then use the completion notification. Try the notification first.
How long until we can use it?
Three to eight weeks for the first useful version. Start with the piece that removes the most daily phone calls, not the piece that looks most impressive.
Should my customers see the schedule too?
Usually not in version one. A customer-facing view means a second kind of login, appointment windows you are then committed to, and notifications when the day moves. Get the office and the crews working first, then decide whether customers need a screen or simply a better text message.
The Bottom Line
Buy the calendar, build the part that tells the office what happened in the field. That is where the money and the time actually are. For a written read on your own version with a cost range, the honest read is free. See also custom software vs off the shelf and what a good software quote looks like.
Roberto Espinoza is CEO of Ruzora, which builds custom software for business owners at a fixed price and places pre-vetted senior LATAM engineers with US teams. Get a free honest read on your idea.
