Kinnetly
Personal CRM relationship intelligence: what to remember without surveillance
“Relationship intelligence” can sound like a promise that software will tell you who matters, who is drifting away and who you should contact next.
In much of the CRM market, that is close to what it means. Tools may analyse communication patterns, assign relationship-strength or health signals, surface warm paths through a firm’s network, or prioritise people for a sales team. Affinity, Microsoft Dynamics 365 and Happenstance each describe versions of that model.
That approach can be useful for the teams it is built for. But it is not the only meaning the phrase can have.
For an individual, a personal CRM can make relationship intelligence much simpler: the context you deliberately chose to record, organised so you can check it before you act.
That is a different promise. It is not a score. It is not a prediction. It is not a background system watching every interaction.
It is a way to remember the things that would otherwise fall through the cracks.
Two very different kinds of relationship intelligence
The first kind is inferred.
A system looks at signals such as email, meetings, organisational connections or communication history, then turns them into an estimate. It might label a relationship strong or weak, suggest a path to someone new, or decide that a contact needs attention.
The second kind is recorded.
You write down the context that matters to you: who introduced you, where you met, what you discussed and what, if anything, you said you would do next. Later, you can see that record and make your own decision.
Neither approach is automatically right for every situation. They serve different jobs.
If you are managing a firm-wide pipeline, inferred signals and shared relationship data may be part of the workflow you want. If you are trying to keep up with the people in your own professional life, the more useful question may be simpler:
What do I need to remember to show up thoughtfully next time?
That is the job Kinnetly is designed around. It is a private, account-scoped personal CRM and relationship map, not a team sales platform or a system that observes your communications in the background.
A relationship record is more useful when it has four parts
A name and a company are rarely enough to bring a relationship back into focus. When you return to a contact months later, the useful detail is usually the story around the name.
A good record does not need to be long. It can be built from four small pieces of context.
1. Origin: how you came to know each other
Start with the connection point.
Maybe Priya introduced you to Jordan at a community event. Maybe you met through a mutual client. Maybe you first spoke after a workshop.
That detail is not just social trivia. It helps you remember the setting and the shared context without turning the introduction into a claim on either person’s time. An introduction records provenance, not permission for future introductions.
2. Setting: where the relationship sits
A person may be connected to an event, a group, a company or several of those things. Linking the right context gives a future conversation somewhere to begin.
For Jordan, that might be the community event and their public-interest design project. You do not need to build an exhaustive profile. You only need enough context to avoid reopening a conversation as if it never happened.
3. Activity: what actually happened
A short, dated activity can be more useful than a vague memory.
For example: “Coffee in October. Jordan mentioned the accessibility workshop they are planning.”
In Kinnetly, activities are records you log. A recent activity can help you see when you last connected, but it is not a relationship-health score. Recency is context, not a verdict on the relationship.
4. Intention: what you chose to do next
If you promised to send Jordan an accessibility checklist, set a one-off reminder for yourself. If there was no promise, there may be no next step to set.
That distinction matters. A reminder reflects your own intention. It does not mean a system has decided Jordan should be contacted, and it does not send a message on your behalf.
Put together, those four parts give you something better than a contact card. They give you a record you can revisit with judgement.
The deliberate-capture test
Before adding a detail, it is worth asking four questions:
- Did I learn this directly?
- Is it accurate and tied to a real moment?
- Will it help me behave respectfully next time?
- Is it appropriate to keep?
The test is practical, not performative. It prevents a personal CRM becoming a place for collecting information simply because it might one day be useful.
A compact note about a conversation you had is usually easier to review and correct than a large, automatically assembled record. It also makes the boundary clear: you are keeping context to support your own memory, not trying to calculate another person’s value.
What Kinnetly records, and what it does not observe
Kinnetly lets you create or import contacts, connect people with companies, groups and events, record introductions, save notes and log activities. You can set follow-up cadences and separate one-off reminders, then search the context you have saved.
It also has a user-set Know / Like / Trust field. That can reflect your own view of a relationship. Kinnetly does not infer or score relationship strength from your emails, meetings or behavioural data.
Just as important is what Kinnetly does not do:
- It does not connect to LinkedIn.
- It does not connect to your inbox or calendar.
- It does not automatically log your emails, meetings, messages or calls.
- It does not enrich your network from third-party profile data.
- It does not rank contacts, infer motives, recommend outreach or send outreach for you.
- It is not a shared team graph or sales pipeline.
Some capture tools are available when you ask for them. For example, you can import contacts, scan a card, dictate an activity or use other user-invoked AI features where available. Those actions are distinct from passive relationship capture, and content sent to AI features may be processed by AI providers. The record remains something you choose to create, review and save.
Kinnetly is private to your account, but it is not an end-to-end encrypted offline vault. Privacy here means a deliberately scoped personal workspace, not an unrealistic claim that no data is ever processed.
Context should help you choose, not choose for you
Months after meeting Jordan, you might open their record and see the introduction, event, activity and reminder. Then you can ask a human question: is the project still relevant, and would reaching out be welcome?
A system cannot answer that question from a timestamp alone.
That is why a personal CRM should not confuse intelligence with surveillance. The most useful relationship context is often the small amount you consciously recorded, kept somewhere you can revisit before taking action.
Map the context you choose to remember with Kinnetly’s private personal CRM.