Your best connector never says no.
That's the problem. Nobody tells you they're tired of being asked. They just get slower. A reply that used to take an hour takes a week. Then the replies stop.
We call this connector fatigue. It's the team version of something every individual knows: the friend you only call when you need something eventually stops picking up.
How it happens
Picture a Series B company with one very well-connected investor partner. Call her Dana.
In January, the CEO asks Dana for an intro to a CFO. She makes it the same day. The meeting goes well.
In February, two AEs find out Dana knows people. Each asks for an intro. One of them sends her a three-paragraph pitch to forward. She rewrites it herself and sends it.
In March, an SDR's sequence tool flags Dana as a path into eight target accounts. The SDR asks for all eight in one email.
Nobody ever tells Dana what happened with the CFO.
By April, Dana is "busy". Nobody at the company did anything wrong on purpose. Everyone just asked.
The three causes
Asked too often. Most teams have no idea how many times a connector has been asked this quarter, because the asks come from different people through different channels. The CEO asked in Slack. The AE asked on LinkedIn. The SDR asked by email. From Dana's side it's one company asking eleven times.
Asked badly. A heavy ask is one the connector has to work on: rewrite, research, explain. "Can you introduce me to your friend who runs procurement at a bank?" is heavy. "Would you forward this two-line note to Jordan? Here it is" is light. Every heavy ask uses up more goodwill than it needs to.
Never told what happened. This is the big one. A connector who makes an intro and never hears back learns one thing: their help disappears into a hole. A connector who hears "the meeting happened, and here's what came of it" learns that their name was well spent.
The first two drain goodwill. The third stops it from refilling.
Why it gets worse with automation
Here's the part that worries me about where the market is going.
Signal tools are very good at finding paths. A modern stack can surface every investor, advisor and customer who knows someone at a target account in seconds. Plug that into a sequencer and you can generate intro requests faster than any human ever could.
Every one of those requests lands on the same few people. Your best connectors are usually your best connectors for a lot of accounts. Automation doesn't spread the load. It concentrates it.
A team that sends a thousand cold emails burns its domain. A team that sends a hundred automated intro requests burns its board.
How to stop it
There's no clever fix. There are four boring ones.
- Count the asks. One log of every intro request per connector, whoever sent it and wherever they sent it from. If you can't answer "when was Dana last asked?" in ten seconds, you can't protect her.
- Cap them. Set a limit per connector per month and a cooldown after each ask. Investors and board members get the lowest caps. Let connectors set their own if they want to.
- Make every ask light. Draft it in the connector's voice, short enough to forward without editing, with one clear reason the target would want to take the meeting. The invite template in how to fill an executive dinner is a good model: three lines, no pitch.
- Close every loop. Within a week of every intro, tell the connector what happened. Even "they passed, thank you anyway" counts. This is the step that turns a one-time helper into a repeat one.
If you want to go one step further, rank paths by the connector score and the connector's recent asks together, so the person who was asked yesterday drops down the list automatically. We wrote about the enforcement side in connector preference enforcement.
The real budget
Most revenue teams think about budget in dollars and headcount. The relationship channel has a different one: the goodwill of a few dozen people who are willing to vouch for you.
It refills slowly. It drains fast. And nobody sends you a warning before it runs out.
Treat it like it's finite, because it is.
Frequently asked questions
What is connector fatigue?
Connector fatigue is when the people who make warm introductions for a company, such as investors, advisors, customers and colleagues, gradually stop responding because they've been asked too often, asked to do too much work per request, or never told what happened with the intros they made.
How many intro requests is too many for one connector?
There's no universal number, and it depends on the relationship. The practical rule is to set an explicit cap per connector per month, with lower caps for investors and board members, add a cooldown after each ask, and let connectors set their own limits.
How do you prevent connector fatigue?
Log every ask per connector across the whole team, cap the number of asks, make each ask light enough to forward without editing, and tell the connector what happened within a week of every intro.
Does automating warm intro requests cause connector fatigue?
It can. Automated path-finding tends to route many requests to the same few well-connected people. Without caps, cooldowns and a shared log, automation concentrates asks on your best connectors rather than spreading them out.
.png)
