A small service company needs ERP only when it handles stock, production and accounting as one connected whole. If the main pain is who goes where and when, a planner for orders and technicians is enough. ERP can handle that brief too, but you will pay for parts nobody opens, and implementation will take months instead of days.
- ERP joins up stock, purchasing, production and accounting. A planner handles technicians' time and the progress of an order.
- The choice is not decided by the number of employees, but by whether it is material or appointments that hold you up.
- ERP implementation is counted in months, planner implementation in days.
- The most common mistake is buying ERP for planning and using one screen of it.
- The reverse order is safer: start with planning and buy ERP once there is something to connect.
How ERP and a planner really differ
Not in scope, but in their centre of gravity. ERP is built around the document and the stock item: purchase order, goods receipt, goods issue, invoice. A planner is built around time and the person: who is free, who has the qualification, when the visit to the customer takes place.
That also explains the difference in what is easy to do in each of them. In ERP it is easy to find out how many filters are in stock and who ordered them. In a planner it is easy to move a job to another day and immediately see whose slot that takes up.
Either can be done in the other tool somehow, but with friction. A service company that bought ERP for planning usually ends up keeping the plan in a spreadsheet on the side anyway, because in ERP moving an appointment takes four clicks.
Five questions that will decide for you
- Is it material or appointments that hold you up more often? Material means ERP, appointments mean a planner.
- Do you have production or assembly from parts that have to be tracked piece by piece? If so, stock is your main topic.
- How many people change the plan every day? If more than one, you need a shared place for the plan regardless of the rest.
- Is your accounting sorted and are you happy with it? If so, the main benefit of ERP falls away.
- How many months of implementation can you bear? ERP implemented halfway is worse than a spreadsheet, because nobody gets used to it.
The answers are usually mixed. The first question decides: whatever holds you up daily is the topic to be dealt with first.
What each route handles
| Area | ERP | Planner for orders and technicians |
|---|---|---|
| Who goes where and when | One module among others | The main screen |
| Stock and purchasing of material | Yes, the core of the system | No |
| Accounting and invoicing | Yes | No |
| History of jobs at a customer | Yes, through documents | Yes, with the order |
| Implementation time | Months | Days |
| Who sets it up | A consultant or the vendor | Someone from the company |
| Risk that nobody uses it | High, the system is broad | Low, it is used daily |
The last row is the most important one in the decision, and at the same time the one most often forgotten. A tool that is only partly used does not deliver part of the benefit but almost none, because a second set of records grows up alongside it.
When ERP makes sense even for a small company
In three cases. The first is your own stock of valuable parts, where you need to know what is where and to whom it was issued. The second is production or assembly, that is a situation where a product is made from material and work in progress needs tracking. The third is a customer's requirement for documents in a specific form and in a specific chain.
In all three cases the planner does not become redundant, but it stops being enough on its own. A combination in which stock and invoicing live in ERP and technicians' time in a planner is common and works, provided it is clear where each piece of data originates.
The rule is simple: each piece of data has exactly one place of origin. As soon as an appointment is entered into both systems, it is only a matter of time before they diverge.
What happens when ERP is bought for planning
First a long implementation, during which stock and the price list are described, although the core of the trouble was elsewhere. Then training on screens the service team will never open. And finally a return to the spreadsheet, because planning in it is faster.
The company thus pays for a system of which it uses a fraction, and the original trouble remains untouched. The plan is still in two places, appointments are still agreed with three phone calls, and technicians still call the office to ask where they should go.
If this description fits your situation, the answer is not another module but separating the two tasks. Stock and documents belong where they already are. The plan belongs in one place where everyone who changes it can see it.
What a planner that is enough looks like
Three things it cannot do without. The first is a grid with technicians in rows and days in columns. In the planning board, assignments are entered by dragging across cells and clashes are reported at the time of entry, not in the morning at the customer's.
The second is one place for the order. Orders and history holds technicians' work logs, notes, attachments and a record of every change, so the history is not hunted for in e-mails and can be found within a minute when a customer asks.
The third is the ability to adapt the terminology to your own operation. Customisation lets you name statuses and order types the way you call them in your company. That is the difference that decides whether the team gets used to the tool or avoids it.
A fourth thing, which is not essential but saves the most phone calls, is the appointment calendar, which distinguishes what is confirmed from what is still being agreed.
The order that works
Start with the part that hurts daily, and for service companies that is almost always the plan. Implementation is short, the result is visible within a week and it commits you to nothing further. Only when the plan is in order and stock or invoicing starts to get in the way does it make sense to look at ERP.
The reverse order is used too, but it requires discipline: first a long implementation and only after it the discovery of whether planning is workable in it. If it is not, a planner is added to the ERP afterwards, and it would have been faster to start with it.
The risk of both routes is reduced in the same way: test on a real week, not on a presentation. Plan next week in the new tool alongside the old way and compare where the plan diverged and how many phone calls were saved.
When neither is enough
There are companies that neither a planner nor ERP will help, because the trouble is not in the tool. You can tell because the plan diverges from reality even in a week when nobody moved anything. The cause is usually a missing rule about who is allowed to promise an appointment to a customer.
A tool will not replace such a rule, it will only make it visible. That is why it pays to introduce it before anything is bought: an appointment is valid only once it is entered in the plan, not after a promise on the phone. Companies that have done this usually manage with a simpler tool than they originally considered.
Frequently asked questions
Can a planner be replaced by ERP later?
Yes, and it is a common route. The condition is that the data can be exported and that the planner is not the place where invoicing and accounting originate. As long as only the plan and the order history live in it, replacing it is a matter of transferring the list of technicians, customers and open orders.
Can ERP handle technician planning?
Usually yes, but planning in it tends to be one module among others, not the main screen. The difference shows in the speed of a routine task: moving a job to another day should be a matter of dragging with the mouse, not opening a form and saving in three steps.
How long does implementing ERP take compared with a planner?
ERP is implemented over months, because stock, price lists, accounting links and approvals have to be described. A planner is implemented in days, because it needs a list of technicians, their qualifications and the open orders. The short implementation time is the main reason it is usually the starting point.
What if we already have an accounting program?
That is an argument for a planner, not for ERP. Accounting is usually the part companies have had sorted the longest. Moving to ERP would rewrite it all over again, whereas a planner leaves it alone and deals only with the half of the operation that causes delays every day.
Does the number of employees decide the choice?
No. The operation decides. A company of three people with dozens of concurrent orders and changing appointments needs order in its plan more than a company of thirty people that goes out on long installations agreed well in advance.
Technicians in rows, days in columns across a continuous 35-day strip. Create a new appointment by dragging; the app warns you about conflicts.
Orders and historyAttachments, internal notes and a record of every change in one place on the order.
Customisation without a developerName statuses, appointment types, labels and qualifications the way your company does.
Your first software for a service company is not chosen by a list of features. What to go by instead, how to run the trial and what to avoid with a first purchase.
Will technician planning software pay for itself? How to work it outNobody can calculate the return on planning software for you in advance. What to measure before and after so your own numbers answer it.
How to roll out planning software step by stepA model schedule for rolling out planning software: what to set up first, who to involve, what to avoid and how to tell that the team is not going back to Excel.
Plan more simply
ServisBook free for 30 days, no credit card.
Free trial →