1. Name Drop vs Direct Intro
There are two ways to use a warm relationship:| Play | What it asks of the connector | When to use |
|---|---|---|
| Direct intro | Write a message, send it, follow up | Tier-1 strategic accounts. Advisors and investors with skin in the game. Connectors you know will follow through. |
| Name drop | Say yes once. That’s it. | Roughly 80% of the time. Best for customers, champions, peers, and prospects you’ve already met. |
2. Where Name Drop Opportunities Come From
The play works best when the next person you’re going to reach out to already knows someone in your existing warm circle. The strongest opportunities come from three sources: Pipeline meetings Every demo, discovery call, and follow-up meeting is a chance to surface “who else does this person know?” — and to plant the seed for an ask at the end of the call. Closed-won customers and champions Anyone who has gotten value from your product is a candidate. Champions in particular are usually willing to lend their name to expand the relationship. Closed-lost champions Often overlooked. People who loved the product but couldn’t get budget or timing right frequently have a social contract feeling — they want to help, and they’ll often agree to a name drop more readily than a customer who’s never given you anything. HiveSight surfaces these opportunities in two places:- Pre-meeting brief on the calendar event — for every upcoming meeting, you see the attendee’s top relationships and whether they overlap with anyone in your ICP.
- CRM tasks — when a deal hits a terminal state (closed-won or closed-lost), HiveSight can drop a task on the rep: “X knows the following Y people in ICP — make the ask.”
3. The Magic Phrase
When asking a connector for permission, the phrasing matters. The line that consistently works:- gives the connector an easy out (“it would hurt — please don’t”)
- frames the ask as a small favor, not a meaningful request
- doesn’t commit them to writing anything
- gets a fast yes/no answer
4. Use the Permission in Your Outreach
Once the connector says yes, the name drop goes at the top of your outbound. The framing has to be honest — you brought their name up, not them, so don’t write the email as if they recommended you reach out:- Lead with the name. Subject line or first sentence. Don’t bury it.
- Be accurate about the relationship. “Working with Sarah” or “I was chatting with Sarah last week” is true. “Sarah said you’re the right person to talk to” is not — they didn’t, you asked permission to mention them. The prospect can call Sarah and check; the framing has to survive that.
- Don’t explain why you’re emailing. “Saw you two are connected” is enough. Lines like “so figured I’d reach out rather than cold” break the spell — they remind the prospect this is a sales email instead of letting the mutual connection do its work.
- Keep it short. The name drop carries the credibility. You don’t need to over-explain.
5. Bulk the Ask
If you have multiple prospects you’d like to mention a single connector to, ask for them all at once.6. When to Use This Play vs the Direct Intro
A simple decision tree:7. Where This Fits in a Rep’s Day
The name drop play should never require a rep to “log in to another tool.” Reps live in three places — their calendar, their inbox, and their CRM. The play has to surface there or it won’t happen. On the calendar Every upcoming meeting carries a brief that includes the attendee’s top relationships. Before the call, the rep already knows: “this person worked with our customer at Stripe; this person engages with our champion at Notion.” That context lets them plant the seed during the call. During the call At the end of a good conversation — whether the deal is moving forward or not — the rep asks the magic phrase. Even a closed-lost deal can convert one champion into three to five name-drop permissions for the next quarter’s pipeline. In the follow-up email The cleanest place to ask. The conversation is fresh, the rapport is built, and the connector has the context to say yes without a back-and-forth. In the CRM as a task When a deal closes won or lost, HiveSight can drop a task on the rep: “Ask X about Y, Z, W before the deal goes cold.” The rep doesn’t have to think about it — the system surfaces the moment. The rep never has to think “should I be running this play?” The data is already where they are.8. Closing the Loop With the Connector
After the name drop sends, a quick update goes a long way toward keeping the connector willing to say yes the next time.Best Practices
A few principles keep this play healthy at scale. Always get permissionNever name-drop without explicit permission. Spammy name drops from connection-list scrapes destroyed this play in many organizations — get the yes first, every time. Use the magic phrase
”Would it help or hurt if I mentioned your name?” The phrasing matters. It gives a fast yes/no and makes declining easy. Default to name drop, reserve intros for tier-1
Roughly 80% name drop, 20% direct intro. Reverse that ratio and the program dies — you’ll burn out connectors fast. Don’t ask the same connector repeatedly
One ask, bulked across three to five prospects, is fine. Coming back every week with a new one-off feels like work to the connector. Close the loop
Send a quick thank-you and an outcome note. Connectors who feel valued say yes more. Make declining easy
”Totally fine to say no” should be in every ask. Connectors who feel pressured say yes once and then stop responding.
What a Healthy Name Drop Motion Looks Like
Over time, teams develop a simple rhythm:- Every rep has their calendar connected — pre-meeting briefs surface relationships automatically.
- After every good call, the rep asks the magic phrase in the follow-up.
- Permissions are tracked in the CRM with attribution back to the original meeting.
- Outbound emails to name-dropped prospects lead with the connector’s name.
- The connector gets a quick update once the prospect responds.
- Closed-won and closed-lost deals trigger a CRM task to bulk-ask the champion about their network.