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 2Find 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.
Start here
Urgent help
Ongoing support
Projects
Small IT problems grow when nobody owns them. A network support 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. We agree those terms with you before anything is signed.
A network support contract is a monthly written agreement that puts the upkeep of a company's servers, network and users in the hands of one technical team, with the scope and response tiers spelled out. It suits companies that never know who to call when something breaks, lost their IT person, or run updates and backups only when someone remembers. Under a PikoSystem contract, the covered assets are listed, response and resolution targets for each priority level are set in the SLA, security updates are installed in an agreed window, logs, disk space and RAID health are checked, and backup jobs are verified with periodic test restores. Most requests are handled remotely, and on-site visits follow the terms in the agreement. You receive network documentation, a monthly report on work done, and a request procedure for your staff.
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. Response and resolution targets for each tier are set 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.
The contract should separate response time from resolution time. Response means work has started and resolution means the service is back, so a contract that only commits to response says nothing about how long an outage lasts. Exclusions need to be explicit too: hardware parts, license purchases and problems with software supported by its own vendor.
Ownership of access is often overlooked. 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. A network with switches, firewalls and servers from several brands and generations needs more documentation and upkeep than a uniform one. Systems past vendor support, such as Windows Server 2012 or old routers with no firmware updates, add risk and handling time.
The number and distance of branches, after-hours coverage and your own documentation requirements also count. 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.
Ask who exactly will work on your systems and who covers when that person is unavailable. Ask to see a sample monthly report and network documentation from another client, with confidential details removed, to judge 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 is written. Overdue work such as missing updates or incomplete backups comes to light at this stage too.
Expect the issue list to get longer 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, and in periodic review meetings we go through the report and adjust the scope together.
It depends on the number of servers and users, the response tiers, coverage hours and how many on-site visits you need. That is why we do not publish a fixed price. 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 level, and coverage hours. It also defines 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, not a sales rep.