Every introduction you've ever been part of is already sitting in your mailbox. Bob reads them out, shows you who has actually connected you to people over the years, and helps you tell them what came of it.
No data entry. No tagging. No spreadsheet to import.
your network, found in your mailNobody typed any of this in. It was already in the mail.
You don't add contacts, tag anyone, or import a spreadsheet. Bob looks for one specific thing: the three-body shape where someone put you and a stranger in the same message and stepped back. That's an introduction, and it's already written down.
What comes back is a page of your own network. Every introduction Bob found, who made it, when, and a link back to the original thread for each one, so you can check any row rather than take its word for it.
Most people are wrong about who their top connectors are.
Three commands. The first one carries the whole thing.
/bob-scan reads your mailbox and pulls out the introductions — both the ones made for you and the ones you made for other people. It knows which seat you were sitting in.
/bob-graph draws your network as a page you can click around. Who connected you to whom, which handful of people account for most of it, and where each one traces back to.
/bob-thanks asks what came of the introductions that took hold — a sentence each, or skip — then drafts the notes. Your sentence is the copy. Drafts only; nothing sends itself.
Someone introduces you to one person, and that person goes on to introduce you to nine more. Bob follows the thread.
← swipe the chain →
An introducer's real reach. Dana introduced you to three people; those three went on to account for sixteen more. That's the difference between counting introductions and measuring them.
"You know Terry because Dana introduced you to Marcus, Marcus introduced you to Priya, and Priya introduced you to Terry." The origin story of a relationship, reconstructed.
An introduction you made is kept apart from one made for you, because you're owed different things in each.
Whether both people replied, whether anyone booked time. An introduction that happened isn't the same as one that landed.
Often the more useful list. A warm introduction going to waste is a door still open.
Each introduction links back to the original thread, so you can verify any claim Bob makes rather than trust it.
Mirror what Bob found into your own base. One-way and additive — re-running never duplicates rows and never deletes anything.
Notes land in your drafts and stay there. Bob reads mail and writes drafts. Sending is yours.
Some of these are choices and some are walls. Either way you should know them going in.
Once you hand two people off to each other, they talk to each other and not to you. Your mailbox stops being evidence at that moment. Knowing more would mean going and asking them — a different feature, not built.
Bob reads email. An introduction can land perfectly well over text, LinkedIn, or a phone call, and Bob will never know. So it asks "did it go somewhere else?" rather than telling you that you never replied.
The chains follow only where every step touched your own mailbox. This is a picture of your network compounding, not a map of everyone's.
Automated LinkedIn access risks your account. That isn't a risk worth handing to anyone's tool, including this one.
Bob is built for one person and one mailbox, so everyone would run their own. A shared view where partners see each other's introductions is a genuinely interesting problem and an honest amount of work.
Bob works and it has been run against a real six-year mailbox. But the people outside its author are only just arriving. Expect rough edges, and expect to be asked what broke.
Including the part that is not as simple as "it stays on your machine".
Two spreadsheet files and a web page, on your own machine. Open them, edit them, back them up, or delete the folder and be done.
Bob holds no credential. It asks Claude to read your mail using the Gmail connector already on your account, so your mail passes through Anthropic's servers — access you have already granted, not a new one. That connector can also send and delete. Bob only ever reads and drafts.
There is no Bob server and no Bob account. Its author holds no credential of yours, because none exists to hold — that part is structural, not a promise.
Bob will tell you when it doesn't know something. A blank field means it didn't look, never that nothing happened.
Anyone who has spent years connecting people and has never once seen the shape of it.
Or from the Claude desktop app: the Code tab → + → Plugins → Bob. Then /bob-setup walks you through the rest.
Bob is free and open source (MIT). You need a paid Claude plan that includes Claude Code, which is how Bob is installed and run, and the Gmail connector switched on for the mailbox you want read. There is no Bob subscription, no account to make, and nothing to pay its author.
Bob is early and hands-on. If you're thinking about running it on your own mail, grab time and ask me anything.