What is CRM? A practical guide to customer records.
Understand what a CRM does, when Excel can still work and how to keep a customer conversation separate from a sales opportunity and the next task.
CRM stands for Customer Relationship Management. It is the practice of managing relationships with current and potential customers; CRM software helps organize the records and work behind those relationships. A useful sales record tells you who the company is, what actually happened, which buying discussion is open and what you should do next. Buying software alone does not create that discipline.
CRM starts with a relationship, not a list.
A contact list answers “Who could we contact?” Relationship management also answers “What did we agree, what remains unresolved and who will act next?” It applies before and after a sale. Sales, marketing and customer service can use different parts of that history.
CRM software can support contact records, conversation history, sales stages, tasks and reporting. Its exact scope varies. Shared access, automatic email capture, integrations, mobile apps and AI features are capabilities to check in a specific product and plan, rather than assumptions attached to the term CRM.
Keep the company, history and next action distinct.
| Record | Question it answers | Example and boundary |
|---|---|---|
| Company / account | Which business is this? | Duru Packaging, company reference C-014. A researched business is not automatically a customer. |
| Contact | Which person is involved, and in what role? | Elif, the company’s commercial contact. Her role does not alone establish purchase authority. |
| Activity / interaction | What actually happened, and when? | Quotation sent on 5 October. A completed event stays in the history when plans change. |
| Opportunity / deal | Which specific possible purchase are we discussing? | A quotation form project requested by the buyer. Separate projects at one company may need separate records. |
| Task | What will someone do next, and when? | Ayşe to check the review outcome on 27 October. A future task is not a completed conversation. |
The company and people are fictional. These are logical distinctions, not a claim that every CRM uses the same objects, names or screens.
One company can have several contacts and several buying discussions. Keep their relationships visible rather than duplicating the whole company for every new person. Conversely, do not merge separate companies just because they share an address or domain; use the company-record decision guide.
A sales pipeline is the set of opportunities arranged by your defined stages. The stage should describe the current buying discussion. “Email sent” may be an activity, while “quotation under review” describes a deal state. Define what evidence permits each stage; a software label cannot prove that evidence exists.
Replay the events without overwriting the history.
Entirely fictional example: Ayşe sells quotation-form implementation services. Duru Packaging and Elif are invented. On 2 October 2026, Elif asks for a quotation for a defined form project. The seller’s spreadsheet later contains one compressed note: “Elif — quote sent — call 12 Oct — review moved.” Budget and final purchase authority are unconfirmed. No sale or Anivo result is represented.
| Event | History to retain | Current work after the event |
|---|---|---|
| 5 October: Ayşe sends the requested quotation. | Record the quotation version and date. Elif agrees to a check-in on 12 October. | Opportunity: quotation under review. Task: Ayşe checks on 12 October. A sent quotation is not an accepted order. |
| 10 October: Elif says the internal review moved to 26 October and agrees to a check-in on 27 October. | Append the new statement and date. Retain the 5 October event and earlier agreement. | Opportunity: review postponed. Mark the 12 October task superseded, with the reason; create the 27 October task. Do not leave both as current follow-ups. |
The later statement changes current work, not the facts known on 5 October. An agreed check-in is not a promised decision or confirmed budget.
| Field | Recorded value |
|---|---|
| Company and contact | C-014 / Duru Packaging / Elif, commercial contact. All fictional. |
| Opportunity | Quotation-form implementation; buyer requested a quotation on 2 October. Current state: review postponed. |
| History | 5 October: requested quotation sent; 12 October check-in agreed. 10 October: review moved to 26 October; 27 October check-in agreed. |
| Previous task | 12 October check-in superseded on 10 October because the buyer moved the review. Keep the change trace. |
| Current task and owner | Ayşe: check the review outcome with Elif on 27 October, using the existing conversation. |
| Still unknown | Approved budget, final purchase authority, acceptance of the quotation and eventual outcome. |
If the only evidence had been a relevant website and an unanswered first email, record a researched prospect and an outreach activity. Do not turn that into a confirmed project. The lead qualification guide helps distinguish fit from a buying decision.
Choose by the work that breaks, not a magic contact count.
Excel or another spreadsheet can be sufficient when one person keeps a clear history, a reliable next-action list and recoverable records. Separate sheets or rows can hold companies, interactions and tasks. A calendar can support reminders. The issue is whether the routine works, rather than whether the file is called CRM.
| Observed situation | Reasonable next step | What to verify |
|---|---|---|
| One person can recover the last agreement and current task without conflicting copies. | Keep the spreadsheet routine while it meets the job. | Try the worked example. Preserve dated history and a clear next action. |
| One person repeatedly loses context between research, notes and follow-ups. | Test an individual CRM workflow on a small, representative set. | Can you find the history, update the current state and replace a task without losing the earlier event? |
| Several people need simultaneous updates, permissions, assignments or approvals. | Evaluate a system that explicitly supports those shared requirements. | Test the actual roles, concurrent edits and access conditions. A one-user workspace does not meet this requirement. |
| The main problem is invoices, stock, orders or accounting. | Evaluate the relevant operational or accounting workflow. | CRM relationship records alone do not establish these capabilities. Check the specific scope and connections. |
| Nobody records the conversation or owns the next step. | Define the recording routine and responsibility first. | Software will still need accurate input and someone who acts on it. |
This is an editorial decision aid, not a measured productivity threshold or a ranking of software vendors.
The CRM category does not tell you every feature.
- Operational CRM
- Supports work around customer interactions, such as sales stages, service requests or scheduled actions. Specific automation depends on the product.
- Analytical CRM
- Uses recorded data to understand patterns and results. Reliable reports need consistently defined events and stages.
- Collaborative CRM
- Supports sharing customer context across people or departments. Check permissions and the actual shared workflow.
These commonly used categories can overlap. Hosting is another question: a CRM can run in the cloud, on an organization’s systems or in a local workspace. Neither the word CRM nor cloud hosting alone tells you who can see the records, which integrations work or how to retrieve your data.
CRM concerns customer relationships. ERP concerns wider operational resources and processes; accounting software covers financial records. A product can connect or combine these functions, but that must be verified. If your request includes stock, billing, payroll or team approvals, write those requirements separately.
Test whether the relationship survives the move.
Use the completed fictional example, decision table and blank transition checks without Anivo or signup. This is a manual TXT form, not a CRM import file.
Keep a recoverable source copy.
Work on a representative test copy and define what needs to move: companies, contacts, dated notes, opportunities and current tasks. Do not start by moving every field indiscriminately.
Map meaning before columns.
Specify which field holds the event date, which holds the current state and where a future task belongs. Mark unsupported fields explicitly.
Replay both events.
Use the 5 and 10 October example. Confirm the earlier event remains readable, the later agreement is visible and only the 27 October follow-up is current.
Inspect the result, then test retrieval.
Reopen the record and check relationships, dates, text and current work. Examine export or backup contents; a report export alone does not prove that all history and tasks can be recovered.
A successful row count is not a successful migration. A tool might accept a company and note while omitting contacts, task status or event dates. Record omissions and the manual work required before deciding to continue. Check actual field mappings and limits in the system you use.
The downloadable form asks you to record the original evidence, target field, retained history, current task, unsupported data and retrieval result. It does not calculate a readiness score or certify a migration. For broader research-tool selection, use the B2B prospecting software guide.
Keep B2B research and the next conversation together.
Anivo is a Windows desktop workspace for B2B company research, evaluation and outreach preparation. Its CRM supports company records, stages, notes and linked tasks. Each plan is for one user and one local workspace. Shared records, team permissions and live multi-user editing require a system that supports those needs.
Describe the companies you need to research.
Explain your offer, market and relevant company characteristics. Review the proposed research plan and approve it before research starts.
Keep a suitable company with its reason.
Check the company information before relying on it. Move a relevant record into the CRM and retain why it fits, along with unresolved questions.
Write what happened and what remains open.
Manually record the conversation date, source, actual agreement and current state in the company’s notes. Do not treat a fit score as a buyer commitment.
Add the next task and revisit it.
Use the linked task for the next action. Write the agreed date in the task text or note, then maintain the current task when the agreement changes.
The five-record model above is a way to think about information. It is not a promise of five separate Anivo object types or automatic migration of the sample. Anivo’s import field mapping needs its own inspection; this TXT form is for manual checking. Use the B2B sales workflow and the Anivo user guide for product steps.
Try one research brief and one company record. Check whether you can recover the context and identify the next action.
Definitions are useful; outcome claims need different evidence.
Microsoft’s CRM explanation distinguishes relationship strategy, processes and software. HubSpot’s database manual explains objects, records, properties, activities and associations in its own product. Salesforce’s training exercise provides a concrete account, contact and opportunity workflow. These are useful product-authored guides, not independent tests of Anivo.
Payne and Frow’s October 2005 paper presents a strategic, cross-functional CRM framework. We could inspect only the publisher’s abstract, not the full paper. It supports the distinction between a business approach and a technology-only view; it does not supply a current SME migration threshold or an Anivo sales result.
The fictional chronology, spreadsheet decisions and transition checks are our practical synthesis. They have not been evaluated as a predictive model or a productivity experiment. Test them against your actual workflow and record what the chosen system preserves.
Questions about CRM and spreadsheet tracking
Separate the meaning of CRM from the capabilities of a particular product.
What does CRM stand for?
CRM stands for Customer Relationship Management. It refers to managing relationships with current and potential customers. CRM software supports the records, activities and processes involved.
What does a CRM do in everyday sales work?
It can keep company and contact context, past interactions, the state of a buying discussion and the next task accessible. Reporting, automation and shared access depend on the actual product and plan.
Is an Excel customer list a CRM?
A spreadsheet can support a relationship-management routine if it preserves dated history, current work and clear responsibility. A list of names alone does not do all of that. Test the routine before choosing software.
When should a small business move from Excel to CRM?
Consider a trial when context is repeatedly lost, follow-ups become unreliable or relationships are hard to maintain. Shared-user needs require explicit shared capabilities. There is no universal contact-count cutoff in this guide.
What is the difference between an activity, opportunity and task?
An activity records something that happened. An opportunity represents a specific possible purchase. A task describes future work. Sending a quotation is an activity, its review may be a deal state, and checking the review is a task.
What is the difference between CRM and ERP?
CRM focuses on customer relationships. ERP covers wider operational resources and processes. Accounting, stock and order functions may be connected or bundled, but the exact scope must be checked in the chosen system.
Does moving spreadsheet rows preserve all customer history?
Not necessarily. Check contacts, associations, dated notes, opportunity state and tasks separately. Reopen the records and inspect retrieval or backup contents. Matching row counts alone do not establish a complete migration.
Can Anivo serve as a shared team CRM?
Anivo supports B2B research and company records with stages, notes and linked tasks in a Windows desktop workspace. Each plan covers one user and one local workspace. Essential team sharing and permissions need a system that supports them.
Sources and reading scope
Checked on 10 October 2026. Relevant public guide sections were read; the academic paper was accessible only as an abstract. Vendor capabilities remain specific to those products.
- Microsoft: What is CRM?
Public definition and capability sections inspected. No visible publication date. Broad enterprise capabilities are not attributed to every CRM or to Anivo.
- HubSpot: Manage your CRM database
Updated 18 September 2026. Public sections on objects, records, associations and activities inspected; describes HubSpot’s own model.
- Salesforce Trailhead: explore CRM work
Public worked account/contact/opportunity exercise inspected. No visible publication date; a vendor training example, not comparative research.
- Payne and Frow (2005): A Strategic Framework for Customer Relationship Management
Journal of Marketing 69(4), 167–176, October 2005. Publisher abstract only; conceptual framework, not a measured transition threshold or Anivo outcome.
- Paraşüt: CRM and operational software scope
Turkish guide dated 25 August 2026. Relevant CRM, accounting and commercial-operation distinctions inspected; product-specific integration claims are not transferred to Anivo.