IT Support for SMEs in Vienna: Services, Costs, and Selection

IT support means reliably ensuring a company's ongoing IT operations—without the need to build an in-house IT department.

For many small and medium-sized enterprises, this represents a practical middle ground. A full-time employee is rarely fully utilized when managing ten to fifty workstations and can never cover the full spectrum of required expertise — ranging from networks and servers to Microsoft 365, security, and data backup. At the same time, the "someone handles it on the side" approach is no longer sustainable as the system landscape grows.

The crucial difference lies not in troubleshooting. Good support is defined by how rarely system failures occur — not by how quickly someone arrives once a problem has happened.

This article outlines the services involved, how the collaboration works, available cost models, and what to look for regarding contracts and response times.

Table of contents

• What IT support entails
• Who benefits from external support
• Overview of services
• How the collaboration works
• Cost models: hourly pool, flat rate, or billing based on actual effort
• Contract and response times
• In-house IT vs. external partner
• Choosing a provider: a checklist
• Conclusion on IT support
• FAQ IT support

What IT support entails

In everyday usage, the terms "IT care"  and "IT support" are generally used interchangeably. Both refer to the ongoing technical support provided to a company by an external partner. "IT service" is the broader term and can also encompass individual projects, consulting, or one-off assignments

IT support, IT management, or managed services?

IT support encompasses the ongoing technical management of workstations, servers, networks, Microsoft 365, security, and data backups.

Managed services go a step further: this typically refers to ongoing, contractually defined support that includes monitoring, maintenance, security measures, defined response times, and regular reviews.

The decisive factor is not the label used, but the agreed scope of service: simple troubleshooting differs significantly from proactive IT support that includes monitoring, documentation, backup verification, and strategic planning.

The scope can be broken down into three levels:

• Reactive: resolving issues, answering user queries, replacing hardware
• Proactive: monitoring, updating, and securing systems before failures occur
• Strategic: planning investments, preparing for system migrations, and defining security standards

The shift from reactive to proactive support makes the real difference. Relying solely on reaction means constantly operating in crisis mode: a server fails because a hard drive had been reporting errors that went unnoticed; a backup process has been failing for months, a fact only discovered when the data is actually needed.

Proactive support shifts the workload to an earlier stage—into scheduled maintenance windows rather than unplanned outages during the workday.

For whom external care is worthwhile

Typical situations that prompt companies to take this step:

• IT is being managed on the side by someone whose primary role lies elsewhere and who lacks the time for it
• There is no backup coverage when that person is on vacation or out sick
• No one knows when a system recovery was last tested
• Systems have expanded over time but were never documented
• A security incident — or a near-miss — has brought the issue to the forefront
• A major project is on the horizon: a server upgrade, a move to the cloud, or opening a new location

In practice, the second point is the most common trigger. As long as everything is running smoothly, the lack of backup coverage goes unnoticed; it only becomes apparent when that coverage is actually needed.

A note on company size: External support is not dependent on a minimum number of employees. Even a business with just five workstations has a server, a network, backups, and security requirements—albeit on a smaller scale. Conversely, companies that employ their own in-house IT staff often collaborate with external partners as well—for instance, to handle specialized tasks or provide backup support.

Overview of service areas

User Support

The most visible aspect: the printer isn't working, the mailbox is full, or a file is missing. What matters here is less about technical feats and more about having accessible points of contact and short lines of communication — ideally, people who are familiar with the business and its specific characteristics.

Maintenance and monitoring

The invisible component that determines the frequency of system failures. This includes structured patch management that deploys security updates in a controlled manner without disrupting operations.

Monitoring systems flag issues before they escalate into actual outages—such as a hard drive showing early signs of failure, storage filling up, or a failed backup run. The crucial factor here is not the technology itself, but rather ensuring that someone actually acts on the alerts.

Security

A multi-layered approach comprising endpoint security, email protection, and access security via multi-factor authentication. This is complemented by raising employee awareness regarding the most common attack vectors — see phishing protection and the broader context of ransomware protection.

Data backup

The last line of defense. A robust backup strategy based on the 3-2-1 rule is essential, as is regularly verifying that data can actually be restored. For Microsoft 365 environments, a dedicated Microsoft 365 backup is also required, since Microsoft does not protect the content in the sense of a data backup.

Consulting

It is the area with the greatest leverage—and the one most frequently overlooked. When is a server fully depreciated and in need of replacement? Is a move to the cloud worthwhile, or is it better to keep operations on-site? (See our article on cloud strategy for more on this.) And what level of security is appropriate without hindering day-to-day operations?

For companies in Vienna and the surrounding area, FIGULI CONSULTING handles these areas as an external IT partner—covering everything from user support, maintenance, and monitoring to strategic planning.

Discuss IT support with FIGULI

How the collaboration works

Professional support does not begin with a contract, but with an inventory assessment.

1. Initial consultation: Current situation, expectations, known issues
2. Inventory assessment: What devices, servers, software, access credentials, and contracts are in place?
3. Evaluation: What is urgent, what is a medium-term priority, and what is non-critical?
4. Agreement: Scope of services, response times, cost model
5. Onboarding: Documenting access, setting up monitoring, establishing workflows
6. Ongoing operations: Support, maintenance, regular reporting, and coordination

The inventory assessment is sometimes viewed as an unnecessary preliminary step. Yet, it is the most critical phase; without it, a partner assumes responsibility for unfamiliar systems, and any misjudgment carries risks for both parties.

One often underestimated aspect is the need to clarify access rights during the handover. In environments that have evolved over time, administrator passwords may be held by a former service provider or a departed employee, or simply remain undocumented. Sorting this out is a laborious but essential task.

Regular coordination — ideally on a quarterly basis — is also crucial; these meetings should focus not on troubleshooting, but on upcoming investments, expiring contracts, and planned initiatives.

Cost models: hourly pool, flat rate, or billing based on actual effort.

For many SMEs, an hourly pool offers a sensible starting point. You purchase a block of hours at a discounted rate and draw upon it as needed. This combines two advantages: costs are predictable because the total amount is fixed, yet you are not locked into a set monthly fee while your actual requirements remain uncertain.

Two questions are crucial here: how long is the block of hours valid, and what is the billing increment—minute-by-minute, in 15-minute intervals, or in full hours? With numerous small requests, the difference can really add up.

A flat-rate package becomes worthwhile once your needs become regular. It typically covers a defined scope of maintenance, monitoring, and support. It is always important to clarify what is *not* included — such as projects, new hardware/software purchases, on-site visits outside business hours, or the resolution of major incidents.

Regardless of the model, the rule is: compare the scope of services, not just hourly rates. A low rate with many exclusions can end up being more expensive than a higher rate with a clearly defined scope.

What is not automatically included

Not every IT support arrangement automatically covers every special case. Projects such as server migrations, cloud migrations, new office locations, major security incidents, data recovery, hardware procurement, licensing costs, or work performed outside agreed business hours should be handled separately.

This is not a disadvantage; rather, it creates clarity. Good proposals clearly distinguish between ongoing support, planned projects, and unplanned special assignments. This makes it easy to track which services are included in the support package and which require a separate order.

For digitalization initiatives in Austria, there is also the option of subsidized consulting via KMU.DIGITAL. It is worth looking into this before launching a major project.

Contract and response times

The contract should clearly define five key points:

• Scope of services: What is included, and what is billed separately?
• Response times: Within what timeframe will a report be acknowledged—tiered according to urgency?
• Availability: During what hours and via which channels? What applies outside these times?
• Responsibilities: Who makes which decisions, and who approves investments?
• Termination: Notice periods and—crucially—the orderly handover of all access credentials and documentation.

The distinction between response time and resolution time is often overlooked. A promised response time of four hours means that someone will acknowledge the issue—not that the problem will be resolved by then. It is difficult to make a reliable commitment regarding resolution time, as it depends on the root cause. Providers who do guarantee it usually include extensive exceptions.

The final point in the contract deserves special attention. Clarify the handover process before the need arises. Switching service providers becomes difficult if access details are undocumented or if licenses are registered in the partner's name rather than your own.

Clarify data protection and data processing on behalf of a controller

Since an IT support provider may have regular access to systems, mailboxes, servers, user accounts, or backups, data protection matters should also be contractually regulated. In many cases, a data processing agreement is required in addition to the service contract.

This agreement should specify which systems the service provider is permitted to access, how access is documented, the applicable confidentiality obligations, whether sub-processors are used, and how data and access credentials are to be handed over or deleted upon contract termination.

Such clarity helps prevent future problems, particularly when switching IT service providers: the company retains ownership of its access credentials, licenses, documentation, and data.

Regulatory requirements regarding network and information security — which may apply depending on the industry and company size—are an increasingly relevant aspect. The Federal Ministry of the Interior provides an overview of network and information security.

In-house IT or external partner

The decision is rarely an "either-or" choice. For organizations with around fifty or more employees, a hybrid approach often makes sense: an in-house staff member for day-to-day user support and operational knowledge, and an external partner to handle servers, networks, and security, as well as to provide backup coverage.

For smaller businesses, the numbers usually clearly favor an external solution—not just because of the costs, but because it is unrealistic to expect a single individual to cover the full breadth of required technical expertise.

Selecting a provider: the checklist

• Is the provider locally available should an on-site visit become necessary?
• Is there a designated contact person, or does the person change with every call?
• How are backup arrangements handled?
• Are systems and access details documented, and do you receive this documentation?
• Are response times specified in writing and tiered according to urgency?
• Is system recovery regularly tested and logged?
• Do you receive regular reports on system status and work performed?
• Are licenses and contracts held in your name?
• Is the handover process defined for the end of the contract?
• Does the provider advise against a purchase if it is not necessary?

The last point is the most telling. A partner who proposes new hardware in response to every inquiry may well be pursuing interests other than your own.

Why regional proximity remains important

Many support issues can be resolved via remote maintenance. Nevertheless, local proximity remains important for IT support—for instance, in cases of network outages, hardware replacements, office relocations, firewall issues, cabling, initial system setup, or situations requiring on-site equipment inspection.

For companies in Vienna and the surrounding area, it therefore makes sense to choose a partner that works efficiently remotely but can also realistically provide on-site support when needed.

The Chamber of Commerce’s IT Security Handbook for SMEs offers practical guidance on operational security requirements.

Schedule an initial consultation with FIGULI

Conclusion on IT Support

For most SMEs, outsourcing IT support is a more cost-effective route to stable IT systems than maintaining an in-house department—primarily due to the breadth of expertise and guaranteed coverage (backup personnel).

Three factors are crucial for success: an honest initial assessment of the existing setup, rather than simply taking responsibility for unknown systems; a cost model tailored to actual needs (where requirements are unclear, an hourly support pool offers the lowest-risk entry point); and clear agreements regarding response times, documentation, and handover procedures to ensure the partnership functions smoothly even when it eventually comes to an end.

However, the ultimate litmus test is simple: ask a potential partner when a full system recovery was last tested—and ask to see the report.

FIGULI CONSULTING supports small and medium-sized enterprises in Vienna and the surrounding area as an external IT partner. Services range from user support, maintenance, monitoring, Microsoft 365 management, endpoint security, and backups to the planning of server migrations, cloud initiatives, and security measures. This transforms IT support from a mere quick fix for problems into a reliable operational model for stable IT.

Start IT support with FIGULI

FAQ on IT Support

What does IT support entail?

User support; maintenance of servers, workstations, and networks; system monitoring; security measures; data backups; and advisory support for investments and system migrations. The scope is defined by contract and ranges from simple troubleshooting to taking over full operational management.

At what company size does external support become worthwhile?

There is no minimum size. Even a business with five workstations has servers, a network, backups, and security requirements. For companies with around fifty workstations or more, a hybrid approach often makes sense: an in-house staff member for daily support, and an external partner for specialized tasks and backup coverage.

How much does IT support cost?

Three models are common: billing based on actual time spent (for low demand), a pre-purchased block of hours (for fluctuating demand), and a monthly flat fee (for ongoing support needs). The key factor is comparing the scope of services, not just the hourly rates.

What is a block of hours?

A pre-purchased quota of hours that can be drawn upon as needed, usually at a discounted rate. It allows for cost predictability without committing to a monthly flat fee. Important details to clarify include the quota's validity period and the billing increments.

What is the difference between response time and resolution time?

Response time indicates the timeframe within which someone acknowledges a reported issue. Resolution time refers to the deadline for fixing the problem — a timeframe that is difficult to guarantee reliably because it depends on the root cause. Guaranteed resolution times usually come with extensive exceptions.

What should I look out for when switching IT service providers?

Above all, ensure an orderly handover: complete documentation of all systems and access credentials, as well as licenses and contracts registered in your company's name. These points should be addressed when the contract is first signed, not just when it is terminated.

Does external support replace in-house IT staff?

For smaller businesses, the answer is generally yes, as it is difficult for a single individual to cover the necessary breadth of expertise. In larger companies, the two approaches complement each other: internal staff provide knowledge of business operations and day-to-day support, while external providers contribute specialized expertise, backup coverage, and strategic insight.

What should be included in an IT support contract?

An IT support contract should outline the scope of services, response times, availability, the cost model, responsibilities, documentation, data protection, license management, and the orderly handover of systems upon contract termination. It is particularly important to ensure that access credentials, contracts, and documentation are not held exclusively by the service provider.

Note:

This article provides general information regarding external IT support. The appropriate scope of services and cost model for a specific case depend on factors such as the system landscape, company size, availability requirements, and industry-specific regulations.