CRM discipline and the pipeline review — Sales process, pipeline & forecasting

CRM — Customer Relationship Management software — is the system of record for everything above. Salesforce dominates enterprise (many enterprise job listings name it as a requirement); HubSpot is common at smaller companies (an early-stage health-tech startup will typically run HubSpot or similar). Both store the same four core objects:

Accounts — companies/organisations (an NHS trust, a pharma company, a GP practice).
Contacts — people, linked to accounts (the pathology lab manager; the practice manager; the CIO). Salesforce also has a separate Lead object for not-yet-qualified people, which gets converted into a contact + account (+ optionally an opportunity) once real — that conversion is literally the lead→opportunity funnel step happening in software.
Opportunities (HubSpot: Deals) — the potential purchases: amount, stage, expected close date, linked account and contacts, and a next step field.
Activities — the logged record of calls, emails, meetings, demos and tasks against all of the above.

Why hygiene matters — "hygiene" (accurate, current CRM data) is the standard word: management runs the business on reports built from this data. Forecasts, coverage dashboards, conversion analytics, marketing attribution — all only as good as what reps log.

There's a personal angle too: if you're ill, promoted or on holiday, the CRM is the only continuity the account has, and at commission time the opportunity record is the paper trail.

The non-negotiables:

every open opportunity has a next step with a date;
stages reflect evidence;
close dates are buyer-validated, not quarter-end defaults;
dead deals get closed-lost promptly;
meaningful activities get logged.

Interviewers ask about CRM discipline partly to filter out the (very common) rep who treats it as bureaucracy. Your line as a career-changer: you regard the CRM as the operating system of the job, not admin — and if you have kept any system of record scrupulously (a project tracker, a lab notebook, a well-run job-search spreadsheet), offer it as evidence the habit already exists.

Field note
Every CRM you will ever inherit is dirtier than anyone admits: duplicate accounts, close dates set to 31 December the previous January, next-step fields reading "follow up". Nobody expects a new joiner to fix that — what they notice is whether your records are clean. In practice hygiene is a habit of minutes, updating the record in the five minutes straight after each call; reps who save it for a Friday-afternoon purge never catch up.

The pipeline review is the weekly ritual where this all becomes visible: you and your manager (sometimes the wider team) walk through your open deals. Its purpose is threefold — validate the forecast, unblock stuck deals, coach. The worst thing you can be in one is vague.

The standard grammar for talking about a deal — worth internalising as a template — is five items: stage, value, close date, next step, risk.

"Millbrook Trust pathology — evaluation stage, £85k ACV, forecast best case for 30 November. They completed the POC last week against the success criteria we agreed and it passed on all five. Next step: results review with the lab director and the deputy CFO, booked for Tuesday. Risk: funding is coming from this year's digital budget and their IG review hasn't started — if it isn't underway by mid-October, this slips to Q1, and I'd move it out of best case."

(Illustrative deal, not a real one.) Every clause is verifiable, dated and buyer-anchored. Practise saying three deals in this format aloud until it's automatic — it's also the format for "tell me about a deal you worked" and for interview role-plays.

Voice from the field
"Maniacally qualifying deals early in the quarter by visiting the Champions of your reps' forecasted deals in the first month of a quarter is one of the surest methods of gaining a deep understanding of your forecast."
— John McMahon, The Qualified Sales Leader (2021)

How this shows up in interviews

1. "Walk me through your pipeline maths for a £600k quota." Do the four-division chain out loud, stating assumptions: "At £40k ACV that's 15 deals; at a 25% win rate that's 60 opportunities; that's £2.4m of pipeline across the year — 4x coverage, which is what a 25% win rate implies; then divide by my conversion rates to get weekly activity." Naming that coverage is the inverse of win rate, and distinguishing annual pipeline generation from point-in-time coverage, marks you as fluent rather than coached.

2. "How would you build pipeline in your first 90 days?" Structure beats heroics: learn the ICP and message (ride along on live deals, listen to call recordings), map the territory into a tiered target list, then run a disciplined outbound cadence alongside inbound follow-up — and state the maths you're building towards ("if the quota implies 15 opportunities a quarter, here's the activity that produces them").

For a long-cycle NHS product, add the worked-example-3 insight: early pipeline generation is really building next year's number, so you'd also inherit and accelerate in-flight deals. Mention warm routes only if you genuinely have them — a prior industry network, communities you belong to, events you can work; if you don't, say the honest version: your first-quarter pipeline will come from disciplined outbound volume and fast learning loops, and that is a perfectly respectable answer.

3. "What win rate and cycle length would you assume for our product, and why?" They're testing whether you researched their motion. For a GP-practice velocity product, reason from any published funnel (the startup in worked example 2 published 70% demo-to-sign in its adverts, so the game is demo volume); for enterprise NHS AI, assume 20–30% and a 6–18 month cycle dominated by procurement, IG and funding cycles. Transparent reasoning from their deal size and buyer is the win; a wrong number with visible reasoning is fine.

4. "How do you decide what to put in commit?" Define the category, then anchor on buyer-verifiable evidence: commercial terms agreed, procurement in motion, a buyer-validated close plan with dates. Contrast with best case (real but with a material unresolved item) and say the values sentence: you'd rather commit a smaller number you'll hit, because the VP builds hiring and board guidance on it.

5. "A deal you had in commit just slipped to next quarter. What do you do?" Diagnose honestly first: was the close date ever buyer-validated, or was it hope? Then tell your manager immediately (no surprises), work the close plan to compress the slip, and check whether anything in best case can be accelerated to cover. Finish with the systemic fix — mutual close plans and earlier procurement engagement, so dates come from the buyer's process, not your quarter-end.

6. "What does good CRM hygiene look like to you?" Every open opportunity carries a next step with a date; stages reflect exit criteria met, not optimism; close dates are buyer-validated; dead deals are closed-lost promptly. Give the "why": the forecast, the coverage maths and the company's planning all run on this data — then make it personal: you treat the CRM as the operating system of the job, not admin, and you can point to any record-keeping you have done rigorously (a project log, research data, a tracked job search) as proof the habit is already yours.

7. "You're at 60% of target with six weeks left. Talk me through your thinking." Run the same arithmetic as worked example 4 with your own numbers: remaining target, closable pipeline × win rate = expected landing, coverage vs required.

Then the four velocity levers prioritised for a six-week horizon: win-rate and cycle moves on live deals first (multi-thread stakeholders, tighten close plans), pull-forwards second, new pipeline third (it mostly won't close in six weeks — build it anyway for next quarter). Close by saying you'd keep the forecast honest rather than defend a number you no longer believe.

8. "Tell me about a deal you worked from start to finish." If you have no sales deal to tell, interviewers of career-changers know that — choose any true episode where you moved a person or organisation from first contact to a committed decision: winning a sponsor for a society, getting a research collaboration approved, landing a job offer, selling a committee on a plan, closing a customer in a side venture.

Then narrate it in funnel language: how it was sourced, how it was qualified, the evaluation against pre-agreed success criteria, the stakeholders, proposal, sign-off machinery, outcome. Using this module's vocabulary accurately while telling a true story is what makes "no quota history" read as "ready for quota" instead.

Cheat sheet

The funnel: Lead (a name) → MQL (marketing's rules say worth attention) → SQL (a human confirmed it's real) → Opportunity (qualified deal: value + stage + close date in CRM) → Closed-won/lost. Conversion points: scoring → first-call judgement → qualification → signature.

Stages & exit criteria: Discovery → Qualification → Demo/Evaluation → Proposal → Negotiation → Procurement/Legals → Closed. A deal sits in the stage its evidence supports; exit criteria should be buyer-verifiable ("decision-maker reviewed proposal and agreed next steps", not "I sent it"). NHS procurement (DTAC, DSPT, IG, clinical safety) is a real stage — plan elapsed time for it.

The maths chain (memorise):

Deals needed = quota ÷ ACV
Opportunities needed = deals ÷ win rate
Pipeline needed = quota ÷ win rate (= opportunities × ACV)
Activity needed = opportunities ÷ step-conversion rates
Coverage = open pipeline ÷ remaining quota — rule of thumb 3–4x, because coverage ≈ 1 ÷ win rate. Count only pipeline closable in the period.
Expected landing = closed + (closable pipeline × win rate).

Key example: £600k quota, £40k ACV, 25% win rate → 15 deals, 60 opps, £2.4m pipeline (4x), ~15 discovery calls/month at 1-in-3 qualification. One NHS-facing startup's funnel (2026 adverts): 10 live practices/week ÷ 70% demo-to-sign ≈ 15 demos/week ≈ 3/day.

Deal-size vocabulary: ACV = one contract's value per year · ARR = whole company's annual recurring revenue · TCV = full contract value over its term incl. one-offs. 3-year £120k deal: ACV £40k, TCV £120k.

Velocity: (opps × avg deal value × win rate) ÷ cycle days = revenue/day. Four levers: more opps · bigger deals · higher win rate · shorter cycle. Harder qualification trades lever 1 up into levers 3–4.

Forecast categories: Commit (hold me to it — buyer-verified close plan) · Best case (possible; one material unknown) · Pipeline (real, not this period). Accuracy ≈ attainment in a VP's eyes. Sins: sandbagging (hiding sure deals to look heroic) and happy ears (forecasting politeness as intent). Slipped = close date pushed; serial slipping = the date was never buyer-validated.

CRM: Accounts (orgs) · Contacts (people) · Opportunities/Deals (value, stage, close date, next step) · Activities (logged touches). Hygiene = next step dated on every deal, evidence-based stages, buyer-validated dates, prompt closed-losts. Deal review grammar: stage — value — close date — next step — risk.

References & further reading

Aaron Ross & Marylou Tyler, Predictable Revenue (2011) — the book that codified the SDR/AE split and the lead-source thinking behind section 1's funnel; read it for the argument that qualified opportunities created per month are the leading indicator of revenue.
Mark Roberge, The Sales Acceleration Formula (2015) — HubSpot's first sales leader treats hiring, training and pipeline as an engineering problem; the single best book on the metrics-driven sales culture this module teaches you to speak.
John McMahon, The Qualified Sales Leader (2021) — a five-time CRO on qualification, champions and forecast inspection in enterprise sales; the closest thing in print to sitting inside a real pipeline review.
Jason Jordan & Michelle Vazzana, Cracking the Sales Management Code (2012) — research-based distinction between metrics you can manage (activities) and metrics you can only measure (results); sharpens the activity arithmetic in section 3.
Jacco van der Kooij & Fernando Pizarro, The SaaS Sales Method (2018) — Winning by Design's compact "sales as a science" treatment, exposing the maths that links marketing, sales and customer success into one revenue model.
David Skok, SaaS Metrics 2.0 (forEntrepreneurs essay, 2013) — the canonical free reference on ARR, churn, CAC and unit economics; the wider metric context that interviewers at funded scale-ups assume you have.
Matt Heinz, Sales Pipeline Radio (podcast) — short practitioner interviews focused squarely on pipeline, demand generation and forecasting; useful for absorbing how operators actually talk about coverage and conversion.
Jason Lemkin, SaaStr blog — the "Dear SaaStr" series — a searchable archive of blunt, short answers on quota setting, coverage ratios and forecast categories; ideal for pre-interview calibration on what "good" looks like at a SaaS scale-up.