Case study
The same morning, seen from four different seats
Dispatch software is four products wearing one name. The owner, the dispatcher, the technician and the customer all need the same Tuesday, and every one of them needs it to look different. Kreworx is built around that, and the demo lets you sit in any of the four chairs.
- React
- Node
- MongoDB
- Live map
- Realtime
What it is for
The group chat is the system
A four-van contractor runs the day across a whiteboard, a paper diary and a group chat, held together by one person who remembers everything. It works, right up until that person takes a holiday, or two people move the same job, or a customer rings about an appointment nobody wrote down.
Four people, four different mornings
The owner wants to know what got done and what is owed. The dispatcher wants the board and the gaps in it. The technician wants his own day and nobody else's. The customer wants one thing: a time. Software that serves one of them well and the rest badly gets abandoned by the three it failed.
The call that costs the most and is worth the least
'What time are they coming' is the most common inbound call a service business takes. It interrupts whoever picks up, it tells the customer nothing they could not have been told automatically, and it happens again an hour later.
Decisions, and why
The parts worth arguing about. Anything here could have gone the other way, and the reason it did not is the actual work.
Four seats, and no sign-up to reach them
The demo opens on a role picker rather than a login. Pick the owner, the dispatcher, the lead technician or the customer, and switch at any time. A single demo account would only ever show one of the four products, and a prospect who saw the dispatcher view would never learn why a technician tolerates carrying it around all day.
Drag the job, do not fill in a form
Rescheduling happens under pressure, usually with a phone against one ear. A modal with a date picker and a Save button is three decisions where there should be one gesture. The job moves on the board and everyone else's view moves with it.
The customer gets a link, not an account
Nobody is installing an app to find out when the furnace engineer arrives. The customer receives a text with a link, the link shows the day, and when the job moves the link already knows. No password, nothing to download, and nothing to delete afterwards.
The board shows state, not just time
A job waiting on a part cannot happen today however much room the calendar says there is. Done, on site, and parts on order each read differently at a glance, because a dispatcher scanning for the next gap is pattern matching rather than reading.
The data resets every night
It is a demo, so it is built to be broken. Move everything, cancel everything, and it is back by morning. Nothing in it is real: Northline Mechanical, its crews and its customers are all invented.
What it deliberately does not do
- It does not take payments. The owner view tells you what is owed, and collecting it is somebody else's job.
- No accounting or payroll integration. A contractor already has one of each, and the useful version of this is an export rather than a second place to keep the same numbers.
- Map tiles are a free tier, which is right for a demo and would be a paid plan for a real fleet.
- It is built for a handful of vans rather than a hundred. The fleet that needs seat-based enterprise pricing is not the one this is for.
Where this one stands
Kreworx is our own product rather than client work, which is why it carries no client logo. It exists to be shown, and for the right contractor, to be installed and run as theirs.
Running the day out of a group chat?
Open the demo, sit in whichever chair matches your job, and see whether the board is better than the whiteboard. If it is, the next step is a twenty-minute call about what your version would need.