The missing step in your Claude Code GTM workflow: warm paths

Claude Code GTM workflows build the ICP, the list, the people and the emails. Almost none ask who already knows the buyer. Here is the step to add, with the one-line setup and four prompts.
Shankar Ganapathy
Co-Founder, Boomerang

By Shankar Ganapathy, Co-founder, Boomerang AI. Published November 16, 2026.

Claude Code GTM workflows are everywhere right now. Build your ICP from won and lost deals, size the market, pull an account list, find three to five people per account, write the first email, review it, load it into your sending tool.

They work. They also share one blind spot.

Between "find the people" and "write the first email", nobody asks the most useful question in sales: does anyone we know already know this person?

Why this step matters

Warm beats cold, and buyers say so. When Norwest Venture Partners asked 177 B2B sales and marketing leaders which outreach tactics worked best, warm referrals from customers or their network came first at 65% (Norwest, 2025 B2B Benchmark Report).

A cold-only workflow treats every account the same. The step below splits your list in two before anything is written: the people you can reach through someone they trust, and the people who get your best cold email.

Where it goes

StepCold-only workflowWith a warm-path check
Build the ICP and the listSameSame
Map 3 to 5 people per accountSameSame
Check who knows themSkippedLook up warm paths for every person
First touchCold email to everyoneIntro ask where a path exists, cold email for the rest
Weekly reviewReply and meeting ratesAlso: accounts with no path, to take to investors and board

Setup: one command

You need Claude Code and a Boomerang AI workspace on the Team, Company or Enterprise plan, which include the MCP server. In Terminal, run:

claude mcp add --transport http --scope user boomerang https://mcp.getboomerang.ai

Start Claude Code, type /mcp, choose boomerang and select Authenticate. Sign-in uses OAuth, so there is no API key. Access is read only and limited to what your role in Boomerang can already see.

Then add these lines to your CLAUDE.md, so every prompt follows them:

# Warm paths
Before drafting any first email, check Boomerang for a warm path to the person.
If a strong path exists, draft an intro ask for the connector instead of a cold email.
Never send anything. Every ask and every email stays a draft.

Prompt 1: Check every person you mapped

Run this after the step that finds people at each account, and point it at whatever file that step saved.

Read the people file from the last step (one row per person: company, name, title).

For each person, use Boomerang to find warm paths to them. Keep the strongest
path per person: connector, how they know the person, relationship strength,
last interaction, and who on our side should make the ask.

Write "no path" where Boomerang finds none. Do not guess.

Save outputs/warm-paths.csv and tell me how many people have a strong path,
a weak path and no path.

What to check: open five rows with a strong path and read the reason. "Worked together for three years" is a path. "Both follow the same company" is not.

Prompt 2: Pick the sender and draft the ask

Read outputs/warm-paths.csv. Keep rows with a strong path.

For each, if more than one connector can reach the person, compare them and
recommend one, with the reason.

Draft two things per row:
1. A short note asking the connector for the introduction, in plain words,
   under 90 words, specific to how they know the person.
2. A forwardable blurb the connector can pass on without editing, under 80 words.

Save outputs/intro-asks.md. Send nothing.

What to check: read each ask as the connector. Would you say yes? If the ask needs a favour bigger than the relationship, move that row to the cold list.

Prompt 3: Split the list before any email is written

Read outputs/warm-paths.csv and the people file.

Make three lists:
- Warm: strong path. These get the intro ask from outputs/intro-asks.md.
- Mention: a real but weaker path. Flag these for me; only mention the
  connector's name in an email if they have said yes to it.
- Cold: no path. These go to the normal first-email step.

Save outputs/warm.csv, outputs/mention.csv and outputs/cold.csv.

What to check: nobody on the warm list should also be in your sending tool. A buyer who gets a cold email on Monday and an introduction on Wednesday has been asked twice.

Prompt 4: Find the accounts nobody can open

Run this weekly, next to your scorecard.

Read the account list and outputs/warm-paths.csv.

List the target accounts where nobody has a path to any of the people we mapped.
For each, use Boomerang to check whether our investors, board members, customers
or partners can reach anyone senior there.

Save outputs/coverage-gaps.md: the accounts, any new paths found, and the
accounts still with no way in.

What to check: take the "still no way in" list to your next board or investor update and ask for specific introductions, not general help.

A real example: Digideck

Digideck, a Boomerang AI customer that sells interactive sales presentations to sports and entertainment, ran this pattern in Claude over the Boomerang MCP. Claude queried more than 6,300 customer and prospect relationships, added public ownership data to find sister companies of existing customers, and gave each rep a map of which customer knows each buyer.

The one rep not at trade shows opened three to four new opportunities within weeks of launch (case study).

Where this breaks

  • Connectors are finite. The same investor cannot introduce you every week. Keep the strongest asks for the deals that justify them.
  • Paths go stale. People change jobs. Re-run Prompt 1 before each campaign rather than reusing last month's file.
  • Name drops need permission. Mentioning a connector without asking spends their relationship, not yours.
  • Claude can still be wrong. Read the warm list before anyone asks for anything.

Where Boomerang AI fits

Boomerang AI is the relationship layer for the workflow you already run. It maps warm paths from your team, investors and board, customers and partners into each target account, scores them by evidence and recommends who should make the ask. The MCP server is included on Team, Company and Enterprise (MCP and API), and full setup for Claude, ChatGPT and Claude Code is on the Boomerang MCP page.

Read next: Sales teams will buy APIs, not tools, Claude Code for GTM and 8 prompts for finding warm intros in Claude.

Sources

Frequently asked questions

Can Claude Code find warm introductions?

Yes, if it is connected to a relationship data source over MCP. With the Boomerang MCP server added, Claude Code can look up who on your team, among investors, customers and partners, can reach each person on your list, and rank the paths by strength.

How do I add Boomerang to Claude Code?

Run claude mcp add --transport http --scope user boomerang https://mcp.getboomerang.ai in Terminal. Then start Claude Code, type /mcp, choose boomerang and authenticate in your browser. It uses OAuth, so there is no API key to manage.

Where does the warm-path check go in a Claude Code GTM workflow?

After you map the people at each account and before you write the first email. That way every person gets either an introduction ask through someone they know or your best cold email, and nobody gets both.

Can Claude Code send the intro requests?

No. The Boomerang MCP connection is read only. Claude Code can find paths and draft the ask and a forwardable blurb, but a person reviews and sends it, and the connector decides whether to make the introduction.

Which Boomerang plans include MCP?

Team, Company and Enterprise include the Boomerang MCP server, so anyone on those plans can use it from Claude Code, Claude or ChatGPT. Company and Enterprise also include the REST API and webhooks. Starter does not include MCP access.