How to convince the board
to buy an ITSM system
Arguments, ROI calculator and a ready-made presentation template for the CFO - proven in 50+ projects
I know this scenario by heart. An IT manager spends weeks analyzing solutions, comparing products, talking to vendors. Picks a system. Then walks into the CFO's office and hears: "Why do we need this? We already have email." This article is the essence of four years and dozens of conversations with CFOs and CEOs of Polish companies.
Why typical IT arguments do not land with the board
The IT manager says: "We need SLA, escalations, CMDB, ITIL workflow."
The CFO hears: "I want to spend money on something I do not understand."
The problem is not the substance but the communication. The board operates in three categories: money, risk, time. Your presentation has to answer three questions before they are asked:
- What does it cost now (no system)?
- What will it save after implementation?
- When does it pay back?
ROI calculator - what the absence of ITSM costs
Technicians' time spent on an email-based help desk
Handling a ticket by email takes time at every step: finding the message in the inbox, replying, tracking status, following up. In an ITSM system the same process is shorter because the ticket has one place, one status and one history. The real time difference is best measured in your own company - below we show how to build that calculation on your own assumptions.
Illustrative example. Assume a company has 200 employees, each one reports on average 3 IT issues per month, and tidying up the process shortens the handling of a single ticket by a certain number of minutes. Then:
- 200 x 3 = 600 tickets per month
- 600 tickets x (minutes saved per ticket) = total hours of technicians saved per month
- Hours saved x cost of one technician hour = monthly saving
- Monthly saving x 12 = annual saving
Plug in your own real figures (number of tickets, cost of an IT FTE, estimated time saving) - the number in your presentation will then be credible and will hold up to questions from the CFO.
This is the cost of having no ITSM system just for ticket handling time. Not counting: unresolved problems, tickets falling into the void, lack of reporting for the board, the risk of a license audit.
The cost of unplanned downtime without an SLA
Companies without formal ITSM often have longer and less predictable resolution times because prioritization and escalation are missing. Illustrative example: if a manufacturing company knows the cost of an hour of downtime and the number of events per year, it can estimate the saving as (reduction in response time) x (hourly cost) x (number of events). Plug in the specific numbers from your own company data.
The cost of a license audit without ITAM
License non-compliance found during an audit can mean surcharges and additional fees - the scale depends on the size of the breach and the vendor's licensing terms. An asset management module (ITAM) helps you maintain a current license inventory and reduce that risk.
Ready arguments for the CFO - one sentence each
"The time of our IT technicians costs X PLN per month on ticket handling. An ITSM system will cut that time by 40% - a saving of Y PLN per year."
"Last year we had Z outages of critical systems. Without an SLA and escalation, the average response time was N hours. The cost of downtime for the company is M PLN per hour."
"NIS2 requires an inventory of IT assets and an incident register. The penalty for failure can reach up to 10 million euros. An ITSM system covers both requirements. Is it worth the risk of not deploying it?"
"Implementing ServiceDesk Plus for 200 users costs X PLN as a one-off and Y PLN annually. Return on investment within Z months according to the calculation I am about to present."
Arguments for the CEO (different from the CFO)
The CEO does not think about operating costs - they think about risk and reputation.
Risk argument: "If a client reported a failure and no one replied for 48 hours because the email went to spam - the CEO learns about it from the client, not from IT. ITSM gives the CEO visibility: how many tickets, how many open, how many overdue."
Scaling argument: "We are growing. Next year we will have 300 employees. At 200 we are already at the limit of an email help desk. An implementation now, at 200 people, is cheaper and faster than at 400." Manufacturing companies can also benefit from the article on ITSM for manufacturing. ROI is even more concrete there.
Competitiveness argument: "Our clients are asking about SLAs. We cannot sign a contract with a contractual penalty for response time if we do not have a tool to measure and enforce those times."
How to build a presentation for the board - 6 slides
| Slide | Topic | Key message |
|---|---|---|
| Slide 1 | Current situation | Data: how many tickets per month, how long handling takes, how many escalations to the boss because the user did not get a reply |
| Slide 2 | Cost of the current situation | One number: "Having no ITSM system costs us [X] PLN per year." Calculation: technicians' time + downtime cost + license audit risk |
| Slide 3 | Proposed solution | One product name. One sentence on what it is. Three bullets on what it does. No more - the board does not need to understand the technical architecture |
| Slide 4 | Implementation costs | Table: Year 1 / Year 2 / Year 3 - one-off and annual. Full transparency builds trust |
| Slide 5 | ROI and payback period | "The investment will pay back in [N] months." One chart: where the cost line meets the savings line |
| Slide 6 | Next steps | Date of the decision. Who is responsible. When a demo can be seen. What you need from the board (decision / budget) |
Most common board objections and how to answer them
"We have it in Excel, it works."
"Excel does not send automatic alerts when an SLA is breached. Excel does not generate a report on how many tickets came in last quarter and how many were resolved on time. Do we see the same risk?"
"It is too expensive."
"How much does the lack of this system cost us? I have done the math - it is [X] PLN per year of technicians' time. The investment is [Y] PLN. Payback in [N] months. Is that too much?"
"We do not have time for an implementation right now."
"That is exactly why I am proposing the implementation now, in a calm period. Every month without the system is [X] PLN of losses. The longer we wait, the harder the implementation will be - the company is growing, tickets are piling up."
"And how does it actually work in practice?"
That is an invitation to a demo. Set a date for the demonstration immediately - in that same meeting.
How much a ServiceDesk Plus implementation costs - real numbers
I am Head of Sales and I am not hiding the fact that I represent ManageEngine. Still, I give you real numbers because transparency builds trust more effectively than marketing. Technical details and project stages are covered in a separate article on the ManageEngine implementation in Poland.
ServiceDesk Plus: licensing model per IT technician
SDP is licensed per IT technician (support staff), not per end user. The number of technicians is typically 3-10% of the company's headcount.
- SDP Standard Edition: free for up to 5 technicians (cloud)
- SDP Professional 10 technicians: approximately $2,295/year = around 8,000-9,000 PLN/year
- Implementation and configuration: 15,000-25,000 PLN one-off (standard 8-10 week implementation)
- Total Year 1 (10 technicians): about 23,000-34,000 PLN
If the savings calculation from the earlier section (computed on your own company data) exceeds the annual cost of the system, ROI is positive in year one. The on-premise version (perpetual license): higher up-front cost, lower annual cost.
FAQ
How long does a typical ServiceDesk Plus implementation take?
A standard implementation for 50-200 users: 6-8 weeks. It covers configuration, data migration from email/Excel, and user training. After go-live we offer an optional hypercare period (typically 2-4 weeks) with project support. The scope and conditions are agreed in the contract.
Will users accept the new system?
That depends on the implementation. The key factors: self-service portal (employees report via the browser, not email), SMS/email notifications about ticket status, intuitive interface. From our experience adoption is fast when users see concrete value from day one. The system is usually actively used 3-4 weeks after go-live.
What about historical data from email?
We can migrate email correspondence history into archived tickets. The scope and depth of migration (e.g. attachments, threads, custom fields) is agreed individually before the project. We usually migrate data from the last 3-6 months. Older archives are treated as read-only or skipped with the client's consent.
Can I start with a small deployment and expand?
Yes. We start with the Incident Management module, after 3 months we add CMDB, after another 3 months - Change Management. You pay for what you actually use.
Want to see the ROI calculation for your company?
Fill in 5 fields (number of employees, number of technicians, cost of an IT FTE) - in 15 minutes I will prepare a calculation ready for your board presentation.
Order a free ROI calculation →