Agreed scope
We list the assets covered (servers, switches, firewall, users) and write down where our responsibility ends. Anything outside that list is agreed separately.
Start here
Free Audits 5Urgent help
Emergency 4Ongoing support
Managed IT 5Projects
Servers & Hosting 6 Network & Virtualization 9 DevOps 5 Security & Recovery 5 Hardware & Licensing 2 IoT & smart automation 3Find out where your servers, security, backups and performance stand, at no cost.
Server down, network out, site hacked or data lost? Call us now.
Monthly network and server support with response times written into the contract.
Setup, configuration, management and migration of Linux and Windows servers, panels and mail.
Network design and cabling, MikroTik, VoIP, branch links, virtualization and private cloud.
Networking & communications
Virtualization & cloud
Containers, Kubernetes, automated delivery, infrastructure as code and observability.
Server hardening, firewalls, backup and DR, ransomware recovery and incident forensics.
Advice, supply and installation of servers and network gear, plus genuine enterprise licenses.
Connected homes, workplaces and devices, from scenario design to control and monitoring.
Start here
Urgent help
Ongoing support
Projects
Without a network support contract, small IT problems tend to grow because nobody owns them. The contract puts that ownership in writing: which systems we look after, how quickly we respond at each priority level and when an engineer comes on site, all agreed with you before anything is signed.
A network support contract is a monthly written agreement that hands the upkeep of a company's servers, network and users to one technical team, with the scope and response tiers spelled out. It fits a company where nobody knows who to call during an outage, the IT person left without documenting anything, or updates and backups depend on someone remembering. Under a PikoSystem contract the covered assets are listed first, and the SLA sets response and resolution targets for each priority level. Routine work covers security updates in an agreed window, checks on logs, disk space and RAID health, and backup jobs verified with periodic test restores. Most of it happens remotely, and on-site visits follow the terms of the agreement. Your staff get a request procedure, and you get network documentation and a monthly report on the work done.
We list the assets covered (servers, switches, firewall, users) and write down where our responsibility ends. Anything outside that list is agreed separately.
Requests are ranked by business impact, for example full outage, partial disruption and routine request, and each tier has its own response and resolution targets in the contract.
Security updates in an agreed maintenance window, review of system logs and Windows Event Viewer, and checks on disk space and RAID health.
We check backup job results and run periodic test restores on a sample, so you know the files can actually come back.
Most requests are handled remotely over a secured connection. The number of on-site visits, or the conditions for one, are written into the agreement.
A summary of tickets, completed work, notable alerts and recommended actions for the month ahead.
Response time and resolution time should be separate lines in the contract. Response means someone has started work; resolution means the service is back. If only response is promised, nothing in the contract limits how long an outage can last. Exclusions need to be explicit too: hardware parts, license purchases and problems with software that its own vendor supports.
Ownership of access is the clause people most often skip. Every password, admin account and document belongs to you and must be handed over in full when the relationship ends. Also check the termination notice period, terms for adding users or a new branch, confidentiality, and who pays travel costs for on-site visits.
Equipment variety changes the workload. Switches, firewalls and servers from several brands and generations need more documentation and upkeep than a uniform network. Systems the vendor no longer supports, such as Windows Server 2012 or old routers that get no firmware updates, carry more risk and take longer to handle.
The number of branches and the distance between them, after-hours coverage and your own documentation requirements count as well. If the infrastructure needs a cleanup at the start, that is usually scoped as a separate initial project, so the monthly fee reflects a stable environment.
Find out who exactly will work on your systems and who covers when that person is away. A sample monthly report and network documentation from another client, with confidential details removed, will show how deep the work goes.
Ask how credentials are stored. Passwords passed around in Excel files or chat apps are a risk in themselves, and a password manager with logged access is safer. The remote access tool, how it is controlled and where changes to your systems are recorded all show how disciplined the provider is.
The first month usually goes into taking over the environment. Credentials are gathered and shared passwords changed, devices that were on no list turn up, and the first version of the network documentation gets written. Overdue work such as missing updates or incomplete backups also comes to light here.
Expect the issue list to grow in the first month, because things nobody looked at before are now visible. We prioritize that list with you and track progress in the monthly review.
We review your network, servers and current way of working, on site or remotely, and note the high-risk areas.
Scope, response tiers, coverage hours and on-site visits go into a draft contract for you to review.
We take over credentials, build the first set of documentation and switch on basic monitoring.
Monthly work runs as agreed. In periodic review meetings we go through the report with you and adjust the scope where needed.
The figure comes from the number of servers and users, the response tiers, coverage hours and how many on-site visits you need, so there is no fixed price on the site. After an initial review we send you a written proposal with a clear figure.
The SLA is the part of the contract that sets priority levels, response and resolution targets for each one, and coverage hours. It also says how requests are logged and who on your side approves work.
Yes, when the contract includes it. Some companies want a fixed weekly or monthly visit, others call us in only when needed. Anything that can be done remotely is done remotely, because it saves time.
In that case we usually act as second-line support. Servers, firewall, backups and harder problems come to us, while day-to-day user issues stay with your team. The split is written into the contract so nothing falls between the two.
Related searches
Quote
A few lines on where things stand and what you want is enough. An engineer calls you back directly; requests don't go through sales.