Sales CRM · a guide for UK sales teams

Sales CRM for UK sales teams: from first lead to signed customer

See how GoHighLevel handles a sales pipeline

What a sales CRM does at each stage of the pipeline, how to organise follow-up and forecasting, when a spreadsheet is still enough, what the main platforms publish as prices, and where GoHighLevel fits and where it does not.

Through this site’s partner link: 30 days with the HighLevel Bootcamp, as confirmed by the partner account holder. Public pricing page: 14 days (gohighlevel.com/pricing, read 22 September 2026). The terms shown at sign-up apply.

Illustration of a pipeline board: every card has an owner, a next action and a date, and the one without is the one to fix. A drawing, not a screenshot of any software.

Six questions a sales CRM should answer for every deal

01Where is my lead?Lead capture and source
02What happens next?Stages and entry rules
03Who owns it?Assignment and handover
04When do we follow up?Next actions and reminders
05What is it worth?Deal value and close date
06What is likely to close?Weighted pipeline

Start here

What a sales CRM is, and what it is not

CRM (customer relationship management) is a broad category. A sales CRM is the same kind of software used with one focus: moving leads through a pipeline to a signed deal, with every follow-up on record. It is a use of CRM, not a separate technology.

A working definition

One place that answers six questions about every deal.

A sales CRM is a shared database of the people and organisations you sell to, organised around deals. Each lead has a record. Each deal (usually called an opportunity) has a value, a stage, an owner, an expected close date and a next action. Every call, email, meeting and note is logged against the person and the deal it belongs to.

On a normal working day, that structure has to answer six questions without anyone opening a spreadsheet or asking a colleague: where is this lead, what happens next, who owns it, when do we follow up, what is it worth, and what is likely to close this month. If your current set-up cannot answer those quickly, that is the gap a sales CRM is meant to fill.

The records a sales CRM keeps, and what each is for
Record	What it holds	Why sales needs it
Lead	A person or company that has shown interest or fits your target, not yet qualified	So new interest is captured once, with its source, and handed to someone
Contact	A named person: role, email, phone, consent and communication preferences	So every rep sees the same history with that person
Company (account)	The organisation: sector, size, address, all its contacts and deals	B2B deals are bought by organisations with several people involved
Opportunity (deal)	A potential sale: value, stage, close date, owner, next action, status	This is what the pipeline and the forecast are built from
Activity	Calls, emails, meetings, messages, notes, with dates	So “when did we last speak to them?” has an answer
Task	A dated action assigned to a person	So a follow-up exists as something due, not as an intention

CRM and sales CRM: what changes

Same software category, different emphasis.

Most CRM platforms can be used for sales, service, marketing or account management. Calling one a “sales CRM” says where the emphasis sits. A sales-focused set-up puts the pipeline at the centre and cares most about:

Leads and prospects: capturing them with their source, and qualifying them consistently.
Opportunities and pipeline: deals with a value, a stage and a date, visible on one board.
Sales activities and follow-ups: every open deal has a next action with a due date and an owner.
Deals and outcomes: won, lost or abandoned, with a reason.
Forecasting and sales reporting: what is likely to close, and how the team is doing against it.

A service-focused CRM puts tickets and response times first; a marketing-focused one puts segments and campaigns first. Many products do all three, which is why the label matters less than how you set it up. The map of neighbouring tools further down explains where a CRM ends and a helpdesk, a marketing automation tool or an ERP begins.

Why sales teams use one

Rewritten from the original FAQ “Why do sales teams use CRM software?”

While a team is small, the pipeline lives in people’s heads, inboxes and a spreadsheet, and that can work. It stops working at predictable points: when a second or third rep joins and leads get worked twice or not at all; when a rep leaves and their deals leave with them; when the manager needs a forecast and has to collect it by message; when follow-ups depend on someone remembering.

A CRM does not fix those problems on its own. It gives the team one agreed place to record things and a set of rules (required fields, stages, tasks, automations) that make the right behaviour the easy one. The value comes from the team using it consistently. A CRM that reps do not update is a more expensive spreadsheet.

The problem

Where deals leak in a sales team’s working week

Most sales teams do not lack leads so much as a reliable way of working them. These are the usual leaks, where each sits in the pipeline, what a CRM can put structure around, and what remains a management job.

Twelve common leaks

Count how many apply to your team before you look at any software.

Lead

01Leads scattered across inboxes and lists

What happens
Web enquiries go to a shared inbox, event lists sit in a download folder, referrals arrive by text. Nobody sees all of them.

What a CRM can structure
Forms and imports create records in one place, each with its source and an owner.

Still your job
Deciding which sources are worth entering at all, and who owns each one.
Lead

02Enquiries with no reply

What happens
An inbound lead arrives out of hours or while the rep is away and waits until someone notices.

What a CRM can structure
An acknowledgement goes out automatically and a first-contact task lands in someone’s queue.

Still your job
Actually calling back. An automatic email is a receipt, not a conversation.
Qualify

03Different reps, different definitions of “qualified”

What happens
One rep opens a deal after a friendly call, another only after a budget conversation. The pipeline mixes both.

What a CRM can structure
Required fields for moving a lead into a deal: need, decision maker, timing.

Still your job
Agreeing the definition, and coaching reps to use it.
Lead

04The same prospect worked twice

What happens
Two reps contact the same company from different lists, or a lead contacted last month is called again cold.

What a CRM can structure
Duplicate checks on email and company, and an activity history visible to everyone.

Still your job
Rules for ownership disputes and for merging records.
Follow-up

05Follow-ups that depend on memory

What happens
A proposal goes out, the buyer goes quiet, and nobody chases because nobody set a reminder.

What a CRM can structure
Every open deal carries a next action with a date; a rule creates a task when a deal has been quiet too long.

Still your job
Deciding what a good follow-up says. Chasing for the sake of it annoys buyers.
Opportunity

06Deals with no value or no date

What happens
The board is full of cards, but half have no amount and no expected close date, so nobody can say what the pipeline is worth.

What a CRM can structure
Value and close date required from a given stage onwards; a report of deals missing them.

Still your job
Making reps estimate honestly rather than type a placeholder.
Negotiation

07Stalled opportunities

What happens
A deal sits in “Negotiation” for months because moving it to lost feels like admitting defeat.

What a CRM can structure
A view of deals whose stage has not changed in N days, and a lost reason when they are closed.

Still your job
Having the conversation in the pipeline review, and letting deals go.
Closed won / lost

08Nobody knows why deals are lost

What happens
Lost deals simply disappear from the board.

What a CRM can structure
A required lost reason from a short list, and a report on it.

Still your job
Choosing reasons that are useful (price, timing, competitor, no decision) and acting on them.
Proposal

09Manual pipeline reporting

What happens
Every Friday the manager asks each rep for an update and merges spreadsheets. By Tuesday it is out of date.

What a CRM can structure
Pipeline and activity reports read straight from the records.

Still your job
Keeping the records current, which is what makes the report true.
Follow-up

10Repetitive admin

What happens
Reps retype the same follow-up email, book meetings by email ping-pong, copy details between tools.

What a CRM can structure
Templates, booking links, automatic logging of emails and calls, simple workflows.

Still your job
Keeping templates personal enough to be worth reading.
Customer

11Poor handover between people

What happens
A rep leaves or a won deal goes to delivery, and the context stays in someone’s inbox.

What a CRM can structure
The whole history on the account; ownership reassigned in one step.

Still your job
A handover routine: a call, a note, an introduction.
Negotiation

12Managers without visibility

What happens
The manager learns a big deal has slipped when the month closes.

What a CRM can structure
Dashboards by stage, owner and close date; alerts on value or date changes you care about.

Still your job
Using the visibility to help, not to micromanage.

If three or more of these describe your team, the pipeline chapter shows where each one is handled, stage by stage. If only one or two apply, a better spreadsheet may be enough for now: see CRM versus spreadsheet.

Next step

GoHighLevel is a CRM and automation platform this site is funded to recommend; see where it fits and where it does not.

See whether it fits your sales process

The core

The sales pipeline, stage by stage

A pipeline is a set of stages a deal moves through, from first interest to signed customer. What matters is not the number of stages but that each has a clear entry rule, the data it needs, and a next action. Here is one workable structure, and what the CRM does at each step.

Eight stages, one question each

An example structure. Rename the stages to match how your buyers actually buy.

01

Lead

Where is my lead?
Enters this stage whenSomeone has shown interest or matches your target: a form, a call, a referral, an event list, a reply to outreach.
- Name, company, role
- Lead source
- Date created
- Owner
What the CRM does
Creates one record per person, links it to their company, stores where it came from and stops the same lead being worked twice.

What can be automated
Create the record from a form; assign an owner; send an acknowledgement; create a first-contact task.

What the manager sees
New leads by source and by owner; leads with no first contact yet.
02

Qualify

Is it worth pursuing?
Enters this stage whenA first conversation has happened, or you have enough information to judge fit.
- Need or problem
- Budget range or buying process
- Decision maker
- Timing
- Disqualification reason
What the CRM does
Holds the answers to your qualification questions in fields, so “qualified” means the same thing for every rep.

What can be automated
Move to the next stage when required fields are filled; tag and park leads that are not ready yet.

What the manager sees
How many leads qualify, from which sources, and why the rest do not.
03

Opportunity

What is it worth?
Enters this stage whenA qualified buyer with a need you can meet and a plausible timeframe. A deal record is opened.
- Deal value
- Expected close date
- Stage
- Owner
- Next action and its date
What the CRM does
Puts the deal on the pipeline board with a value and a close date, linked to the contact and the company.

What can be automated
Create an opportunity when a discovery call is booked; notify the owner; set a default next-action task.

What the manager sees
Pipeline value by stage and owner; deals with no value or no close date.
04

Follow-up

When do we follow up?
Enters this stage whenEvery open deal, at every stage. Follow-up is not a stage you pass through but a rule that runs underneath all of them.
- Next action
- Due date
- Last activity date
- Channel used
What the CRM does
Keeps one task queue per rep and one activity history per deal, so a quiet deal is visible rather than forgotten.

What can be automated
Create a task when a deal has had no activity for a set number of days; remind the owner before a due date.

What the manager sees
Overdue tasks, deals without a next action, deals with no activity in N days.
05

Proposal

What have we offered?
Enters this stage whenA quote or proposal has been sent.
- Quote or proposal sent date
- Amount quoted
- Version
- Decision date
What the CRM does
Stores what was sent and when, and keeps the deal value in line with the quote.

What can be automated
Remind the owner a few days after sending; flag proposals past their decision date.

What the manager sees
Proposals out, their total value, and which are past their decision date.
06

Negotiation

What is likely to close?
Enters this stage whenThe buyer is discussing terms, price, scope or contract.
- Open points
- Revised value
- Revised close date
- Forecast category
What the CRM does
Keeps the revised value and date current, which is what the forecast is built from.

What can be automated
Alert a manager when a discount or value change passes a threshold you set.

What the manager sees
Deals likely to close this period, and those whose close date keeps moving.
07

Closed won / lost

Why did we win or lose?
Enters this stage whenThe buyer has signed, said no, or gone silent past the point you set for abandoning a deal.
- Status: won, lost or abandoned
- Lost reason
- Final value
- Close date
What the CRM does
Records the outcome and the reason, so win and loss patterns can be read later instead of guessed.

What can be automated
On won: hand over to onboarding or delivery. On lost: schedule a check-in months later if the reason allows it.

What the manager sees
Won and lost value, lost reasons, conversion from each stage.
08

Customer

Who owns it now?
Enters this stage whenThe deal is won. The relationship continues: delivery, renewal, expansion, referrals.
- Account owner
- Start or renewal date
- Products bought
- Next review date
What the CRM does
Keeps the whole sales history on the account for whoever looks after the customer next.

What can be automated
Start a renewal task before the renewal date; send a review or referral request after delivery, where consent allows.

What the manager sees
Renewals due, accounts without an owner, upsell opportunities opened.

An example pipeline in eight steps, from first interest to customer. A diagram of a sales process, not a software screen.

Designing your own stages

Stages should describe what the buyer has done, not what the rep hopes.

Name stages after verifiable events. “Discovery call held” and “Proposal sent” can be checked; “Interested” and “Warm” cannot.
Keep them few. Five to seven open stages is common. Too many and reps stop moving cards; too few and the board says nothing.
Write the entry rule down. One sentence per stage, agreed by the team, pinned where reps can see it.
Require data at the right moment. Value and close date when the deal is opened; lost reason when it is closed. Asking for everything up front leads to placeholder data.
Run separate pipelines for different motions. New business, renewals and partner deals move differently. Mixing them makes the numbers meaningless.

In GoHighLevel, for example, stages are yours to define and a pipeline can hold leads, deals or customers^[1]; each opportunity carries a value, a source, a stage and an owner, and can be marked open, won, lost or abandoned, with a lost reason^[2]^[3]. Other sales CRMs use similar building blocks under different names.

The vocabulary a sales team needs to share

Most pipeline arguments are really arguments about definitions.

Lead: Someone who has shown interest or fits your target, not yet qualified. Some teams call qualified leads “prospects”.
Lead source: Where the lead came from: website form, referral, event, outbound list, partner. Recorded once, at creation, or it is lost.
Qualification: The check that a lead has a need you can meet, someone who can decide, and a plausible timeframe. Frameworks such as BANT (budget, authority, need, timing) are one way to write it down.
Opportunity: A qualified potential sale, with a value and an expected close date. Many CRMs call it a deal.
Pipeline stage: A step in your sales process with a clear entry rule.
Deal value: The amount you expect to invoice if the deal is won. Decide whether it means first-year value, contract value or monthly recurring value, and use one meaning everywhere.
Close date: When you expect the buyer to decide. Not when you would like them to.
Probability: The chance a deal at a given stage is won, set by your team and ideally checked against your own history. Used to weight the pipeline.
Next action: The single next thing that moves the deal forward, with a date and an owner.
Sales activity: A logged call, email, meeting or message. Activity counts measure effort, not results.
Stalled opportunity: An open deal with no stage change or activity for longer than your rule allows.
Conversion: The share of records that move from one stage to the next, or from lead to won. Only meaningful from your own data over time.

Next step

Stages, values and statuses as described above are all configurable in GoHighLevel^[1]; a trial is the place to check the fit before any real prospect data goes in.

Build this pipeline in a trial account

Keeping deals moving

Follow-up and sales automation: triggers, actions and limits

Every automation is a rule: when something happens (the trigger), do something (the action), provided a condition holds. Written that way, it is easy to see which automations help a sales team and which ones just send more email.

Nine automations worth considering

Each with its trigger, its action and what to check before switching it on.

Rule 01

Lead assignment

WhenA new lead is created from a form, import or integration.

ThenAssign an owner by territory, source or rotation, and notify them.

Check firstWhat happens when the owner is on leave. Round robin without cover rules strands leads.
Rule 02

First-contact task

WhenA lead is assigned.

ThenCreate a call task due the same working day.

Check firstWhether the task queue is actually used. Tasks nobody opens are noise.
Rule 03

Enquiry acknowledgement

WhenA form is submitted.

ThenSend a short email or text confirming receipt and saying when someone will be in touch.

Check firstThat it promises only what the team can deliver. Texts to sole traders and consumers need a lawful basis under PECR (see below).
Rule 04

Follow-up reminder

WhenA deal has had no logged activity for N days.

ThenCreate a task for the owner; after a second interval, notify the manager.

Check firstThat N matches your sales cycle. Five days can be too short for an enterprise deal and too long for an inbound quote.
Rule 05

Proposal chase

WhenA deal enters “Proposal sent”.

ThenSchedule a task a few days later to call, not just email.

Check firstThat the task can be closed when the buyer replies first.
Rule 06

Appointment reminders

WhenA discovery call or demo is booked through a booking link.

ThenConfirm the booking, then remind the prospect before the call.

Check firstTime zones, and a reschedule link in every reminder.
Rule 07

Pipeline update on an event

WhenA meeting is booked, a form is signed, a payment arrives.

ThenMove the deal to the matching stage.

Check firstThat only verifiable events move deals automatically. Reps still own judgement calls.
Rule 08

Email sequence for nurturing

WhenA lead is marked “not ready yet” with a reason.

ThenSend a small number of useful messages over weeks, and stop on reply.

Check firstConsent and opt-out, and a stop condition on any reply or booking.
Rule 09

Re-engagement of lost deals

WhenA deal was lost for “timing” N months ago.

ThenCreate a task to check in, or send one message.

Check firstThat the reason was timing, not “not interested”, and that the person has not opted out.

In GoHighLevel these follow the documented model of a trigger followed by actions^[4]. Triggers include form submissions, bookings and replies, a date stored on a record^[5], and changes to a deal’s stage, value, owner or status^[6]. Tasks can sit on contacts or on deals and be filtered by owner and status^[7].

What not to automate

Automation repeats whatever you give it, including mistakes.

Judgement. Whether a deal is qualified, or whether to discount, is a human decision. Automate the reminder to decide, not the decision.
The first real conversation. An instant automatic reply is useful; an automatic sequence standing in for a call to a warm inbound lead is not.
Messages you would not send by hand. If a follow-up email would embarrass you when read aloud, sending it automatically does not improve it.
Anything before the data is clean. Automations built on duplicate or incomplete records send the wrong message to the wrong person, faster.

Emails and texts to prospects: the UK rules in brief

B2B does not mean anything goes. It depends on who the subscriber is.

Limited companies and LLPs (corporate subscribers): the PECR rule on marketing by electronic mail does not apply to them, so a marketing email to a company address does not need consent under PECR^[8].
Sole traders and some partnerships: treated as individuals. Marketing by email or text needs consent or the “soft opt-in” for existing customers, with an opt-out in every message^[8]^[9].
Named business contacts are still personal data. UK GDPR applies when you hold the name of the person who represents a business^[8]: you need a lawful basis, you must tell them how you use their data, and you must honour an objection to marketing.
Texts count as electronic mail under PECR^[9], so the same rules apply to SMS sequences.

In practice, a sales CRM should record which kind of subscriber each contact is, the basis you rely on, and any opt-out, and your sequences should check those fields before sending. No software makes a sequence lawful by itself.

Next step

Workflows, booking links, tasks and conversations across email, SMS and other channels are documented in GoHighLevel’s help centre^[10]; usage charges apply to messages^[11].

Explore sales and automation features

What is likely to close

Sales forecasting in a CRM: useful, and only as good as the data

A CRM can add up your pipeline in several ways. None of them predicts the future. A forecast is a set of assumptions (values, dates, probabilities) applied to records your reps keep, and it is worth what those records are worth.

Pipeline value, weighted value, forecast categories

Three ways of reading the same deals.

Pipeline value: the sum of all open deal values. Useful to see volume, misleading as a revenue figure because it assumes every deal closes.
Weighted pipeline: each deal’s value multiplied by the probability for its stage. Smooths optimism across many deals; meaningless for a handful of large ones.
Expected revenue for a period: weighted or committed deals whose close date falls in that period. Depends entirely on close dates being honest.
Stage probabilities: set by your team. Start with an estimate, then compare against your own won and lost history each quarter and adjust.
Forecast categories: a rep’s judgement on top of the stage, commonly “commit” (will close), “best case” (could close) and “pipeline” (too early to say). Categories catch what stages miss, such as a late-stage deal the rep has doubts about.

A worked example

Five invented deals and probabilities a team might choose. Not benchmarks.

Qualified10%
Discovery done25%
Proposal sent50%
Negotiation75%

Worked example: five invented deals, value multiplied by stage probability
Deal	Stage	Value	Probability	Weighted	Close date	Rep’s category
Deal A	Proposal sent	£8,000	50%	£4,000	this month	Best case
Deal B	Qualified	£15,000	10%	£1,500	next quarter	Pipeline
Deal C	Negotiation	£4,500	75%	£3,375	this month	Commit
Deal D	Discovery done	£22,000	25%	£5,500	next month	Pipeline
Deal E	Proposal sent	£6,000	50%	£3,000	overdue	Best case
Total		£55,500		£17,375

Deal value Weighted value. Same invented deals as the table.

The two totals tell different stories. The unweighted pipeline says there is a lot of business in play; the weighted figure says much of it is early. Deal E shows the other half of the problem: an overdue close date on a live-looking deal usually means the date, the stage or both are wrong. A forecast review is mostly about deals like that one.

Data quality: why the forecast drifts

Six problems that make a pipeline report look better or worse than reality.

Common data problems in a sales CRM, their effect, and a rule that limits them
Problem	Effect on the numbers	A rule that helps
Duplicate contacts and companies	The same buyer counted twice; activity split across records	Duplicate check on email and domain at creation; a monthly merge review
Incomplete deals	Deals with no value or date drop out of totals or are filled with placeholders	Required fields from the stage where they become knowable
Outdated leads	Lists grow with people who left or never answered	An age rule: review, recycle or delete leads untouched for a set period
Inconsistent stages	Two reps’ “proposal” mean different things; conversion rates mean nothing	Written entry rules; stages named after buyer actions
Missing next actions	Deals stall silently	No open deal without a dated next action; a daily view of exceptions
Close dates that never move until they are overdue	The forecast for this month is always too high	A weekly check of overdue dates in the pipeline review

Software can help with the first line (duplicate detection, required fields, saved lists of exceptions such as “no activity in 14 days”^[13]). It does not clean data by itself, and it cannot tell whether a close date is honest. That part is management.

Sales management

What a sales manager should get from a CRM

For a manager, the CRM is where the team’s week becomes visible: which deals are moving, which are stuck, and whether the process everyone agreed on is being followed. The aim is earlier, better conversations with reps, not surveillance.

Five views worth having

Each answers a question you would otherwise ask by message.

Manager views in a sales CRM and the question each answers
View	Question it answers	Built from
Pipeline by stage and owner	Where is the value, and is it spread sensibly across the team?	Deal stage, value, owner
Deals closing this period	What is likely to close, and what has slipped since last week?	Close date, stage, forecast category
Exceptions	Which deals have no next action, no activity in N days, or an overdue close date?	Tasks, activity dates, close dates
Lead response	Are new leads being contacted, and by whom?	Lead creation date, owner, first activity
Won and lost, with reasons	Why are we winning and losing, and from which sources?	Status, lost reason, lead source

Activity counts (calls made, emails sent) are easy to report and easy to misread. They show effort, not progress. Use them to spot a rep who is struggling, never as a target on their own.

Running a weekly pipeline review

Thirty minutes, the same questions for every deal that matters.

What changed since last week?
Deals that moved stage, changed value or changed close date.
What is the next action, and when?
Any deal without one is the first thing to fix.
Is the close date still real?
Anything overdue, or moved more than once.
Who else is involved on the buyer’s side?
Deals relying on a single contact.
Should this deal still be open?
Stalled deals: mark lost or abandoned, with a reason, rather than let them inflate the pipeline.

Run the review from the CRM screen, not from a separate report. If a deal’s record is not up to date, the review is the moment to update it; after a few weeks the records start being updated before the meeting.

Consistency, permissions and handovers

The unglamorous part that decides whether the numbers can be trusted.

One process, written down: stages, entry rules, required fields, when to mark lost. Reviewed quarterly.
Permissions that fit the team: whether reps see only their own deals or the whole pipeline is a choice. GoHighLevel, for example, has an “Only Assigned Data” setting that limits a user to the leads and deals assigned to them^[14].
A change log: who changed what and when. In GoHighLevel the audit log is kept for 60 days^[15], so export anything you need longer.
Handover in one step: reassign a leaver’s leads and deals, then call the key accounts. The history stays on the record.

Next step

GoHighLevel documents pipeline dashboards filtered by stage, status, owner and source^[12]. Weighted forecasting is not described there; check what you need in a trial.

Explore the reporting side of the CRM

Small teams

Sales CRM versus a spreadsheet: when Excel or Google Sheets is enough

A well-kept spreadsheet is a perfectly good pipeline for one person with a few dozen deals. The case for a CRM grows with the number of people, the number of deals, and the number of things that must happen on time without someone remembering.

Criterion by criterion

No winner: each column is right for a different team.

Spreadsheet and sales CRM compared on twelve criteria
Criterion	Spreadsheet (Excel, Google Sheets)	Sales CRM
Centralisation	One file, if everyone uses the same one and nobody keeps a copy	One database with contacts, companies and deals linked
Activity history	A notes column, overwritten or growing sideways	Every call, email and meeting logged with a date against the person and the deal
Pipeline visibility	Filters and pivot tables you build and maintain	A board by stage, and reports by owner, stage and date
Permissions	Whole file or protected ranges; hard to limit a rep to their own rows	Roles, and settings limiting a user to their own records
Automation	Possible with scripts or add-ons, maintained by whoever wrote them	Built-in rules: assignment, tasks, reminders, sequences
Follow-ups	A “next action date” column you must sort and read every day	Tasks with due dates in each rep’s queue, and alerts on quiet deals
Reporting	Manual, and only as current as the last edit	Read directly from the records, still only as current as the last edit
Collaboration	Simultaneous editing, easy to overwrite each other	Separate records, internal notes and mentions
Email and calls	Kept in each person’s inbox and phone	Logged against the record, or sent from it
Integrations	Imports and exports by hand, or a connector you configure	Forms, calendars, email and webhooks feeding records directly
Scalability	Slows and breaks down with more people and more rows	Built for more users and records; cost usually grows with seats
Cost	Usually already paid for	A subscription, plus set-up time and sometimes usage charges

When a spreadsheet is enough, and when it is not

Signals to look for in your own team.

A spreadsheet can still do the job

One or two people sell, and they sit together.
A few dozen open deals at a time, with long cycles and few touches.
Leads arrive from one or two sources you check by hand.
Nobody needs a forecast more often than monthly.
You have the discipline to update one shared file every day.

Time to look at a sales CRM

Three or more people work leads, and you have seen the same prospect contacted twice.
Follow-ups have been missed because a date column was not checked.
Leads arrive from forms, calls, events and outreach at once.
Building the weekly pipeline report takes more than a few minutes.
A rep has left and their deals were hard to pick up.
You need to limit who sees which deals or customer data.

If you stay on a spreadsheet for now, give it the structure of a CRM: one row per deal, a lead source column, a value, a stage from a fixed list, a close date, an owner and a next-action date. Moving to a CRM later is then an import rather than a rescue.

Next step

Import a copy of your sheet with invented names into a GoHighLevel trial account and see whether the board, the tasks and the reminders do more for you than the columns did.

Try a CRM against your spreadsheet

The tool map

Sales CRM and the tools around it

A sales team often uses several systems at once. They are not interchangeable: each has a job, and each meets the CRM at a particular point. Knowing which is which avoids buying a CRM to do an ERP’s work, or the reverse.

Eleven categories, one line each on the border

Some products span several categories. The jobs stay distinct.

Sales CRM

Its job
Leads, contacts, companies, deals, pipeline stages, activities, follow-up tasks, sales reporting.

Not its job
Invoicing, stock, support tickets, contract generation.

Where it meets the CRM
It is the centre of this map.
CRM (general)

Its job
Customer records for any team: sales, service, marketing, account management.

Not its job
Nothing different in kind: “sales CRM” describes a sales-first set-up of the same category.

Where it meets the CRM
Often the same product, configured with sales pipelines.
Lead management software

Its job
Capturing, deduplicating, scoring and routing inbound leads, often from ads and forms.

Not its job
Managing deals after qualification.

Where it meets the CRM
Hands qualified leads to the CRM, ideally with source and history.
Sales engagement platform

Its job
High-volume outbound sequences of emails, calls and tasks for SDR and BDR teams.

Not its job
Being the system of record for deals and customers.

Where it meets the CRM
Reads contacts from the CRM, writes activities and replies back.
Marketing automation

Its job
Campaigns, segments, nurture emails, landing pages, lead scoring before sales is involved.

Not its job
Running the deal once a salesperson owns it.

Where it meets the CRM
Passes leads to sales at an agreed point; receives won and lost outcomes back.
ERP

Its job
Finance, accounting, stock, procurement, orders, operations.

Not its job
Prospecting, pipeline, follow-up.

Where it meets the CRM
A won deal becomes an order or a customer account in the ERP; invoices may flow back for reference.
Customer service / helpdesk

Its job
Support tickets, response times, a knowledge base.

Not its job
Selling, though it may flag renewal or upsell signals.

Where it meets the CRM
Shares the customer record, so sales sees open issues before calling.
CPQ (configure, price, quote)

Its job
Building accurate quotes for complex products, discounts and approvals.

Not its job
Managing the relationship or the pipeline.

Where it meets the CRM
Creates the quote from a deal; the quoted value updates the deal.
Sales intelligence

Its job
Company and contact data, firmographics, buying signals for prospecting.

Not its job
Tracking your own deals and conversations.

Where it meets the CRM
Enriches or creates records in the CRM; mind UK GDPR on the source of personal data.
Spreadsheet

Its job
Flexible lists, calculations and one-off analysis.

Not its job
Reminders, permissions per record, activity history.

Where it meets the CRM
Imports and exports; often where a CRM’s data is analysed.
Project management software

Its job
Delivering work after the sale: tasks, timelines, resources.

Not its job
Selling. A sales pipeline built in a project tool usually lacks contact history and email.

Where it meets the CRM
A won deal starts a project; the handover note travels with it.

Some platforms, GoHighLevel among them, combine a CRM with marketing automation features such as forms, booking calendars and messaging. That can reduce the number of tools a small team pays for. Whether it does for you depends on what you already use and what you would still need alongside it: the GoHighLevel chapter lists what it does not cover.

Commercial investigation

How to choose a sales CRM: features, tests and pricing models

Feature lists all look alike. The way to compare sales CRMs is to decide which capabilities your process depends on, test each one with your own scenario, and cost the whole thing at your team size.

Fifteen criteria, and how to test each

With what GoHighLevel’s documentation shows for each, since this site is funded by it.

Records
Contact management
One record per person, linked to their company, with history and consent.

How to test itImport 20 contacts with two deliberate duplicates. Does it catch them?

GoHighLevel: DocumentedContacts with a conversation history across channels^[10].
Records
Lead management
New interest captured with source and owner, from every channel you use.

How to test itSubmit a form and check the record, its source and its owner.

GoHighLevel: DocumentedForms create contacts^[16]; first and latest source stored^[17].
Pipeline
Pipeline
Your stages, on a board, with values.

How to test itBuild your real stages and move five deals through them.

GoHighLevel: DocumentedCustom pipelines and stages^[1].
Pipeline
Opportunity management
Value, owner, close date, status and lost reason on every deal.

How to test itClose one deal as lost and check the reason is required and reportable.

GoHighLevel: DocumentedValue, source, owner, statuses and lost reasons^[2]. A close date is a custom field you add.
Follow-up
Follow-up and tasks
A dated next action on every deal, in each rep’s queue.

How to test itCreate tasks on deals and filter by rep and by overdue.

GoHighLevel: DocumentedTasks on contacts and deals, filtered by assignee and status^[7].
Follow-up
Automation
Assignment, reminders and sequences without scripts.

How to test itBuild the “no activity for 7 days” rule and trigger it.

GoHighLevel: DocumentedTrigger and action workflows^[4], including on deal changes^[6].
Follow-up
Calendar and booking
Prospects book calls without email ping-pong.

How to test itBook a call from a link and check it lands on the right deal.

GoHighLevel: DocumentedBooking calendars with Google Calendar sync^[18].
Insight
Reporting
Pipeline by stage and owner, won and lost, sources.

How to test itRecreate your current weekly report and time it.

GoHighLevel: DocumentedOpportunity dashboards by stage, status, owner and source^[12].
Insight
Forecasting
Weighted pipeline and categories for the period.

How to test itEnter probabilities and check the weighted total by hand.

GoHighLevel: Not foundNot described in the dashboard article read^[12]; would need custom fields or an export.
Set-up
Integrations
Email, calendar, phone, accounting, your website.

How to test itList the three systems you cannot drop and check each connection.

GoHighLevel: Build or checkInbound webhooks let other systems start workflows^[19]; named connectors must be checked case by case.
Set-up
Customisation
Fields and objects that match what you sell.

How to test itAdd the five fields your qualification needs.

GoHighLevel: DocumentedCustom fields on opportunities^[2].
Set-up
Usability
Reps will not use what slows them down.

How to test itAsk a rep to log a call and move a deal without training.

GoHighLevel: Build or checkOnly your own team can judge this. The platform covers much more than sales, which some find busy.
Control
Permissions
Who sees which deals and customer data.

How to test itCreate a second user limited to their own deals and try to open another’s.

GoHighLevel: DocumentedRoles and an “Only Assigned Data” setting^[14].
Control
Scalability
More users, more records, more pipelines without a rebuild.

How to test itAsk about limits on users, records and pipelines on your plan.

GoHighLevel: DocumentedUnlimited users and contacts on every plan^[11].
Vendor
Pricing model and support
The real cost, and help when something breaks.

How to test itPrice your team for a year including usage; raise one support question during the trial.

GoHighLevel: Build or checkPer-account pricing plus usage^[11]; support quality is something to test yourself.

Next step

“Documented” means described in the vendor’s help articles read for this site, not tested by us. Run the tests above in the trial before moving real prospect data.

Test GoHighLevel against this checklist

Pricing models, and what they mean for a sales team

How you are charged matters as much as the headline price.

Common pricing models for sales CRM software
Model	How it works	What to watch
Per user (per seat)	A price per named user per month	Cost rises with every rep, manager and occasional user; some vendors set minimum seats
Tiered plans	Features unlock at higher tiers	Forecasting, automation or permissions are often in a higher tier than the entry price suggests
Per account	One price regardless of users	Cheaper for larger teams; check what is metered instead
Monthly subscription	Pay month by month, cancel with notice	Usually a higher unit price than annual
Annual billing	Pay for a year, often at a discount	The advertised price may be the annual one; check what monthly costs
Usage-based charges	Per SMS, email, call minute, AI use or contact volume	Budget from your own volumes; these can outgrow the subscription
Add-ons and onboarding	Paid modules, extra channels, one-off onboarding fees	Ask for the full list before comparing

Published prices at four team sizes

List prices only, in the currency each vendor published, read on the date shown.

Monthly list cost by number of users, before usage charges, add-ons and VAT
Plan	1 user	3 users	5 users	10 users	Basis
GoHighLevel Starter^[11]	$97	$97	$97	$97	per account, billed monthly. Per account, unlimited users; SMS, email and call usage extra. Read 22 Sept 2026.
GoHighLevel Unlimited^[11]	$297	$297	$297	$297	per account, billed monthly. As Starter, unlimited sub-accounts. Read 22 Sept 2026.
Salesforce Starter Suite^[23]	£20	£60	£100	£200	per user, billed monthly or annually. Entry edition. Read 22 Sept 2026.
Salesforce Pro Suite^[23]	£80	£240	£400	£800	per user, billed annually. Billed annually. Read 22 Sept 2026.
HubSpot Sales Hub Starter^[20]	$20	$60	$100	$200	per user, billed monthly. $7 per seat on annual billing. Read 21 Sept 2026.
HubSpot Sales Hub Professional^[20]	$100	$300	$500	$1,000	per user, billed monthly. Plus a one-time $1,500 onboarding fee. Read 21 Sept 2026.
Freshsales Growth^[24]	$9	$27	$45	$90	per user, billed annually. Monthly-billing price not shown. Read 21 Sept 2026.
Freshsales Pro^[24]	$39	$117	$195	$390	per user, billed annually. Monthly-billing price not shown. Read 21 Sept 2026.
monday CRM Standard^[21]	€51	€51	€85	€170	per user, billed annually. Minimum 3 seats; €25 list price. Read 21 Sept 2026.

Not converted and not taxed. Dollar and euro prices are shown as published; an exchange rate would be one more figure to go out of date. VAT is not included.
Not the whole cost. GoHighLevel charges for SMS, email and calls on top^[11]; HubSpot Professional adds a one-time onboarding fee^[20]; monday CRM has a three-seat minimum^[21]. Set-up time and integrations are extra everywhere.
Missing on purpose. Zoho showed no sterling price to our reader^[22], and Pipedrive’s pricing page could not be read for this edition, so neither is priced here. The Pipedrive price on the previous version of this page could not be checked and is not repeated.
Per account versus per user. A per-account price looks cheaper as the team grows, but compare like with like: what each plan includes, and what is metered.

Sales CRM comparison

Seven sales CRMs, without scores

This site earns a commission from one of these vendors, so it does not rank them. Instead, each platform is described by the kind of sales team it tends to suit and not suit, from its own published material, with its published price and the date it was read. Test your shortlist with the checklist above.

Who each platform tends to suit

Categories and prices from each vendor’s own pages. Features not tested by this site.

GoHighLevel

Funds this site

CRM with marketing automation, messaging, booking and forms in one account
Tends to suit
- Small and mid-sized teams that sell from inbound enquiries, booked calls and follow-up sequences
- Teams wanting forms, calendars, messaging and pipeline in one account
- Teams where per-user pricing would be a burden
Tends to suit less
- Teams that need built-in weighted forecasting or complex territory structures
- Enterprise sales with deep ERP or CPQ integration
- Teams that want a narrow, sales-only interface
Published price: Starter $97 per account per month, Unlimited $297; unlimited users; usage charged extra; 14-day public trial.^[11]
Salesforce Sales Cloud

Enterprise sales CRM with a large ecosystem of editions and add-ons
Tends to suit
- Larger organisations with complex processes, territories and approval chains
- Teams with an administrator or a partner to configure it
- Businesses already on other Salesforce products
Tends to suit less
- Small teams without anyone to own configuration
- Buyers wanting one predictable price, since features are spread across editions
Published price: Starter Suite £20 per user per month; Pro Suite £80 (billed annually); Core £156, Advanced £316, Max £440 (billed annually). 30-day trial.^[23]
HubSpot Sales Hub

Sales CRM on a shared platform with HubSpot’s marketing and service products
Tends to suit
- Teams where marketing already uses HubSpot
- Very small teams starting on the free tier
- Inbound-led sales with content and email at the front
Tends to suit less
- Budgets sensitive to per-seat growth at higher tiers
- Teams that need higher-tier features but not the rest of the tier
Published price: Free for up to 2 users; Starter $20 per seat monthly ($7 annual); Professional $100 monthly ($90 annual) plus $1,500 onboarding; Enterprise from $150.^[20]
Pipedrive

Pipeline-first sales CRM for small and mid-sized teams
Tends to suit
- Teams whose main need is a clear deal board and activity reminders
- Reps who want a simple interface with little set-up
Tends to suit less
- Teams that want marketing, booking and messaging in the same product without add-ons
- Complex permissions or large multi-team structures (check the tiers)
Published price: Not shown: the pricing page could not be read for this edition. Check pipedrive.com for current prices.
Zoho CRM

Configurable CRM within Zoho’s wider suite of business apps
Tends to suit
- Businesses already using Zoho for finance, HR or projects
- Teams comfortable configuring fields, rules and layouts themselves
- Very small teams on the free edition (up to three users)
Tends to suit less
- Teams with nobody to own configuration
- Buyers who need a sterling price before they talk to sales
Published price: Free edition for 3 users; paid editions per user per month. No sterling price could be read.^[22]
Freshsales

Sales CRM within Freshworks’ suite, alongside Freshdesk
Tends to suit
- Businesses already using Freshdesk for support
- Teams wanting a lower per-user entry price
Tends to suit less
- Teams outside the Freshworks ecosystem who need deep integrations elsewhere (check the list)
Published price: Growth $9, Pro $39, Enterprise $59 per user per month, billed annually. 21-day trial.^[24]
monday CRM

CRM built on monday.com’s work-management platform
Tends to suit
- Teams already running projects on monday.com
- Sales processes that hand over directly into delivery work
Tends to suit less
- Teams of one or two, given the three-seat minimum
- Buyers needing sterling prices shown up front
Published price: Basic €12, Standard €17, Pro €28 per seat per month on annual billing (list €18, €25, €41). Minimum 3 seats.^[21]

The previous version of this page made unsourced claims about which of these platforms can send text messages. They are not repeated. If texting prospects matters to you, check each shortlisted vendor’s current channel list and the cost per message.

Next step

If GoHighLevel is on your shortlist, compare it on the same tests as the others: your stages, your follow-up rule, your weekly report.

Explore the platform

The platform this site is funded by

GoHighLevel for sales teams: where it fits and where it does not

GoHighLevel is a CRM and marketing automation platform: contacts, pipelines, opportunities, workflows, booking calendars, forms and conversations across email, SMS and other channels, priced per account rather than per user. It was built with agencies and small businesses in mind, not as a specialist enterprise sales tool. For many small and mid-sized sales teams that combination fits well; for some it does not.

What it does that matters to a sales team

Documented in HighLevel’s help articles, read for this site.

Pipelines with your own stages, holding leads, deals or customers^[1].
Opportunities with value, source, owner and custom fields, and four statuses: open, won, lost and abandoned, with a lost reason^[2]^[3].
Workflows started by forms, bookings, replies, dates on a record, or changes to a deal’s stage, value, owner or status^[4]^[5]^[6].
Tasks on contacts and deals, filtered by owner and status: a follow-up queue^[7].
One conversation history per contact across email, SMS, WhatsApp and social messages, with internal comments^[10], and a browser dialler that logs calls to the contact^[25].
Booking calendars with Google Calendar sync for discovery calls and demos^[18], and forms that create contacts^[16].
Dashboards of opportunities by pipeline, stage, status, owner and source, including lost reasons^[12].
Roles and permissions, including limiting a rep to assigned leads and deals^[14].
Pricing per account, not per user, with unlimited users and contacts on every plan, plus usage charges^[11].

Next step

30 days through this site’s partner link, with the HighLevel Bootcamp, as confirmed by the partner account holder; the public pricing page lists 14 days^[11]. The terms shown at sign-up apply.

See how GoHighLevel works

Limits, and when a specialist sales CRM is the better choice

Read this before the trial, not after.

Forecasting is not documented as a feature. The dashboard article read for this site mentions no weighted pipeline, stage probability or forecast category^[12]. You can add fields and calculate outside, but if a formal forecast process runs your business, a CRM with built-in forecasting will suit you better.
No close date by default in the fields described. Expected close date is a custom field you create^[2]; make it required.
Broad rather than sales-specific. The platform includes websites, funnels, social planning, reputation tools and much more. Reps who only need a deal board may find it busy; hide what you do not use.
Permissions are simpler than enterprise CRMs. Admin and user roles plus “only assigned data”^[14]; no territory hierarchy is described. Test your structure with a second user.
Integrations mean webhooks or a connector. Inbound webhooks can start workflows from other systems^[19]; check each system you rely on (accounting, quoting, telephony) before committing.
Usage costs add up. SMS, email and calls are charged on top of the plan, and WhatsApp has its own monthly and per-message charges^[11]^[26].
Data is hosted in the United States^[27]; see UK GDPR and prospect data.
The change log keeps 60 days^[15].

A sales set-up you can build in it

One pipeline, a handful of fields, five workflows.

A suggested structure for a sales team in GoHighLevel
Element	Built with	Detail
New business pipeline	A pipeline	Stages: new lead, contacted, qualified, discovery held, proposal sent, negotiation; then won, lost or abandoned as statuses
Deal fields	Opportunity value and custom fields	Expected close date, forecast category, probability, next action date, competitor
Contact fields	Custom fields on contacts	Subscriber type (company or individual), lawful basis, marketing opt-out date, role
Lead intake	Forms and a booking calendar	Enquiry form creates the contact; booking a call creates the opportunity
Follow-up rules	Workflows and tasks	Assignment, first-contact task, proposal chase, no-activity reminder, date reminder before close date
Manager view	Dashboard and smart lists	Pipeline by stage and owner; lists of deals with no next action or an overdue close date

Sources: opportunity fields^[2], date-based triggers^[5], smart lists^[13]. Once it works, a snapshot can copy the configuration to another account, without contact data^[28].

A seven-step test plan for the trial

Decide with evidence from your own pipeline, not from a demo.

Pick three leaks
From the twelve above, and write down how you will know each is fixed.
Build your pipeline
Your stages, with an entry rule each, and the deal fields from the table above.
Import invented data
Twenty contacts and ten deals with made-up names. No real prospect data until your processing agreement and privacy information are in place.
Build three workflows
Lead assignment with a first-contact task, the proposal chase, and the no-activity reminder. Trigger each one.
Recreate your weekly report
Pipeline by stage and owner, deals closing this month, and exceptions. Note what you had to calculate outside.
Test permissions
A second user limited to assigned data, trying to open records they should not see.
Price a year honestly
Your plan, plus SMS, email and call usage at your volumes, plus WhatsApp if needed, plus any integration tool.

Next step

Use the 30 days to run the seven steps, then decide.

Try GoHighLevel with this test plan

Prospect and customer data

UK GDPR and prospect data in a sales CRM

A sales CRM is mostly personal data: names, job titles, work emails, phone numbers, call notes. The UK GDPR and the Data Protection Act 2018 apply to it, B2B or not. No software is “compliant” on its own; compliance depends on how you configure it and how the team uses it.

What applies to the data in your pipeline

A summary to discuss with whoever handles data protection in your business. Not legal advice.

Business contacts are personal data. Holding the name of the person who represents a business brings UK GDPR into play^[8].
A lawful basis for each use. Prospecting business contacts is often done on legitimate interests, which needs a documented balancing test; marketing by email or text to individuals and sole traders also needs to meet PECR^[9].
Privacy information. People whose details you collect, including from lists or research, must be told who you are and how you use their data.
Retention. Decide how long you keep leads that never became customers, and lost deals, and set a review date. A CRM makes this easy to automate and easy to forget.
Access and permissions. Give each role the access it needs and no more; remove leavers on their last day.
Rights requests. You must be able to find, export, correct or delete one person’s data across the CRM and anything connected to it.
Processors. Your CRM vendor, and every integration that receives data from it, processes data on your behalf and needs a written agreement.

What GoHighLevel states about its role

The vendor’s own statements, with what they do not cover.

HighLevel acts as processor and you as controller of your customer data, under its data processing agreement, which also refers to the EU-U.S. Data Privacy Framework^[29].
Its infrastructure is in the United States, and “use of the HighLevel product alone does not make you GDPR compliant”^[27].
Whether the UK Extension to the Data Privacy Framework covers your transfer is for you to check in the official list on the day you sign.

Questions

Sales CRM questions answered

The fifteen questions of the original page, answered without rankings or unsourced figures.

Frequently asked questions

Open a question to read the answer.

Which sales CRM is best for a UK sales team?

There is no single answer, and this site, funded by one vendor, is not in a position to rank them. The right choice depends on team size, how you sell (inbound, outbound, account management), what you must integrate, and how much configuration you can take on.

Use the fifteen tests on a shortlist of two or three, with your own stages and your own weekly report. The platform notes describe which kind of team each tends to suit.

Why do sales teams use CRM software?

To keep every lead, deal and follow-up in one shared place, so the team can answer where each deal stands, who owns it, what happens next and what is likely to close, without collecting updates by hand. More on this above.

Which CRM software is best for lead management?

For lead management, look at how each tool captures leads from your real sources, stores the source, deduplicates and assigns an owner, then how fast a first-contact task reaches a rep. Test those four steps with a form on your own site during a trial. If your volume is very high and marketing-led, dedicated lead management or marketing automation may sit in front of the CRM (see the tool map).

Can GoHighLevel automate sales workflows?

Yes. Its workflows run actions after a trigger such as a form submission, a booking, a reply, a date on a record, or a change to a deal’s stage, value, owner or status^[4]^[6]. Actions include messages, tasks and pipeline updates. What to automate, and what not to, is covered in the automation chapter.

How does GoHighLevel compare to Salesforce for sales teams?

They aim at different buyers. Salesforce Sales Cloud is an enterprise sales CRM priced per user, from £20 to £440 per user per month depending on edition^[23], with deep configuration usually handled by an administrator or partner. GoHighLevel is a CRM and marketing automation platform priced per account, with unlimited users and usage charges^[11].

Large teams with territories, formal forecasting and complex integrations will generally find Salesforce the more natural fit. Smaller teams focused on response and follow-up may find GoHighLevel simpler to justify. Test both on your own process.

Is GoHighLevel better than HubSpot for sales?

Neither is better in general. HubSpot Sales Hub sits on the same platform as HubSpot’s marketing tools and is priced per seat, with a free tier for up to two users and an onboarding fee on Professional^[20]. GoHighLevel bundles CRM, booking, forms and messaging per account^[11]. If your marketing already runs on HubSpot, that weighs heavily; if per-seat cost is the constraint, GoHighLevel’s model may suit you. Compare them with the cost table at your team size.

How much does GoHighLevel cost?

On the public pricing page read on 22 September 2026: Starter $97 a month, Unlimited $297, Agency Pro $497, Enterprise on request, all in US dollars per account with unlimited users and contacts. SMS, email and call usage is charged on top^[11]. No sterling price and no VAT treatment are published there.

The public page lists a 14-day trial; through this site’s partner link it is 30 days with the HighLevel Bootcamp, as confirmed by the partner account holder. The terms shown at sign-up apply.

What CRM features improve sales forecasting?

A required value and close date on every deal, stage probabilities you can set, forecast categories, a view of deals closing in a period, and history of won and lost deals to check your probabilities against. Features only help if the data is kept current: see data quality.

Can a CRM replace multiple sales tools?

Sometimes. A CRM with built-in forms, booking and messaging can replace separate tools for those jobs in a small team. It will not replace an ERP, accounting, a helpdesk for a large support operation, or a CPQ for complex quotes. List the tools you use, then check which the CRM genuinely covers: the tool map helps.

How long does it take to implement a sales CRM?

It depends on data migration, the number of integrations, how many pipelines and fields you need, and the time the team can give it. A small team with a clean spreadsheet and one pipeline can be working in days; an organisation with several teams and integrations should plan in weeks or months. The original page’s “1-2 weeks” for GoHighLevel and “3-12 months” for Salesforce had no source and are not repeated.

What is the difference between CRM and marketing automation?

Marketing automation works on groups before a salesperson is involved: segments, campaigns, nurture emails, lead scoring. A sales CRM works on individual deals once someone owns them: stages, tasks, calls, proposals. Many platforms, GoHighLevel and HubSpot among them, offer both; the jobs are still different. See the tool map.

How does CRM automation improve sales team productivity?

By removing repeat steps (assigning leads, creating follow-up tasks, sending booking confirmations, logging emails) and by making exceptions visible, such as deals with no next action. How much time it saves depends on your process; no figure is given here because none could be sourced.

Which CRM is best for SDR teams?

SDR and BDR teams doing high-volume outbound often use a sales engagement platform for sequences alongside a CRM that holds the record. For smaller outbound teams, a CRM with sequences, tasks and a dialler can be enough. Check call logging, sequence stop rules, and the PECR position of your targets (see the rules).

Do CRM systems improve sales conversion rates?

A CRM can make follow-up more consistent and show where deals stall, which are common reasons deals are lost. Whether your conversion improves depends on how the team uses it. Measure your own stage-to-stage conversion before and after; this site gives no generic figure because none could be sourced.

Is GoHighLevel suitable for large sales teams?

It allows unlimited users on every plan^[11], and has roles and an “only assigned data” setting^[14]. It does not document territory hierarchies or built-in weighted forecasting in the articles read for this site^[12]. Large teams with formal forecasting and complex structures should test those needs specifically, and may be better served by an enterprise sales CRM.

Next step

Take your remaining questions into the trial, and check them against the tests in the seven-step plan.

Explore the CRM

Ready to test a pipeline on your own deals?

Take three leaks, your own stages and the seven-step test plan into a trial account. Use invented data until your processing agreement and privacy information are in place.

Start the GoHighLevel trial

Sources

Every factual claim on this page rests on one of these, read on the date shown. Addresses are printed as text, not linked. Each entry says what the source supports and what it does not.

[1] HighLevel: Understanding Pipelines

HighLevel Support · https://help.gohighlevel.com/support/solutions/articles/155000001982-understanding-pipelines · read 21 September 2026

“Pipelines are visual workflow tools that show the progress of leads, deals, or customers from start to finish.” “A pipeline is made up of stages, with each stage representing a step in your sales or customer journey.”

Supports: You define the stages yourself, and a pipeline holds leads, deals or customers.

Does not support: No ready-made sales process, no limit per plan, nothing about win rates.
[2] HighLevel: Editing Opportunities

HighLevel Support · https://help.gohighlevel.com/support/solutions/articles/155000002001-editing-opportunities · read 22 September 2026

Fields named in the article: “contact’s name, contact information, opportunity value, and opportunity source”; “pipeline stages, owners, tags, or any other custom fields”. “Possible statuses for an opportunity are ‘Open’, ‘Won’, ‘Lost’ and ‘Abandoned’”. “Marking an opportunity lost also allows you to add a lost reason”.

Supports: An opportunity carries a value, a source, a stage, an owner and custom fields, and a lost opportunity can carry a reason.

Does not support: Nothing about a close-date field or stage probabilities: those would be custom fields you create.
[3] HighLevel: Opportunity Statuses, Won, Lost and Abandoned

HighLevel Support · https://help.gohighlevel.com/support/solutions/articles/48000982199-opportunity-statuses-won-lost-and-abandoned · read 22 September 2026

“Opportunities with the ‘Open’ status are actively being pursued and are still in progress.” “The ‘Won’ status indicates that the opportunity has been successfully converted into a sale or deal.” “Opportunities with the ‘Lost’ status represent deals that have been unsuccessfully concluded.” “The ‘Abandoned’ status indicates that the opportunity has been neglected or disregarded, either by the lead or by the sales team.”

Supports: The four statuses and what each one means in the product.

Does not support: When your team should mark a deal abandoned rather than lost is your rule to write.
[4] HighLevel: Introduction to Workflows and Automations

HighLevel Support · https://help.gohighlevel.com/support/solutions/articles/155000002445-introduction-to-workflows-and-automations · read 21 September 2026

“A trigger is an event that sets your workflow into motion.” “An action is the task performed in response to a trigger.” Triggers named as examples include an appointment booking, a form submission and a reply to a message.

Supports: The documented model (a trigger, then actions) and the examples the vendor gives.

Does not support: Not a complete list of triggers, and no time saving.
[5] HighLevel: Workflow Trigger, Custom Date Reminder

HighLevel Support · https://help.gohighlevel.com/support/solutions/articles/155000002674-workflow-trigger-custom-date-remimder · read 21 September 2026

“The Custom Date Reminder Workflow Trigger starts a workflow before, on, or after a date field you select.”

Supports: A workflow can start before or after a date stored on a record, such as an expected close date or a renewal date.

Does not support: You create and maintain the date fields yourself.
[6] HighLevel: Workflow Trigger, Opportunity Changed

HighLevel Support · https://help.gohighlevel.com/support/solutions/articles/155000000886-workflow-trigger-opportunity-changed · read 22 September 2026

“The ‘Opportunity Changed’ workflow trigger in HighLevel automates actions when any changes occur in an opportunity record.” “Unlike ‘Opportunity Status Changed,’ which only tracks status updates, this trigger can respond to broader modifications such as updates to lead value, pipeline stage, assignment, or custom fields.”

Supports: A workflow can start when a deal changes stage, value, owner or a custom field, or when its status changes.

Does not support: The trigger says nothing about which actions are sensible; that is your process.
[7] HighLevel: Unified Task Management Across Contacts and Opportunities

HighLevel Support · https://help.gohighlevel.com/support/solutions/articles/155000005529-unified-task-management-across-contacts-and-opportunities · read 21 September 2026

“Unified Task Management in HighLevel allows you to create and manage tasks from both the Contacts and Opportunities modules using the same interface.” · “You can filter tasks by assignee or task status”.

Supports: Tasks on contacts and on deals, filtered by rep and by status: the raw material of a follow-up queue.

Does not support: Nothing about how many tasks a rep should carry.
[8] Business-to-business marketing

Information Commissioner’s Office (ICO) · https://ico.org.uk/for-organisations/direct-marketing-and-privacy-and-electronic-communications/business-to-business-marketing/ · read 22 September 2026

“The PECR rule on direct marketing by electronic mail does not apply to corporate subscribers.” · Some businesses “are actually classed as individual subscribers. This includes: sole traders; certain types of partnerships” · “The UK GDPR still applies to B2B marketing if you are processing personal data. For example, if you hold the name of the individual who represents the business.”

Supports: Marketing emails to limited companies do not need consent under PECR; sole traders and some partnerships are treated as individuals; named business contacts are personal data under UK GDPR.

Does not support: The guidance does not assess any software, and it is a summary, not legal advice for a given campaign.
[9] Privacy and Electronic Communications Regulations 2003, regulation 22

legislation.gov.uk · https://www.legislation.gov.uk/uksi/2003/2426/regulation/22 · read 21 September 2026

22(2): no unsolicited direct marketing by electronic mail “unless the recipient of the electronic mail has previously notified the sender that he consents for the time being to such communications being sent”. 22(3) allows it where details were obtained in a sale or negotiation, the marketing is for similar products or services, and the recipient was given a simple means to refuse at collection and in every message.

Supports: Marketing emails and texts to individual subscribers need consent or the narrow “soft opt-in”, with an opt-out in every message. “Electronic mail” in PECR includes SMS.

Does not support: The regulation does not classify a given message. Whether a sequence is direct marketing depends on its content and context.
[10] HighLevel: Getting Started with the New Conversations Experience

HighLevel Support · https://help.gohighlevel.com/support/solutions/articles/155000006610-getting-started-with-the-new-conversations-experience · read 21 September 2026

“Read the full history across Email, SMS, WhatsApp, Facebook/Instagram messages, and Internal Comments.” · “Team Inbox: All conversations within the account (requires full data access).”

Supports: One history per contact across email, SMS, WhatsApp and social messages, plus a team inbox and internal comments.

Does not support: No per-channel costs (WhatsApp is a paid add-on) and no response rates.
[11] HighLevel: Pricing

HighLevel · https://www.gohighlevel.com/pricing · read 22 September 2026

Starter “$97” a month with “3 Sub-Accounts”, “Unlimited Contacts” and “Unlimited Users” · Unlimited “$297” with “Unlimited Sub-Accounts” · Agency Pro “$497” · Enterprise on request. “14 Day Free Trial”. Usage charges for calls, SMS and email sending are added (read on 2026-09-21: “*Usage based charges apply.”).

Supports: Plan names and list prices in US dollars per account per month, unlimited users and contacts on every plan, the publicly listed 14-day trial, and usage charges on top.

Does not support: No sterling prices, no UK VAT treatment, no UK SMS rates. Terms that apply through this site’s partner link are not on this page.
[12] HighLevel: Opportunities Widgets in Dashboards and Reports

HighLevel Support · https://help.gohighlevel.com/support/solutions/articles/155000008109-opportunities-widgets-in-dashboards-reports · read 22 September 2026

“Opportunities Widgets let you track and analyze your pipeline directly inside your dashboards and custom reports.” “There are 17 Opportunities Widgets available.” Widgets can be filtered by pipeline, stage, status, assignee and attribution source; one widget is “Lost Opportunities By Reason”.

Supports: Pipeline dashboards filtered by stage, status, owner and source, including lost reasons.

Does not support: The article does not mention forecasts, weighted pipeline value or stage probabilities. A weighted forecast would have to be built (for example with custom fields) or done outside; check this in a trial account.
[13] HighLevel: Getting Started With Smart Lists

HighLevel Support · https://help.gohighlevel.com/support/solutions/articles/48001062094-how-to-create-manage-smart-lists · read 21 September 2026

A Smart List is “a dynamic contact list in HighLevel that updates automatically based on predefined filters and conditions.”

Supports: Saved segments (for example, leads with no activity in 14 days) that update as records change.

Does not support: The fields you filter on have to exist and be kept current by your team.
[14] HighLevel: Manage Sub-Account User Roles & Permissions

HighLevel Support · https://help.gohighlevel.com/support/solutions/articles/155000002544-user-roles-permissions-and-assigned-data-subaccount · read 21 September 2026

“Admin: full access to all modules and settings in the sub-account” · “User: restricted access; granular permissions apply.” · “Toggle Only Assigned Data to restrict a user's visibility to only the leads, opportunities, and data explicitly assigned to them.”

Supports: Two roles, finer permissions, and a setting that limits a rep to the leads and deals assigned to them.

Does not support: No territory hierarchy or manager-sees-team role is described in this article; test the set-up you need with a second user.
[15] HighLevel: Audit Logs

HighLevel Support · https://help.gohighlevel.com/support/solutions/articles/155000006667-audit-logs · read 21 September 2026

“Audit Logs are the source of truth for who did what and when across your HighLevel account.” “Audit Log entries are retained for 60 days and then purged.”

Supports: A change log with user and time, kept for 60 days.

Does not support: No record beyond 60 days. Keep your own log for anything you must prove later.
[16] HighLevel: How to Create and Manage a Contact Form

HighLevel Support · https://help.gohighlevel.com/support/solutions/articles/155000004549-how-to-create-and-manage-a-contact-form-in-highlevel · read 21 September 2026

“When a new lead submits a HighLevel form, a contact record is automatically created so the information can be managed inside the CRM.”

Supports: An enquiry form creates the contact, which a workflow can then assign and follow up.

Does not support: Nothing about the privacy wording on the form; you write it.
[17] HighLevel: Understanding Attribution Source

HighLevel Support · https://help.gohighlevel.com/support/solutions/articles/48001219997-understanding-attribution-source · read 21 September 2026

“Attribution provides a breakdown of which channels or sources a contact came from.” · “Both are always stored on every single contact.” (first and latest attribution)

Supports: Each contact stores its first and latest source, if your forms and links are tagged.

Does not support: No accuracy guarantee: attribution depends on how tracking is set up.
[18] HighLevel: Integrating Google with HighLevel Calendars

HighLevel Support · https://help.gohighlevel.com/support/solutions/articles/155000002369-integrating-google-with-highlevel-calendars · read 21 September 2026

“Google Calendar integration with HighLevel enables real-time scheduling, streamlined availability management, and seamless syncing across platforms.” From “Getting Started: Setup a Booking Calendar”: “Share the calendar link to start booking appointments!”

Supports: Booking links for discovery calls and demos, with Google Calendar sync.

Does not support: Nothing about other calendar systems in detail, and no effect on no-shows is claimed.
[19] HighLevel: Workflow Trigger, Inbound Webhook

HighLevel Support · https://help.gohighlevel.com/support/solutions/articles/155000003147-workflow-trigger-inbound-webhook · read 22 September 2026

“The Inbound Webhook Trigger captures incoming POST/GET/PUT requests sent to a HighLevel Webhook URL (unique for each trigger).” “This enables the system to react to events from external applications […]”.

Supports: Another system (an accounting package, a quoting tool, an integration platform) can start a workflow.

Does not support: No ready-made connector to any named ERP or CPQ tool. The help centre also lists a separate premium webhook trigger; whether it costs extra is to be checked in the account.
[20] HubSpot Sales Hub: Pricing

HubSpot · https://www.hubspot.com/pricing/sales · read 21 September 2026

Free $0 (up to 2 users) · Starter $20/seat monthly ($7 annual) · Professional $100/seat monthly ($90 annual), one-time onboarding fee $1,500 · Enterprise $150/seat annual, onboarding $3,500.

Supports: Per-seat prices and onboarding fees as shown in US dollars.

Does not support: UK visitors may be shown sterling prices, which were not read for this site.
[21] monday.com: Pricing (monday CRM)

monday.com · https://monday.com/pricing · read 21 September 2026

monday CRM: Basic €18 struck through, €12 seat/month; Standard €25 → €17; Pro €41 → €28; Ultimate custom. Minimum 3 seats. “Prices do not include tax. The price is determined by the user’s billing country.”

Supports: List and discounted annual prices, the three-seat minimum, and currency set by billing country.

Does not support: No sterling price was shown to this reader.
[22] Zoho: CRM pricing

Zoho · https://www.zoho.com/crm/zohocrm-pricing.html · read 21 September 2026

Editions Free (3 users), Standard, Professional, Enterprise, Ultimate, each priced per user per month, with an annual discount. The page served prices in Indian rupees; the UK-specific URLs tried returned 404.

Supports: Edition names, per-user billing, and a free edition for up to three users.

Does not support: No sterling price could be read. None is reproduced here.
[23] Salesforce Sales Cloud: Pricing (UK)

Salesforce · https://www.salesforce.com/uk/sales/pricing/ · read 22 September 2026

Starter Suite “£ 20 GBP/User/Month (Billed monthly or annually)” · Pro Suite “£ 80 GBP/User/Month (Billed annually)” · Core “£ 156” · Advanced “£ 316” · Max “£ 440”, per user per month, billed annually. “Try Sales Cloud free for 30 days.” (trial read on 2026-09-21)

Supports: Published sterling prices per user for the Sales Cloud editions, and the trial length.

Does not support: Implementation, partner or add-on costs are not on this page.
[24] Freshworks: Freshsales pricing

Freshworks · https://www.freshworks.com/crm/pricing/ · read 21 September 2026

Growth “$9/user/month, billed annually”; Pro “$39/user/month, billed annually”; Enterprise “$59/user/month, billed annually”. “When you sign up, you instantly get access to the fully-loaded CRM for 21 days”.

Supports: Per-user prices on annual billing and the 21-day trial.

Does not support: Shown in US dollars; monthly-billing prices are not stated in this view.
[25] HighLevel: The Phone Dialer Overview

HighLevel Support · https://help.gohighlevel.com/support/solutions/articles/155000005807-the-phone-dialer-overview · read 21 September 2026

“The Phone Dialer is a browser-based calling interface that allows users to place and receive calls directly from HighLevel without external phone hardware or apps.” “All calls are logged to contact records with timestamps, duration, and call status.”

Supports: Calls from the browser, logged on the contact record.

Does not support: No call rates, nothing on UK number availability or call recording rules.
[26] HighLevel: WhatsApp Pricing, Billing and Rebilling Guide

HighLevel Support · https://help.gohighlevel.com/support/solutions/articles/155000001428-whatsapp-pricing-billing-and-rebilling-guide · read 21 September 2026

“Agency Charge $10 / month per sub-account” · “WhatsApp in HighLevel now uses a per-message pricing model, charging businesses for each delivered message”.

Supports: WhatsApp costs $10 a month per sub-account where enabled, plus a charge per delivered message.

Does not support: No UK per-message prices in this summary.
[27] HighLevel: Security and Compliance Overview

HighLevel Support · https://help.gohighlevel.com/support/solutions/articles/155000000574-highlevel-security-and-compliance-overview · read 21 September 2026

“Our product infrastructure resides in the United States.” · “While HighLevel seeks to enable your GDPR compliance efforts, use of the HighLevel product alone does not make you GDPR compliant.”

Supports: The vendor states that its infrastructure is in the United States, and that using the product does not by itself make anyone GDPR compliant.

Does not support: No choice of UK or EU data location is described. These are the vendor’s own statements.
[28] HighLevel: Snapshots Overview

HighLevel Support · https://help.gohighlevel.com/support/solutions/articles/48000982511-snapshots-overview · read 21 September 2026

“Snapshots can copy many configuration assets from a source sub-account.” · “Snapshots are designed to transfer configuration and selected reusable assets, not live account activity or customer records.”

Supports: A sales set-up built once (pipelines, fields, workflows, forms) can be copied to another account, without contact data.

Does not support: Not a migration tool for data coming from another CRM.
[29] HighLevel: Data Processing Agreement

HighLevel · https://www.gohighlevel.com/data-processing-agreement · read 21 September 2026

“HighLevel will act as a Processor of Customer Personal Data. Customer will act as the Controller of Customer Personal Data.” · “HighLevel is certified to the EU-U.S. Data Privacy Framework […]”.

Supports: A processing agreement exists; your business remains the controller of prospect and customer data.

Does not support: Whether the UK Extension to the Data Privacy Framework covers your transfer on the day you sign is for you to check in the official list. The agreement does not replace your own lawful basis, privacy information or retention policy.

Sales CRM for UK sales teams: from first lead to signed customer

A working definition

CRM and sales CRM: what changes

Why sales teams use one

Twelve common leaks

01Leads scattered across inboxes and lists

02Enquiries with no reply

03Different reps, different definitions of “qualified”

04The same prospect worked twice

05Follow-ups that depend on memory

06Deals with no value or no date

07Stalled opportunities

08Nobody knows why deals are lost

09Manual pipeline reporting

10Repetitive admin

11Poor handover between people

12Managers without visibility

Eight stages, one question each

Lead

Qualify

Opportunity

Follow-up

Proposal

Negotiation

Closed won / lost

Customer

Designing your own stages

The vocabulary a sales team needs to share

Nine automations worth considering

Lead assignment

First-contact task

Enquiry acknowledgement

Follow-up reminder

Proposal chase

Appointment reminders

Pipeline update on an event

Email sequence for nurturing

Re-engagement of lost deals

What not to automate

Emails and texts to prospects: the UK rules in brief

Pipeline value, weighted value, forecast categories

A worked example

Data quality: why the forecast drifts

Five views worth having

Running a weekly pipeline review

Consistency, permissions and handovers

Criterion by criterion

When a spreadsheet is enough, and when it is not

Eleven categories, one line each on the border

Sales CRM

CRM (general)

Lead management software

Sales engagement platform

Marketing automation

ERP

Customer service / helpdesk

CPQ (configure, price, quote)

Sales intelligence

Spreadsheet

Project management software

Fifteen criteria, and how to test each

Contact management

Lead management

Pipeline

Opportunity management

Follow-up and tasks

Automation

Calendar and booking

Reporting

Forecasting

Integrations

Customisation

Usability

Permissions

Scalability

Pricing model and support

Pricing models, and what they mean for a sales team

Published prices at four team sizes

Who each platform tends to suit

GoHighLevel