












































It reads the archive you already own, builds the graph, and drafts the follow-up inside the thread where the promise was made.








































The network is already yours. It just isn’t retrievable at the moment it matters.
Maya HaddadCRYPTO PM · 6 YEARS · 3 WEEKS IN DUBAI
You
Marta
Fatima
85 CONTACTS · ONE WARM PATH · TWO HOPS
Same shape every time: an archive the user already owns, exported by them — never scraped.














Three people, ranked by how warm the path is — and what you last said to them.
Every line is a message it can point at — the graph gives the who and when, the index gives the what.

Drop the LinkedIn export. Connections, messages, embedded.

“Who do I know in crypto product in Dubai?” — ranked, with the route.

A mention in the thread. It reads what was said and looks up the rest.

It writes the message and stops. The button does not say Send.

Approve → contact, activity and task in the workspace.
What ships today is one agent with a toolset — not twenty. It reads the thread, queries the graph, searches the web on the mention, drafts, and files. One agent, five tools, two surfaces.
The six groups on the ring are the target shape, taken one-to-one from the stack that already runs for twenty-three clients. Outreach is the group that ships here, because it is the only one that writes the graph — the other five read it.
Thread in → signal, card, draft out.
Channels in Slack, React in the web app.
Contact, note, task — as the agent's own identity.
Enrichment the thread only named.
Search by meaning, not by keyword.












































