When an organization asks for several proposals for IT services, the first impression is almost always similar. Every document includes words like support, monitoring, backups, information security and professional service. The prices may differ, but on paper it sometimes seems that everyone is offering more or less the same thing. And then you start reading in depth. What exactly is included in the price? During which hours is there a response? Who handles a fault that happens at two in the morning? And what happens when something is needed that was not explicitly mentioned in the proposal?
This is where the real differences begin. The most convenient way to compare is to put the same questions to every provider and ask for clear answers in writing. In this article we will go over the service models common in the Israeli market, see who each one suits and what to look for inside the proposal itself. We will also touch on information security, regulation and backups, and finally see what an orderly start of work with a new provider looks like, from the moment the first conversation takes place until the service becomes part of the organization's routine.
Which Service Models Exist in the Market?
Before comparing prices or response times, it is worth understanding which service model is being offered to you at all. Two providers can present a very similar-looking proposal, while in practice one offers handling as needed and the other takes ongoing responsibility for the entire computing environment. The match between the model and the organization matters much more than one more line in the specification. The five common models:
- Hourly, per call — handling incidents only. Suits a small organization with few systems.
- Monthly retainer — a block of hours agreed in advance. Suits an organization with stable needs.
- Full management — infrastructure, monitoring and support. Suits an organization without an internal team.
- Support for an internal team — depth in specific areas. Suits an organization with a systems person.
- Managed cloud — a cloud environment and ongoing management. Suits an organization that has moved or is moving to the cloud.
A full management model usually suits organizations that have no internal technology team managing the systems day to day. In such a situation the provider becomes the central address for managing infrastructure, monitoring, backups, security and user support. For a management team that wants to know whom to call for every fault or question, this can be a very convenient model. What matters is to define the boundaries of responsibility in advance: which systems are included, what happens outside operating hours, and when a particular service becomes a separate project.
The support model suits better an organization that already employs a systems person or an IT team. In this case the provider reinforces it in areas where additional knowledge is needed, provides backup during hours when the team is unavailable, and can take responsibility for defined professional areas. The organization's unique knowledge stays in-house, and the provider adds the layer that is missing.
What Is Worth Checking Inside the Proposal Itself?
The first thing to look for is the boundary between what is included in the service and what will be charged separately. It is not enough to see a clause called full support. It is worth understanding which systems are covered, which users, during which hours, and what happens when a request goes beyond the ongoing service. A good way to understand the boundaries is to ask the provider for a few real examples: a user who cannot connect from home, a server that goes down in the evening, installation of new software or an employee moving between departments. Is each of these cases included? The answers give a much clearer picture than a general sentence at the beginning of the proposal.
Response times, too, should be written in a way that is hard to interpret in two ways. What counts as an urgent incident? Within how long does handling begin for a fault that shuts down an entire department? And what happens when the incident is not resolved within the defined time? An organization that works at night, on weekends or on holidays needs to check that the response it is buying truly exists during those hours, and that there is a person able to begin handling it and not just a system that receives the request and waits until morning.
Backups also deserve more than a single line in the proposal. How often are backups taken? Where is the copy stored? How many versions are kept and for how long? When did someone last actually perform a restore test? The last question is especially important, because a backup file that has not been tested does not yet mean the organization knows how to get back to work in the event of a fault. It is worth understanding also how long restoring a central system is expected to take. If the ERP system is down, for example, the difference between a restore of an hour and a restore that takes a whole day is felt immediately across the organization. These are things that are easy to find out at the proposal stage and much less pleasant to discover in real time.
How Do You Check Security and Regulation?
Almost every IT proposal today includes an information security clause, so the words themselves already say very little. The more interesting question is what happens in practice. Which security systems are managed by the provider? Who sees the alerts? Is there continuous monitoring, or does someone check the system only after the customer reports that something is wrong? And what happens from the moment a suspicious alert is received until someone decides whether it is a real incident? When a provider can describe the process simply and clearly, it is much easier to understand what the organization is really getting.
Organizations operating in sensitive fields need to add to the check the requirements that applied to them in the first place. Healthcare, finance, law and other fields work with information that calls for tighter control, so it is worth making sure the provider knows the relevant requirements and knows how to implement them in the computing environment. At ExSitu we operate in accordance with the ISO 27001 standard and the requirements of GDPR and HIPAA, and work with the Israel National Cyber Directorate.
And what happens if, despite all the protections, an incident occurs? This conversation is better held before signing. Who is the first person to receive the alert? Who notifies the organization? Who coordinates the handling and who is authorized to make decisions during the incident? It is important to understand also what documentation is kept afterward and what management receives at the end. When all these things are defined in advance, there is no need to start searching for phone numbers and sorting out areas of responsibility at exactly the moment when every minute counts.
What Does an Orderly Start of Work Look Like?
The move to a new provider is not supposed to begin on the day the old service ends. A good start opens with a survey of the existing situation. You go over the servers, workstations, licensing, communications, backups, permissions, security systems and places where gaps already exist. Sometimes you discover a system nobody has touched in years, a backup that has not been tested for a long time or a license that depends on an employee who has already left. The goal at this stage is to understand the environment as it truly works, and then set priorities: what must be handled immediately, what can wait and what is right to change later. That way the first months do not turn into a series of surprises.
After the survey comes the handover. If there is a previous provider or an internal team, this is the stage where documentation, permissions, system details and knowledge accumulated over the years are transferred. In a complex organization the handover can take several weeks, and that is fine. It is better to transfer responsibility gradually than to discover a month after the move that nobody knows who holds the access details for a certain system.
Afterward you settle into routine: ongoing handling, monitoring of the systems, periodic meetings and reporting to management. For many organizations, one short meeting per period, a report summarizing what happened and an orderly plan for what comes next provide exactly the level of visibility needed. Management knows what is going on, the technical team knows what is being handled now, and important issues do not wait until they turn into a fault.
A Good Comparison Is Made on the Details, Not the Headlines
When you lay several proposals on the table, it is easy to start from the price. But before reaching the bottom line, it is worth checking whether you are comparing the same service at all. Hourly calls, a retainer, full management, support for an internal team and managed cloud are very different models. An organization without an IT team may need a party that takes broad responsibility for the computing environment, while an organization that employs a systems person may be looking precisely for additional professional knowledge and coverage at times when the internal team is unavailable. That fit has to come before the financial comparison.
Once the model is clear, you can move on to the details that will really affect the day to day: what is within scope, who is available and during which hours, how response times and escalation are defined, how backups are managed and when the last restore was tested. In information security, it is worth understanding who monitors the systems and what happens from the moment an event is identified. If the organization is subject to regulatory requirements, these too should enter the comparison. And finally, it is worth asking what the first weeks will look like. A provider that already at the proposal stage presents an orderly survey, a handover process, a division of responsibility and a reporting routine gives you a much better picture of life with them after signing.
In the end, peace of mind comes when the organization knows who is responsible for everything, and these things are clear to both sides before the first fault.
ExSitu: Managed Cloud, System Administration Services and Information Security
ExSitu provides managed cloud, system administration and information security services to businesses and organizations in Israel, from startups to enterprise organizations. The team includes about fifty technology experts and serves hundreds of customers and tens of thousands of users, including public companies, healthcare organizations, government bodies and law firms. The service setup includes monitoring and security centers operating around the clock alongside 24/7 human support, and work in accordance with the ISO 27001 standard and the requirements of GDPR and HIPAA, with an ongoing interface with the Israel National Cyber Directorate.
If you are comparing IT companies for business right now, do not settle for headlines that look similar in every proposal. Send us the same questions you are putting to the other providers. We would be happy to explain exactly what is included, what response times look like, what happens in a real incident and what the joint work will look like from the first moment.
