Comparison
CRM vs Address Book: What's the Difference?
An address book stores how to reach people; a CRM tracks what happens with them. The real difference.
An address book stores how to reach people; a CRM tracks what happens with them over time. The address book is a static list of names and contact details. The CRM is a process tool that records interactions, stages, and tasks. They are two different artifacts solving two different problems — and there is a useful gap between them.
That gap is where a personal relationship layer lives: more than a list, less than a sales pipeline.
The address book: a list of reachability
An address book — your phone’s Contacts app, a Rolodex, a spreadsheet of emails — answers one question: how do I contact this person? It holds names, numbers, emails, companies, maybe a birthday.
It is static by design. A contact entry does not change after you talk to someone. That is its strength (low maintenance, always current for reachability) and its limit (it forgets everything that happened between you).
The CRM: a record of process
A CRM (customer relationship management system) is built around what happens with people: interactions logged, deals moved through stages, tasks assigned, reports run. Sales CRMs like HubSpot or Pipedrive are the familiar examples.
A CRM is dynamic and process-shaped. It assumes a pipeline — a deal moving toward a close — and usually a team that shares the data. That structure is powerful for revenue work and heavy for anything else.
The three-way comparison
The middle column is the part most people overlook.
| Address book | Relationship memory | Sales CRM | |
|---|---|---|---|
| Core question | How do I reach them? | What should I remember about them? | Where is this deal? |
| Shape | Static list | Person-centered notes over time | Pipeline and stages |
| Changes after a conversation | No | Yes | Yes |
| Built for teams | No | No (single-user) | Yes |
| Reminders with a reason | Rarely | Yes | Yes (task-driven) |
| Privacy default | Personal | Private, local-first | Shared cloud |
| Example tool | Apple / Google Contacts | Intriq | HubSpot, Pipedrive |
The address book and the CRM sit at two extremes — reachability versus revenue process. Relationship memory fills the middle: it remembers people without forcing them into a pipeline.
Where the gap shows up
You feel the gap when an address book is too thin but a CRM is too much. For example:
- You met someone twice and cannot recall what you discussed the first time.
- A friend mentioned a job change you wanted to follow up on, but it lives nowhere.
- You do not run deals, so a pipeline tool feels absurd, yet a flat contact list keeps losing context.
A CRM would over-engineer these. An address book cannot hold them. This is the relationship-memory job:
Drinks with Aisha after the alumni panel. Just moved into product at a health startup, finding the pivot from consulting hard. Mentioned her brother’s wedding in autumn. Asked about coaching recommendations. Send her two names and check in after the wedding.
That note is not a contact field and not a deal record. It is memory about a person.
Who needs which?
- Just an address book if your relationships are mostly functional — you need to call, text, or email and nothing more.
- A sales CRM if you run deals, report on a pipeline, or share customer data with a team.
- A relationship layer if you keep forgetting context about people who matter and a pipeline is overkill.
Many people need two of the three: an address book for reachability and a memory layer for context, with a sales CRM only if revenue process is involved. For the practice that underpins the address-book side, read what is contact management; for the personal end of the CRM spectrum, see what is a personal CRM.
Where Intriq fits
Intriq lives squarely in the middle column. It is a private, iPhone-first relationship memory app: jot a quick note — typed or spoken — and it becomes searchable, person-centered memory. Ask “what did Aisha need coaching recommendations for?” and it answers from your saved note and shows the source, rather than fabricating one. Notes stay local-first with encrypted on-device snapshots.
It is honest about its lane. Intriq is iPhone-only — no Android, web, or desktop app, no team features, and no contact enrichment. It is not your address book (keep Contacts for numbers) and not a sales CRM (it has no pipeline). It is the memory between them. This contrast with the address book is also why people say relationship memory is not the same as contact management.
Key takeaway: An address book stores reachability and a CRM stores process; relationship memory fills the gap between, remembering people without forcing them into a pipeline — which is exactly the lane Intriq occupies on iPhone.
FAQ
Is a CRM just a fancy address book?
No. An address book is a static list of contact details; a CRM is a process tool that tracks interactions, stages, and tasks over time. They look similar because both store people, but they answer different questions.
Do I need a CRM if I already have a good address book?
Only if you run a process — deals, a pipeline, or shared customer data. If your real problem is forgetting context about people rather than tracking deals, a relationship memory layer fits better than a full CRM.
Where does relationship memory sit between the two?
In the middle. It is person-centered like an address book but dynamic like a CRM, recording what matters about each person over time without the pipeline overhead. It is built for individual recall, not team process.
For the wider category, visit the personal CRM hub.