Enrichment should ask, not tell

The moment software edits your own words without telling you, you stop being able to rely on any part of it.

A bank of cloud lit pink at dusk, with a distant aircraft above it

The problem with silent updates

Automatic enrichment is easy to sell and hard to live with. A third party disagrees with something you wrote, the field changes, and nothing marks the difference between what you observed and what a vendor guessed.

After that, every field carries a question you cannot answer: did I write this?

Suggestions preserve authorship

Updates arrive for review instead. You keep what you trust and ignore the rest, and nothing overwrites what you put there yourself.

It is slower in the demo and better in the second year, which is the only timescale a relationship record is really judged on.

Keep reading

Ask your assistant about your own network

Relladex speaks the Model Context Protocol, so Claude and other assistants can read your own contacts, notes and company figures as you talk.

A relationship file is not a sales pipeline

Most CRMs are organised around deals moving through stages. A record organised around the people you know is a different tool entirely.