The intro request you hesitate over is an unscheduled audit.
When an introduction request makes you pause, that pause is data. It measures exactly how well you maintained the relationship you're being asked to spend.
The reply you started and didn't send
Someone you respect messaged this morning asking for an introduction to a person in your network. You started to type yes. Then you stopped. Not because the request was strange, and not because you dislike either party. You stopped because a quiet question surfaced: do I actually know this third person well enough to put my name on the line for them? That flicker of doubt feels like etiquette. It isn't. It's the most honest feedback you'll get all week about the state of your network, delivered by the one system that never flatters you, your own memory.
The unscheduled audit
Call it the unscheduled audit. Every introduction request is a test you didn't book, graded in real time, on a single relationship. The person asking has handed you a name and, without meaning to, asked you to price your own credibility against how well you actually know the other side. When the yes comes instantly, you maintained that relationship. When you hesitate, you didn't. The hesitation is the score. It's uncomfortable precisely because it's accurate. A calendar reminder is easy to ignore. A live ask, from someone watching for your reply, is not.
Should I make this introduction?
The internet answers this one as manners. Search the question and you'll find etiquette guides on phrasing, on double opt-in mechanics, on how to say no politely. All useful, all beside the point. The discomfort you feel has nothing to do with the wording of the reply. What it exposes is the gap between the contact you have and the relationship you assumed you had. Treating that as an etiquette problem is like treating a check-engine light as a flaw in the dashboard design. The polite decline is the workaround. The signal underneath is the thing worth reading.
What the ask actually reveals
Spend time in founder communities like r/YCombinator and one scenario keeps returning: an ex-colleague or former co-founder resurfaces after two quiet years and asks to be introduced to an investor or a customer. The replies split fast. Some people vouch on the strength of the old relationship. Others go quiet, because two years of silence turned a strong tie into a stranger with shared history. The fix that community reaches for is the double opt-in introduction, a long-standing norm in venture circles: you get the third party's permission before making the connection. Good practice. But notice what forces you to reach for it. You default to double opt-in exactly when you can't personally vouch, which is the audit telling you the relationship thinned while you weren't looking.
Three ways the hesitation shows up
The pause isn't one feeling. It comes in three distinct flavors, and each points at a different failure in how the relationship was kept. First: you can't picture the person's face. You met once, traded cards at a conference, never followed up, so there's a contact with no relationship under it. Second: you remember the name but not the why. You saved them, then lost the context, and the record outlived the reason you made it. Third is the sneakiest. You're genuinely in touch, but only at the surface. You like each other's posts and swap pleasantries, yet you couldn't describe what they're building or what they'd actually want from the person you'd introduce. Reach without depth. Each flavor is diagnostic. Read it before you reach for the etiquette guide.
The hesitation
What actually happened
What it's measuring
You can't picture their face
You met once and never followed up
A contact captured, a relationship never built
You remember the name, not the why
You kept them but lost the context
The record survived; the reason for it didn't
You know them but can't vouch for specifics
You stayed in touch, only shallowly
Reach without depth: pleasant, not load-bearing
The unscheduled audit: three hesitations, three maintenance failures.
How to decline an intro, and how to stop needing to
If the hesitation is a measurement, the decline is easy and clean. 'I don't know them well enough right now to make a strong intro, but let me reconnect and come back to you.' No guilt, no burned bridge, honest. The harder work is upstream, so the audit stops catching you short. Proactive maintenance isn't mysterious and it isn't a second job. It's three habits. Capture context the moment you meet someone, not the card alone but the why: what they're building, what they're looking for, one specific thing from the conversation. Revisit on a light cadence, a few minutes before you'd need the relationship rather than after. And log the changes, so the record ages with the person instead of freezing on the day you met. Do that and the next intro request gets a fast, confident yes, because the answer was already on file.
A referral spends trust you may not have deposited.
Where the context actually lives
Most contact tools are built to store the card. Name, company, email, done. The card was never the hard part. What decays first is the context: the reason you kept someone, the thing they said, what they'd want next. That's the exact material an intro request asks you to recall on the spot. Met is built around keeping that context, not just the identity. Capture the why in the moment, keep it local and iCloud-only so it stays yours and isn't sold to anyone, and revisit it before the ask instead of scrambling after. What that buys you is a shorter path from 'can you introduce me' to a yes you can stand behind.
What we're watching
The interesting shift is who runs the audit on themselves. The people who never hesitate on intro requests usually aren't the best-connected. They maintain fewer relationships more deliberately. The bet here is that deliberate depth beats large-network drift on the one metric that matters for a connector: how often you can say yes to a vouch without flinching. Bring the receipts and we'll revisit.
Keep the context, not just the card. Get Met.
Met is built for people whose work runs on relationship recall: the founders, recruiters, advisors, and BD operators who meet more people in a week than any memory holds. Capture stays local, iCloud-only, never sold. The point isn't a bigger contact list. It's keeping the context that makes a name worth vouching for when someone asks.
