What IT outsourcing covers
- helpdesk and remote user support
- Microsoft 365, accounts and permissions administration
- server maintenance, backup, monitoring and security
- coordination of vendors, hosting, domains and websites
SysGroup / IT outsourcing
managed IT, external IT department
IT outsourcing for companies
We take responsibility for your company's day-to-day IT: users, Microsoft 365, servers, backup, monitoring, websites and security procedures.
Monitoring of agreed systemsPolish teamSubscription & clear SLADiagnosis and action plan
Who it's for
- companies of 10-150 seats without their own IT team
- companies with vendor chaos and no single point of responsibility
- organisations that want an SLA and predictable costs
The outcome
- one partner for IT
- clear ticket priorities
- less downtime and less reliance on random individuals
Illustrative scope, not a ready-made package
One office and Microsoft 365: how we define support
An example starting point is a company with 10-29 users, one office and Microsoft 365 mail. This is a scope-planning scenario, not a client case study or a promise of one price for every business.
Ongoing support
We agree which accounts, devices, network and services the helpdesk covers, who can request changes and the support hours. The system list and exclusions form part of the proposal.
Initial work
We review documentation, access ownership, backups and outstanding issues. The proposal separates the handover from the ongoing subscription and identifies how initial work and supplier costs are charged.
Handover outcome
We agree and provide a list of supported systems, responsibility boundaries, ticket channels, escalation rules and a plan for identified gaps. Technical tests and their scope are agreed before execution.
Changes outside support
Mail migration, network replacement and larger rebuilds have a separate scope, outcome and quote. Licences, equipment and third-party services are identified separately from our team's work.
For the first conversation, prepare user and location counts, the systems in use and your main issue. Do not send passwords or client data. If a paid diagnosis is needed, we agree its scope and cost before starting.
Scope and commercial model
What we agree before we price the work
We do not assume that a subscription includes every change. First we establish the responsibility boundary, the type of work and the current state of the environment.
| Model | What it is for | Boundary |
|---|---|---|
| Subscription | Recurring support, agreed systems, ticket flow, monitoring and SLA where it is in the agreement. | It covers only the agreed responsibility, hours and services. |
| Project | Diagnosis, migration, implementation or a defined change with an agreed result. | The project ends according to its agreed scope; it is not ongoing on-call cover. |
| Separate quote | Larger rebuilds, work outside the agreed pool, application code, or third-party costs. | We confirm the scope and price before starting rather than silently treating it as part of a subscription. |
What affects the price
Number and role of systems, business criticality, support availability, documentation quality, backup state and the scope of project work.
What the first handover should leave behind
A responsibility map, ticket route, priorities, available documentation and a plan for the next agreed actions.
How we start
First we establish the current state and the required diagnostic scope. For ongoing subscription support, we then agree responsibility, SLA, ticket flow and a plan for taking over access, documentation and monitoring.