Technology AI

IT support options for small agencies

DIY, break-fix, managed service, in-house and supplier support compared for small estate and letting agencies, with decision criteria and contract checks.

Ava research teamPublished 6 min read

On this page
  1. How IT is usually handled in agencies
  2. The options compared
  3. What support has to cover
  4. Readiness for an incident falls with size
  5. Choosing the right model
  6. Questions to ask a managed service provider
  7. What the agency must always own
  8. Starters and leavers: the test of any support model
  9. Worked example: from break-fix to managed
  10. Running the relationship
  11. Frequently asked questions
  12. References

Key takeaways

  • About 90% of UK estate agencies are micro businesses with nine or fewer staff, so IT often falls to the owner or whoever is good with computers[1].
  • Small firms are least prepared for incidents: 21% of micro businesses have a formal incident response plan, against 76% of large ones[2].
  • A managed service suits most agencies with more than a handful of staff; break-fix suits very small offices with a capable internal owner.
  • Whatever you choose, the agency must keep the admin accounts, domain, password vault and system list in its own hands.

How IT is usually handled in agencies

There were 31,430 real estate agency enterprises in the UK in 2026, and 28,330 of them, about 90%, had nine or fewer employees[1]. Another 24,260 enterprises managed real estate on a fee or contract basis, including many lettings and property management firms[1]. Few of these businesses employ anyone whose job is IT. Instead, the owner, a branch manager or the newest negotiator becomes the unofficial help desk.

That works until it does not: a leaver who still has access to email, a laptop that has not updated for a year, a backup nobody has tested, or a CRM integration that breaks on a Saturday. Lack of expertise is also one of the most commonly reported barriers to AI adoption among UK businesses[3], so the same gap holds back new tools. The question is not whether to have IT support but what kind fits the agency's size and risk.

The options compared

Common IT support models for agencies and where each fits.
OptionBest forStrengthsWeaknesses
Internal championVery small offices with a capable, willing personKnows the business; fast for simple fixesSingle point of failure; security often neglected
Break-fix local IT firmOffices with few devices and simple systemsPay only when something breaksNo prevention; slow when busy; no one watching backups
Managed service providerMost agencies with several staff or branchesMonitoring, updates, security and a help deskOngoing contract; quality varies widely
In-house IT personLarger groups with many branchesDedicated, on site, knows the systems deeplyCostly for small firms; cover needed for holidays
Supplier supportCRM, phone and email platformsExpert on their own productWill not fix anything outside it

Most agencies end up with a combination: supplier support for the CRM and phone system, a managed service or break-fix firm for devices, accounts and security, and an internal champion who knows who to call. The important part is that every system has a named owner and every task has someone responsible.

What support has to cover

  • Accounts: setting up starters, removing leavers on their last day, and multi-factor authentication for every login.
  • Devices: laptops, phones and printers, kept updated, encrypted and listed.
  • Email and security: filtering, phishing protection and alerts for suspicious sign-ins.
  • Backups: separate from everyday storage, checked and test-restored regularly.
  • Phones and internet: lines, Wi-Fi, call forwarding and the plan if the connection fails.
  • Business systems: the CRM, portals, e-signing and accounting, and the connections between them.
  • Incidents: who responds, how fast, and what happens out of hours.

Write this list down and mark who covers each item today. Gaps are usually obvious within ten minutes, and they are the starting point for choosing support.

Readiness for an incident falls with size

The government's 2025/26 survey found that 25% of UK businesses had a formal incident response plan, falling to 21% of micro businesses, while 57% of medium and 76% of large businesses had one[2]. Larger firms usually have someone whose job includes planning for a bad day. Small agencies need that planning to come from somewhere, and good IT support should provide it.

Businesses with a formal incident response plan, by size, 2025/26Most estate agencies are micro businesses.
Businesses with a formal incident response plan, by size, 2025/26Column chart. Micro: 21%; All businesses: 25%; Medium: 57%; Large: 76%.0%20%40%60%80%Micro: 21%21%MicroAll businesses: 25%25%All businessesMedium: 57%57%MediumLarge: 76%76%LargeBusinesses with a formal incident response plan, by size, 2025/26Column chart. Micro: 21%; All businesses: 25%; Medium: 57%; Large: 76%.0%20%40%60%80%Micro: 21%21%MicroAll businesses: 25%25%Allbusines-sesMedium: 57%57%MediumLarge: 76%76%Large

Source: Department for Science, Innovation and Technology (GOV.UK), 2026[2]

Show the data
ItemValue
Micro21%
All businesses25%
Medium57%
Large76%

A practical test of any support arrangement is to ask: if our email were taken over at five o'clock on a Friday before a busy completion week, who would we call, and what would they do in the first hour? If nobody can answer, the arrangement is not working.

Choosing the right model

  1. One office, up to about five staff, simple systems and a capable internal owner: internal champion plus a break-fix firm, with security basics set up once by a professional.
  2. One or two offices, more staff, client money and lettings management: a managed service provider with monitoring, security and help desk.
  3. Several branches, central lettings or a property management team: managed service plus a part-time or full-time internal IT coordinator.
  4. Large groups: in-house IT, with specialist partners for security and specific systems.
  5. Whatever the size: supplier support for each platform, and a named internal owner for each system.

An in-house hire also brings employment costs beyond salary, including employer National Insurance at 15% on earnings above the secondary threshold[4]. Compare the full cost and the cover for holidays and sickness before deciding that a hire is cheaper than a contract.

Questions to ask a managed service provider

  • What exactly is included, and what is charged as extra work?
  • What are your response and fix times for urgent issues, and do they apply at weekends?
  • How do you handle multi-factor authentication, backups and updates, and how will we know they are working?
  • Do you support other estate or letting agencies, and which CRMs and phone systems do you know?
  • Who holds our admin passwords and documentation, and what happens if we leave?
  • What do you need from us, and who is our named contact?

Ask for a sample monthly report. A good provider can show patch status, backup checks, security alerts and tickets resolved in plain language that an owner can understand.

What the agency must always own

  1. Admin accounts

    At least one top-level admin account for email, cloud storage and the CRM belongs to the agency, protected by multi-factor authentication and stored in the agency's password vault.

  2. Domain and website

    The domain registration and website hosting are in the agency's name, with renewal reminders going to an agency address.

  3. System list

    A current list of every system, its supplier, its owner, its renewal date and how to get support.

  4. Documentation

    Network diagrams, device lists and configuration notes are handed over and updated by the provider as part of the contract.

  5. Exit plan

    The contract states how the provider hands everything back and how quickly, if you change supplier.

Starters and leavers: the test of any support model

Staff changes are where IT support most often fails in agencies, because negotiators move between firms and branches regularly. Whoever provides support should run the same checklist every time, and the branch manager should sign it off.

  • Starter: accounts created only for the systems the role needs, multi-factor authentication set up on day one, device issued and recorded, and the security basics explained in person.
  • Mover: access to the old branch or team removed, not just new access added.
  • Leaver: every account disabled on the last day, mailbox forwarded or shared with a manager, device returned and wiped, and shared passwords they knew changed.
  • Leaver's phone number: business numbers and portal logins moved to a colleague so client calls and leads keep arriving.

If a leaver could still log in a week later, the support arrangement needs fixing, whatever the contract says.

Worked example: from break-fix to managed

Example: a fictional three-branch agency relies on a local IT firm that it calls when something breaks. In one year it has a laptop stolen with no remote wipe, a former negotiator who could still read email for six weeks, and a backup that failed silently for two months. Each fix is quick, but nobody is preventing the next problem.

Example, continued: the owner moves to a managed service. In the first month the provider turns on multi-factor authentication for all accounts, sets up device management, replaces the old backup with a monitored one and writes a starter and leaver checklist. The internal champion, an office manager, keeps the system list and meets the provider monthly. The help desk now handles small issues the same day, and the owner stops being the person everyone calls.

Running the relationship

Book a short monthly review with your provider or champion. Look at open tickets, any security alerts, backup checks, devices due for replacement and starters or leavers coming up. Once a year, review the contract against what you actually needed. The National Cyber Security Centre's small organisations guide is a useful shared checklist for those reviews, covering backups, protecting devices and accounts, and spotting scams[5].

For the security basics every support model should deliver, see cybersecurity basics for agencies, and for planning the wider spend, what agencies pay for tech.

Frequently asked questions

Does a small estate agency need managed IT support?

Not always. A very small office with a capable internal owner can manage with break-fix support, provided security basics such as multi-factor authentication and tested backups are set up properly. Most agencies with several staff benefit from a managed service.

What should an IT support contract include?

Clear scope, response times including weekends, security and backup responsibilities, regular reporting, documentation the agency owns and an exit plan.

Can our CRM supplier be our IT support?

They will support their own product, but not your devices, email, network or other systems. You still need someone responsible for everything else.

Who should hold our admin passwords?

The agency. Providers can have their own admin access, but at least one top-level account for each key system should belong to the agency and sit in its own password vault.

References

  1. Office for National Statistics (Nomis) (2026). UK Business Counts: enterprises by industry and employment size band (SIC 68310, 68320), 2026 (opens in a new tab) ↑

  2. Department for Science, Innovation and Technology (GOV.UK) (2026). Cyber security breaches survey 2025/2026 (opens in a new tab) ↑

  3. Office for National Statistics (2026). Artificial intelligence in UK businesses: 2023 to 2026 (opens in a new tab) ↑

  4. HM Revenue & Customs (GOV.UK) (2026). Rates and thresholds for employers 2026 to 2027 (opens in a new tab) ↑

  5. National Cyber Security Centre (2026). Small organisations guide to cyber security (opens in a new tab) ↑

Book a demo

See Ava handle your calls.

Book a short demo. We’ll walk through your calls and workflow, and agree what Ava should take care of.

Book a demo