Same person, many relationships

Tom is a past client, a referrer, and a peer at the same time. The CRM lets him be all three.

The problem

Tom did one project with you in 2024. Since then he's introduced you to two paying clients, and you bump into him at industry events twice a year. Right now he's a past client, a referrer, and a peer — three things at once.

Enterprise CRMs make you pick one. So you pick "past client" and lose the rest. Your search for "who's referred me work?" doesn't return Tom. Your reflection on "who do I run into at conferences?" doesn't either. The information was always there in your head; the system just couldn't hold it.

Real networks don't fit into one column.

What changes

A person carries a list of roles, not a single label. You tag what's true:

• Tom — past client, referrer, peer
• Anna — current client
• Sarah — prospect
• Mum — personal only
• An old colleague on sabbatical — peer, dormant

When you ask the CRM "who's referred me paid work?" — every contact tagged referrer comes back, with the engagements they brought in. When Tom's next project lands he gains current_client without losing the other three. When the project wraps he moves back to past_client, but he's still a referrer and a peer. Nothing about the relationship gets lost when a chapter of it ends.

Two roles do double duty as gates:

• personal_only — Mum is a person, but she never appears in work-related lists, regardless of how long it's been since you spoke. Family and close friends accidentally captured through shared calendars sit here.
• dormant — explicitly paused. Useful when someone's on sabbatical, or there's been mutual silence and you don't want the CRM nudging you about it. History stays intact; the cadence reminders go quiet.

Why we built it this way

Your network is messier than a sales pipeline, and forcing it into one label loses information you actually use. Multi-tagging is the closest the data can get to the truth.

Roles are also yours to set, not the CRM's to infer. The system never decides "Tom must be a friend because you message him weekly." That's the same auto-discovered-intimacy trap cadence cohorts avoid — it ends up wrong, and it feels surveilling even when it's right. If you haven't tagged a contact, the CRM knows nothing about how they fit your network. Silence is the safe default.

What to read next

→ When the brief quietly changes — how the CRM notices when someone's budget, scope, or timeline has shifted from what they said last month.