A beginner most often chooses software for a service company by the list of features, and that is exactly the dead end. The lists look alike for every tool, because they are written off each other. A single question should decide: can the tool handle the situation that repeats in your company every day, without you having to work around it in a spreadsheet?
- Do not choose by the feature list, but by one situation that repeats daily.
- Run the trial on a real week, not on an empty demo.
- Check the permissions on notes, logging from a phone and your own terminology.
- Do not start with timesheets and invoicing; they add work before they take any away.
- From three people, the cost of coordination shows enough that it starts to pay back.
First name what hurts
Before you start comparing tools, write down three situations that repeat in the company and cost time. For service companies it is usually one of these:
- A customer calls and wants an appointment. You do not immediately know who is free and allowed to do it, so you promise to get back to them.
- An emergency comes in the morning and the plan has to be reshuffled, which means several phone calls.
- A technician calls the office to find out what was done at the customer last time.
- Nobody knows who is on holiday next week until someone asks.
- The paperwork for invoicing is collected a week after the month ends.
This list is your specification. A tool that solves the first three points but not the fourth is better for you than one that can do everything and handles none of them comfortably.
Four categories of tools and what to do with them
| Category | What it is for | Where it fails a service company |
|---|---|---|
| Spreadsheet and shared drive | Cheap, understandable, available right away | Concurrent editing, attachments, the field |
| General calendar or task planner | Good for meetings | Cannot handle people's capacity or multi-day assignments |
| Planning and order software | Plan, capacity, job history | Does not handle accounting or stock |
| Enterprise system (ERP) | Everything together | Set-up and cost a small company cannot sustain |
A beginner usually hesitates between the first and the fourth row, that is, between what they have and what sounds thorough. The practical answer tends to be in the middle: start where time is lost daily, and leave accounting where it is.
The comparison with today's practice, that is, with a spreadsheet, is described in the comparison of ServisBook with Excel.
How to run the trial so that it shows something
Clicking through an empty trial in an afternoon finds out nothing. This procedure does:
- Re-enter one real week into the tool, one you already have behind you, holidays and sick leave included.
- Enter one multi-day order into it, if you do such orders, and try moving it by a week.
- Have one technician log two jobs from a phone, not from the computer in the office.
- Try two morning changes to the plan the way they actually happened to you. Measure how many clicks and phone calls it took.
- Try to find what was done at one customer last time, without knowing the order number.
Point three is skipped most often, yet it decides the most. A tool that technicians will not log into stays half empty.
Questions to ask before signing
Three things are hard to change once the company is up and running on it:
Who can see internal notes. A note about a customer has its place in the system, but it must be certain that the customer will not see it.
Whether a technician can manage logging on a phone. Not whether a mobile version exists, but whether a job can be logged in it one-handed next to the van. Mobile for technicians is in practice the part that the rollout stands or falls on.
Whether you can name things your own way. A company that has for years called a job a call-out and an installation an action adapts to someone else's terminology reluctantly. In customisation without a programmer, statuses, appointment types and labels are named according to the company's habits.
What to avoid with a first purchase
Do not buy based on a demo in which everything fits. The demo is prepared for an ideal operation, and yours is not ideal.
Do not start with timesheets and invoicing. It is the most measurable part and the worst start, because it adds work for the technicians before it takes any away from them. The rollout then stalls on their resistance and not on the properties of the tool. The order of steps is discussed in rolling out planning software.
Do not roll out two tools at once. When something goes wrong, you will not be able to tell which one is to blame, and you will give up on both.
And do not re-enter old history into the new tool. Transfer the customers and the orders in progress, and let the rest run its course where it is. Re-entering the archive is work that nobody will appreciate and that drags the rollout out by months.
From how many people it starts to make sense
From three. Up to two people, coordination is cheap: one person keeps the plan, asks the other across the street and offers an appointment from memory. The cost that software would remove is small there.
From three it changes, because combinations grow faster than people. Technicians alternate at a single customer, the question of qualification is added to free time, and half-arranged appointments that nobody has confirmed yet are added to today's plan.
One could object that an experienced planner can manage it from memory even with five people. They can, as long as they are at work. The cost is then not paid every day, but all at once, in the week of their holiday.
What software will not solve
It will not change how the company works. A tool sorts out where information lies and who can get to it, but it will not decide how much time to allow for a job or whom to send to a difficult customer.
Nor will it ensure discipline in logging. If a technician does not write down what they did, the history will be incomplete in any system. Software can make logging cheap enough that it is worth doing on site; it cannot force anyone to do it.
What goes away is searching and repeating the same thing over and over. The answer to who is free on Thursday and what was done at the customer last time exists in one place.
Frequently asked questions
What should you go by when choosing your first software for a service company?
By the one situation that repeats most often in your company, not by a list of features. The lists look alike for every tool. The difference only shows once you re-enter a real week of your operations into the free trial, absences and half-arranged appointments included.
Should a small service company go straight for a large system?
Usually not. Large systems require a set-up that a small company cannot sustain, and their benefit only comes after months of rollout. It is more practical to start with what hurts daily, that is, the plan and the order records.
How long should the trial last and what should you do in it?
Ideally a month, and on real data. Re-enter one ordinary week into the tool, have a technician log a few jobs in it and try two changes to the plan. An empty trial clicked through in an afternoon shows nothing.
What should you check before the company commits?
Who can see internal notes, whether a technician can manage logging on a phone, and whether you can name the statuses according to your own habits. These three things are hard to change afterwards.
From how many people does software for a service company make sense?
From three. Up to two people, one person keeps the plan in their head and asks the other across the street. From three, technicians alternate at customers and the combinations of free capacity and qualifications grow faster than the headcount.
Technicians in rows, days in columns across a continuous 35-day strip. Create a new appointment by dragging; the app warns you about conflicts.
Customisation without a developerName statuses, appointment types, labels and qualifications the way your company does.
Mobile for techniciansThe technician opens a browser, sees their day, starts work and logs the tasks performed.
The cost of software for a service company over three years of use: how pricing models behave over time, how to calculate it and what decides by team size.
Installation planning for beginners: where to start and what to avoidInstallation planning differs from service in job length and crew size. Six steps to start with and the mistakes that most often sink it.
A service log in Excel: what belongs in it and when it stops being enoughA service log in Excel is enough as long as one person fills it in. What belongs in it, what Excel can handle with the right design and what stays expensive in it.
Plan more simply
ServisBook free for 30 days, no credit card.
Free trial →