Northstar IT & Cyber Advisory
  • About
  • Services
    • Fractional IT & Cyber Director
    • Board-Level IT & Cyber Risk Review
    • AI Readiness & Advisory
    • Service Pages
    • Cyber Insurance Readiness
    • Fractional vs Full-Time IT Director
  • How We Help
    • Cyber Incident Response
    • M&A IT Due Diligence
    • Cyber Essentials
    • IT Spend Review
    • Fast Growth IT
    • Compliance Advisory
    • IT Supplier Failure
    • AI Strategy & Readiness
    • AI Governance & Policy
    • See all nine situations →
    • ⭐ Free Guide: Ten Questions
    • ⭐ Free Checklist: SME Cyber Risk
    • ⭐ Free Guide: AI Risk
  • Industries
    • Professional Services
    • Financial Services
    • Legal
    • Property
    • Distribution
    • Manufacturing
    • Locations
    • London
    • Kent
    • Essex
    • Sussex
    • Surrey
    • South East
    • Don’t see your sector? Get in touch →
  • Insights
  • FAQs
  • Get in Touch
Northstar IT & Cyber Advisory
  • About
  • Services
  • Fractional IT & Cyber Director
  • Board-Level IT & Cyber Risk Review
  • AI Readiness & Advisory
  • Cyber Insurance Readiness
  • Fractional vs Full-Time IT Director
  • How We Help
  • Cyber Incident Response
  • M&A IT Due Diligence
  • Cyber Essentials
  • IT Spend Review
  • Fast Growth IT
  • Compliance Advisory
  • IT Supplier Failure
  • AI Strategy & Readiness
  • AI Governance & Policy
  • See all nine situations →
  • Free Guide: Ten Questions
  • Free Checklist: SME Cyber Risk
  • Free Guide: AI Risk
  • Industries
  • Professional Services
  • Financial Services
  • Legal
  • Property
  • Distribution
  • Manufacturing
  • Locations
  • London
  • Kent
  • Essex
  • Sussex
  • Surrey
  • South East
  • Don’t see your sector? Get in touch →
  • Insights
  • FAQs
Get in Touch
cs@northstaritadvisory.com 0333 577 1714

Month one with a new client usually starts the same way: nobody can tell me what they are actually paying for IT.

The idea of a fractional IT director is easy enough to grasp in principle: board level oversight without the cost of a full time hire. What is harder for most SME leaders to picture is what the engagement actually involves once it starts, week to week and month to month.

That gap matters. If you cannot picture what you would be paying for, it is hard to judge whether it is worth it. So here is a plain description of how the work runs, from the first week through to the ongoing rhythm.

Why the role exists

Most SMEs reach a point where IT is too important to leave to chance, but not big enough to justify a full time IT director.

The cost of a permanent hire is significant. Robert Walters puts IT director salaries in the South of England at between £80,000 and £150,000, and in London at £110,000 to £170,000. Add employer’s National Insurance, which for 2026 to 2027 is 15% on earnings above £5,000 a year, plus pension, benefits and recruitment fees, and the true cost of the seat is considerably higher.

For a business of 30, 50 or even 100 people, that is often hard to justify, particularly when much of the day to day work is already handled by an MSP. The result is a gap. Technology decisions get made by whoever is nearest, usually the MD or FD, on top of everything else they are doing. Nobody owns the bigger picture.

That gap shows up in the national data. According to the government’s latest Cyber Security Breaches Survey, only 31% of UK businesses have someone at board or senior management level with explicit responsibility for cyber security. A fractional IT director fills that seat for a fraction of the cost, for as many days a month as the business genuinely needs.

Month one: discovery

Month one is discovery. The aim is to build an honest, independent picture of where the business actually stands, usually for the first time anyone has done it.

In practice, that means:

Mapping the supplier landscape. Every IT supplier, from the MSP to the phone system provider to the dozens of software subscriptions. Who they are, what they provide, who in the business manages the relationship, and when each contract renews.

Pulling together the spend. Invoices, card payments, direct debits and expense claims, brought together in one place. This is often the most revealing exercise of the whole engagement.

Reviewing contracts. Notice periods, auto renewal clauses, service levels, exit terms and who actually owns the data.

Assessing risk exposure. The basics of cyber security, backup and recovery, access control, supplier dependency, insurance requirements and any compliance obligations.

Talking to people. The leadership team, the people who use the systems every day, and the MSP. The best insights usually come from asking the people closest to the work what frustrates them.

It is common at this stage to find licences being paid for twice, contracts nobody remembers signing, and a genuine surprise at what the total IT spend actually is once it is all in one place. Licence waste in particular is widespread: Zylo’s research found that 53% of software licences go unused within 30 days.

Discovery usually ends with a short report for the board: what we found, what it costs, where the risks are, and what we recommend doing first.

Months two and three: priorities and quick wins

Once the picture is clear, the next step is agreeing priorities with the leadership team. Not everything needs fixing at once, and not everything needs fixing at all.

Typically this produces two things. The first is a set of quick wins: cancelling duplicate or unused licences, closing obvious security gaps such as missing multi factor authentication, testing that backups actually restore, and putting renewal dates in a calendar so nothing auto renews by surprise. Quick wins often go a long way towards covering the cost of the engagement in the first few months.

The second is a short roadmap for the year ahead, covering the bigger pieces of work: renegotiating a key contract, preparing for Cyber Essentials, replacing an ageing system, or resetting the MSP relationship around clear outcomes. The roadmap is written in business terms, with costs, benefits and risks, so the board can make informed decisions rather than approving technical projects on trust.

The ongoing rhythm

From there, the work settles into a regular rhythm. The exact pattern depends on the business, but it usually looks like this.

Every month

Supplier review meetings. The MSP and other key vendors are held to account against agreed service levels rather than simply trusted to be doing a good job. That means looking at ticket volumes and response times, but more importantly asking the harder questions. Are recurring problems being fixed or just patched over? Is the MSP bringing ideas, or waiting to be asked? Are security updates being applied on time?

A check on the risk register. A short, living list of the main IT and cyber risks, who owns each one and what is being done about it.

Availability for decisions. When a question comes up, whether it is a new software purchase, a supplier proposal or a security concern, there is someone independent to ask.

Every month or quarter

A board report. This frames IT and cyber risk in commercial terms the leadership team can actually act on, rather than a technical status update nobody outside IT can interpret. A good board report answers a handful of simple questions. What are we spending, and is it good value? What are our biggest risks, and are they going up or down? What decisions do we need to make? What is coming up in the next quarter?

Every quarter

Renewals and contracts. A look at what is coming up for renewal in the next six months, so there is time to review, benchmark and negotiate rather than accepting whatever lands.

Security and resilience checks. Reviewing access, checking backup tests, and from time to time running a short incident response exercise with the leadership team.

Every year

Strategy and budget. An updated roadmap and IT budget aligned with the business plan.

Insurance and compliance. Preparing for the cyber insurance renewal questionnaire, Cyber Essentials recertification and any customer or regulatory requirements, with evidence gathered in advance rather than under a deadline.

Whenever it matters

The independent voice in significant decisions. Supplier negotiations, contract renewals, system selections, office moves, acquisitions and anything else where technology is a material factor. The point is that the business is never relying solely on the judgement of the people selling it something.

What it is not

It helps to be clear about what a fractional IT director does not do.

It is not a helpdesk. Password resets and broken laptops stay with the MSP or internal support team. The fractional IT director makes sure that support is good, rather than providing it.

It is not a replacement for the MSP. A good MSP remains essential. The role is to oversee and get the best from that relationship, not compete with it.

It is not a reseller. An independent fractional IT director should not be earning commission on the products or services they recommend. If they are, their advice is not independent.

It is not a one off consultant. It is not someone who visits once, writes a report and leaves. It is a standing function that builds knowledge of the business over time, which is what makes the advice better each month.

Who it suits

Fractional IT direction tends to work best for businesses that:

  • Have grown past 25 or 30 people and now depend heavily on technology
  • Rely on an MSP but have nobody independently overseeing it
  • Have a founder, MD or FD still making most IT decisions
  • Face growing pressure from customers, insurers or investors about cyber security
  • Are planning a significant change, such as a new system, an office move, rapid growth or preparing for sale

A standing function, not a one off

The simplest way to describe the role is this. It is a standing, independent function that sits above the day to day IT support relationship and makes sure someone is asking the harder questions on an ongoing basis.

Most businesses do not need that every day. But they do need it every month.

If you are not sure what your business spends on IT in total, or who is holding your suppliers to account, it is worth a conversation.

Most businesses have not yet decided whether their staff should be using AI tools with company data. The problem is that their staff have already decided for them.

ChatGPT, Copilot, Gemini and a growing list of similar tools have become a routine part of how people get work done. Drafting emails, summarising documents, preparing for client meetings, writing proposals, analysing data. The tools are fast, capable and, from the user’s perspective, entirely unremarkable. They are just another way of getting something done.

What most users do not consider, and what most businesses have not addressed, is what happens to the information they put in.

What the risk actually is

The concern is not primarily that AI providers are malicious or careless with data. The concern is more practical than that.

When a member of staff pastes a client contract into ChatGPT to ask it to summarise the key terms, that text is submitted to an external system outside your control. Depending on the tool, the version being used and the account settings in place, that text may be used to train future models, may be retained by the provider, may be accessible to the provider’s staff for safety and quality review, or may be stored in ways that are subject to data protection laws in jurisdictions other than the UK.

The same applies to financial data pasted in to build a model, HR information submitted to draft a sensitive communication, technical specifications shared to generate documentation, and pricing or commercial information used to prepare a pitch.

None of this requires a breach, a hack or any malicious intent. The data simply leaves your control the moment it is submitted, and in most SMEs nobody has assessed whether that is acceptable.

Why this is harder to manage than it looks

The difficulty with AI data risk is that the tools are genuinely useful. Banning them outright is both practically ineffective and commercially counterproductive. Staff will use them anyway, through personal devices or personal accounts, and you will simply lose visibility rather than reducing the risk.

The second difficulty is that the risk is not uniform. Submitting a generic marketing brief to an AI tool carries a different risk profile from submitting a due diligence report, a personnel file or a client’s financial statements. Most governance approaches treat all AI use as equivalent, which means they either overreact to low-risk activity or underreact to high-risk activity.

The third difficulty is pace. New tools emerge constantly, existing tools add AI features without announcement, and the default settings of tools your business already uses may have changed without anyone noticing. The Microsoft 365 suite in particular has introduced AI capabilities across Word, Outlook, Teams and Excel that many businesses have not consciously adopted but are already using.

What good governance looks like

The starting point is visibility. Before you can govern AI use, you need to understand what is already happening. That means asking directly, reviewing software in use across the business, checking the settings of tools already deployed, and accepting that the answer will be more extensive than most leaders expect.

The second step is classification. Not all data carries the same sensitivity, and not all AI tools carry the same risk. A governance framework that distinguishes between genuinely sensitive data, such as client personal information, commercially confidential material, financial data and HR records, and lower-sensitivity material gives staff a workable basis for decision-making rather than a blanket prohibition they will quietly ignore.

The third step is tooling. For businesses that want to allow staff to use AI tools productively while controlling what data is submitted, enterprise versions of the major tools offer substantially better data protection terms than free or consumer accounts. Microsoft 365 Copilot, ChatGPT Enterprise and Google Workspace with Gemini all operate under contractual terms that prohibit training on your data and offer stronger retention controls. The cost is meaningful but for most SMEs it is recoverable in the productivity benefit alone, and the governance position it creates is significantly more defensible.

The fourth step is policy. A written AI use policy does not need to be long or complex, but it does need to exist. It should cover which tools are approved for which types of use, what categories of data must not be submitted to external AI tools under any circumstances, what the approval process is for using a tool that is not on the approved list, and what the reporting expectation is if something goes wrong. Most SMEs do not have this in place. Having it means you have a defensible position under UK GDPR, a clear expectation for staff, and a governance basis for your insurers.

The regulatory dimension

UK GDPR places clear obligations on organisations that share personal data with third parties. An AI tool that processes personal data on your behalf is a data processor under that framework, which means you need a Data Processing Agreement in place, you need to have assessed that the tool meets appropriate security standards, and you need to be able to demonstrate that you have done both.

Most businesses using consumer AI tools with personal data have none of this in place. That is not a theoretical risk. The ICO has been increasingly active in its scrutiny of AI-related data processing, and the position “we did not realise the tool was processing personal data” is not a defence.

The same consideration applies to professional and sector-specific obligations. Legal firms, financial services businesses and healthcare adjacent organisations carry additional confidentiality requirements that extend well beyond GDPR. A solicitor asking an AI tool to draft a letter using client case details, or an accountant summarising a client’s financial position, may be breaching professional conduct obligations regardless of whether personal data is technically involved.

A practical starting point

For most SMEs the right starting point is a short audit of current AI tool use, followed by a classification of what data the business holds and which categories of that data warrant specific controls.

That work does not need to be lengthy or expensive, but it does need to be done by someone who understands both the commercial context and the data governance obligations. Leaving it to IT support without board involvement tends to produce either an unworkable blanket ban or a policy that exists on paper but has no practical effect.

The businesses that handle this well treat it as a governance question first and a technology question second. The question is not which tools to allow. The question is what data you are responsible for protecting, what your obligations are to the people and organisations whose data you hold, and what controls you need to have confidence that those obligations are being met.

AI tools are not going away, and the productivity case for using them is real. The governance case for using them properly is equally real, and for most SMEs it remains unaddressed.

If your business uses AI tools and you are not confident that your data governance keeps pace with that use, Northstar can help. We work with SME leadership teams to assess AI-related risk and put proportionate controls in place.

Prices are softening. The questions are not.

If your cyber insurance renewal is due in the next few months, there is a good chance the headline news will be welcome. Premiums have been easing. According to Marsh, global cyber insurance rates fell by 4% in the second quarter of 2026, the twelfth consecutive quarter of decreases. Across the wider UK commercial market, Marsh reports average rates down 8%.

That makes it tempting to treat this year’s renewal as routine: sign the form, pay the slightly lower premium, move on.

That would be a mistake. While prices have softened, underwriting has not gone back to the box-ticking of a few years ago. Marsh notes that as conditions stabilise after prolonged rate reductions, underwriting is becoming more selective. In a competitive market, insurers are choosing which risks they want, and the questionnaire is how they decide.

The questions have changed

Older cyber proposal forms asked broad questions. Do you have antivirus? Do you back up your data? Do you use multi-factor authentication? A confident “yes” was usually enough.

Current forms probe specifics, and increasingly expect you to be able to prove your answers. The shift looks something like this:

What older forms askedWhat current forms ask
Do you use MFA?Is MFA enforced for all users, on email, remote access and every privileged or admin account? Are there exceptions?
Do you patch your systems?How quickly are critical vulnerabilities patched? Can you evidence it? What happens to systems that cannot be patched?
Do you take backups?Are backups stored offline or immutable? Are they separated from your main network credentials? When were they last restored in a test, and how long did it take?
Do you train staff?How often? Do you run phishing simulations? What do you do with the results?
(Not asked)What AI tools are in use, what data goes into them, and what governance sits around them?

None of these questions are unreasonable. They reflect what insurers have learned from paying claims. But each one turns a general statement of good intent into a specific, checkable claim about how your business actually operates.

The new section: AI

The most noticeable addition in many 2026 questionnaires is a section on artificial intelligence. Underwriters want to know what AI tools the business uses, what data is being sent to third-party AI providers, and what controls and oversight are in place.

This matters because adoption is running well ahead of governance. The government’s latest Cyber Security Breaches Survey found that nearly a third of UK businesses are using, adopting or considering AI, but only 24% of those have cyber security measures in place to manage the associated risks.

For many SMEs, the honest answer to “what AI tools are in use?” is “we’re not entirely sure”. Staff use ChatGPT, Copilot or other tools, sometimes through company accounts and sometimes through personal ones, often without anyone having decided what data is acceptable to put into them.

The insurance market is still working out how to handle this. Commentators describe a move away from “silent AI”, where AI risks were implicitly covered by existing policies without being mentioned, towards AI-specific exclusions and revised wording. For now, cyber policies remain the most stable source of cover, with many insurers treating AI as an extension of traditional cyber risks such as unauthorised access, data breaches and social engineering. Some insurers have gone further and written affirmative cover in; Coalition, for example, introduced an AI endorsement covering events such as fraudulent instructions sent via deepfakes, and later built it into its base policy.

The practical point for an SME is simple. If the form asks about AI and you cannot describe what you use and how it is controlled, that is likely to count against you, and you should check carefully whether your policy wording now limits cover for AI-related losses.

Who actually fills in the form

The people signing off these renewals are usually FDs or MDs, not IT specialists. They are often working through a long questionnaire close to a deadline, relying on a quick conversation with the MSP or whoever “looks after IT”.

That creates two problems. First, the questions are technical, and the difference between “MFA is on” and “MFA is enforced for every user and admin account with no exceptions” is not obvious unless you know why it matters. Second, the answers carry legal weight. Under the Insurance Act 2015, businesses have a duty of fair presentation: to disclose what they know, or ought to know, about their risk. An answer given in good faith but turning out to be wrong can still affect a claim.

The gap between what the new questions actually mean and what the business can genuinely evidence is often far wider than anyone realised until the form is in front of them.

The backup that existed and the test that did not

One pattern comes up repeatedly. A business has had backups running reliably for years. The MSP set them up, the reports arrive, nobody has ever had a reason to worry. Then the renewal form asks: when did you last test a full restore, and can you evidence it?

Nobody can remember a test. There is no record of one. The backup existed. The test did not.

That single gap, invisible in day-to-day operations, can be the difference between a smooth renewal and a difficult one. At renewal, it may mean a higher premium, a narrower policy or additional conditions. After an incident, it is worse: if backups turn out to be unusable, or the business told the insurer they were tested when they were not, the claim itself may be at risk.

The same pattern repeats elsewhere. MFA that is on for most users but not the finance director who found it inconvenient. Patching that happens, but with no reporting to prove how quickly. A training programme that ran once, two years ago. In each case, the control mostly exists. The evidence does not.

Why a soft market makes this more important, not less

It is easy to assume that falling prices mean insurers are relaxed. In reality, competition means insurers are differentiating, not just on price but on which businesses they want to cover and on what terms. Marsh notes insurers are competing through broader cover and lower deductibles as well as price.

Those better terms go to businesses that can demonstrate good controls. A business that can evidence MFA coverage, patching times, tested backups and AI governance is in a strong position to negotiate. A business that answers vaguely, or cannot back up its answers, may still get cover, but on worse terms than it could have had, and with more risk of a dispute if it ever needs to claim.

Treat the questionnaire as a review, not a formality

Treating the annual questionnaire as a formality is no longer a safe assumption. The better approach is to treat it as a free, annual health check on your security, written by the people who pay out when things go wrong.

In practice, that means:

  1. Get last year’s form and this year’s form side by side as early as possible. Note the new questions.
  2. Translate the technical questions into plain terms, so the person signing understands what they are confirming.
  3. Test each answer against reality, including the exceptions. “Yes, except for…” needs to be written down, not glossed over.
  4. Gather evidence before you answer: MFA reports, patching reports, backup restore test results, training records.
  5. Take stock of AI use across the business, including tools staff use on their own initiative, and agree basic rules on what data can go into them.
  6. Fix quick wins before renewal, such as running and documenting a backup restore test, or closing MFA gaps.
  7. Talk to your broker about any answers you are unsure of, and check the policy wording for AI-related exclusions or limits.

This is worth doing with someone independent of the people who run your IT, ideally a few weeks before the renewal lands, not while filling in the form under a deadline. An honest internal review costs a few hours. The alternative is finding out what your answers really meant when you need to make a claim.

Your cyber insurance policy has conditions. Most SMEs have not read them.

A cyber insurance policy is not a blanket safety net. It is a contract with conditions attached, and those conditions typically require specific controls to be in place and evidenced before an incident occurs, not after. Multi-factor authentication on key systems. Patch management within a defined timeframe. Backups that are not just taken, but tested.

For many SMEs, the gap between what they assumed the policy covered and what it actually requires is only discovered at the worst possible moment: when a claim is being assessed.

Cyber insurance is growing fast, and so are claims

More UK businesses are buying cyber cover than ever. Among small businesses, take-up rose from 49% in 2024 to 62% in 2025, according to the government’s Cyber Security Breaches Survey. Across the wider market, the ABI reports that 17% more policies were taken out in 2024 than the year before.

Claims are rising sharply too. The ABI found that £197 million was paid out to help UK businesses recover from cyber incidents in 2024, a 230% increase on 2023. Malware and ransomware made up 51% of claims, up from 32% the year before. And those figures predate the major attacks on household-name retailers and manufacturers in 2025.

None of this is bad news for insurance. Most legitimate claims are paid, and a good policy brings more than money: access to incident response specialists, legal support and forensic experts at the moment you need them most. But as payouts climb, insurers are understandably scrutinising claims more closely, and asking harder questions at underwriting and renewal. That is where SMEs get caught out.

Why claims get declined

Declined claims are rarely about whether the incident was genuine. Nobody disputes that the ransomware happened or the invoice fraud was real. The question is whether the controls the policy required were actually in place, and whether you can prove it.

Most problems fall into a handful of categories.

1. The application form said one thing, reality said another

When you buy or renew cyber cover, you complete a proposal form or questionnaire about your security. Do you enforce MFA? Do you patch critical vulnerabilities promptly? Are your backups stored offline and tested? These answers form the basis on which the insurer agrees to cover you and sets your premium.

The trouble is that these forms are often filled in quickly, by someone in finance or operations, ticking “yes” in good faith based on what they believe to be true. If the insurer later finds the answer was inaccurate, it may treat that as misrepresentation.

A widely discussed 2025 case in Canada illustrates the point. Commentary on the case highlighted that the attack began through an exploited internet-facing server where MFA was missing, and affected 80% of the network. Analysts suggested the claim may have been declined either because the policy had a minimum security standards condition, or because the organisation had stated it enforced MFA for all remote access when it did not.

In the UK, the Insurance Act 2015 places a “duty of fair presentation” on businesses buying insurance. In plain terms, you must disclose what you know, or ought to know, about your risk. An insurer’s remedy depends on what it would have done had it known the truth, which can range from adjusting the premium to declining the claim entirely. “We thought MFA was on everywhere” is not a strong position.

2. MFA was on, but not everywhere

This is the single most common gap I see. MFA is switched on for Microsoft 365, but not for the VPN. Or it is on for staff accounts, but not for the admin accounts that matter most. Or it is enforced for everyone except the two directors who found it inconvenient.

Insurers increasingly expect MFA across email, remote access and privileged accounts as a baseline. If an attacker gets in through the one account without it, partial deployment offers little comfort.

It is worth knowing how common this gap is across UK businesses. The government’s latest survey found that only 47% of businesses use any form of multi-factor authentication. Many of those will be partial deployments.

3. Backups that exist but don’t restore

Almost every business believes it has backups. Far fewer have tested whether they can actually restore from them, how long it would take, and whether the backups would survive an attacker who has gained admin access to the network.

Policies often require backups to be taken regularly, stored separately from the main network, and tested. If your backups fail during an incident, or turn out to have been encrypted along with everything else, the insurer may question whether the conditions were met and whether your losses could have been reduced.

4. Patching that slipped

Many policies expect critical security updates to be applied within a defined timeframe. If an attacker exploits a vulnerability that was publicly known and patched by the vendor months earlier, expect questions about why the update was not applied.

In SMEs, patching usually sits with the MSP. That is fine, but it means you need visibility of what is being patched, how quickly, and what has been excluded. “The MSP handles it” is not evidence.

5. Breaking the rules during the incident itself

Some claims run into trouble not because of what happened before the incident, but during it. Common examples:

  • Calling in your own IT company or a forensic firm before contacting the insurer’s incident response line, when the policy requires you to use their panel.
  • Paying a ransom, or negotiating with attackers, without the insurer’s consent.
  • Delaying notification to the insurer beyond the timeframe set in the policy.
  • Wiping and rebuilding systems before evidence has been preserved.

All of these are understandable reactions in a crisis. That is exactly why they need to be worked out in advance and written into an incident response plan. The government’s survey found only a quarter of UK businesses have a formal incident response plan. Without one, the first time anyone reads the claims procedure is often during the incident.

6. The cover was never there in the first place

Finally, some businesses discover that the loss they suffered simply was not covered. Common examples include business interruption cover that is too low or subject to a long waiting period, social engineering or invoice fraud being excluded or heavily sub-limited, and losses at a key supplier not being covered at all.

Cyber policies are rarely one single pot of cover. They are usually split into sections, such as incident response, data restoration, business interruption, extortion, fraud and third-party liability, each with its own limits, excesses and conditions. A claim can be paid under one section and declined under another.

The real gap is evidence

The common thread in all of this is evidence. A business that has MFA switched on for some systems but not others, or has never tested whether its backups genuinely restore, can find itself with a policy that looks comprehensive on paper and offers far less protection in practice than the premium suggested.

When a claim is assessed, the insurer or its appointed experts will want to see records. Screenshots or reports showing MFA enforcement. Patch reports. Backup logs and restore test results. Training records. Your incident response plan. If those records do not exist, it can be difficult to show the controls were in place, even if they mostly were.

This is also a governance issue. The government’s survey shows only 31% of UK businesses have someone at board or senior management level with explicit responsibility for cyber security. When nobody owns the question, nobody checks that what the proposal form says matches what is actually happening.

Treat the policy as a checklist, not a formality

This is not a reason to distrust cyber insurance. For most SMEs, it is a sensible part of managing risk. It is a reason to treat the policy as a checklist rather than a formality.

In practice, that means:

  1. Read the conditions and exclusions properly, not just the schedule and the headline limits. Look specifically for minimum security requirements, conditions precedent and claims procedures.
  2. Pull out the last proposal form and check every answer against reality. Where an answer was wrong, tell your broker before renewal, not after a claim.
  3. Map each required control against what is in place, across every system, user and location. Look for the exceptions, because that is where attackers and loss adjusters both look.
  4. Gather the evidence now: MFA reports, patching reports, backup restore tests, training records. Keep them somewhere you can reach if your systems are down.
  5. Check your MSP contract covers what the policy requires, and that your MSP knows what you have told the insurer.
  6. Write the claims process into your incident response plan, including the insurer’s emergency number, kept somewhere accessible offline.
  7. Make someone accountable at leadership level for keeping this aligned through the year, not just at renewal.

Reading the conditions properly and mapping them against what is actually in place takes a few hours. It closes a gap that most SMEs do not know exists until it is too late to matter.

If nobody in your business has read your cyber policy’s conditions line by line in the last twelve months, that is worth putting right before the next renewal, not after a claim.

Speak to your broker if you have any concerns, they will be able to offer legal advice.

At 15 people, informal IT works fine. At 35, it starts costing you money you cannot see.

There is a specific point in a growing business where the IT setup that carried you from ten people to twenty-five simply stops working. Almost nobody sees it coming, because nothing dramatic happens to mark the moment. No system crashes. No single bad day. It is a slow build-up of friction that gets absorbed, mostly by the founder or MD, until it becomes normal.

I see the same pattern again and again. The business has grown well. Revenue is up, the team has doubled, maybe there is a second office or a hybrid workforce. But the way technology is run has not changed since the days when everyone sat round one table and the most technical person in the room “did the IT”.

Why it happens between 25 and 35 people

In the early days, informal IT is the right answer. Decisions are fast, everyone knows everyone, and the cost of getting something slightly wrong is small. The founder picks a few tools, an MSP handles the laptops and the email, and it works.

The problem is that complexity does not grow in a straight line with headcount. Every new person adds accounts, devices, permissions, data and another way for things to go wrong. Every new team tends to bring its own tools. Research from BetterCloud shows how quickly this happens: young companies of one to two years old typically start with around 29 SaaS apps, and by the time they are three to six years old that figure has jumped to about 103. Nobody sat down and decided to run a hundred systems. It just happened, one sensible decision at a time.

Around the 25 to 35 mark, the volume of change finally exceeds what one busy founder and a reactive support contract can absorb. The exact point varies depending on how technical the founding team is and how fast growth has been, but the symptoms are remarkably consistent.

The five warning signs

1. Onboarding takes days, not hours

When access provisioning is manual and undocumented, every new starter becomes a small project. Someone has to remember which systems they need, who has admin rights to each one, and what the laptop should have on it. Inevitably something is missed.

This is not unusual, but it is expensive. One industry study found that 43% of new hires waited more than a week for basic workstation logistics and tools, and 18% waited over two months for the tools they needed. Even a short delay adds up. As one estimate puts it, two days of onboarding delay for a well-paid employee means roughly two days of paid time with nothing to show for it, and across 20 hires in a growth year that becomes a significant direct loss, before you count the time spent by whoever is doing the provisioning.

For a business hiring steadily, that is real money leaking out every month. It also sends new starters the wrong message in their first week.

The flip side matters just as much. Offboarding is usually worse than onboarding. If you cannot say with confidence that every leaver lost access to every system on their last day, you have a security problem as well as an admin one.

2. Nobody has a complete list of your systems

Ask most growing businesses for an authoritative list of every system they run, who owns it, what data sits in it and what it costs, and you will get a pause. The list exists in pieces: in the finance system as card payments, in people’s heads, in an MSP’s asset register that only covers the hardware.

This matters for three reasons. First, cost: unused and duplicate subscriptions are common, and Zylo’s research found that 53% of licences go unused within 30 days. Second, risk: you cannot protect data you do not know you hold. Third, resilience: if a key person leaves, the admin rights and institutional knowledge for a critical system can leave with them.

3. The MSP has become reactive

Many MSP relationships start well. When the business is small and simple, tickets in and fixes out is exactly what is needed. But as the business grows, you need someone thinking ahead: planning for the next office move, the next 20 hires, the renewal of your main line-of-business system, the security controls your biggest customer is now asking about.

That forward-looking work is rarely in a standard support contract, and it is not the MSP’s job to set your technology direction. So it falls into a gap. The MSP waits to be asked, the business does not know what to ask, and the relationship drifts into pure break-fix. When something does go wrong, the MSP calls the founder.

4. Security gaps open up because nobody owns the question

This is the most serious sign, and the one most often hidden. In a growing business, security is everyone’s problem and therefore no one’s. The MSP assumes the business will tell them what it needs. The business assumes the MSP has it covered.

The UK data backs this up. According to the government’s latest Cyber Security Breaches Survey, 43% of UK businesses identified a cyber security breach or attack in the previous 12 months. Crucially, the rate climbs with size: 65% of medium businesses reported a breach, compared with 42% of micro and 46% of small businesses. A business crossing from 25 to 50 people is moving directly into that higher-risk bracket, often without changing how it manages security at all.

Yet ownership remains thin. Only 31% of businesses have someone at board or senior management level with explicit responsibility for cyber security. Only a quarter have a formal incident response plan, meaning most businesses that suffered a breach responded without a defined approach. And just 5% of UK businesses hold Cyber Essentials certification, while fewer than half use two-factor authentication.

Supplier risk is a growing blind spot too, and highly relevant when you depend on an MSP and dozens of SaaS providers. The survey found only 22% of small businesses review risks from their immediate suppliers, and 10% review their wider supply chain.

The consequences are getting more serious. The proportion of businesses reporting loss of revenue or share value after a breach rose from 2% to 5%. Increasingly, the question is not just about attacks either. Larger customers, insurers and investors now ask pointed questions about your controls during procurement, renewals and due diligence. A business that cannot answer them loses deals, pays more for cover or takes a hit on valuation.

5. The founder is still the IT department

Underneath all of this sits the most expensive symptom of all. The founder or MD is still the person who gets pulled into IT decisions, often several hours a week. Approving a new tool. Chasing the MSP. Resetting the admin password on the website. Answering the security questionnaire from a prospective customer at 10pm.

Individually, each of these takes a few minutes. Together, they take a real slice of the most valuable time in the business, and they pull attention away from sales, people and strategy at exactly the point where growth demands it most. Because the cost never appears on an invoice, it rarely gets challenged.

This is a governance problem, not a technology problem

The instinct at this point is often to buy something: a new platform, a bigger support contract, another tool. Sometimes that helps. But the root cause is almost never a lack of technology. It is a lack of ownership, visibility and decision-making structure around the technology you already have.

The businesses that navigate this stage well do a few simple things:

  • They give someone clear accountability for IT and cyber risk at leadership level, even if that person is not full-time.
  • They build a single register of systems, data and suppliers, with named owners and renewal dates.
  • They standardise joiners, movers and leavers, so access is granted and removed consistently and quickly.
  • They reset the MSP relationship around agreed outcomes, regular reviews and a forward plan, not just ticket volumes.
  • They put the basics in place: multi-factor authentication everywhere, tested backups, a written incident response plan, and a recognised baseline such as Cyber Essentials.
  • They report IT and cyber risk to the board in plain business terms, so decisions are made deliberately rather than by default.

None of this requires a full-time IT director on a large salary. For most businesses at this size, fractional or part-time oversight is enough to set direction, hold suppliers to account and take the founder out of the loop.

The key is timing. Bringing in oversight before the friction becomes a crisis is far cheaper than doing it after a breach, a failed audit or a lost contract.

Is this you?

A quick self-check. If you answer “no” or “not sure” to more than a couple of these, you are probably at the inflection point:

  • Can a new starter be fully productive on day one?
  • Could you produce a complete list of your systems and who has access to them within an hour?
  • Are you confident every leaver lost access to everything on their last day?
  • Does your MSP bring you ideas and plans, or just close tickets?
  • Is a named person at leadership level accountable for cyber risk?
  • Do you have a written incident response plan that has been tested?
  • Have you stepped back from day-to-day IT decisions?

If new starters are waiting days for access, or you are still the person the MSP calls when something breaks, it is worth a conversation.

Most founders only bring IT and cyber into the exit conversation once the data room is open and the buyer’s advisers have started asking questions. By then, most of the useful work is already too late to do properly.

IT due diligence rarely kills a deal outright. What it does, far more often, is quietly reduce the price, add conditions, or generate warranties the seller has to carry for years afterward. Research from West Monroe’s M&A cybersecurity study found that 40% of acquirers discovered cybersecurity problems only after the deal had already closed, and 80% now rate cybersecurity as highly important to due diligence, up from a smaller share just two years earlier.

Tellingly, most of those buyers said they rarely walk away over what they find. Instead, 47% use it to plan post-deal remediation, a third use it to decide whether to proceed at all, and a fifth use it purely to negotiate better terms. The issues do not stop deals. They cost sellers money and leverage.

None of this is exotic. It is the same territory a fractional IT director would already have under control if one had been in place. A buyer’s technical advisers will look at several things in sequence, and each has its own way of quietly eroding value:

Infrastructure age and resilience. Ageing servers, unsupported operating systems, no tested backup or disaster recovery plan. RSM’s private equity practice has documented cases where a decades-old, custom-built system was found, post-close, to be incapable of supporting integration with the acquirer’s platform, running remediation costs into the tens of millions. Most SME findings are smaller than that, but the pattern, a technology estate that has quietly aged past the point of being fit for purpose, is common.

Licence compliance. Under-licensed software, expired agreements, unclear ownership of custom-built systems. A software audit during diligence that turns up a compliance gap becomes a true-up cost the seller usually ends up funding, either through a reduced price or a specific warranty.

Cyber posture. Patch management, access control, whether Cyber Essentials or an equivalent is in place, and whether there has been an incident that was never formally logged. This is the category buyers now treat as standard rather than optional, and it is also the one most likely to surface a nasty surprise, since many SMEs simply do not know what they do not know here.

Supplier contracts and change of control. Key supplier and customer contracts often contain change of control clauses that trigger renegotiation, or worse, termination rights, the moment ownership changes. A contract that looks fine on day one of ownership can unravel on day one of new ownership.

GDPR and data handling. Where personal data actually lives, who can access it, and whether the paperwork matches the practice. Gaps here tend to be structural rather than dramatic: no data processing register, informal sharing arrangements with suppliers, retention that nobody has reviewed in years.

Key-person dependency. How much of the IT picture exists only in one person’s head. This is the finding that unsettles buyers most, because it cannot be fixed with a purchase order. It has to be documented and handed over, and that takes time the exclusivity period rarely allows.

The businesses that come through diligence cleanly are usually the ones where someone independent has been asking these questions for a year or two beforehand, not the ones scrambling to produce an asset register the week the data room opens.

Grant Thornton’s own exit readiness work lists IT explicitly as one of the enabling functions boards need to have in order well before a transaction starts, alongside financials and governance, precisely because issues in these areas “can surface late in the process when time is limited.” And when they do surface late, they surface as leverage against the seller, not the buyer. Roughly one in seven warranty and indemnity insurance policies ends up seeing a claim, and every claim is a reminder that whatever was not caught and fixed before signing gets carried as risk afterward, by someone.

If a sale is somewhere in your next two or three years, even as a loose ambition rather than a firm plan, the IT and cyber picture is worth an honest look now. Fixing a gap eighteen months out is a project. Fixing it during exclusivity is a negotiating point, and it will not be in your favour.

A short, independent review now costs far less than a renegotiated price later. Get in touch and I’ll give you a straight, no-obligation read on where you actually stand.

Ask most SME leaders whether their business uses artificial intelligence and the answer is cautious. “We are looking at it.” “We have not made a decision yet.” “We want to understand it better before we commit.”

The reality in most organisations is rather different. AI is already present, often extensively, in the software and platforms the business already pays for, in the tools individual staff have adopted independently, and in the features that have been enabled by default without anyone actively choosing them.

Understanding what is already in use is the essential starting point for any sensible approach to AI governance. You cannot manage what you do not know about.

The AI tools most commonly found in SMEs

*Microsoft 365 Copilot features

Even businesses that have not purchased a Copilot licence may have AI features active within their Microsoft 365 environment. Microsoft has been progressively embedding AI functionality into existing products, in Outlook, in Teams, in Word and Excel, sometimes as opt-in features, sometimes enabled by default as part of product updates. A review of your Microsoft 365 admin settings will typically reveal AI features that nobody in the business actively enabled.

*Grammarly

Widely used across business functions for proofreading and editing, Grammarly processes the text it is asked to review. For most business use this includes emails, reports, proposals and other documents, some of which will contain client information, commercially sensitive content or personal data. Most users have not considered what Grammarly does with the text it processes.

*ChatGPT and similar large language model tools

Direct use of ChatGPT, Claude, Gemini and similar tools for work tasks is widespread in most organisations, regardless of whether any formal decision about AI adoption has been made. Staff use these tools to draft emails, summarise documents, research topics and generate content. The data they input, including frequently, client and commercially sensitive information is processed by the tool provider’s systems.

*AI features in CRM and business software

Salesforce, HubSpot, Notion, Monday.com and many other common business platforms have added AI features in recent product updates. These features may be active by default and may be processing customer data, communication records and business information in ways that were not assessed when the platform was originally selected.

*AI writing and content tools

Jasper, Copy.ai, and similar tools used for marketing content generation are AI platforms that process the briefs, brand information and content context provided to them. Where this information includes client details, campaign data or proprietary business information, the data handling implications require assessment.

*AI features in communication platforms

Zoom, Teams and other video conferencing platforms now offer AI-powered transcription, summarisation and action tracking. Where these features are active, meeting content including confidential client conversations, board discussions and commercially sensitive negotiations, is being processed by AI systems.

What this means for governance

The first implication is practical. If you do not know which of these tools are in use in your organisation, you cannot assess the data protection and confidentiality implications. A structured AI usage audit, asking staff what tools they use for work, reviewing platform settings for enabled AI features, and reviewing software subscriptions is the starting point.

The second implication is regulatory. Where personal data is being processed through AI tools, the requirements of UK GDPR apply. This includes ensuring that there is a lawful basis for that processing, that there are appropriate contractual protections with the tool provider, and that individuals whose data is processed have been informed as required.

The third implication is commercial. Client confidentiality obligations, professional conduct requirements and contractual data handling commitments may all be relevant to how AI tools are used in your organisation. Understanding whether current AI usage is compatible with these obligations requires an assessment, not an assumption. The starting point for all of this is understanding what is already happening. In most organisations, that picture is more extensive than leadership expects.

In a significant proportion of UK SMEs, the primary point of contact for the managed service provider is the Managing Director.

Not because the MD has particular IT expertise. Not because IT is their core responsibility. But because nobody else in the business has the seniority to hold the supplier accountable, and the supplier knows it.

This dynamic has real commercial consequences, for the quality of the service received, for the MD’s available time, and for the business’s ability to make good technology decisions.

How it develops

The pattern is consistent. The business engages an MSP. The MSP relationship is managed informally, issues raised on an ad hoc basis, no structured service reviews, no performance metrics tracked. When something goes wrong that cannot be resolved at staff level, it escalates to the MD.

Over time the MD becomes the de facto IT manager. They are the person the MSP calls when something needs a decision. They are the person who signs off on proposals for new technology. They are the person who handles renewals and, occasionally, complaints.

The supplier is often comfortable with this arrangement. An MD without technical IT knowledge, managing the relationship informally, alongside all the other demands on their time, is significantly easier to manage than a structured, informed client with clear performance expectations.

Why it is a problem

It consumes MD time that should be spent elsewhere – Senior leadership time is the scarcest resource in most SMEs. An MD spending two to four hours per month on IT issues, supplier conversations and technology decisions is an MD not spending that time on clients, strategy and growth. The opportunity cost is real.

It produces poor commercial outcomes – An MD without technical IT knowledge and without the time to develop it is not well-positioned to challenge a supplier’s technical recommendations, negotiate contract terms effectively, or identify when a proposed solution is unnecessary or overpriced. Suppliers, consciously or not, take advantage of this asymmetry.

It means nobody is asking the strategic questions – The MD managing IT supplier issues reactively is not thinking about IT governance, cyber risk, technology strategy or whether the current setup is appropriate for where the business is heading. Those questions go unasked.

It creates a single point of failure – If the MD is the only person with knowledge of the IT supplier relationship and the systems it supports, that knowledge does not exist anywhere in the business in a structured form. When the MD is unavailable or when they eventually move on, the institutional knowledge goes with them.

The alternative

The alternative is not necessarily hiring a full-time IT director. For most SMEs the economics do not justify that hire. The alternative is ensuring that IT supplier management is handled by someone who has the technical knowledge to evaluate performance, the commercial seniority to hold the supplier accountable, and the time to do both properly.

In practice, this means either developing internal capability, which requires hiring or training or bringing in independent IT oversight on a fractional basis.

The fractional model means the person sits above the MSP relationship on the client’s behalf. He conducts the service reviews. He manages the renewal negotiations. He escalates issues at the right level and with the right technical and commercial context. He attends board meetings and reports on IT and cyber risk in terms the board can act on.

The MD gets their time back. The supplier operates in a properly managed relationship. And the business gets better IT outcomes at a lower cost than the informal management model was producing.

Auto-renewal clauses are standard in most IT contracts. They exist because they serve the supplier’s commercial interests, ensuring that revenue continues without the friction and uncertainty of a renegotiation. For clients, they represent a recurring and largely avoidable source of overspend.

Understanding how these clauses work, and what to do about them, is one of the most straightforward ways a business can reduce its IT costs without changing its suppliers or its technology.

How auto-renewal clauses work

A typical auto-renewal clause reads something like this: “Unless either party provides written notice of termination not less than [30/60/90] days prior to the expiry of the current term, this agreement shall automatically renew for a further period of [12 months] on the same terms and conditions.”

The effect is that if you do not actively notify the supplier that you do not wish to renew, within a specific and often narrow window the contract continues for another full term at the existing price, regardless of how the service has performed, regardless of whether the market has moved, and regardless of whether the scope still reflects your requirements.

Why they are so effective at trapping businesses

*The notice window is easy to miss – A 30-day notice window on a contract that expires on a specific date requires you to know the expiry date and act before a deadline that may not appear anywhere prominently. Most businesses do not maintain a contract renewal calendar and discover the renewal has happened after the fact.

*Suppliers rarely remind you proactively – An MSP with a commercial interest in automatic renewal at existing rates has no incentive to remind you that your notice window is approaching. Some suppliers do notify clients as a matter of good practice. Many do not.

*The contracts are long and the clause is buried – Auto-renewal clauses typically appear in the standard terms and conditions rather than the commercial summary. They are not the part of a contract that people read carefully at signing and are rarely remembered at renewal time.

*Switching feels harder than renewing – Even when a business recognises that a supplier is underperforming or overcharging, the perceived complexity and disruption of switching often leads to accepting another auto-renewed term rather than pursuing an alternative. The supplier benefits from this perception whether or not it accurately reflects the actual cost of switching.

The financial impact

The financial cost of auto-renewal at above-market rates accumulates quickly. Connectivity and telephony services in particular have seen significant price reductions over recent years. A leased line or MPLS circuit contracted five years ago may be renewing annually at a rate 30 to 40 percent above what equivalent or better service costs today. Each auto-renewed year locks in that above-market rate for another twelve months.

Across a typical SME IT estate – MSP contract, connectivity, telephony, cloud services, security software – the aggregate overspend from unreviewed auto-renewals can easily reach tens of thousands of pounds per year.

What to do about it

*Build a contract renewal calendar immediately – List every IT contract, its expiry date, and its notice period. Set calendar reminders for three months before each notice deadline. This single action prevents the majority of accidental auto-renewals.

*Review every contract before it auto-renews – The renewal moment is your leverage point. Use it. Even a brief assessment of whether the service has performed, whether the pricing is still competitive, and whether the scope still reflects your requirements gives you the basis for a negotiation.

*Benchmark before you renew – You do not need to go to full tender. A conversation with one or two alternative providers about indicative pricing gives you a market reference point and, if shared with your existing supplier, changes the dynamics of the renewal conversation.

*Negotiate notice periods on new contracts – When signing new IT contracts, push for shorter notice periods, 30 days is more client-friendly than 90, and for clear exit provisions that specify what happens to your data and systems if you choose to leave.

Microsoft Copilot has now been available to Microsoft 365 business subscribers for long enough that the early adopter experience is giving way to a more measured assessment of what the product actually delivers in practice, as opposed to what the marketing promised.

The picture that emerges from businesses that have deployed it, including SMEs that have shared their experience with Northstar is more nuanced than either the enthusiastic vendor narrative or the sceptical dismissals suggested. There are genuine use cases where Copilot delivers consistent, measurable value. There are others where the gap between promise and reality remains significant.

Where Copilot is genuinely delivering

*Meeting summaries and action tracking

The Teams integration that generates meeting summaries, captures action items and produces follow-up notes is consistently the most positively received feature among business users. For organisations with frequent internal or client meetings, the time saving is real and the output quality is generally adequate for the purpose.

The caveat is that this only works where meetings are conducted in Teams with recording and transcription enabled. Organisations that conduct meetings in other ways, or where participants are uncomfortable with recording, will not benefit.

*Email thread summarisation

For individuals managing high volumes of email, the ability to summarise a long email thread and extract the key points and required actions is genuinely useful. The quality is variable, it performs better on straightforward factual threads than on complex, nuanced conversations, but for the majority of business email the summarisation is adequate and time-saving.

*First-draft generation for structured documents

Copilot’s ability to generate a structured first draft of a report, proposal or presentation from a brief or an existing document reduces the blank-page problem significantly for roles that involve regular long-form writing. The drafts require meaningful editing before they are suitable for external use, but the acceleration of the drafting process is real.

Where Copilot is underdelivering

*Data quality dependency

Copilot’s ability to answer questions about your organisation, “summarise the key points from our Q3 sales reports” or “what did we agree in the last client review?” depends entirely on whether the relevant information is in your Microsoft 365 environment in a form Copilot can find and process.

Most organisations’ SharePoint and Teams environments are not organised in a way that supports this kind of retrieval. Files are poorly named, folder structures are inconsistent, and large amounts of relevant information exist in email attachments that are not indexed effectively. The result is that Copilot either cannot find the relevant information or retrieves the wrong information confidently.

*Inconsistent output quality across user types

The productivity gains from Copilot are concentrated in specific roles and tasks. For someone who spends significant time writing, summarising, and processing information, Copilot can deliver meaningful efficiency gains. For someone whose work is primarily operational, client-facing or involves physical activity, the benefit is minimal.

Licensing all users in an organisation to achieve benefits for a subset of them is not always the right commercial decision, and it is not a decision that Microsoft or an MSP with a licensing margin incentive will make on your behalf.

*The data governance prerequisite

This is the issue that Northstar most consistently flags to clients considering Copilot. The product works by accessing the information your users are permitted to access in the Microsoft 365 environment. If your permissions are not properly configured and in most SMEs they are not, Copilot can surface content that should not be visible to that user.

This is not a minor technical detail. It means that before deploying Copilot, organisations should conduct a review of their Microsoft 365 permissions, ensure that sensitive content is appropriately protected, and confirm that the information Copilot will access on behalf of each user is information they should legitimately be able to see.

The honest assessment for SMEs

Copilot is a good product that delivers real value in the right context. It is not the universal productivity transformation that Microsoft’s marketing suggests, and it is not a product that every user in every organisation will benefit from equally.

For UK SMEs evaluating Copilot, the right approach is to identify the specific roles and use cases within your organisation where the benefit is most likely to be real, pilot the product with those users before committing to broader licensing, ensure your Microsoft 365 environment and permissions are in a suitable state, and take independent advice before committing to the licensing cost. Anyone telling you Copilot is definitely right for your business without understanding your specific workflows, your data environment and your team structure is selling, not advising.

© 2026 Northstar IT & Cyber Advisory Limited. Company registered in England & Wales. Company No. 17038464. About What We Do How We Help Insights FAQs Free Cyber Risk Guide Free Checklist Free AI Risk Guide Privacy PolicyCookie PolicyTerms & ConditionsAccessibility
Fractional IT & Cyber Leadership for UK SMBs & SMEs
Locations: London Kent Essex Sussex Surrey South East