ROI calculator
What breakdowns and paperwork cost you.
Four numbers you already know, multiplied. No coefficients of ours, no savings percentages and no promises: the result comes entirely from what you put in.
What it costs you per year
€129,200
between breakdowns and manual admin
It is an order of magnitude, not an accounting figure: it comes from four estimates of yours. And it is what it costs you today, not what you would save: no system takes this to zero.
In breakdowns
€120,000
In manual admin
€9,200
What to put in each field
Unplanned breakdowns per month
Only the ones nobody saw coming. A scheduled service does not count here, because you were going to do it anyway. If you do not keep count, ask the maintenance manager: they remember every one.
Average cost per breakdown
This is where almost everyone underestimates. It is not the price of the part: it is the hour of stopped line, the technician's hours, the rush order that costs more and the order that arrived late. If in doubt, put in the one you could defend to your finance director: this field is the one that moves the result most.
Admin hours per week
The time your team spends copying things up. Filling in the sheet again on a computer, reconciling the store spreadsheet, hunting for the certificate a customer asked for, assembling the monthly report. That is not maintenance time: it is typing time. And if the hours a technician spends writing up a breakdown are already inside the field above, do not count them again here.
Average hourly cost of the team
The real cost to the company of an hour of those people, not their take-home pay. If the person copying things up is a technician or a plant manager, this figure climbs more than you would think.
The arithmetic, in full
That is all of it. There is nothing else behind it, which is why the number that comes out is yours and not ours.
The 46 are effective working weeks, not the 52 on the calendar: nobody has their team copying up paperwork during the holidays. Thirty working days of leave plus public holidays take out around six weeks. If yours are different, adjust the weekly hours and it works just as well.
On breakdowns
breakdowns per month × 12 × average cost
On manual admin
hours per week × 46 × hourly cost
What it costs you a year
the sum of the two
Why you will not see an "estimated saving" here
Almost every calculator of this kind ends up applying a percentage: "cut your downtime by 30 %". That number has to come from somewhere, and when it does not come from measured deployments it comes from an assumption. And an assumption, once typed into a spreadsheet, stops looking like one.
Here you will only see what it costs you today, worked out from the four figures you entered yourself. The comparison you make with what you already know about your plant. We publish figures when we can say exactly where they come from, and not one before.
The four doubts it usually raises
None of them is answered by asking you to take our word for it. All four can be checked against the sum written above.
“That number looks high”
It may be, or it may be low: the figure is worth exactly what the four inputs are worth, and you entered them. If somebody on your team would put in different ones, change them and see what comes out. From there the argument is no longer about this screen but about what a stoppage really costs in your plant, which is the one worth having.
“Is there a hidden coefficient?”
No. Breakdowns times twelve months, and hours times forty-six working weeks. Nothing else, and it is written above so you can check it without trusting us. If you were expecting a savings percentage buried inside the sum, there is not one.
“We pay those hours anyway”
True, and that is why it is not a payroll saving: it is capacity. They are hours of qualified people that today go into typing and could go into maintaining. If they do not count as a cost in your company, keep only the breakdowns part: the figure drops and stays real.
“And how much of this would FluX save me?”
It depends on your case, and a percentage printed here would mean nothing. What can be done is look at where the bulk comes from and separate which part FluX touches and which part it does not. That takes half an hour, with your data in front of you.
What the number is good for
It puts a price on doing nothing
Any improvement proposal competes against leaving things as they are, which appears to cost zero. This is what that option actually costs, and it is what turns "we ought to sort this out" into something you can take to a management meeting.
It tells you where to start
They are almost never split evenly. If the weight is on breakdowns, the problem is preventive work and critical spares. If it is on manual admin, it is capture and traceability. That points the first decision, whatever you end up buying.
It holds up even if you never call us
The four inputs are yours and the sum is published above, so the number stands on its own: to compare tools, to justify an internal project, or to decide that this is not the year. And if you want, we go through it together and tell you which part FluX can touch and which part it cannot. There are things it cannot.
Tell us about your operation
Thirty minutes, your case, no slides. We leave the call telling you whether this is useful to you, and if it is not, we tell you that too.