The problem it addresses
Most people who work through relationships do not fail to remember that someone matters. They fail to remember the specifics — where the person moved, what they said they were struggling with, what was promised and by whom, which of two similarly named companies they actually joined. The specifics are what makes a follow-up land, and they decay within days.
The usual answers make the wrong trade. A notes app keeps the detail but knows nothing about who is in it, so nothing surfaces when it matters. A sales CRM knows about people but demands a shape most of this work does not have: an opportunity, an amount, a close date, a stage. Faced with structure that does not fit, people stop entering things, and a half-filled CRM is worse than no CRM because it looks authoritative while being wrong.
Relladex takes the opposite approach: write the way you would tell a colleague, and let the structure be derived. A person types or dictates two sentences. What comes out is the people, the organisations, and the commitments contained in those two sentences, filed where they can be found again.
What it does, concretely
Capture in seconds
A note is written or spoken in plain language. Relladex reads it and identifies who was involved, where they work, and what was said would happen next. The person writing does not fill in fields, pick from dropdowns, or decide in advance which record a thought belongs to.
Follow-ups that come from what you wrote
“I’ll send her the deck Thursday” is a commitment, and it is treated as one — attached to the person it concerns rather than living in a separate task list that has to be kept in sync by hand.
Profiles that update as suggestions, never silently
When a contact’s details can be brought up to date, the update arrives as something to accept or ignore. Nothing overwrites what a person wrote themselves. This is a deliberate constraint: a record that edits itself is a record you stop trusting, and a relationship file is worthless the moment you cannot tell what came from you.
Companies as first-class records
People carry their employers with them. Companies a person follows carry their own context — what is happening to them, how they are performing — so a conversation can be opened with something current rather than something remembered.
A business card, a screenshot, a pasted block of text
Capture is not only typing. Photograph a business card, or paste in a signature block, a conference list, a message someone forwarded you — the people in it are read out and filed against the right companies. The point is the same as with notes: whatever form the information arrived in, it should not have to be retyped to become a record.
Company detail worth walking in with
Companies are not just a label on a contact. A company you follow carries what is happening to it — the news that has broken about it, and how it is actually performing: revenue, earnings, the shape of the balance sheet, how the market has priced it lately. It is the difference between knowing where somebody works and knowing what their week has been like.
Ask across your whole network, and get sources
The assistant works over the record you have built. Who have I not spoken to since the spring, who do I know at this company, what did this person say they needed, who should I be introducing to whom. Answers come with what they were drawn from, so a claim can be checked rather than taken on faith — an assistant that cannot show its working is one you have to re-verify by hand, which is no saving at all.
Reachable from the assistant you already use
Relladex connects to Claude and other assistants that speak the Model Context Protocol, so your own contacts, notes and company news can be asked about from inside a conversation you are already having — without opening Relladex, and without copying anything out of it.
An assistant can look things up on your behalf and save finished work back to your Capture. It cannot change or delete anything you already have, it cannot act as you, and it cannot spend your enrichments or Rella tokens — everything it reads has already been collected. What it can see is what you can see, and nothing more. Setting it up.
Ask who you should be talking to
A company can be put to the assistant directly — who is worth knowing there, who owns the decision, who to approach first. It answers with names, and the ones worth keeping are added to the network with them already placed against that company. This is the one part of the product that starts from a company rather than from a person you have already met.
Your mailbox, on your terms
A Google or Microsoft mailbox can be connected so the people in your address book come across, and so messages you write can go out as you, from your own account. What is read is the address book and what is sent is what you wrote — the inbox itself is not read, downloaded or stored.
Private to one account
A network belongs to the person who built it and syncs across that person’s devices. It is not a shared team asset, it is not sold, and it is not published.
What it is not
The exclusions are as load-bearing as the features, and most of them are choices rather than gaps.
- Not a team sales CRM. No pipelines, no deal stages, no forecasting, no manager’s dashboard. If several people need to work one pipeline together, Relladex is the wrong shape and will stay the wrong shape.
- Not a bought list. Names surface in answer to a question about a company you are working on, one at a time, and land in your own private record. There is no directory to browse, nothing to bulk export, and nothing sold to anyone.
- Not a social network. Nobody else can see a person’s network, and there is nothing to broadcast.
- Not an autopilot. It does not send messages on its own initiative or decide who deserves attention. It prepares; the person acts.
How a relationship file differs from a CRM
| Sales CRM | Relationship file | |
|---|---|---|
| Organised around | Deals moving through stages | People and what passed between you |
| Belongs to | The company; the team shares it | One person |
| Filled in by | Required fields, entered to satisfy the process | A sentence written the way you would say it |
| Succeeds when | Reporting is accurate for a manager | You walk into the next conversation knowing what happened in the last one |
| Fails when | People stop entering data the process demands | The record stops being trustworthy |
The two are not competitors so much as different objects. A salesperson with a quota needs the pipeline. The same person may still want a relationship file for the hundreds of people who are not in any pipeline and never will be — the ones who introduce, advise, hire, and reappear years later.
Who it fits
- Founders holding investors, advisors, candidates, early customers and the people who introduced them, none of which fits a pipeline.
- Investors who meet far more companies than they fund and need last year’s conversation to be findable this year.
- Recruiters and headhunters whose value is a long memory about people they placed nowhere, yet.
- Consultants and agency owners whose next engagement usually comes from someone already known.
- Anyone who meets more people than they can keep straight and has felt the specific embarrassment of not remembering something they were told.
The principles behind it
These are the rules the product is built to, and they explain most of its decisions.
- Capture must be cheaper than remembering. If writing the note costs more than carrying it in your head, the note does not get written and nothing else matters.
- Never silently overwrite a person’s own words. Automation proposes; the person disposes. A record you cannot trust is not a record.
- One person’s network is that person’s. Private by default, not shared by default with an opt-out.
- Structure is derived, not demanded. The software does the filing; the person does the writing.
- Absence of a feature can be the feature. No pipelines is a decision, and keeping it is what stops this becoming another CRM nobody fills in.
Connecting Relladex to an assistant
Relladex runs a remote Model Context Protocol server, so any assistant that speaks MCP can read your Relladex while you are talking to it. There is one address, and it is the same for everyone:
https://api.relladex.com/functions/v1/relladex-mcp
You sign in with your own Relladex account and approve the connection on a page we show you. Nobody can connect on your behalf, and the assistant only ever sees your account.
In Claude
- Open Settings → Connectors and choose to add a custom connector.
- Paste the address above and continue.
- Approve the connection on the Relladex page you are sent to. It lists exactly what the assistant will be able to read before you agree to anything.
In ChatGPT
- On the web, open Settings → Apps → Advanced settings and turn on developer mode. The option to add a custom connector only appears once it is on.
- Add a connector, paste the address above, and choose OAuth for authentication.
- Approve the connection on the Relladex page you are sent to.
Other MCP clients — Cursor, VS Code, and the rest — take the same address and the same sign-in. Nothing about the connector is specific to one assistant.
What it can read
- Your contacts — names, roles, employers, work history, and how you met.
- Your notes — everything you have written about the people and companies you track.
- Companies you follow — company records, collected news, and financial results drawn from their filings.
- Your Insights conversations — questions you have asked Relladex and the answers it gave.
- Your follow-ups — the reminders and suggestions Relladex has queued for you.
What it can write, and what it cannot
One thing, and only one: a finished piece of work can be sent back to your Relladex Capture, where it arrives as an unassigned note you can read and file. Ask for a research brief or meeting prep and it lands beside the people it is about.
Nothing else writes. No tool changes a contact, edits a note, or deletes anything — and no tool can start a web search, a company crawl, or an enrichment, which means connecting an assistant cannot spend your enrichments or Rella tokens. Everything it reads was collected before the conversation started. That is a deliberate limit rather than a missing feature: an assistant decides to call a tool far more readily than a person decides to press a button, and a bill should not be able to grow while something is thinking.
Things worth knowing
- The connector needs a paid plan — Starter or above.
- It reads the archive only. A company nobody has opened in Relladex has nothing stored, and the assistant will say so rather than guess.
- Figures come from your own account, so they agree with what you see in the app. A number found on the web may not.
- You can disconnect at any time, from your assistant or from Relladex settings. Revoking access takes effect immediately.
Common questions
What is Relladex, in one sentence?
A private relationship file: you write a note about a conversation and it files the people, companies and follow-ups that note implies.
Is it a CRM?
A personal one. It has no pipeline, no deal stages and no forecasting, and it belongs to one person rather than a team. If shared pipelines are the requirement, Relladex is the wrong tool.
Can I use Relladex from Claude or another AI assistant?
Yes. It connects over the Model Context Protocol, so your contacts, notes and company news can be asked about from inside an assistant conversation. The connection can look things up on your behalf; it cannot spend anything or act as you.
Do I have to type everything?
No. A note can be spoken instead of typed, a business card photographed, or a block of text pasted in — a signature, a list, a forwarded message — and the people in it are filed against the right companies.
What does it know about companies?
What has been happening to them and how they are performing: news, revenue, earnings, the shape of the balance sheet, how the market has priced them lately. Enough to open a conversation with something current.
Does it read my email or calendar?
Only if connected deliberately. The core of the product is what someone chooses to write down.
What does it cost?
Undecided, and saying so is better than quoting a number that changes. The direction is paying for capacity rather than for features, with every plan holding the whole product.
Can I use it today?
Not yet. Signups are closed while pricing is settled. There is a waitlist, and everyone on it is emailed once — the day it opens.
Who makes it?
Firelink Labs Inc., trading as Relladex.
Terms as this product uses them
- Relationship file — a personal record of people and what passed between you, kept for recall rather than for reporting.
- Capture — writing or dictating a note in plain language, from which the structure is derived.
- Enrichment — bringing a contact’s details up to date, offered as a suggestion to accept or ignore.
- Follow-up — a commitment found in something you wrote, attached to the person it concerns.
- Personal CRM — the nearest established category name, though the sales machinery the term implies is exactly what this leaves out.