Become an SDR/BDR · Beginner · ~4 hours

CRM & Sales Technology

Understand CRM records, pipelines, reporting and the privacy responsibilities of sales data.

Status: Catalogue ready. This lesson version is available in review mode while subject-matter, accessibility and assessment checks are completed.

CRM as a shared revenue workspace

Records, objects and data minimisation

45 min

course progress0 of 3 lessons complete

By the end of this lesson

Explain the purpose of common CRM records and relationships.
Enter relevant business information accurately and consistently.
Apply data minimisation and privacy-safe note practices.

Build a clear mental model

A CRM is a shared record of a business relationship, not a personal notebook and not a complete biography of a contact. Common records may include an account or organisation, a person, an activity, an opportunity and a task. The exact names differ by system, but the principle is stable: each record should answer a work question and have an owner. If a contact's role matters to the decision, record the role. If a personal detail does not affect the work, do not add it simply because it was discovered. Data quality depends on definitions. A company name, role, source, contact preference, last interaction and next action should use agreed fields and formats. Free-text notes can provide context, but they should not become a place to bypass required permissions or write subjective judgements. A CRM record should be understandable by the next authorised colleague and safe if the customer requests an explanation of how their information is used. Evidence makes learning and commercial work safer. In a busy workplace, people often move quickly from an observation to a conclusion: a team has grown, therefore its process must be failing; a person asked a question, therefore they are ready to buy; a learner used a spreadsheet, therefore they can manage a CRM. A better habit is to name the observation, the interpretation and the question that would test it. This does not slow every decision down. It directs attention to the assumptions that could create the most harm if they are wrong. It also helps a colleague continue the work without having to guess what was meant. Use a simple evidence note: context, observable detail, impact or desired change, uncertainty and next action. Context describes the setting without exposing personal or confidential information. Observable detail records what someone did, said or published, using their own words where that is appropriate. Impact describes a consequence without inventing a number. Uncertainty names what has not yet been checked. The next action should have an owner and should be easy to accept, decline or revise. This pattern works for a learning reflection, a customer conversation, a process review and a career example. Good evidence is also proportionate. A small practice task does not require a research report, and a complex business decision should not rest on a single enthusiastic comment. Label sources and dates, keep the minimum information needed, and be honest about the limits of the conclusion. When a learner cannot share a workplace example, a fictional case can demonstrate the reasoning without disclosing private information. The aim is dependable judgement, not a performance of certainty.

Apply the method in a real conversation

For a fictional account, create only the minimum records needed to support the next action. Use a controlled value for industry or stage, a date for activity and a short evidence-labelled note. Link related records rather than duplicating information. Before saving, check spelling, source, permission, owner and whether the information is still relevant. When importing, test a small sample, map fields deliberately and document the source and transformation. Never import a real contact list into a learning exercise. A repeatable method turns a concept into behaviour. First, define the outcome in plain language: what should be easier, safer, clearer or more measurable after this work? Second, identify the people, systems and constraints involved. Third, choose the smallest useful action that will create new information. Fourth, review what happened and decide whether to continue, change direction or stop. This sequence avoids the common trap of producing activity without learning. It also makes it easier to explain why a particular message, spreadsheet, call, meeting or system change was chosen. When applying the method, use inclusive language and make room for different communication styles. A person may need extra processing time, a written alternative to a live role-play, captions, a transcript or a clear agenda. Accessibility is not a separate favour; it improves the quality of information available to everyone. Ask what format helps, avoid assuming confidence from speed of speech, and record only relevant support needs through approved processes. Review the work against the original outcome rather than against a vague idea of being busy. Did the note help another person act? Did the question invite a useful answer? Did the process reduce avoidable effort? Did the learner protect confidential information? If not, revise the method and try again. A respectful correction is a sign of professional maturity, not evidence that the first attempt was worthless.

Use judgement and leave a useful record

Convenience can create privacy risk. Do not infer sensitive characteristics, store passwords or paste private correspondence into a general record. Follow retention and deletion rules, and ask the data owner when a field's purpose is unclear. A request to remove or correct information should use the approved process. The CRM is there to support a relationship, not to create an unrestricted view of people across teams or businesses. Professional judgement includes deciding what not to do. A request may be outside scope, a data source may be unreliable, a buyer may not have a current need, or a learner may need more practice before taking on a complex task. Saying “not yet”, “I do not know” or “this is not the right fit” can protect trust. It is especially important in technology sales, where optimistic language can create expectations about product capability, implementation, security or career outcomes that no one has verified. Pressure-free practice means giving people a clear choice and enough context to make it. Do not use manufactured scarcity, fear, personal vulnerability or hidden follow-up. Explain what will happen next, what information is required and how a person can pause or opt out. In a learning context, feedback should describe the work and the next improvement rather than label the person. In a customer context, the same principle appears as accurate notes, transparent limits and a willingness to recommend a safer alternative. Finally, make the work reviewable. Keep a short record of the decision, the evidence used, the uncertainty that remains and the date to revisit it. Never put real personal data, credentials, private contact details or confidential employer information into a practice exercise. These habits build trust gradually and create evidence that can be improved, audited and shared with the right people.

Workplace example

Fictional Northstar Analytics keeps an account record, two role-based contacts and an opportunity note. The learner records the source and business relevance, leaves out personal details and marks the finance contact as not yet confirmed rather than guessing.

Try this walkthrough

1.Name the work question the CRM record must support.
2.Create fictional account, contact, activity and task records using controlled fields.
3.Add a concise evidence-labelled note and owner.
4.Review source, permission, relevance and retention before saving.

Watch for these traps

Using free text for information that has a controlled field.
Copying personal or sensitive details because they are available.
Guessing a role, contact preference or decision authority.
Duplicating records instead of linking them.

Practice studio

Make a decision. Test a response. Leave evidence.

Use the case from this lesson to practise judgement without creating a score or changing your course record.

Scenario decision

Fictional Northstar Analytics keeps an account record, two role-based contacts and an opportunity note. The learner records the source and business relevance, leaves out persona…

Choose a response

Branching roleplay

A colleague asks you to move this situation forward. What do you say next?

Evidence workspace

Draft a short known / assumed / next note from the fictional case. Use fictional details only.

KnownAssumedNext step

This is a session-only practice draft. It is not saved, graded or added to your learning record. Never enter real personal or confidential information.

Practical assignment

Create a fictional CRM data dictionary and four sample records for a technology buyer. Define each field's purpose, source, allowed values and privacy check, and include one example of information deliberately excluded.

Pass this lesson's knowledge check before recording it as complete.

Portfolio evidence

Practical portfolio project

Design a fictional CRM pipeline with clean contact records, defined stages, follow-up tasks and a simple report.

Turn the practical project into a bounded evidence record. Save a draft while you work, then submit it for human review when it is ready.