Consultative Selling & ClosingFollow-up cadences and CRM hygiene · Lesson 15 of 16

CRM hygiene: records that help you sell

Article · 13 min · 8 min lecture

Video lecture

CRM hygiene: records that help you sell

11 chapters · about 8 min · full transcript

Coming soon

Chapter 1 of 11

CRM hygiene

  • What a CRM is for
  • Six hygiene rules
  • Stages = buyer actions
  • Weekly pipeline review
  • AI features + data protection

The narrated lecture is in production

Every chapter is scripted and ready. Browse the chapters and read the full transcript now — the video will appear here when it’s published.

Chapters

What a CRM is for

A CRM (customer relationship management system) is where you record contacts, conversations, opportunities and next steps. It can be a dedicated tool, the CRM features within a platform, or even a well-organised spreadsheet if you're starting out. The point isn't the software — it's never losing track of a person, a promise or a next step.

The hygiene rules

  1. Log every meaningful interaction within 24 hours. Date, channel, summary, what was agreed.
  2. Every open opportunity has a next step and a date. No next step = the deal is drifting.
  3. Use consistent stages. For example: Lead → Qualified → Discovery done → Proposal sent → Negotiation → Won / Lost.
  4. Record why deals are won or lost. This is your best source of learning.
  5. Keep contact data accurate and minimal. Only store what you need, with a lawful reason, and update or delete out-of-date information.
  6. Review weekly. Fifteen minutes to update stages, chase overdue next steps and close dead deals.

Fields worth tracking

  • Contact name, role, organisation, preferred channel, time zone.
  • Source (referral, inbound DM, event, campaign).
  • Qualification notes (need, budget, process, fit — or MEDDICC).
  • Stage, estimated value, expected decision date.
  • Next step and due date.
  • Notes: key quotes from discovery in the buyer's words.
  • Outcome and reason.

Stages and honest forecasting

Your pipeline is only useful if it's honest. Common problems:

  • Happy ears — marking a deal as likely because the buyer was friendly.
  • Zombie deals — opportunities with no activity for months still counted as live.
  • Sandbagging — deliberately underreporting to look good later.

Define stage criteria based on buyer actions, not your feelings. For example, "Proposal sent" only when the buyer has agreed to review it with the decision-maker.

Data protection basics

CRMs hold personal data, so data-protection laws apply in many places — for example the UK GDPR and EU GDPR, Saudi Arabia's Personal Data Protection Law, the UAE's federal data-protection law, and other regional laws. At a principle level:

  • Collect only what you need (data minimisation).
  • Use it only for the purpose people would reasonably expect.
  • Keep it secure: strong passwords, two-factor authentication, restricted access.
  • Don't export contact lists to personal devices or share them with others without authority.
  • Delete data you no longer need, and respect requests to access or delete personal data.

Worked example: a weekly pipeline review

Sadia, a junior sales executive at a Dubai agency, runs her Friday review:

  • Three deals in "Proposal sent" have no next step. She emails each with a specific question and a proposed call time.
  • One deal has had no response for six weeks. She sends a permission-to-close message and moves it to "Lost — no decision" with a note.
  • A won deal lacks a reason. She adds: "Won because of tracked-code reporting; competitor couldn't offer it."
  • Two contacts have changed roles; she updates their records.

Her forecast is now realistic, and her Monday plan is clear.

Using notes to sell better

Great CRM notes capture the buyer's words: "Worried partner will say it's too expensive" or "Main goal: fill weekday slots before Ramadan". When you prepare follow-ups or proposals, these quotes help you tailor your message — and show the buyer you listened.

Do and don't

Do log interactions promptly and set next steps for every deal. Do record win/loss reasons. Do protect personal data.

Don't keep zombie deals in your forecast. Don't store unnecessary personal information. Don't share contact lists without authority.

Hands-on: set up a clean pipeline in HubSpot or Salesforce

Both HubSpot and Salesforce let you define deal stages, required fields and probabilities (menu names change, so follow the current help docs). A sensible starting configuration:

StageExit criteria (buyer action)Required fields to leave the stage
DiscoveryPain and "why now" confirmedPain (in their words), lead source
QualifiedMetrics, decision process, economic buyer identifiedClose date, amount estimate, economic buyer
SolutionCriteria known; solution mappedDecision criteria, competitors
ProposalBuyer agreed to review with economic buyer on a dateProposal date, review meeting date
NegotiationCommercials under discussion; paper process knownPaper-process steps + dates
Closed won / lostSigned / clear noWin or loss reason (picklist + notes)

Use forecast categories separately from stages — for example Commit (you'd bet on it this period), Best case and Pipeline — so your forecast reflects judgement on evidence rather than stage alone.

A weekly pipeline review agenda (30 minutes)

  1. Hygiene (10 min): every open deal has a next step and date; close dates in the past are updated; zombie deals (no activity in, say, 30+ days) are closed or revived with a specific action.
  2. Top deals (15 min): for each, the MEDDICC/MEDDPICC gaps and the one action that closes the biggest gap.
  3. Learning (5 min): one win reason and one loss reason worth sharing.

AI features in CRMs — use with care

Modern CRMs include AI that summarises calls and emails, suggests next steps and scores deals (for example HubSpot's Breeze and Salesforce's Einstein and Agentforce features). They're useful for saving time, but: check summaries against what was actually said; don't let an AI score replace buyer-verified exit criteria; and make sure recording and transcription have the consent required in each participant's location.

Before and after: a CRM note

Before: "Good call. Interested. Follow up."

After: "Call 12 May (Zoom, 30 min) with Sana (Ops) and Imran (Owner). Pain: 'weekday covers down since Ramadan; reviews at Gulberg branch hurting us'. Metric: weekday covers. EB: Imran. Process: decide by 1 June after seeing two options. Competitor: in-house nephew doing social. Next step: send options A/B by 15 May; review call 17 May 11:00 (invite sent)."

Measuring CRM hygiene

Track: percentage of open deals with a future-dated next step (aim for all of them), deals with close dates in the past, deals with no activity in 30+ days, and forecast accuracy (forecast vs actual each month). Clean data makes every other lesson in this course easier to apply.

Key takeaways

  • A CRM exists so you never lose track of a person, promise or next step.
  • Every open opportunity needs a next step and a date.
  • Define stages by buyer actions to keep forecasts honest.
  • Apply data-protection principles: minimise, secure, delete when no longer needed.

Check your understanding

Quick questions to lock in the lesson. They don’t count towards your certificate.

  1. An opportunity has had no activity for three months but is still marked 'Negotiation'. What is this called?
  2. Which stage definition is most reliable?
  3. Which is good data-protection practice for a CRM?

Put it into practice

Set up (or clean up) your pipeline: define stage criteria based on buyer actions, add a next step and date to every open deal, and close any zombie deals.

Enrol for free to save your progress

Reading is always free. Enrol to keep your place, take the final assessment and earn a verifiable certificate.