Personal CRM vs. sales CRM: people are not deals

A sales CRM and a personal CRM differ in one decision that decides everything else: what the core record is. Sales CRMs store deals and attach people to them; personal CRMs store people and attach life to them. That’s why Salesforce feels absurd for friendships — not missing features, wrong subject.

The data model is the whole difference

Open any sales CRM and look at what it’s made of. The atom is the deal (Salesforce calls it an opportunity): an object with a monetary value, a probability, a pipeline stage, and a close date. Contacts exist, but structurally they’re satellites — people associated with the deal. The dashboards, the reports, the famous forecasting — all of it aggregates deals, because deals are what the business runs on. That’s not a flaw. For a sales team it’s exactly right.

A personal CRM inverts the model. The atom is the person: who they are to you, how you met, what’s currently happening in their life, how often you want to be in touch, when you last genuinely talked. There’s no value field, no stage, no close date — because none of those concepts exist in a friendship. The “pipeline view” is replaced by an overdue list: who’s drifting past the rhythm you chose for them.

This is the same distinction that separates an address book from any CRM at all — the address book vs. CRM line is about adding state and history to static contact data. The sales/personal line is about which state: transaction state, or relationship state.

One person, two records: Mara, twice

Abstract data models become obvious with a concrete person, so meet Mara — a former client you genuinely like.

In the sales CRM, Mara exists as a contact attached to a deal: Website relaunch, €14,000, stage: closed-won, closed November 2025. Her record holds her company, her role, the email thread, and the invoice trail. Since the close date passed, no dashboard has shown her to anyone. Structurally, the system is finished with Mara — she converted, which is the only verb it knows. Ask it “how was Q4?” and it answers brilliantly. Ask it “how is Mara?” and it returns a closed deal.

In the personal CRM, Mara exists as a person: met at the 2023 industry conference; two kids; planning a sabbatical in spring; loves brutalist architecture; cadence: every 90 days; last real conversation: March, about whether she should take the CMO offer. No value field anywhere. The system’s only opinion about Mara is that 90 days are nearly up and you might want to ask how the sabbatical planning is going.

Now run the tape forward. Mara takes the sabbatical, comes back as CMO somewhere new, and needs an agency. In the sales-CRM-only world, nobody has spoken to her in fourteen months, because closed-won contacts live outside every queue — the relationship existed, and the model lost it. In the two-system world, you’d checked in twice, knew about the new role before LinkedIn did, and the inbound email starts with “obviously I thought of you first.” Same person, same goodwill; the difference is entirely which record type was keeping watch.

That’s the comparison in miniature: neither system is smarter, they’re pointed at different things. The deal record watched the transaction until it ended. The person record watched the person, who continued existing.

Why HubSpot feels wrong for your mentor

The mismatch isn’t aesthetic — it shows up in concrete, daily friction. Three examples from people who’ve tried it:

The fields interrogate you. Create a contact in a sales CRM and the form asks for lifecycle stage, lead status, and company. Your university mentor is not a marketing qualified lead. You can leave fields blank, but the software keeps asking, and every report and automation assumes you answered. You spend your time fighting defaults instead of remembering a person.

The lifecycle has a direction. Sales CRMs model contacts as moving toward something: lead → opportunity → customer → (silence). When a deal closes, the record’s job is done, and the system quietly stops surfacing it. Friendships move in no direction at all — they just need recurring, low-key attention. A tool whose deepest assumption is progress through stages has no native concept of “stay close to this person indefinitely”.

The frame leaks. This is the quiet one. When every person in your system carries a deal value, you start ranking people by yield — not because you’re cynical, but because the interface sorts that way. Notes like “ask how her father’s surgery went” have no field, no report, no automation. What the tool measures becomes what you notice. With friends and mentors, that’s precisely the wrong thing to optimize.

None of this makes sales CRMs bad. It makes them specific. An excavator is excellent at excavating; the problem starts when you use it to repot houseplants.

When you genuinely need both

If you sell anything for a living — freelance work, consulting, a product — “personal vs. sales” isn’t either/or. The two systems answer different questions, and plenty of people legitimately run both.

The clean dividing rule: a contact lives where its next action lives. There’s an open proposal with Acme? That’s deal state — pipeline, sales CRM, close date and all. The project shipped eight months ago and you simply like the people? That’s relationship state — personal system, with a cadence so they hear from you twice a year without a reason.

The handoff matters more than most people expect, and the evidence is old and solid: Granovetter (1973) showed that opportunities disproportionately arrive through weak ties — the casual, low-frequency relationships at the edge of your network — rather than through your closest contacts. Your closed-won column is a warehouse of exactly such ties, going stale because the pipeline lens has no reason to show them. Moving a finished deal’s humans into your personal system, with a rhythm attached, is how referral networks are actually built.

Mechanically, the handoff is small: once a month, scan the deals that closed, and for each human you’d genuinely like to know in five years, create a person record on the other side — context note, a generous cadence like 120 days, done. Ten minutes, maybe four records. The deliberateness is the point: you’re choosing who graduates from transaction to relationship, instead of letting the pipeline’s archive decide by default.

What you shouldn’t do is run one system for both jobs. A sales CRM stuffed with friends produces guilt-inducing dashboards; a personal CRM tracking quotes in note fields loses deals. Separation is a feature.

The cost question, honestly

Sales CRMs are priced for organizations that recoup the spend in revenue — per seat, per month, in ascending tiers. Using one for personal relationships means paying business prices for features (forecasting, territory management, sequence automation) that do nothing for friendship. Personal CRMs cluster around €0–10 a month, with some one-time-purchase options; over three years the gap between categories is usually several hundred euros, before you count setup time. The CRM cost calculator compares specific vendors over a 3-year horizon if you want numbers for your shortlist.

And the disclosure, stated plainly: we build Endearist, a personal CRM, so we benefit when this article convinces you the category exists. The data-model argument doesn’t depend on us being right about our product — it’s an argument about shape, and it holds for every personal CRM, including our competitors’. Whether you need anything in this category at all is the prior question, and we’ve written the honest version of that one too: the self-diagnostic, including the outcomes where the answer is no. If you’re past the diagnostic and weighing build-vs-buy, the full category comparison is the next read.