Skip to main content
GullySystem
Managed IT Support

Helpdesk, patching, Microsoft 365 and Google Workspace administration, tested backups and leaver checklists for offices without an IT team

Managed IT support is routine care for offices without an IT team. A helpdesk takes faults from staff, laptops are patched and encrypted, Microsoft 365 and Google Workspace tenants are administered, and backups are proved by restore tests. Account changes follow a checklist.

  • Accounts and licences are in the client’s name.
  • Every request becomes an owned ticket.
  • A backup counts only once restored.

The work is mailboxes, laptops, shared drives, Wi-Fi, backups and user accounts for small and medium businesses, with remote cover as the default and on-site visits agreed per client. None of it is glamorous. It keeps an ordinary day uninterrupted.

The problem

Where Support Gaps Build Up in Small Offices

Informal IT Support

Informal support breaks at month end. A relative or a technical colleague fixes faults beside their own job, and when the accounts machine fails that person may be in a meeting or on leave.

Shared Administrator Passwords

One password opens everything. It lives on paper, in a chat group and in the memory of former staff, and nobody dares change it without a list of what it opens.

Backups Without Restore Tests

Backup jobs report success. Whether a file can actually be recovered stays unknown until the day someone needs it, and sometimes a disk swap broke the job months earlier without any message.

Accounts That Outlive Employment

Access lingers after exit. The mailbox stays live, the laptop goes home with the employee, and customer files sit in a personal drive, because handover covered the client list and little else.

Duplicate Licences

Nobody sees the duplicates. Departments buy their own subscriptions, some for people who left long ago, and renewals land on personal cards with no single list to check them against.

Slow Laptops Left as They Are

Small drag adds up. Updates are deferred, the disk fills, and the user restarts the machine twice every morning, yet nobody raises a ticket because the laptop still works.

Phishing Reaching the Accounts Desk

The only control is caution. A message styled as an instruction from the owner asks for a payment to a new account, and without two-step login or mail filtering the clerk decides alone.

None of this needs a full-time IT department. It needs a support contact, a record of what the business owns, routine tasks on a schedule, and access that follows a process instead of a favour.

What we build

Routine IT Work on a Schedule With a Support Contact

The work starts with a count. An inventory lists devices, accounts, licences, mailboxes and connections, and who has access to each one, from the file server to the accounts clerk’s phone. Routine tasks then run on a schedule: patching, backups with tested restores, security baselines, joiner and leaver handling and a helpdesk that staff reach by email, phone or WhatsApp. Staff describe a fault once, and the ticket carries the rest.

Illustration with sample figures. Your screens are built around your own records.

Tickets for Every Request

Nothing gets fixed twice from scratch. Each request is logged, given an owner and kept for later lookup, so a fault that keeps returning shows up in the ticket history, not in one engineer’s memory.

Restore Testing

An untested backup is a guess. Recovery is tried on a schedule with real files from the file server and mailboxes, and the result goes into a log the client can read at any time.

Access Tied to Roles

Roles decide the login. Accounts are created by role when someone joins and closed on the last working day, with the mailbox forwarded or held and the files moved to the manager.

What changes

What Changes With Managed Support in Place

What the business gets, before any talk of technology.

Requests

A Route for Raising Faults

Small faults stop being worked around. Staff report a slow laptop or a jammed printer through the helpdesk, and the ticket is assigned, followed up and closed with a note of the cause.

Inventory

A Record of What the Business Owns

Expiries become visible early. Devices, licences, mailboxes, domains and hosting are listed with an owner and a renewal date, so a duplicate purchase or a lapsing SSL certificate appears on the register first.

Restores

Backups Checked by Recovery

A restore path exists. Recovery is tested on a schedule and recorded in a restore log, so when a disk dies or a folder is deleted the engineer follows written steps.

Access

Joiners Set Up and Leavers Closed Out

Nothing is left open. A joiner gets a mailbox, a login and role-based permissions before day one, and a leaver’s access is closed on the last day with files moved to the manager.

Sign-In

Basic Attack Routes Closed

Known weaknesses get closed. Two-step login covers mail and administrator accounts, mail passes through a filter, and devices are patched and encrypted, because most incidents at this size come from ordinary, known weaknesses.

Renewals

A Planned View of IT Spend

IT spend gets a calendar. A monthly arrangement, a renewal calendar and a replacement plan for ageing machines mean that a failed laptop or a lapsed domain is planned for, not a surprise invoice.

Scope of service

What Managed IT Support Includes

Everything from the first discovery session to production and long-term upkeep.

Helpdesk and Ticketing

One place for every fault. Staff report problems by email, phone or WhatsApp, and each request is logged, assigned, prioritised and closed with a note of what was actually done.

Remote and On-Site Support

Most faults never need a visit. A remote session fixes them during working hours, and where hands are needed an engineer visits nearby offices; elsewhere a client-appointed local vendor does that work.

Laptop and Desktop Management

Every machine has a record. Setup, operating system and software updates, disk encryption, antivirus and performance checks are done, and a register shows which laptop is with whom and how old it is.

Microsoft 365 and Google Workspace Administration

Admin consoles get real attention. Mailboxes, shared drives, groups, aliases, licence assignment, sharing rules and mail routing are managed, and spam and phishing filtering and two-step login apply across the whole tenant.

Joiner, Mover and Leaver Process

Each event has a checklist. Accounts are created by role on the first day, changed on a transfer and closed on the last day, with the mailbox and files handled as written steps.

Backup and Tested Recovery

A restore is the proof. Servers, shared drives, mailboxes and business applications are backed up, and restores are tested on a schedule, with the result recorded instead of inferred from a success message.

Security Baseline and Monitoring

Alerts catch the odd sign-in. Two-step login, password practice, reviewed administrator rights, device encryption and endpoint protection form the baseline, and monitoring fires on impossible sign-ins and mass downloads.

Network, Wi-Fi and Firewall Basics

Guests stay off the office network. Router and firewall configuration, a separate guest Wi-Fi and a VPN for remote access are set up, and faults on the internet line are chased with the provider.

Server and Business Application Support

Nothing hides in the corner. The machine running the accounting software, the shared file server and any local application are patched, monitored, backed up and documented, so a disk failure becomes a planned recovery.

Asset, Licence and Renewal Register

Renewals stop lapsing quietly. Devices, subscriptions, domains, SSL certificates and hosting accounts are listed with owner, cost and renewal date, and each review catches duplicates, orphaned seats and dates about to pass.

Vendor Coordination

Office staff stop waiting on hold. GullySystem deals with the internet provider, the printer company, the accounting software support desk and the hosting vendor on the client’s behalf, and reports back with a ticket note.

Reporting and Technology Review

The review is a conversation. It covers tickets raised, recurring faults, machines due for replacement, licence spend and risks worth acting on, and it is discussed in a meeting, not mailed as a file.

Where it is used

Where Managed IT Support Is Used

The processes this service is most often asked to set up and automate.

Trading Firm With One Accounts Machine

Backups go to a USB drive. One desktop runs the accounting software for the whole business, and the work adds a scheduled backup with tested restores, a second machine able to take over and written licence steps.

Design Studio With Twelve Mailboxes

A studio on Google Workspace receives a phishing mail asking for a payment to a changed account, because nobody ever switched on two-step login. Support adds two-step login across the tenant, tightens mail filtering, sets alerts on suspicious sign-ins, and runs a short briefing so staff know what a changed-account request looks like.

Clinic Group With a Shared Login

Everyone is the same user. Reception staff at three branches share one login on every machine, and the fix is individual accounts, roles on the shared drive and no local administrator rights.

Manufacturer With Manual Leaver Handling

Leavers still have keys. Former employees hold live mailboxes and one keeps a VPN login, so a joiner and leaver checklist is agreed with HR and a review lists who holds access.

Professional Firm With Scattered Subscriptions

Seats outlive their owners. Three departments buy subscriptions on personal cards, seats for leavers included, and a register moves renewals to a company account with the domain and hosting in the firm’s name.

Small Team That Needs Setup Only

A monthly fee adds little here. A six-person team works on laptops in Google Workspace with no servers and no office network, so a one-off setup covers two-step login, sharing rules, a backup and notes.

Audience fit

Is this the right service for you?

It suits businesses that have outgrown manual processes and want a system they can rely on.

Businesses With No Full-Time IT Person

Support is whoever answers. It currently comes from the owner’s relative, the most technical member of staff, or whoever installed something once and still picks up the phone. That arrangement has a limit.

Offices of About Ten to Two Hundred People

Hours lost add up. Offices of this size lose real working hours to broken technology, yet a full-time IT team and an internal service desk are hard to justify.

Companies Running Accounting Software on a Local Server

The corner machine is the risk. One machine carries the accounts or the shared files, and nobody can say what happens to the invoices, the payroll sheet or the customer folders after a disk failure.

Businesses With Branches or Remote Staff

Remote staff need remote admin. Laptops rarely come to the office and mailboxes are opened from home, so access has to be granted and removed without anyone sitting at the machine.

Firms Answering Client Security Questions

Questionnaires arrive from buyers. Larger customers send forms on two-step login, backups, device controls and access reviews, and honest answers depend on the work having been done before the form arrives.

Cases Where a Monthly Fee Is Not Needed

A one-off setup may be enough. A small team on laptops and Google Workspace, with no server, office network or shared line-of-business software, may need only two-step login, sharing rules, device basics and a backup. A business that already has a capable IT person may need help with one specific project rather than a support contract, and GullySystem says so at the assessment stage.

What it does

What it can do, in plain terms.

Single Point of Contact

One place to report anything. Every report becomes a ticket, so the request is still on record, with its owner and its outcome, long after the day it was made.

Agreed Response Targets

Urgency is agreed in advance. A dead billing counter outranks a slow printer, and each priority category has a stated response target, so nobody argues about urgency during an outage.

Remote Support Sessions

Remote sessions skip the travel. Most faults are handled in a remote session during working hours, so a user with a frozen Outlook or a stuck print queue is back at work.

Patch and Update Management

Users stop deferring updates. Operating system and application updates are applied on a schedule and reported, so a pending Windows update is a line on a report, not a prompt each user postpones.

Endpoint Protection and Encryption

A stale laptop cannot hide. Antivirus and disk encryption run on each machine through BitLocker or FileVault, and a report shows which devices are behind and why.

Identity and Access Management

Admin rights are a short list. Accounts are created by role and two-step login is enforced, while administrator rights are limited to a few named people and reviewed so old privileges do not pile up.

Mail Security and Filtering

Lookalike invoices meet a filter. Spam and phishing filtering, correct SPF, DKIM and DMARC records on the domain, and alerts on sign-ins from unexpected places protect each mailbox from spoofing and takeover.

Backup With Verified Restores

Backups include the awkward parts. Servers, drives, mailboxes and application data are backed up on a schedule, restore tests are run against real files, and each result is written down for the client.

Asset and Licence Register

Nothing lapses without warning. Devices, subscriptions, domains, certificates and hosting are listed with owner, cost and renewal date, so an expiring domain or certificate is flagged before the website or mail stops working.

Joiner and Leaver Checklists

Nobody improvises an exit. A repeatable process covers access on day one and removal on the last day, including files, mailboxes and any shared passwords the person knew, each step ticked off.

Monitoring and Alerts

Alerts reach a person. Servers, disk space, backup jobs, internet links and critical applications are watched, and alerts go to a named engineer, not to a shared mailbox that nobody opens.

Documented Environment

Documentation is not a secret. A written record shows what runs where, how it is configured and how to recover it, and the client keeps a copy in its own storage, not only GullySystem.

How the work runs

How the work runs, step by step.

From the first conversation to a release your team uses every day. Each step says what you provide and what you get back.

  1. 01

    Inventory and Assessment

    Start by counting everything. Every device, account, licence, server and connection is listed, along with who has access to what, and the client gives administrator access to the mail tenant and network. The client also lists recurring faults.

  2. 02

    Risk Report and Priorities

    The report sets the order. It covers what is exposed, unsupported or failing quietly and what to fix first, and where a fix needs hardware or a licence, the client decides on the spend.

  3. 03

    Stabilise the Basics

    Basics come before anything clever. Two-step login, working backups, patching, endpoint protection and removal of shared administrator accounts are done in a short window the client allows, with staff warned before logins change.

  4. 04

    Helpdesk Onboarding

    The helpdesk opens its doors. The channel opens, priorities are agreed, staff learn how to reach it, and the client names one internal contact who approves access requests and decides what is urgent.

  5. 05

    Routine Operations

    The routine takes over. Patching, monitoring, backup checks, restore tests, access reviews and the joiner and leaver process run on a schedule, and HR tells support about joiners and leavers before the date.

  6. 06

    Periodic Review

    Reviews need a decision-maker. It covers tickets, recurring faults, ageing machines, licence spend and open risks, and the client sends an owner who can attend and take decisions on the spot.

Asset handover

What you receive when the work is done.

Everything needed to run, maintain and extend the software without depending on us.

Full inventory of devices, accounts, licences, domains and hosting
Written risk report with priorities and costs
Helpdesk channel with agreed priorities and response targets
Patching and endpoint protection in place across machines
Backup configuration with a schedule of tested restores
Two-step login and access baseline across mail and administrator accounts
Joiner, mover and leaver checklists agreed with HR
Monitoring and alerting on servers, backups and critical applications
Environment documentation covering what runs where and how to recover it
Periodic review report on tickets, risks, renewals and machines due for replacement
Connected ecosystem

It connects to the systems you already use.

Tools that work stay. The new system is joined to them rather than replacing them.

Productivity Platforms

  • Microsoft 365
  • Google Workspace
  • Microsoft Entra ID
  • SharePoint and OneDrive
  • Google Shared Drives

Endpoints and Devices

  • Windows laptops and desktops
  • macOS
  • Android and iOS handsets
  • Printers and scanners
  • Mobile device management

Servers and Hosting

  • On-premises Windows and Linux servers
  • AWS
  • Azure
  • Shared and VPS hosting
  • Accounting software on a local server

Security and Backup

  • Endpoint protection
  • Disk encryption
  • Password managers
  • Cloud backup services
  • Firewalls and VPN

Business Applications

  • Desktop accounting software
  • Zoho One
  • Custom ERP and portals
  • Accounting and payroll software
  • Internet and telecom providers
Technology

Chosen for reliability and a long life.

Picked to match your scale and to stay maintainable for years.

Identity and Access

Microsoft Entra IDGoogle AdminTwo-factor authenticationPassword managers

Device Management

Microsoft IntuneGoogle endpoint managementRemote support toolsPatch management

Security

Endpoint protection suitesBitLocker and FileVaultMail filteringFirewall and VPN appliances

Backup and Recovery

Cloud backup servicesMailbox backupServer imagingScheduled restore testing

Monitoring and Service Desk

Uptime monitoringAlerting to on-callTicketing systemsAsset registers
Why GullySystem

Why owners choose GullySystem.

Everything Stays in the Client’s Name

The client holds the keys. Domains, tenants, hosting and licences are registered to the client’s business with its own billing, and GullySystem is added as an administrator who can be removed at any time.

Restores Tested, Not Backup Reports

Success messages prove nothing. Recovery is performed on a schedule from real data and the result is recorded, because backup software can report a finished job while the restore itself fails.

Engineers Who Also Build Software

Code is not a closed door. If the fault is in an application, not a laptop, the team can read the database, the server and the code instead of sending the client to the vendor.

Stated Limits on On-Site Cover

Our reach has a stated limit. GullySystem works from a single office, so visits work nearby and support for farther sites is remote, with on-site tasks going to a vendor the client picks. This is agreed before signing.

Documentation Kept by the Client

Handover needs no archaeology. What runs where, how it is configured and how to recover it is written down and handed over, so a new provider can pick it up without reverse engineering.

Advice on When Not to Pay Monthly

Sometimes the answer is no retainer. Some businesses need a setup and a support contact, not a monthly fee, and a small team on laptops and Workspace with no server often falls in that group.

Ways of working

How the engagement can be shaped.

Each model says what it suits and how the work is scoped. Pick the one that fits, or ask which one we would suggest.

IT Assessment

A review before committing

For a business that does not know what it owns or where it is exposed, the assessment of devices, accounts and backups is a defined piece. A support engineer and a security reviewer compile the inventory, with the owner or office manager as your contact. A further location is priced through a note. The report stands alone.

Setup and Hand Over

One-time, no retainer

Suited to a team that needs a sound setup once and no continuing cover: logins, mail, drives, device baseline, backups and documentation, itemised. A support engineer does the configuration, and your office contact confirms users and devices. An extra device group or service is costed before it is touched. Admin credentials are handed over, and nothing renews.

Managed Support

Monthly, per user or per device

This suits a business wanting day-to-day cover under agreed priorities, priced per user or per device each month so cost follows headcount. A helpdesk engineer, a systems engineer and a named account owner provide the service, and one person on your side raises and approves requests. Adding users is routine, while a new site or service waits for a written note. Notice ends it.

Co-Managed With Your IT Person

Alongside your own staff

Meant for a company with an internal IT person who needs specialist backup, on a monthly amount for areas such as the mail tenant, servers and leave cover. The engineers work through your person, who stays the contact and decides what reaches them. An area added to the arrangement is described and priced beforehand. Records go to your staff on exit.

Common questions

Questions owners ask first.

Plain answers to the questions asked before work starts.

Do you come to our office, or is support remote?

Both. Most faults are fixed in a remote session. On-site visits work near our office, and their frequency is agreed as part of the arrangement. For offices farther away support is remote, and where hands are needed a local vendor appointed by the client does the on-site work. GullySystem runs no national field-service network.

How do your staff reach you when something breaks?

By email, phone or WhatsApp. Each request becomes a ticket with an owner and a priority, so it is not lost in a chat and repeat faults show up as a pattern. Priorities are set with the business in the first workshop, and a dead billing counter is treated differently from a printer with faint prints.

What is actually covered in a monthly arrangement?

The usual scope is the helpdesk, patching, endpoint protection, monitoring, backup checks with tested restores, account and access management, vendor coordination and a periodic review. Hardware purchase, third-party licence fees, cabling and civil work, projects such as an office move or server migration, and software development usually sit outside it. The agreement states the boundary.

Can you look after our Microsoft 365 or Google Workspace?

Yes. Mailboxes, groups, aliases, shared drives and licence assignment are tidied, two-step login is enforced across the tenant, and mail filtering and domain records are set. Sharing rules are reviewed so files are not open to anyone holding a link, and alerts are added for suspicious sign-ins and mass downloads. Billing stays with the client.

Who owns our domain, licences and accounts?

The client does. Domains, tenants, hosting and subscriptions are registered in the business name with its own billing details, and GullySystem is added as an administrator. If the client leaves, our access ends.

How do you handle backups, and how do we know they work?

Every backup is tested by restoring from it. Backup software can report success while recovery fails, often because something changed after setup, which is why a sample is recovered periodically and opened to confirm it is readable. Servers, shared drives, mailboxes and business application data are all covered, and the restore log, with the date and the file tested, joins every periodic review.

What happens when an employee joins or leaves?

A checklist agreed with HR runs each event. On joining, accounts are created by role, groups and drive permissions are set, and a prepared device is handed over with a record. On leaving, access is removed on the last working day, the mailbox is held or forwarded as the client decides, and files go to the manager. The laptop is collected and wiped. Any shared password the person knew is changed. HR informs the support team before the date.

Do you support our accounting software?

Yes, for the environment it runs on. That covers the machine or server, the licence, the network path staff connect over, the data folder and its backup, and the restore when something fails. Questions on recording a transaction go to the accountant or the software’s own support, while connecting it to other software is integration work and is quoted separately.

What does managed IT support cost?

It is usually priced per user or per device each month, and the price follows headcount, machines, servers, sites, cover hours and expected on-site attendance. Third-party costs such as licences, backup storage and hardware belong to the client and appear as separate lines on the quote, so the monthly fee never hides them. A quote follows the inventory.

Our systems are a mess. Is that a problem for starting?

No. A mess is no reason to wait, since shared administrator passwords, unpatched machines, untested backups, live accounts for people who left and duplicate licences are where we usually begin. First comes an inventory, then a stabilising pass. Some fixes need a licence or a replacement machine, and the risk report lists each one in priority order with an estimate of the cost.

Can you work with our existing IT person?

Yes. Your person keeps the daily work. GullySystem takes areas such as security baselines, backups and restore testing, the mail tenant, servers, out-of-hours escalation and leave cover, each area named in a written ownership list. Co-managed work needs this clarity. Otherwise each side assumes the other is watching.

What security do you put in place?

Ordinary controls aimed at ordinary attacks. They are two-step login on mail and administrator accounts, individual logins instead of shared ones, limited administrator rights, and patched, encrypted devices with endpoint protection. Mail filtering and correct domain records come next. Then come alerts on impossible sign-ins and bulk downloads, and periodic access reviews that list who holds which right in each system. Penetration testing is separate. So is work on sensitive personal data.

How quickly do you respond?

Response depends on the agreed priority. A dead billing counter, an unreachable mail server or a suspected breach sit in the top category, while one user unable to print does not. The agreement states which category covers which fault, the hours the response targets apply, and how out-of-hours escalation works, so nobody guesses during an outage.

Guides

Read before you decide.

Practical notes on the questions this service raises, not product marketing.

Let’s Connect

Let’s Build the Right Software for Your Business

Tell us about your current operational challenge, spreadsheet bottleneck, or software requirement. An experienced engineer will review your workflow and reply within one business day.

  • No obligation consultation
  • Senior engineer reviews your brief
  • Your operational details stay 100% confidential

Start with your requirements

Seven short steps that tell us what you need. A senior engineer reads them before anyone gets in touch.

Share your requirements