Talking about tools in an interview with no hands-on access — The sales stack: CRM, tools and data discipline

The reframe that makes this work: an interviewer is not checking whether you have a licence — they are checking whether you will be a burden. The fear is a hire who needs three months of hand-holding to grasp why records matter. You defeat it with evidence, and the evidence is free.

Build something small and real. The most effective move is to build an actual instance and describe what is in it. HubSpot's free CRM tier is the fastest route: an account costs nothing and gives you working contact and company records, a deal pipeline with configurable stages, activity logging, tasks and basic reporting — every concept in sections 1 to 3 in usable form. Roughly two hours: pick a real target market (UK diagnostics companies, or NHS trusts in one region); create ten company records; add two or three contacts each with plausible roles — clinical lead, procurement, IT/IG; rename the pipeline stages to a proper sales process and write the exit criteria down so you can recite them; create six deals with amounts, stages, close dates and a dated next step on each; log activities so there is a history; then build one report and one dashboard — pipeline by stage, and deals with no activity in 14 days.

You can now say, truthfully: "I built a small CRM instance with a defined stage model, exit criteria per stage, and a hygiene dashboard I run on myself." That is a more specific claim about CRM competence than most experienced reps make about themselves.

Salesforce takes more effort and is worth it for enterprise targets. Two free routes complement each other: a Developer Edition org — a free, full-featured instance signed up for at developer.salesforce.com/signup — and Trailhead, Salesforce's free learning platform, which teaches through short modules with hands-on challenges verified inside a Trailhead Playground.

Voice from the field
Salesforce's own documentation describes a Trailhead Playground as a free Developer Edition org that does not expire, pre-loaded with the Trailhead helper package and sample data, with several available per account — in other words, a real Salesforce instance you can break, rebuild and practise in for as long as you like, at no cost.
— Salesforce Help and Trailhead documentation (paraphrased)

Aim at an outcome rather than badge-collecting. Eight to twelve hours: complete the admin-oriented beginner trails, and in your own playground create a custom field, build a report and dashboard, walk an opportunity through the stages, and set up a validation rule. If you can then explain what a validation rule is for — exit criteria enforced at the point of data entry — you have crossed from "has heard of Salesforce" to "understands why companies configure it".

Certifications worth the hours. Be selective; certifications signal effort, not competence, and the wrong one signals the wrong career. HubSpot Academy is free end to end and its sales-relevant courses and certifications run a few hours each — the best value per hour available to a career changer, and shareable on LinkedIn. Salesforce's entry-level credential — Platform Foundations, previously the Salesforce Certified Associate — targets people with zero to six months' exposure and has no prerequisite; learning is free via Trailhead, the exam is paid. Worth it if you want a hard signal, unnecessary if badges plus a built playground already tell the story. Salesforce Certified Administrator is serious and well respected, and it is the right investment for a sales operations or RevOps path — but for an AE role it is over-engineered, and can read as a signal that you would rather configure systems than carry a number. Add a Sales Navigator trial or Apollo's free tier for a week and you will learn more about prospecting workflow than a month of reading.

Budget honestly: two hours in HubSpot, eight to twelve on Trailhead plus playground practice, a part-time week inside a data tool building a target list for a company you are interviewing with. Under twenty hours, and it converts the worst question in your interview into one of the better ones.

The honest framing, adapted to what you have actually done:

"Not in a commercial environment — I want to be straight about that. What I have done is build my own: a HubSpot instance with a defined stage model and written exit criteria, a hygiene dashboard for deals with no next step or no recent activity, and enough Trailhead and a Salesforce developer org to be comfortable with objects, reports and validation rules. So I know what an opportunity record holds, why the next-step field matters more than it looks, and how a pipeline gets inspected. What I don't know is how your org is configured — and that's the part I'd expect to learn from your team in the first fortnight."

Four things make that work: it concedes the gap immediately, replaces it with something specific and checkable, demonstrates the concepts rather than the clicks — which is what transfers between systems — and names the realistic learning curve, which is configuration, not concepts.

What not to say, ever: any version of "yes, I've used Salesforce" built on a Trailhead account. One follow-up ("how was your org set up — did you work leads, or straight to opportunities?") and the collapse is unrecoverable, because it converts a skills gap into an honesty problem. Avoid dismissiveness ("CRM is just admin, I focus on relationships"), which confirms exactly what a sales manager fears about a hire. And do not oversell: "I built X in a free HubSpot instance" is credible; "I've managed a CRM" is not.

Then the transfer argument, stated once and dropped: tool proficiency is a few weeks of on-the-job learning, and every company retrains new joiners on its own configuration anyway. Judgement about what belongs in the record — evidence-based stages, buyer-validated close dates, a dated next step on every deal, honesty when the number is bad — takes far longer to instil and does not ship with the software. Show that you already have the second thing and the first stops being interesting.

How this shows up in interviews

1. "Have you used a CRM? Have you used Salesforce?" Answer honestly in one sentence, then convert. No commercial use; here is what you built and what you understand. Name the object model (accounts, contacts, opportunities/deals, activities), name the artefact (a stage model with exit criteria, a hygiene dashboard), and name the gap you expect to close on the job — their configuration. If you have maintained any adjacent system of record rigorously (a project tracker, a lab notebook, a research database), offer it as evidence the habit exists rather than as a claim of equivalence. The failure modes are silence, dismissiveness and bluffing; all three are worse than the honest answer.

2. "What does good CRM hygiene look like to you?" Give the non-negotiables as a list, because a list sounds like a practice rather than an opinion: a dated next step on every open opportunity; stages reflecting exit criteria met, not optimism; close dates derived from the buyer's process; dead deals closed-lost promptly; activity logged within minutes, not on Friday. Then the why at two levels — the company's (forecast, planning and territory design all run on this data) and yours (commission is reconciled from the record, and continuity for the customer depends on it). Finish with the memory-and-forecast framing if there is room.

3. "Walk me through what you'd do in the CRM straight after a discovery call." A workflow question wanting specifics. Log within five minutes: who was on it, what they said in their own words, what changed, what was agreed. Update only the structured fields the conversation actually changed — stage if the exit criterion is now met, close date if the buyer gave you one, amount if scope moved. Add any new stakeholder as a contact with a role on the opportunity. Set the next step with a date and a named participant. Create the follow-up task. Mentioning that you would push a conversation-intelligence auto-summary into the record rather than retype it lands well: it shows you think about the stack, not just the CRM.

4. "Which sales tools are you familiar with?" Do not recite a list you cannot support. Structure by category and purpose — system of record, prospecting data, sales engagement, conversation intelligence, scheduling, e-signature, CPQ — saying what each is for and why a company pays for it. Then be precise about your own exposure: what you have actually used (a Sales Navigator trial, Apollo's free tier, HubSpot's free CRM, Trailhead and a developer org) versus what you know about but have not touched. A candidate who explains why a company buys Gong beats one who has logged into it and cannot say what it changed.

5. "How would you use AI in this role?" Answer with a boundary, not enthusiasm. Good uses: research briefs, call summarisation and CRM population, first-draft outreach, deal-risk flags as a second opinion. Boundaries: never send an unverified factual claim about a person or company; never let a model's description of the product reach a customer unread, which in regulated markets is a compliance point rather than a style one; treat scores as a prompt to investigate, not a verdict; keep personal data inside approved tools. Then the etiquette line — announce recording bots and accept refusal instantly. Most candidates are either uncritically keen or vaguely suspicious; neither sounds like judgement.

6. "What do you know about GDPR in the context of prospecting?" Proportionate awareness, delivered calmly. UK GDPR governs personal data; PECR governs electronic marketing; both apply. PECR treats corporate subscribers (limited companies, LLPs, Scottish partnerships) differently from individual subscribers (individuals, sole traders, ordinary partnerships), which is why cold B2B email is workable here. Calls are screened against TPS and CTPS plus an internal do-not-call list. The usual lawful basis is legitimate interests, which needs a documented assessment rather than an assertion, and people must be told where their data came from. An objection to direct marketing is absolute — you stop, everywhere, immediately. Close with the escalation line: anything genuinely borderline goes to whoever owns compliance.

7. "Our team runs Salesforce, Outreach and Gong. How quickly could you get up to speed?" Be concrete rather than confident. Week one: get access, shadow live calls, read six months of a live account's history, learn the stage definitions and their exit criteria, find out who owns the CRM and how requests are prioritised. By week three: run your own hygiene reports, work sequences with your own personalised top-of-sequence copy, use the call library to learn objection handling from the best rep on the team. And what you will not pretend: their configuration is specific and you will have questions. Adding the reverse question — "which of these do your AEs use daily, and which sit with ops?" — turns the answer into a conversation.

8. "How would you keep your pipeline accurate when you're busy?" A question about systems, not willpower, so answer with a system. The five-minute rule after every call. A saved view of deals with no next step, checked every morning before anything else. A weekly self-inspection using the same reports your manager runs, so their pipeline review holds no surprises for either of you. A standing habit of marking dead deals closed-lost rather than letting them rot. Finish honestly: the reason is not compliance, it is that the pipeline is the only instrument you have for diagnosing your own performance, and a dirty one blinds you first.

Cheat sheet

Object model: Account (HubSpot: Company) = the organisation · Contact = a person at it · Lead = Salesforce's pre-qualification object, converted into Account + Contact (+ Opportunity); HubSpot instead uses lifecycle stages · Opportunity (HubSpot: Deal) = a specific potential purchase defined by amount + stage + close date · Activity = logged calls, emails, meetings, tasks. Also: Products/Price Book, Quote, Contract, Case, Campaign, contact roles (the buying group). Every record has an owner; picklists exist so reports can count things; validation rules enforce exit criteria at data entry.

Two jobs at once: the CRM is the company's memory (narrative — what they said, what changed) and its forecast (structure — stage, date, amount). Do only one and it fails at the other.

Salesforce ↔ HubSpot: org ↔ portal · Account ↔ Company · Opportunity ↔ Deal · field ↔ property · Flow ↔ Workflow · Cadence ↔ Sequence · List View ↔ Saved view. Salesforce = enterprise, every org configured differently. HubSpot = scale-up, opinionated, runnable without a specialist.

Five phrases to own: Salesforce admin (the person configuring objects, fields, validation rules, reports, permissions) · reports and dashboards (a report is a filtered, grouped, summarised query; a dashboard is a screen of charts built from reports) · opportunity stages (a picklist that is a claim about evidence) · pipeline hygiene (real stages, buyer-validated dates, real amounts, prompt closed-losts, dated next steps) · single source of truth (one authoritative system; the enemy is the shadow spreadsheet).

A day of CRM work: morning hygiene sweep (no next step, no activity 14 days) → run the call → log within five minutes (who / their words / what changed / what was agreed) → advance the stage only if the exit criterion is met → set the close date from the buyer's process → add new stakeholders as contact roles → next step with a name and a date. An empty next step is the most damning field in the system — it proves no next action was agreed. It also fails if undated, or if only you do it.

The stack in four rings: data in (Sales Navigator, ZoomInfo, Cognism, Apollo) · engagement out (Outreach, Salesloft, HubSpot Sequences) · intelligence back (Gong, Chorus, Clari) · paperwork through (Calendly/Chili Piper, PandaDoc, CPQ, DocuSign). Everything writes back to the CRM or it is failing. Glue: activity capture, bi-directional sync, enrichment.

CPQ = Configure, Price, Quote: valid combinations, priced by rule, quoted with discount approval workflows — margin protection and error prevention, part of quote-to-cash. Plan for the approval delay; better, design the deal to avoid the exception.

AI — good at: call summarisation and CRM field population · research briefs · first-draft outreach · deal-risk and forecast-hygiene flags · coaching at scale. AI — embarrassing at: fabricated personalisation (never send an unverified claim about a person or company) · generic sequences at scale (reply rates fell; Google/Yahoo/Microsoft enforce authentication, one-click unsubscribe and low spam thresholds) · over-trusted scores (a score is not evidence; exit criteria are) · unedited product claims in front of customers (a compliance risk in regulated markets). Etiquette: assistance yes, deception no; never simulate an observation you did not make; apply the defensibility test ("how did you know that?"); keep personal data in approved tools; announce recording bots and accept refusal.

UK rules, short version: UK GDPR = personal data; PECR = electronic marketing; both apply. PECR corporate subscribers (Ltd, LLP, Scottish partnerships) sit outside the consent rule for unsolicited marketing email; individual subscribers (people, sole traders, ordinary partnerships) do not. Never conceal sender identity; always give a working opt-out. Calls: screen TPS + CTPS + your own do-not-call list, identify yourself, display a number. Lawful basis is usually legitimate interests — documented assessment, not assertion. Tell people where their data came from. Objection to direct marketing is absolute — stop, everywhere, immediately. Never put patient or special-category data in a sales CRM. The Data (Use and Access) Act 2025 raised maximum PECR penalties from £500,000 to UK GDPR levels (up to £17.5m or 4% of global turnover).

No-access credibility plan (under 20 hours): free HubSpot CRM — 10 companies, 20 contacts, a named stage model with written exit criteria, 6 deals with dated next steps, one report, one dashboard (~~2 hrs) · Trailhead + a free Developer Edition org at developer.salesforce.com/signup — custom field, report, dashboard, validation rule (~~8–12 hrs) · a Sales Navigator or Apollo trial to build a real target list (~1 week, part-time). Certifications: HubSpot Academy (free, best value per hour) · Salesforce Platform Foundations, formerly Associate (entry-level, free learning, paid exam) · Salesforce Administrator (serious, but over-engineered for an AE — right for a RevOps path).

The line: "Not in a commercial environment — I've built my own: a HubSpot instance with a defined stage model and exit criteria, and a hygiene dashboard I run on myself. What I don't know is how your org is configured, and that's what I'd expect to learn in the first fortnight." Never claim enterprise experience you do not have; one follow-up question turns a skills gap into an honesty problem.

References & further reading

ICO — Business-to-business marketing (ico.org.uk) — the regulator's own plain-English page on how PECR and UK GDPR apply to B2B, including the corporate versus individual subscriber distinction. The single most useful page on this list for a UK salesperson; read it before your first cold email.
ICO — Guidance on direct marketing using electronic mail (ico.org.uk) — the detailed email and text rules: solicited versus unsolicited, consent and the soft opt-in, the prohibition on concealing sender identity, and the requirement to provide a valid opt-out address.
ICO — Guidance on direct marketing using live calls (ico.org.uk) — the calling rules, including TPS and CTPS screening obligations and identification requirements. Read it properly if any part of your role involves the phone.
Salesforce Trailhead (trailhead.salesforce.com) — free, structured, hands-on learning across Salesforce administration, sales fundamentals and AI, with challenges verified inside a free Trailhead Playground. The most efficient route from zero to credible Salesforce vocabulary.
Salesforce Developer Edition sign-up (developer.salesforce.com/signup) — a free, full-featured Salesforce instance to build in. Pair it with Trailhead: read a module, then build the thing yourself in your own org.
HubSpot Academy (academy.hubspot.com) — free courses and certifications covering CRM use, pipeline management, reporting and inbound sales, alongside HubSpot's free CRM tier. The fastest way to have something real to point at in an interview.
Gong Labs (gong.io/resources/labs) — Gong's research arm, publishing analysis of large volumes of recorded sales conversations on multi-threading, discovery, objection handling and deal risk. Vendor research, so read it sceptically, but the best free evidence base on what correlates with won deals.
Salesforce — State of Sales research (salesforce.com/sales/state-of-sales) — the recurring large-sample survey of sales professionals covering AI adoption, how sellers' time is really spent, and data-quality complaints. Useful for calibrating what the industry currently claims about itself.