A client was quoted forty thousand pounds for GDPR compliance. The actual gap took six weeks and cost a fraction of that.

There is a consistent pattern in how SME compliance anxiety gets created, and it is not usually the regulation itself. It is the way regulation gets described to the business.

Compliance obligations are often presented at their most expansive and complex. Sometimes that reflects genuine caution. Sometimes it reflects the fact that a larger, more complicated problem supports a larger, more complicated engagement. Either way, the board is left with the impression that compliance is a vast, expensive undertaking, and either overspends or, just as often, does nothing because the whole thing feels too big to start.

The question that trips up most SME boards is a simple one: what does the law actually require of a business our size? The honest answer is usually more manageable than they have been led to believe.

Why compliance feels bigger than it is

There are a few reasons the picture gets distorted.

Framework creep. Large organisations need extensive policy suites, dedicated data protection officers and formal governance committees. Those frameworks are often sold, lightly adapted, to businesses a fraction of the size. A 40 page policy pack might be appropriate for a bank. It is rarely appropriate for a 35 person professional services firm.

Headline fines. The maximum penalties under UK GDPR are eye catching, and they get quoted often. But the ICO’s approach is risk based and proportionate. It prioritises issues that cause real harm to people, and for small businesses many cases end in reprimands and remediation rather than fines. That is not a reason for complacency. Reprimands are often published, and the reputational damage is real. But it is a long way from the catastrophe some pitches imply.

Incentives. Anyone selling a compliance solution has a natural incentive to describe the problem in a way that fits it. That does not make them dishonest. It does mean the board benefits from at least one voice in the room with no stake in the size of the answer.

What proportionate GDPR compliance actually looks like

For a business of 30 to 50 people with a typical data profile (staff records, customer and supplier contacts, perhaps some marketing), UK GDPR does not require a sprawling programme or an indefinite retainer. It requires a defined set of things done properly and kept up to date.

1. Know what data you hold. A working data register, sometimes called a record of processing: what personal data the business holds, where it lives, why it holds it, who it is shared with and how long it is kept. This is the foundation for everything else.

2. Have a lawful basis for each use. For each purpose, be clear whether you rely on contract, legal obligation, legitimate interests or consent. Many SMEs over rely on consent when another basis fits better.

3. Tell people what you do. A clear, accurate privacy notice for customers and a separate one for staff. Plain English, not legal boilerplate.

4. Put the right contracts in place with suppliers. Data processing agreements with the suppliers who handle personal data on your behalf: your MSP, payroll provider, CRM, email marketing platform and so on.

5. Keep data only as long as you need it. A simple retention schedule, and evidence that it is actually followed. Old data you no longer need is risk with no benefit.

6. Protect it sensibly. Security proportionate to the risk: access controls, multi factor authentication, encryption on laptops, backups. This is where data protection and cyber security overlap, and where many of the real risks sit.

7. Know what to do when something goes wrong. A short breach procedure, including how to assess whether a breach needs reporting to the ICO within the 72 hour window.

8. Handle people’s rights requests. A process for subject access requests and other rights. Since the Data (Use and Access) Act 2025 came into force, organisations need only carry out a reasonable and proportionate search when responding to a subject access request, which helps smaller businesses considerably.

9. Have a complaints process. This is the newest requirement and the one most SMEs have missed. Since 19 June 2026, all organisations must give people a way to make data protection complaints and acknowledge them within 30 days. The ICO has confirmed there are no exemptions, regardless of size or industry.

10. Make sure staff understand their part. Short, practical training with a record that it happened, so people know how to spot a phishing email, handle a subject access request and recognise a breach.

11. Pay the ICO fee. Most businesses that process personal data must pay an annual data protection fee unless an exemption applies. For most SMEs this is either £52 or £78 a year, depending on size and turnover. It is a small cost and an easy thing to get right.

That is a meaningful list, but it is not an enormous one. For most SMEs, working through it is a project measured in weeks, not months, and priced accordingly. Much of it involves documenting things the business already does, closing a few specific gaps and putting simple processes around them.

Where the real risk usually sits

In practice, the gaps that cause SMEs genuine problems are rarely the absence of a policy document. They are usually operational:

  • Personal data scattered across shared drives, inboxes and old systems nobody has cleaned up
  • Former staff who still have access to systems containing customer or employee data
  • Suppliers handling personal data with no contract in place
  • No clear plan for what happens if a laptop is lost or an email account is compromised
  • Data protection complaints or subject access requests arriving with nobody sure who handles them

These are fixable, and fixing them reduces real risk. A beautifully formatted policy suite that nobody follows does not.

Proportionate does not mean casual

None of this means compliance should be ignored or treated casually. The risk is genuine. A data breach, a mishandled subject access request or a complaint that escalates to the ICO can have real commercial consequences, from regulatory action to lost customer trust to awkward questions from your cyber insurer.

Customers increasingly ask about data protection during procurement, too. A business that can answer confidently, with simple evidence to hand, wins work that a business with vague answers loses.

But there is a meaningful difference between what the law actually requires of a business your size and what a broad framework would like you to adopt. Understanding that difference is often the single most valuable piece of clarity a board can get.

Questions to ask before you sign the next quote

If you are weighing up a compliance proposal, a few questions will quickly tell you whether it is proportionate:

  • Which specific legal requirements does each part of this work address?
  • Which of these do we already meet, at least partly?
  • What is a one off project, and what genuinely needs ongoing support?
  • What would a minimum compliant position look like for a business our size, and what does each step beyond that add?
  • Will we be able to maintain this ourselves afterwards, or are we being designed into a dependency?

A good adviser, whether a lawyer, consultant or anyone else, will welcome those questions and answer them clearly.

A proportionate view

An independent, proportionate assessment of what your business genuinely needs to do, stripped of anyone’s incentive to oversell it, is a conversation worth having before the next quote lands on your desk.

This article is general information, not legal advice. Where your business has complex data processing or specific legal questions, take advice from a qualified data protection lawyer.

← All Insights
← Previous Next →

More Insights

AI & Technology

Why Banning AI Tools Does Not Work, and What Does

Banning AI tools doesn’t stop staff using them. It stops them telling you. Here’s what the evidence shows, and what a proportionate, usable AI policy looks like for an SME

20 November 2026 · 7 min read
IT Governance

What a Fractional IT Director Actually Does Month to Month

Board level IT oversight without a full time hire sounds good in principle. Here is what the work actually looks like, from month one discovery to the monthly and quarterly rhythm.

6 November 2026 · 8 min read
AI & Technology

How to Stop Staff Putting Sensitive Company Data Through AI Tools

Most businesses have not decided whether their staff should be using AI tools. Their staff have decided for them. Here is what that means for your data.

26 October 2026 · 6 min read