Free tool · no signup
A signal just fired at a target account. Every vendor saw it too. Pick who on your side should reach out, then get the ask and the forwardable note, written for that sender.
1 · Which signal fired?
2 · How senior is the buyer?
3 · Who on your side knows them?
Pick every one that applies. The tool ranks them for this signal and this buyer.
4 · The details
Start with a verb, as something your team did. For example: shipped SSO and audit logs.
The sender and the buyer. For example: worked together at Northwind.
Public and purchased signals reach every vendor at once. A funding round or a new hire shows up in every competitor's feed the same morning. Timing stopped being the edge.
A busy executive decides what to read by who sent it, then reads it. A note from someone they know gets opened. The message only matters once it is opened.
The signal is the reason to reach out now. What changed since you last spoke is the reason to reply. Put it in the first line, and leave the pitch out.
This tool picks the sender once you know the relationships. Boomerang maps them across your team, customers, investors and partners, scores the strongest path when a signal fires, and drafts the ask for the connector to send. Rudy never sends on anyone's behalf.
Find your warm paths freeWorked examples
Every pick and message below is the exact output of the tool above. Each case starts from a real kind of signal and a different set of relationships, so you can see how the sender changes. For the signals worth watching, see the warm intro signal library. When you already have the sender and only need the intro itself, use the introduction email generator.
After a raise, a CEO hears most from their investors and board. Marcus outranks the rep here, so the rep becomes the backup, not the sender.
Signal: Funding round · Buyer: C-level · Who knows them: Investor or board member, Rep who worked with them before
Recommended sender
Marcus, your investor or board member
After a raise, investors and board members have their attention. Their notes get read.
Backup sender
The rep who worked with them before
Jessica knows the rep, but a rep note after a raise still reads like every other vendor.
Do not send from
A rep or SDR they have never met, in a sequence
Every vendor emails after a raise. A stranger in a sequence gets filtered with the rest.
Hi Marcus, Halden just raised, and you know Jessica better than anyone on our side. You and Jessica sat on the Northwind board together. Since we last spoke with Jessica, we built a native Salesforce sync. Would you forward the note below to Jessica, or send your own version? A note from you gets read. A cold note from us lands next to every other vendor. Any of these is a fine answer: 1. Yes, happy to 2. Not right now 3. Wrong person, try X 4. I would rather not Thanks, Sam
Hi Jessica, Wanted to pass something on: Sam's team built a native Salesforce sync, and with the raise at Halden, it felt timely. I know the team well and would not pass it on otherwise. If it is useful, Sam can do twenty minutes, or send a short written summary instead. Marcus
Signal: Funding round at Halden. Buyer: Jessica (C-level). Chosen sender: Marcus, your investor or board member. Backup: The rep who worked with them before. Status: ask sent to sender, buyer not contacted directly. Do not add this buyer to a sequence while the ask is open.
New leaders lean on people they trusted in past jobs. Ashley worked with Daniel before, so she goes first, and your executive is the backup.
Signal: New executive · Buyer: VP · Who knows them: Our executive is their peer, Former colleague on our team
Recommended sender
Ashley, a former colleague on your team
New leaders lean on people they trust from past jobs. A former colleague is one of them.
Backup sender
Your executive, their peer
New leaders build their peer network early. A note from your executive lands as one of those.
Do not send from
A rep or SDR they have never met, in a sequence
New leaders are flooded in their first weeks. Unknown senders are the first to go.
Hi Ashley, Daniel just joined Brightline. New leaders lean on people they already trust. You and Daniel worked together at Corvid. Since we last spoke with Daniel, we added EU data hosting. Would you forward the note below to Daniel, or send your own version? A note from you gets read. A cold note from us lands next to every other vendor. Any of these is a fine answer: 1. Yes, happy to 2. Not right now 3. Wrong person, try X 4. I would rather not Thanks, Sam
Hi Daniel, Wanted you to hear it from me first: we added EU data hosting, and with you new in the role, it felt timely. I would rather you heard it from me than from a sequence. If it is useful, I can set up twenty minutes, or send a short written summary instead. Ashley
Signal: New executive at Brightline. Buyer: Daniel (VP). Chosen sender: Ashley, a former colleague on your team. Backup: Your executive, their peer. Status: ask sent to sender, buyer not contacted directly. Do not add this buyer to a sequence while the ask is open.
Emily already knows the product and the rep who worked the last deal. With only one path, the tool says to use it well rather than spread the ask.
Signal: Champion arrived · Buyer: Director or manager · Who knows them: Rep who worked with them before
Recommended sender
Jordan, the rep who worked with them before
Emily already trusts the rep who worked the last deal. That history is the whole signal.
Backup sender
Nobody else: one strong path beats two weak ones
Do not spread the ask. If this path says no, wait for the next signal.
Do not send from
A rep or SDR they have never met, in a sequence
A cold sequence to someone who already knows you wastes the relationship.
Hi Jordan, Emily, who used us before, just joined Marlow Health. You know the history better than anyone. You and Emily ran the rollout together at Ardent. Since we last spoke with Emily, we added approval workflows. Would you forward the note below to Emily, or send your own version? A note from you gets read. A cold note from us lands next to every other vendor. Any of these is a fine answer: 1. Yes, happy to 2. Not right now 3. Wrong person, try X 4. I would rather not Thanks, Sam
Hi Emily, Wanted you to hear it from me first: we added approval workflows, and with you now at Marlow Health, I thought of you. Given what we talked about last time, it seemed worth a note. If it is useful, I can set up twenty minutes, or send a short written summary instead. Jordan
Signal: Champion arrived at Marlow Health. Buyer: Emily (Director or manager). Chosen sender: Jordan, the rep who worked with them before. Backup: Nobody else: one strong path beats two weak ones. Status: ask sent to sender, buyer not contacted directly. Do not add this buyer to a sequence while the ask is open.
Keystone said no because there was no SSO. Now there is. Rachel, your executive, reopens it as a peer, with the investor as backup.
Signal: Closed-lost, blocker gone · Buyer: C-level · Who knows them: Investor or board member, Our executive is their peer, Rep who worked with them before
Recommended sender
Rachel, your executive, their peer
Executive to executive keeps it a business talk, not a rep chasing a lost deal.
Backup sender
Your investor or board member
An investor can reopen the door without it feeling like the rep circling back.
Do not send from
A rep or SDR they have never met, in a sequence
A stranger reopening a lost deal reads as chasing, and closes the door again.
Hi Rachel, We lost Keystone last time. The blocker is gone, and this is best reopened peer to peer. You and Tom have met at a few industry dinners. Since we last spoke with Tom, we shipped SSO and audit logs. Would you forward the note below to Tom, or send your own version? A note from you gets read. A cold note from us lands next to every other vendor. Any of these is a fine answer: 1. Yes, happy to 2. Not right now 3. Wrong person, try X 4. I would rather not Thanks, Sam
Hi Tom, Wanted you to hear it from me first: we shipped SSO and audit logs, which I believe was the sticking point last time. I would rather tell you directly than have it arrive as another vendor email. If it is useful, I can set up twenty minutes, or send a short written summary instead. Rachel
Signal: Closed-lost, blocker gone at Keystone. Buyer: Tom (C-level). Chosen sender: Rachel, your executive, their peer. Backup: Your investor or board member. Status: ask sent to sender, buyer not contacted directly. Do not add this buyer to a sequence while the ask is open.
Fernway is researching tools like yours. Kevin uses your product and knows Megan, so his note gives her an honest view, and nobody mentions the research.
Signal: Activity spike · Buyer: VP · Who knows them: A customer who knows them
Recommended sender
Kevin, a customer who knows them
Megan is researching. A customer who knows them gives the honest answer they are looking for.
Backup sender
Your executive, introduced by the recommended sender
A senior buyer will take a call with a peer when someone they trust makes the link.
Do not send from
A rep or SDR they have never met, in a sequence
Citing their activity in a cold sequence reads as tracking and ends the conversation.
Hi Kevin, Fernway came up on our radar this week, and Megan may want an honest view from someone who uses us. You and Megan worked together at Pellam. Since we last spoke with Megan, we launched a usage-based pricing plan. Would you forward the note below to Megan, or send your own version? A note from you gets read. A cold note from us lands next to every other vendor. Any of these is a fine answer: 1. Yes, happy to 2. Not right now 3. Wrong person, try X 4. I would rather not Thanks, Sam
Hi Megan, Wanted to pass something on: Sam's team launched a usage-based pricing plan, and I thought of you. We use them ourselves, which is the only reason I am mentioning it. If it is useful, Sam can do twenty minutes, or send a short written summary instead. Kevin
Signal: Activity spike at Fernway. Buyer: Megan (VP). Chosen sender: Kevin, a customer who knows them. Backup: Your executive, introduced by the recommended sender. Status: ask sent to sender, buyer not contacted directly. Do not add this buyer to a sequence while the ask is open.
No one on your side knows Ryan. The tool says so plainly, points you to a path or a name-drop, and gives a three-sentence direct note for when there is no other option.
Signal: Funding round · Buyer: VP · Who knows them: None of these
Recommended sender
Nobody yet
No warm path. The signal alone puts you in the same inbox as every other vendor.
Backup sender
Find a path, or name-drop
Ask who knows Ryan first. If a mutual name would not mind being mentioned, use the name-drop email generator instead of asking for an intro.
Do not send from
A rep or SDR they have never met, in a sequence
Every vendor emails after a raise. A stranger in a sequence gets filtered with the rest.
1. Find a path first. Ask who in your wider network knows Ryan: investors, board members, customers, partners and past colleagues. 2. If there is a mutual connection you can mention without asking for an intro, use the name-drop email generator: getboomerang.ai/tools/name-drop-email-generator 3. If you must go direct, lead with what changed and keep it to three sentences, like the note below.
Hi Ryan, We built a native HubSpot integration, and with the raise at Oakline, it felt timely. No pitch, just a short note in case it is relevant. If it is, I can do twenty minutes or send a written summary. Sam
Signal: Funding round at Oakline. Buyer: Ryan (VP). Chosen sender: nobody yet, no warm path found. Status: looking for a path, buyer not contacted directly. Do not add this buyer to a sequence while you look for a path.
Questions
The person on your side the buyer already knows and trusts, chosen to fit the signal. After a funding round, that is usually an investor or board member. When a new executive joins, it is a former colleague. When a past champion arrives, it is the rep who worked with them. When a lost deal reopens, it is your executive, speaking to a peer.
The rep who owns the account is often the last choice, not the first. A rep the buyer has never met, sending from a sequence, is the one sender to avoid in every case.
Because the buyer decides whether to open a message before they read a word of it. A busy executive scans the sender line and sorts: people they know get opened, everyone else waits or gets deleted. A well written email from a stranger often goes unread. A plain note from someone they trust gets read and answered.
Signals make this worse, not better. When a funding round is announced, every vendor tracking it sends something that week. The sender is the only part of the email your competitors cannot copy.
Signal-based selling means reaching out when something changes at an account, such as a funding round, a new leader, or a spike in research, instead of working a static list. The signal tells you why now. It does not tell you who should reach out, and that is the part most teams skip.
For the full approach, read our guide to signal-based selling. For the signals that point to a warm path, see the warm intro signal library.
Often, yes. Executive-led multithreading works because a senior buyer will take a note from a peer that they would ignore from a rep. It reads as a conversation about plans, not a vendor chasing a deal. It matters most for C-level and VP buyers, and for reopening a deal you lost, where a note from the rep can read as circling back.
Keep it short and in the executive's own voice. Write the note for them, and let them edit it and send it from their own account. Do not send it on their behalf.
Make it easy to say yes and easy to say no. Name the buyer, say why now in one line, and say what has changed since you last spoke. Then attach a short note they can forward as it is, or rewrite in their own words.
End with simple reply options: yes, not right now, wrong person, or I would rather not. An investor gets many of these asks. The ones that take a minute to answer are the ones that get answered.
Lead with the change, not the relationship. If you lost because a feature was missing and you have now shipped it, say that in the first line. The buyer remembers why they said no, so the note only works if it answers that reason.
For a C-level or VP buyer, have your executive reach out as a peer, with an investor as the backup. For a director or manager, the rep who worked the deal knows the history best and should send it. Either way, do not put the buyer back into a sequence.
Then the honest answer is nobody yet. A signal alone puts you in the same inbox as every other vendor who saw it. Look for a path first: ask your investors, board, customers, partners and past colleagues who knows the buyer.
If there is a mutual connection you can mention without asking for an intro, use the name-drop email generator. If you must go direct, lead with what changed and keep it to three sentences.
A short note, written for the connector, that they can send to the buyer as it is. It is two to four sentences in the connector's voice. It leads with what changed, makes no pitch, and offers twenty minutes or a written summary.
It exists because the hardest part of an intro is the writing. A connector who has to compose something from scratch will put it off. A connector who can forward a ready note, or edit it in a minute, usually sends it. If you want to write the intro request itself, try the introduction email generator.
No. While the ask is open, the buyer should hear from your connector and nobody else. If they get a cold sequence from your team the same week, the warm note looks like part of a campaign, and the connector looks like they were used.
Log the ask in your CRM or Slack, mark the buyer as not contacted directly, and wait for the connector to reply. Boomerang works this way by design. Rudy, its AI agent, finds the warm path, scores the relationship and drafts the ask, and the connector reviews it and sends it from their own account. Rudy never sends on anyone's behalf.
