SaaS CRM · a buyer’s guide for the UK

A SaaS CRM is a delivery model, not a category of software

CRM describes what the software does: keep track of the people you sell to and serve, and of everything said to them. SaaS describes how you get it: the supplier runs the system, you reach it through a browser, and you pay a subscription rather than buy a licence. Putting the two words together answers a question about plumbing, not about capability. This guide covers what that plumbing changes for a British business: what you control, what you do not, what it really costs, and how to tell one platform from another without relying on anybody’s score out of ten.

Explore a SaaS CRM platform Start with the operating model

Figures dated and sourced at the foot of the page

Definitions that actually matter

Two words, two different questions

The pairing confuses buyers because it joins a function to a delivery method. Separating them makes every later decision easier.

A customer relationship management system is a place to keep people, organisations, opportunities and the history of what happened between you. That is the function. Nothing about it says where the software runs or how you pay for it. Firms ran CRM systems on a server in a cupboard for twenty years before anybody said the word cloud out loud.

Software as a service is a way of delivering that function. The supplier operates the system, applies updates on its own schedule, and charges a recurring fee for access rather than a one-off licence. You reach it over the internet, usually in a browser, and you configure it rather than install it. The trade at the centre of the model is simple: you give up control of the machinery in exchange for not having to run it.

So a SaaS CRM is a customer database delivered that way. Saying a business must choose between SaaS and CRM is like asking whether it wants a car or a lease: one is the thing, the other is how you hold it. The useful comparison is between delivery models, and that comparison has real winners and losers depending on who is asking.

Where this guide is written from

This site is paid by one platform’s partner programme, which is stated on every page. That is why it does not rank products, publish scores or quote competitor prices it has not read on the supplier’s own page. What it publishes instead are criteria, questions to ask, and figures with the date they were taken.

The operating model

What runs where, and who is answerable for it

Seven layers between a member of staff and a result. The interesting column is the third one: what stays under your control once the supplier runs the platform.

Run by the supplier
Shared
Yours to decide

The people using it

Sales, service and marketing staff working from a browser or a phone, wherever they happen to be.
Yours to decide

What stays yours
Who has an account, what each role can see, and whether leavers are removed the day they leave.

Ask the supplier
How are user permissions defined, and can I see an audit of who accessed what?
The browser and the network

No installation on a machine: the software is reached over the internet, which makes access easy and connectivity a dependency.
Shared

What stays yours
Your connectivity, your devices, your second factor. Nothing works offline unless the vendor offers it.

Ask the supplier
What happens to the mobile app and to queued messages when a connection drops?
The platform itself

One codebase serving many customers, updated by the vendor on its own schedule. This is the defining trait of the delivery model.
Run by the supplier

What stays yours
Nothing about the release cycle. You choose a tier, you configure inside it, and updates arrive whether they suit you or not.

Ask the supplier
How much notice is given before a breaking change, and is there a release note I can read?
Your records

Contacts, companies, opportunities, conversations, notes, files and the history that makes the rest useful.
Shared

What stays yours
The data is yours; the storage is not. Which is exactly why the export route matters more than the import route.

Ask the supplier
Which objects can I export, in what format, and does the export include activity history and files?
Pipelines and processes

Stages, fields, forms, calendars and the rules that move a record from one state to the next.
Yours to decide

What stays yours
Almost everything. This is where a CRM starts to look like your business rather than a demo.

Ask the supplier
What are the limits on custom fields, pipelines and record types on the tier I am buying?
Automation

Triggers, delays, conditions and actions that send a message or change a record without anyone clicking.
Yours to decide

What stays yours
The logic, and the discipline of stopping it when a human replies.

Ask the supplier
Can automations be exported or rebuilt elsewhere, and are they versioned when someone edits them?
Integrations and messaging

Connections to accounting, billing, telephony, email delivery and whatever else the business already runs.
Shared

What stays yours
The choice of tools, the credentials, and usually the usage bill for messages and calls.

Ask the supplier
Which integrations are native, which need a connector, and what is billed by usage rather than by the plan?

Read the diagram as a boundary rather than a stack. Everything above the platform line is yours to decide and yours to get wrong: who has access, how the pipeline is shaped, what the automation says. Everything at the platform line belongs to the supplier, including the release you did not ask for. The layers either side are shared, and shared is where most unpleasant surprises live, because both parties assume the other one has it covered.

Two practical consequences follow. The first is that evaluating a SaaS CRM means evaluating a supplier as much as a product: its release habits, its support, its pricing history, its willingness to answer a written question. The second is that the export route matters more than the import route. Getting data in is the supplier’s problem and it is always solved; getting data out is your problem and it is only solved if you check.

See how one platform arranges these layers

Opens GoHighLevel, one of the platforms this guide uses as an example.

The real comparison

SaaS, hosted, self-hosted, on-premise

Fourteen criteria and what each model does to them. No scores: the right answer depends on who you are, and half of these rows change places depending on the size of your IT function.

Criterion	SaaS	Hosted for you	Self-hosted	On-premise
Getting started	An account is created and you configure. Days, sometimes hours.	The vendor provisions an instance for you. Days to weeks.	You install the software on infrastructure you rent. Weeks.	You install on hardware you own or lease. Weeks to months.
Who runs the servers	The vendor, on shared infrastructure.	The vendor, on an instance dedicated to you.	You, on a cloud provider of your choosing.	You, in your own data centre or office.
Updates	Automatic, on the vendor’s schedule, for everyone at once.	Scheduled with you, usually within a window the vendor sets.	When you apply them. Skipping them becomes a security decision.	When you apply them, with a test environment if you keep one.
Money up front	Little or none beyond the first subscription period.	Setup or migration fees are common.	Licence or support contract, plus the build.	Hardware, licences and implementation before anyone logs in.
Money over time	A subscription that must be renewed for the software to keep working.	A subscription, usually higher than shared SaaS.	Hosting, maintenance and the staff time to do it.	Hardware refresh, maintenance and staff time.
Adding people	A setting, and an invoice line. Fast either way.	A contract change and sometimes a resize.	Capacity planning, then a resize you perform.	Procurement.
Working away from the office	Built in: a browser and a login.	Built in.	Depends on what you expose, and how safely.	Usually a VPN, which someone has to maintain.
How far you can bend it	Configuration within the vendor’s limits; the code is not yours to change.	Configuration, sometimes plus vendor-built extensions.	Configuration, extensions and, if the licence allows, the code.	The most freedom, and the most responsibility for what you break.
Connecting other systems	Native connectors and an API, within rate limits you do not set.	Similar, occasionally with direct database access.	Whatever you can build, including direct data access.	Whatever you can build, inside your own network.
Who is responsible for security	Shared: the vendor secures the platform, you secure accounts, permissions and what you put in it.	Shared, with more of the configuration on your side.	Mostly you: patching, backups, access, monitoring.	You, end to end, including the physical layer.
Backups and restore	The vendor backs up the platform. That is not the same as being able to restore your records to yesterday: ask.	Usually contractual, with a stated recovery objective.	Yours to design and, more importantly, to test.	Yours, including off-site copies.
Getting your data out	Whatever the export tools and API allow, which is the single most important thing to test before you commit.	Often a database extract on request.	Direct access to your own database.	Direct access.
Dependency on the supplier	High: price changes, feature removals and outages are theirs to decide and yours to absorb.	High, with more contractual room to negotiate.	Moderate: you depend on releases, not on uptime.	Lowest, and correspondingly the most work.
Leaving	Cancel, export, and hope the export contains the history. Plan this on day one, not on the last day.	Notice period, then an extract.	You already hold the data; the work is standing up the next system.	You hold everything, including the problem of decommissioning.

SaaS

Getting started
An account is created and you configure. Days, sometimes hours.
Who runs the servers
The vendor, on shared infrastructure.
Updates
Automatic, on the vendor’s schedule, for everyone at once.
Money up front
Little or none beyond the first subscription period.
Money over time
A subscription that must be renewed for the software to keep working.
Adding people
A setting, and an invoice line. Fast either way.
Working away from the office
Built in: a browser and a login.
How far you can bend it
Configuration within the vendor’s limits; the code is not yours to change.
Connecting other systems
Native connectors and an API, within rate limits you do not set.
Who is responsible for security
Shared: the vendor secures the platform, you secure accounts, permissions and what you put in it.
Backups and restore
The vendor backs up the platform. That is not the same as being able to restore your records to yesterday: ask.
Getting your data out
Whatever the export tools and API allow, which is the single most important thing to test before you commit.
Dependency on the supplier
High: price changes, feature removals and outages are theirs to decide and yours to absorb.
Leaving
Cancel, export, and hope the export contains the history. Plan this on day one, not on the last day.
Hosted for you

Getting started
The vendor provisions an instance for you. Days to weeks.
Who runs the servers
The vendor, on an instance dedicated to you.
Updates
Scheduled with you, usually within a window the vendor sets.
Money up front
Setup or migration fees are common.
Money over time
A subscription, usually higher than shared SaaS.
Adding people
A contract change and sometimes a resize.
Working away from the office
Built in.
How far you can bend it
Configuration, sometimes plus vendor-built extensions.
Connecting other systems
Similar, occasionally with direct database access.
Who is responsible for security
Shared, with more of the configuration on your side.
Backups and restore
Usually contractual, with a stated recovery objective.
Getting your data out
Often a database extract on request.
Dependency on the supplier
High, with more contractual room to negotiate.
Leaving
Notice period, then an extract.
Self-hosted

Getting started
You install the software on infrastructure you rent. Weeks.
Who runs the servers
You, on a cloud provider of your choosing.
Updates
When you apply them. Skipping them becomes a security decision.
Money up front
Licence or support contract, plus the build.
Money over time
Hosting, maintenance and the staff time to do it.
Adding people
Capacity planning, then a resize you perform.
Working away from the office
Depends on what you expose, and how safely.
How far you can bend it
Configuration, extensions and, if the licence allows, the code.
Connecting other systems
Whatever you can build, including direct data access.
Who is responsible for security
Mostly you: patching, backups, access, monitoring.
Backups and restore
Yours to design and, more importantly, to test.
Getting your data out
Direct access to your own database.
Dependency on the supplier
Moderate: you depend on releases, not on uptime.
Leaving
You already hold the data; the work is standing up the next system.
On-premise

Getting started
You install on hardware you own or lease. Weeks to months.
Who runs the servers
You, in your own data centre or office.
Updates
When you apply them, with a test environment if you keep one.
Money up front
Hardware, licences and implementation before anyone logs in.
Money over time
Hardware refresh, maintenance and staff time.
Adding people
Procurement.
Working away from the office
Usually a VPN, which someone has to maintain.
How far you can bend it
The most freedom, and the most responsibility for what you break.
Connecting other systems
Whatever you can build, inside your own network.
Who is responsible for security
You, end to end, including the physical layer.
Backups and restore
Yours, including off-site copies.
Getting your data out
Direct access.
Dependency on the supplier
Lowest, and correspondingly the most work.
Leaving
You hold everything, including the problem of decommissioning.

Most British small and medium businesses land on SaaS for the same three reasons: nobody has to patch anything, the cost is an operating expense rather than a capital one, and staff can work from anywhere without a VPN. Those are real advantages and they are worth the trade for a great many firms.

The reasons to land somewhere else are equally real. A regulated business with a specific data location requirement, an organisation with heavy bespoke integration into systems it owns, or a firm with enough in-house capability that running the software is cheaper than renting it: all three have a defensible case for the other columns. Anyone who tells you the answer before asking about your constraints is selling, not advising.

On the word cloud

Cloud CRM and SaaS CRM are used interchangeably in most marketing, and for the common case they describe the same arrangement. They are not strictly synonymous: software can run in a cloud without being sold as a service, for instance when a firm installs a CRM on infrastructure it rents and manages itself. When a supplier says cloud, the question worth asking is whether the instance is shared, dedicated, or simply yours to run.

Money

Pricing models, and the costs that sit outside the plan

The headline figure is a licence to compare. It is rarely what the arrangement costs a year in.

Per user, per month
The common model. Cost grows with headcount, which is predictable but punishes giving read-only access to people who only need to look.
Ask whether inactive or read-only users are chargeable.
Flat rate per account
One price whatever the number of users. Attractive for teams that grow, and less so for a single operator.
Check what is metered instead: contacts, messages, storage.
Tiered by feature
The capability you actually need often sits one tier above the price you were quoted.
Write down your three must-have features, then find the cheapest tier that contains all three.
Usage-based elements
Telephony, text messages, email volume and sometimes automation runs are billed on consumption, separately from the plan.
Estimate a normal month before signing, and a busy one.
Add-ons
Extra pipelines, extra storage, a second brand, an integration connector: individually small, collectively a second subscription.
Ask for the full price list, not the plan page.
Annual commitment
A discount in exchange for the flexibility you may need if the platform turns out to be the wrong choice.
Take the monthly price for the first period unless the discount is large and the fit is proven.

Comparing platforms on their headline price alone produces the wrong answer surprisingly often, because the models are not comparable. A per-seat price of twenty pounds and a flat price of two hundred are the same money at ten users and very different money at three, or at thirty. Work out the cost at the size you will be in eighteen months, not the size you are today.

The subscription itself, at the tier that contains your must-have features.
Implementation: the hours someone spends configuring pipelines, fields, templates and permissions.
Data migration, including the cleaning that nobody budgets for.
Integrations, whether a connector subscription or developer time.
Usage: messages, calls, email volume, storage.
Training, and the second round of training six months later.
Support tiers, if the included one has a response time you cannot live with.
The cost of leaving: exporting, rebuilding automations elsewhere, and running two systems during the changeover.

This guide publishes no savings calculation, and you should be wary of any that you read. A figure like “businesses save forty per cent by consolidating tools” has to assume which tools you already pay for, at which tier, with which usage. Nobody writing a web page knows that. What you can do honestly is list your current subscriptions, mark the ones a single platform would genuinely replace, and compare that total with the tier that contains your must-have features.

The only prices on this site

One supplier’s published prices appear further down, with the date they were read and a link to the page they came from. No other platform’s prices are reproduced here, because they were not read at source. A price quoted second hand is a rumour with a currency symbol in front of it, and implementation fees quoted that way are worse.

Selection

What to compare, and the question that settles each one

Sixteen criteria in four groups. Each one carries the question to put to a supplier, because a demonstration answers the question you ask, not the one you meant.

Records and the shape of your business

A CRM that cannot represent how you actually sell will be worked around within a month.

Contacts, companies and the link between them
Business-to-business work falls apart when a contact cannot belong to an organisation, or when one person sits at two.

Can one contact belong to several companies, and what happens to history when they move?
Custom fields and record types
Every business has two or three fields that decide everything. If they live in a notes box, reporting is guesswork.

How many custom fields does my tier allow, and can I report on them?
Pipelines and stages
Stages should be named after what happened, not after how it feels. Several pipelines are normal once you sell more than one thing.

How many pipelines can I have, and can a record move between them without losing its history?
Duplicates and merging
Imports create duplicates. What matters is how easily you find and merge them afterwards.

Does the system detect duplicates on import, and is merging reversible?

Doing the work

The daily use decides adoption. A system nobody opens is an expensive spreadsheet with a login screen.

Conversations in one place
Email, calls and messages attached to the record are the main reason people stop searching four inboxes.

Which channels land on the record automatically, and which need a manual copy?
Calendars and booking
Appointment-driven businesses live here: availability, confirmations, reminders and what happens on a cancellation.

Does booking respect working hours, buffers and time zones without manual fixes?
Tasks and ownership
Follow-up fails when nobody owns it. Ownership plus a due date is most of what a CRM is for.

Can I see, in one view, everything overdue across the team?
Mobile use
Trades, field sales and service teams do not carry a laptop to a site visit.

What can be done from a phone, and what silently requires the desktop version?

Automation and reporting

Automation multiplies whatever process you already have, good or bad. Reporting is how you find out which it was.

Triggers and stop conditions
An automation that keeps sending after a customer replies does more damage than no automation at all.

How do I stop a sequence on a reply, and can I see every automation a record has entered?
Templates and personalisation
Merge fields fail loudly. Test them with awkward records: no surname, two phone numbers, an apostrophe.

What does a message look like when a merge field is empty?
Reporting you can defend
A dashboard is only useful if you can explain where each number comes from and reproduce it.

Can I export the underlying rows behind any figure on a dashboard?
Deliverability settings
Sending from a shared domain without authentication is how a legitimate campaign ends in spam folders.

What domain authentication does the platform require, and who fixes it when reputation drops?

Administration, security and the exit

The parts that never feature in a demonstration, and that decide the third year.

Roles and permissions
Not everyone should see every deal, every price and every phone number.

Can permissions be set per pipeline, per field and per record owner?
Audit and accountability
UK data protection law asks you to demonstrate compliance, not merely to claim it.

Is there a log of exports, deletions and permission changes, and can I read it?
Data export and portability
The export is the only guarantee that the relationship is a subscription rather than a hostage situation.

Can I export contacts, companies, opportunities, notes, conversations and files, and how long does a full export take?
Support and onboarding
A platform with more depth needs more help at the start; a simpler one may need none.

What is included at my tier, and what is charged separately?

A practical way to use this list: pick the four criteria that would make you cancel in month three if they went wrong, and test only those in a trial. Testing everything produces a tour; testing four things produces an opinion. Use your own records while you do it, because a workspace full of tidy sample data behaves impeccably and tells you nothing.

Test these criteria in a live account

A trial account is the only place where these questions get answered honestly.

Portability

Getting your data out, and what lock-in actually looks like

Vendor lock-in is rarely a clause in a contract. It is usually the accumulated cost of rebuilding what you configured.

Three things tie a business to a platform. The records, which are usually exportable. The history, which often is not, or not completely. And the configuration: the pipelines, the fields, the templates and above all the automations, which no export format carries and which have to be rebuilt by hand wherever you go next. The third is the expensive one, and it is invisible when you sign.

Can I export contacts and companies, with their custom fields, myself and without asking support?
Does the export include activity history: emails, calls, notes, stage changes and dates?
Are uploaded files and attachments included, or only their file names?
What happens to the data when the subscription ends, and for how long is it retrievable?
Can automations and templates be exported in any form, or are they rebuilt by hand elsewhere?
Is there an API, and what are its rate limits for a full extraction?
Are integrations portable, or does each one have to be reconnected from scratch?
Who signs the data processing terms, and where is the processing carried out?

Ask these before you commit, and ask them in writing. A supplier that answers plainly is telling you something about how it will behave when you want to leave; a supplier that redirects you to a sales call is also telling you something. Then, during the trial, actually run an export and open the file. The gap between “data can be exported” and “the export contains what you need” is where unpleasant discoveries live.

A reasonable test

Export your contacts in week one, before you have any real data in the system. It takes ten minutes and it tells you what the exit looks like while leaving costs nothing.

Data protection

Security, UK GDPR and where the responsibility sits

A CRM holds personal data by definition. That puts obligations on you, not only on your supplier, and no product can be bought that discharges them.

Under UK data protection law, the business deciding why and how personal data is processed is the controller, and a SaaS supplier processing that data on its instructions is a processor. Choosing a platform does not move the accountability: the controller has to be able to demonstrate compliance, which is a documentation exercise as much as a technical one.

The controller shall be responsible for, and be able to demonstrate compliance with, paragraph 1 (‘accountability’).
Information Commissioner’s Office · ico.org.uk/for-organisations/uk-gdpr-guidance-and-resources/data-protection-principles/a-guide-to-the-data-protection-principles · read on 2026-09-22 · source 06

In practice that means knowing what a platform stores, for how long, who can see it and what happens when someone asks for a copy or for deletion. The seven principles set out by the Information Commissioner’s Office, from lawfulness through to accountability, are a workable checklist for a CRM configuration review, and storage limitation in particular is the one CRMs fail: they accumulate.

Where the processing happens is a separate question, and it has become a practical one for SaaS buyers. If personal data goes to an organisation outside the United Kingdom, the transfer has to be covered by a recognised mechanism, and relying on safeguards brings an assessment with it.

You must also ensure that you have completed a transfer risk assessment (TRA). […] If you cannot rely on UK adequacy regulations, appropriate safeguards or an exception, you must not make the transfer.
Information Commissioner’s Office · ico.org.uk/for-organisations/uk-gdpr-guidance-and-resources/international-transfers/international-transfers-a-guide · read on 2026-09-22 · source 07

What a guide cannot tell you

No website can declare a platform “GDPR compliant” on your behalf. Compliance depends on your configuration, your retention rules, your contracts with the supplier and its subprocessors, and what your staff actually do. Ask the supplier for its data processing terms and its list of subprocessors, and read the retention section before the feature list.

Fit

Which shape of business gets the most from this model

The delivery model suits some situations far better than others, and the difference is rarely about industry.

A founder and a spreadsheet
Under about ten live opportunities, a shared calendar and a disciplined inbox genuinely compete with a CRM. What tips the balance is not volume but handover: the moment a second person has to know what was promised.
A small team that sells and delivers
Two to ten people, one pipeline, quotes that need chasing. Here a SaaS CRM earns its subscription quickly, mostly by making follow-up somebody’s job rather than somebody’s memory.
A growing team with specialisms
Separate sales and service, several pipelines, reporting that leadership reads. Permissions, duplicate control and export start to matter as much as features.
A larger organisation
Procurement, security review, integration with finance systems and a formal contract. The questions change from “can it do this?” to “who is accountable when it cannot?”, which is a contract question before it is a software one.

One pattern runs through all four: a SaaS CRM pays for itself when work has to be handed over. Between people, between weeks, between someone leaving and someone joining. If every customer conversation lives in one head and always will, the software is solving a problem you do not have.

See whether this shape of platform fits your team

Thirty days through the partner link, fourteen on the public pricing page.

One platform, examined

Where GoHighLevel fits, and where something else is better

This site is paid by this supplier’s partner programme. That is precisely why the second list exists and is as specific as the first.

Contacts, opportunities and pipelines in one place
The core CRM objects are documented, with pipelines you define rather than inherit.
Documented in Opportunities & Pipelines
Automation with triggers and actions
A visual builder with triggers across CRM events, appointments and payments, which is the part most single-purpose CRMs leave to a separate tool.
Documented in Workflows
Communication in the same workspace
Email, calls and messages attached to the record, with usage billed separately from the plan.
Documented in HighLevel: Pricing
Several client accounts under one roof
Sub-accounts and white-label resale are documented parts of the product, which is unusual outside agency-oriented platforms.
Documented in SaaS Configurator

When the requirement is depth in one discipline
A dedicated service desk, a dedicated marketing automation suite or a dedicated accounting integration will go deeper than a platform that covers all three.
When procurement asks for a specific certification or data location
Those requirements are answered by the vendor in writing, not by a guide. Ask before you build.
When the team is one person with ten customers
Breadth costs configuration time. A calendar, a shared inbox and a simple pipeline may serve better until the volume justifies more.
When you need to own the software
A SaaS product is not self-hosted. If the requirement is running the system inside your own infrastructure, this is the wrong shape of product entirely.

GoHighLevel is a broad platform: customer records and pipelines, messaging, calendars, pages and forms, and an automation builder connecting them. For a business whose problem is fragmentation, several subscriptions doing adjacent jobs badly, that breadth is the point. For a business whose problem is depth in one discipline, the same breadth is a distraction.

Starter97 USD per month
Unlimited297 USD per month
Agency Pro497 USD per month

Enterprise is quoted on request and has no public price. Prices as published on gohighlevel.com/pricing, read on 2026-09-22. Messaging and telephony usage is billed on top.

Those are the supplier’s published prices in US dollars, read on the date shown, and they are the only platform prices on this site. Messaging and telephony are billed on usage on top, and the public page says the free trial runs 14 days. The partner link on this page opens 30 days with the HighLevel Bootcamp included, a length confirmed by the holder of the partner account rather than read on a public page; both figures are given so you can see which is which.

Open a trial account and run the four tests

The criteria above are answered in an account, not on a comparison page.

Decision

A short way to decide

Four questions, in order. If the first two have no answer, the rest is shopping.

First: what breaks today? Name the failure in one sentence, with a cost attached. Quotes go unanswered for a fortnight. Nobody knows who called back. Two people ring the same customer. If no sentence comes, a CRM will be a tidy place to store an unsolved problem.

Second: who will own it? Not the software, the process. Somebody has to decide what a stage means and hold people to it. Systems fail for want of that person far more often than for want of a feature.

Third: what would make you cancel? Write down four things, then test only those during a trial, with your own data. Fourth: what does leaving look like? Run an export in the first week. A platform you can leave is a platform you can commit to.

If a platform clears those four, the remaining question is commercial rather than technical: the tier that holds your must-have features, the usage you will genuinely incur, and whether the total replaces subscriptions you already pay or simply adds to them.

Start the four tests on a live platform

Free for the trial period; billing starts at the end unless cancelled.

Direct answers

Questions buyers ask

What is a SaaS CRM in plain English?

A customer database run by a supplier and reached through a browser, paid for by subscription. CRM is what it does; SaaS is how you get it. The alternative is not “a CRM without SaaS” but the same function delivered differently: hosted for you, self-hosted by you, or installed on your own hardware.

Is cloud CRM the same as SaaS CRM?

In everyday use, yes, and most suppliers use the words interchangeably. Strictly they are not identical: software can run in a cloud without being sold as a service, for example when you install a CRM on rented infrastructure and manage it yourself. If precision matters, ask whether the instance is shared, dedicated, or yours to run.

Is SaaS always cheaper than on-premise?

No. It is cheaper to start and it converts a capital cost into a recurring one, which suits most small and medium businesses. Over a long horizon, with stable requirements and in-house capability, the arithmetic can favour running the software yourself. The honest answer depends on headcount, growth and who would maintain it.

What does a SaaS CRM actually cost?

Plan price, plus usage such as messages and calls, plus implementation time, plus integrations, plus whatever you keep running alongside. This site publishes one supplier’s prices with a date and a source, and no estimates for anyone else, because unverified price comparisons are how buyers end up with the wrong shortlist.

How do I compare platforms without scores?

Pick the four things that would make you cancel in month three, then test only those with your own records. Scores out of ten aggregate criteria you do not weight the same way as the person who wrote them, which is why this guide replaced its own scoring table with criteria and questions.

What is vendor lock-in, concretely?

Mostly the configuration. Records usually export; history sometimes does; pipelines, templates and automations almost never do, and rebuilding them is the real cost of moving. That is why exporting once in the first week, while it costs nothing, is worth more than any promise about portability.

Does a SaaS CRM make my business GDPR compliant?

No, and no supplier can sell you compliance. You remain the controller: you decide what to collect, how long to keep it and who may see it, and you must be able to demonstrate that. A platform can make it easier with permissions, retention settings and an audit trail; the accountability stays with you.

Where is my data held?

That depends on the supplier, and it is a fair question to ask in writing before signing. If personal data leaves the United Kingdom, the transfer must be covered by a recognised mechanism, and relying on safeguards requires a transfer risk assessment. The supplier should be able to tell you where processing happens and who its subprocessors are.

How long does implementation take?

This guide publishes no setup time, because it would be invented. What can be said usefully is the order that shortens the work: contacts first, then the stages you already use on paper, then one communication channel, then one automation. Businesses that try to build everything at once usually finish nothing.

Do I need a CRM at all?

If you sell in a single conversation, keep no list and never hand a customer over, probably not. A shared calendar and a disciplined inbox are a reasonable system at that size. The moment somebody other than you needs to know what was promised, the answer changes.

What is this site, and how is it paid?

A guide written outside the companies it discusses, paid by one of them: the links to GoHighLevel are paid, and a commission is earned if you subscribe. That is stated in the footer of every page. It is also why this version quotes suppliers with dates instead of scoring them.

Why does this guide not rank the platforms?

Because a ranking is a measurement, and this guide has no measurement to publish. A score out of ten aggregates criteria the reader does not weight the way the author does, and a table of ticks hides the question that decides each row. Criteria with the question to ask are slower to read and you can actually apply them.

Sources

Every figure on this page, and where it came from

Each page below was opened and read on the date shown. Nothing on this site is quoted from memory or from another article.

01
HighLevel: Pricing

HighLevel · gohighlevel.com/pricing · read on 2026-09-22

“14 Day Free Trial”. Starter $97/Month, Unlimited $297/Month, Agency Pro $497/Month, Enterprise on request. “HighLevel operates on a month-to-month basis. There are no long-term contracts, and you can upgrade, downgrade, or cancel your account at any time directly from your dashboard.” “Billing begins automatically at the end of any free trial unless canceled, and usage-based fees for telecommunications or third-party services may apply during the trial.”
02
HighLevel Support Portal: solution categories

HighLevel Help Center · help.gohighlevel.com/support/solutions · read on 2026-09-22

Official list of help categories, including Contacts, CRM, Conversations, Opportunities & Pipelines, Workflows, Calendars & Appointments, Phone System, Email, Sites, Marketing, Reporting, Account Snapshots, SaaS Configurator, Integrations, Compliance.
03
Workflows

HighLevel Help Center · help.gohighlevel.com/support/solutions/48000455132 · read on 2026-09-22

“Introduction to Workflows and Automations”, “Workflow Builder”, “Workflow Triggers” (CRM, Events, Appointments, Courses, Payments), “Workflow Actions”.
04
Opportunities & Pipelines

HighLevel Help Center · help.gohighlevel.com/support/solutions/48000449589 · read on 2026-09-22

Help category covering opportunities and pipelines.
05
SaaS Configurator

HighLevel Help Center · help.gohighlevel.com/support/solutions/48000453216 · read on 2026-09-22

Help category covering white-label resale and sub-account configuration.
06
A guide to the data protection principles

Information Commissioner’s Office · ico.org.uk/for-organisations/uk-gdpr-guidance-and-resources/data-protection-principles/a-guide-to-the-data-protection-principles · read on 2026-09-22

Seven principles: lawfulness, fairness and transparency; purpose limitation; data minimisation; accuracy; storage limitation; integrity and confidentiality (security); accountability. Article 5(2): “The controller shall be responsible for, and be able to demonstrate compliance with, paragraph 1 (‘accountability’).”
07
International transfers: a guide

Information Commissioner’s Office · ico.org.uk/for-organisations/uk-gdpr-guidance-and-resources/international-transfers/international-transfers-a-guide · read on 2026-09-22

A restricted transfer occurs when “the UK GDPR applies to your processing of the personal information you are sending”, “you’re initiating the transfer of personal information to an organisation outside of the UK” and “the organisation receiving the information is a separate legal entity to you”. Such a transfer “must be covered by one of the following transfer mechanisms”: UK adequacy regulations, appropriate safeguards, or an exception. When relying on safeguards you “must also ensure that you have completed a transfer risk assessment (TRA)”. If none applies, you “must not make the transfer”.