Build a Relationship Coverage Report for Your Target Accounts

Every account plan says which companies you want. Very few say how you will get into them.

A relationship coverage report answers that for the whole list at once. For each target account it shows whether anyone in your network can reach the buyers, who the strongest connector is, and which accounts have no way in at all. It turns "we should use our network" into a list someone can work this week.

This recipe builds one in Claude with Boomerang's MCP server. It works for a quarterly territory review, a pipeline push on a tier one list, or a board meeting where someone asks how the network is helping.

What you need

• Claude connected to Boomerang's MCP server. Setup takes a few minutes, see How to find warm intros in Claude.
• Your target account list, as account names. Twenty to fifty accounts is a good first run. If Claude stops partway through a long list, split it into batches of ten.
• The roles you sell to, for example CRO, VP Sales and RevOps lead.

Step 1: Give Claude the list and the brief

Paste your accounts and the buyer roles into one message, then ask:

"For each of these accounts, use Boomerang to find whether anyone in our network can reach the CRO, VP Sales or Head of RevOps. Give me one row per account with the strongest path, the connector, how they know the buyer, and the relationship strength."

Claude works through the list using your workspace's relationship data and returns a table. Keep the table. It is the backbone of the report.

Step 2: Sort accounts into three groups

Ask Claude to group the table:

"Group these accounts into three buckets: strong warm path to a buyer, weak or indirect path only, and no reachable stakeholder."

Each bucket gets a different play.

• Strong path. These are this week's asks. The connector knows the buyer and the relationship is strong enough to ask.
• Weak or indirect path. Someone knows someone. Work these with a two-hop ask or by multithreading into a different stakeholder.
• No path. These are your real gaps, and they are worth naming out loud.

Step 3: Pick the right connector for each strong path

For every account in the strong bucket, compare the options before anyone asks:

"For each strong-path account, show all connectors who can reach the buyer and recommend the best one, considering strength, seniority and last interaction."

The best path is not always the most senior person. It is the one whose ask the buyer will actually answer.

Step 4: Work the weak paths through the buying group

For the weak bucket, widen the search beyond your first target role:

"For these accounts, show me other senior stakeholders in sales, RevOps or finance and who on our team can reach each one."

A warm path to a VP of Finance can still get you into the right room. This is where multithreading starts.

Step 5: Turn the gap list into asks for your wider network

The no-path bucket is the most useful part of the report. Take it to the people who are not in the CRM:

• Share it with your investors and board and ask who they can help with.
• Check it against your customers and champions. Former colleagues of your champions often sit inside target accounts.
• Bring it to partners who already sell into those companies.

Then run step 1 again a month later. Accounts that move out of the no-path bucket are the clearest proof that your network is growing in the right places.

Step 6: Draft the asks, then send them yourself

For each strong path, ask Claude for a draft:

"Draft a short intro request to the connector for each strong-path account, using the Boomerang context on how they know the buyer."

Review every draft and send it from your own account. The connection is read-only, so nothing goes out on its own, and the connector always decides whether to make the intro.

What to do with the report

• Territory planning. Weight accounts with strong paths higher this quarter.
• Pipeline reviews. Track how many target accounts have a warm path to a buyer, and watch the number move.
• Board updates. Show the gap list and ask the board for specific introductions instead of general help.

Claude is the fastest way to build the report. Running the asks at scale happens in Boomerang, where Rudy routes each request to the connector, checks their preferences, nudges when it goes quiet and writes outcomes back to Salesforce, HubSpot or Attio. Rudy never sends on anyone's behalf. Start a free trial or book a walkthrough to see your own coverage.