Own All Your Addresses

A small team I run was operating out of a scatter of email addresses. A few different ones for the same handful of people. I had wired up a pipeline to triage incoming mail, and it kept tripping over itself - de-duplicating the same person across two and three identities, guessing which thread belonged to which version of us.

The fix was tiny. An afternoon, mostly. What it taught me was not.

Because I went in thinking I was solving a routing problem. I came out understanding I had been leaking credibility for months.

The problem you think you have

If you run a small team, you know the shape of this. Someone signed up for a tool with a personal account. Someone else used a company alias that got set up in a hurry. A founder still answers important threads from the address they have had since college. Mail arrives in three places. You build little bridges between them - forwarding rules, a pipeline, a habit of checking everything twice.

It feels like a logistics tax. Annoying, manageable, the kind of thing you will clean up when there is time.

So I treated it like logistics. My operator OS - the spine that holds all my ventures together - already had a triage layer, and I just kept widening it to absorb the mess. More addresses in, more de-duplication logic to reconcile them. I was getting better and better at managing fragmentation instead of removing it. That is the trap. A pipeline can make a structural problem feel solved when it has only been hidden.

The tell was the de-duplication itself. If my own system could not tell which identity belonged to which person without extra logic, neither could the people we were emailing.

The problem you actually have

Here is what fragmentation does that nobody puts on the cost sheet.

Every partner, every investor, every customer is quietly assembling a picture of who you are. Each address is a different brushstroke. One thread comes from a personal account, the next from a company alias, the next from a founder's old handle. None of it is wrong, exactly. But none of it lines up either.

The reader does the reconciling you offloaded. They wonder, half-consciously, which you am I dealing with today? Is this the company, or a person using the company's name? Is this the operation, or a side conversation? They do not file a complaint. They just trust you a notch less, and they could not tell you why.

That is the real cost. Not wasted cycles in a pipeline. A slow, invisible discount on your credibility, applied by everyone you most need to take you seriously.

Coherence is a trust feature. A single, predictable identity tells the reader they are dealing with one entity that has its act together. Scatter tells them the opposite, and it tells them before you have said a word.

Own all your addresses

The rule I came away with is simple. Consolidate early, and own all your addresses.

You can have a split. One address for operations, one for the company, whatever the structure demands. That is fine. The two requirements are that the addresses are coherent - a reader can look at any one of them and know exactly which function they are talking to - and that they are yours. You at the company, not a personal account wearing the company's clothes. Not an alias someone spun up that you do not really control.

Owning them matters as much as consolidating them. A personal account doing company work is a single point of failure dressed up as a convenience. When that person leaves, or changes their handle, or just stops checking it, the company's history walks out the door. Ownership is the difference between an identity the company has and an identity it borrows.

The technical payoff was real. My pipeline got simpler the moment the inputs got coherent. The de-duplication logic disappeared because there was nothing left to de-duplicate. Fewer wasted cycles, fewer edge cases, a triage layer I could actually reason about.

But that was the secondary win, and I want to be clear about the order. The primary win is that nobody we work with ever has to wonder which version of us they have reached. Every thread looks like it came from the same outfit because it did. The picture they are assembling finally matches the one we want them to have.

That is the lesson I keep returning to as I run these orbits off one spine. The things that present as cleanup - reconciling identities, merging accounts, picking one canonical address - are rarely just cleanup. They are coherence work. And coherence, for a small team that wants to be taken seriously by people much larger than it, is not housekeeping. It is the product.

Field Notes from the Agentic Operator is a personal series. These are my own views, not those of my employer or any organization I work with, and nothing here relies on non-public information.