What a CRM actually is

Sales Academy · from no sales experience to landing an AE job, with a UK life-sciences & health-tech specialism. UK English. No prior sales experience assumed; every term is defined at first use.

There is a moment about twelve minutes into a sales interview that ends more candidacies than any objection-handling question ever has. It sounds like this: "So — have you used Salesforce?"

If you are changing careers the honest answer is no. The fatal answer is a mumbled no followed by silence, because what the interviewer heard was not "this person lacks a login" but "this person has never seen how a commercial team operates". Every deal you work will live in a system of record. Every forecast the business commits to is assembled from fields reps typed. Every commission cheque is reconciled against a record with your name in the owner field.

It is also the cheapest gap on your list to close. You cannot manufacture five years of quota history, but you can know what an opportunity record holds, what "pipeline hygiene" means to the person saying it, why an empty next-step field is the most damning thing in a CRM, and where UK law draws its lines around B2B prospecting. You can do all of it this month, for nothing, on free tiers vendors deliberately give away — and then say something far better than a bluff: "Not in a commercial environment. I've built one, though — here's what's in it."

What you'll learn

• What a CRM actually is — accounts, contacts, leads, opportunities and activities in plain English, how they relate, what a record contains, and why one system must serve as the company's memory and its forecast.
• Salesforce and HubSpot in practice — a translation table between them and the five phrases an interviewer expects you to own.
• A worked day of CRM work — logging a call, advancing a stage against exit criteria, setting a dated next step, adding to the buying group, and the hygiene reports your manager will run on you.
• The wider stack — sales engagement, prospecting data, conversation intelligence, scheduling, e-signature and CPQ: what each does, why companies buy it, what a rep touches daily.
• AI in the sales stack in 2026 — where it earns its keep, the four ways it humiliates people, and the etiquette of AI-drafted outreach.
• Data discipline — hygiene as self-interest, "single source of truth", and UK GDPR/PECR ground rules for B2B prospecting.
• How to talk about tools with no access — free tiers, Trailhead and developer orgs, which certifications earn their hours, and the honest framing that beats a bluff.

1. What a CRM actually is

CRM — Customer Relationship Management — names two things: a category of software, and the discipline of keeping a structured record of every commercial relationship. When a job advert says "Salesforce experience preferred" it means the software. When a sales director says "our CRM is a mess" they mean the discipline has failed.

Underneath every CRM is an object model — a small set of record types and the relationships between them. Learn it once and every other CRM is a dialect, not a new language.

Account (HubSpot: Company). The organisation you sell to — an NHS trust, a pharma company, a GP federation. Everything hangs off it. Fields: legal name, sector, size, address, owner, parent account (so "Barchester Trust — Pathology" sits under the trust).

Contact. A person, linked to an account. The lab manager, the head of digital, the procurement lead. Fields: name, title, email, phone — and the ones reps skip and later regret: role in the buying group, preferred contact method.

Lead. Salesforce keeps a separate object for people not yet qualified. When one turns out to be real you convert it, which creates an account, a contact and optionally an opportunity in a single action. HubSpot does it differently: everyone is a contact from the start, and a lifecycle stage property records progress (subscriber → lead → MQL → SQL → opportunity → customer). Same funnel, different plumbing — and knowing the two vendors diverge here is itself a credibility marker.

Opportunity (HubSpot: Deal). A specific potential purchase. Three fields define it — amount, stage, close date — and every pipeline report and forecast the company commits to is computed from those three across all open deals.

Activity. The logged history: calls, emails, meetings, tasks, notes. Each is stamped to a who (contact) and a what (account or opportunity), which is how the system can later say "this deal has had no contact for 23 days".

Around these sit objects you should be able to name without having used: Products and Price Book, Quote, Contract, Case (a support ticket), Campaign (for attributing which marketing programme sourced a deal), and contact roles (the buying group attached to an opportunity).

How they relate. One account has many contacts and many opportunities. One opportunity belongs to one account and carries many contact roles. Every activity points at a person and, ideally, at the deal it concerns. Every record has an owner — the user accountable for it, which drives territory reporting, forecast roll-up and who gets paid.

Records are made of fields. Many are picklists — fixed lists of allowed values — because free text cannot be reported on: if six reps type "NHS", "N.H.S.", "nhs trust" and "National Health Service", no dashboard can count them. Administrators add custom fields and custom objects, and validation rules — logic refusing to save a record until conditions are met, e.g. no move to Proposal without a completed close plan.

What a record looks like. Illustrative, and the kind you would open twenty times a day:

(Illustrative record, not a real customer.) Note how much is structured rather than narrative. That is deliberate.

Memory and forecast, in one system. A CRM does two jobs that pull in opposite directions. As memory it is institutional recall: when you are on holiday, ill or gone, it is the only continuity the customer has, and a colleague should be able to pick up the thread without making the buyer repeat themselves. Memory wants narrative. As forecast it is a measurement instrument: sum open amounts by stage and close date, apply win rates, and you have the number the VP commits to the board — which drives hiring, cash and investor communication. Forecast wants structure.

Reps who write beautiful notes but leave stage and close date stale build a system that remembers everything and predicts nothing. Reps who tick fields but log no substance build one that forecasts confidently and remembers nothing, so the account becomes a stranger the day they leave. "It has to work as the company's memory and as its forecast at the same time, and those need different things from me" is a sentence very few candidates can produce.

Field note

In life sciences the CRM question has a second layer. Pharmaceutical field sales runs on industry-specific, compliance-heavy platforms rather than generic ones — historically Veeva CRM, built on Salesforce, and IQVIA's OCE. Veeva's Salesforce partnership ended in 2025 and its customers are migrating to Veeva's own Vault CRM over a window running to 2030, while Salesforce pushes its Life Sciences Cloud into the same space. You need not have used any of them. But at a pharma or medtech commercial interview, knowing this category exists — because calls on prescribers are regulated activity, not just sales activity — separates someone who has read the industry from an outsider.

2. Salesforce and HubSpot in practice

Salesforce is the enterprise default: enormous, endlessly configurable, and almost never used out of the box. Each customer's instance is an org, shaped over years by administrators and consultants into something specific. So "I've used Salesforce" tells an interviewer less than they would like — which is exactly why they follow up on what you did in it. HubSpot is the scale-up default: it began in marketing, grew into a full platform, and is deliberately opinionated where Salesforce is configurable, so a small team can run it without a specialist. A thirty-person UK health-tech startup will almost certainly be on HubSpot; a 3,000-person diagnostics manufacturer on Salesforce. Also common: Microsoft Dynamics 365, Pipedrive, Zoho, and the pharma-specific systems above.

The five phrases to own

"Salesforce admin." Not a job you are applying for, but a person you depend on. The admin configures objects, fields, page layouts, picklists, validation rules, permissions, automations, reports and dashboards, and handles imports and deduplication. In a scale-up it is one overworked RevOps person. When you say "the CRM won't let me do X", the admin is who you ask — and how you ask determines whether your requests get built. "Who owns the CRM here, and how do requests get prioritised?" is a genuinely good interview question.

"Reports and dashboards." A report is a query with a shape: pick a record type, filter it (my open opportunities closing this quarter above £25k), group it (by stage, by owner), summarise it (count, sum, average). A dashboard is a saved screen of charts built from reports, refreshed on a schedule, that managers stare at. Reps are expected to build their own core set: pipeline by stage, deals with no activity in 14 days, close dates in the past, weekly activity. Being the rep who builds their own instead of asking for a screenshot is a cheap reputation.

"Opportunity stages." The named steps a deal moves through, each with exit criteria — the verifiable event required before it may advance (Module 2). In the CRM they are a picklist with a default probability, often policed by validation rules. When an interviewer asks how you decide a deal has moved stage, they are testing whether you treat that picklist as a claim about evidence or as a mood ring.

"Pipeline hygiene." The health of the deal data: stages that reflect reality, close dates that came from the buyer rather than the quarter end, real amounts, dead deals marked closed-lost, and a dated next step on every open opportunity. It is inspected by report — no next step, no activity in N days, close date in the past, days in stage beyond threshold. Assume your manager runs those weekly; run them on yourself first.

"Single source of truth." One system holds the authoritative version and everything else defers to it. The enemy is the shadow spreadsheet — the rep's private tracker holding the "real" pipeline while the CRM holds a decorative one. It feels efficient and is quietly corrosive: the forecast breaks, the spreadsheet leaves with the rep, and (section 6) an unmanaged personal file of named contacts is also a data-protection problem.

A last framing point. "Have you used Salesforce?" is rarely a knockout and almost never a licence check. It is a proxy for three things: do you understand that commercial work is systematised, will you keep records without being chased, and can you talk to sales ops without an interpreter. Candidates who answer only the literal question lose to candidates who answer the real one.