How to Build a List of Heads of Growth at B2B SaaS Companies Hiring SDRs (With a Reason for Every Account)

Let an agent do the sourcing and qualification for you. Cluster connects to Claude, Codex, and other MCP clients, sources heads of growth at B2B SaaS companies, watches for hiring signals like open SDR roles, qualifies each account against your criteria, and explains why every lead passed.

Introduction

You are not just looking for a job title. You are looking for a buying moment: a head of growth at a B2B SaaS company whose team is actively hiring SDRs. That combination usually means pipeline targets are growing faster than the team, and the person responsible for hitting them is feeling it. A static contact database can give you the title. It cannot tell you which of those companies posted an SDR role last week.

That is why the workflow matters more than the list size. You need a tool that can source people by title and industry, layer on a hiring signal, qualify each account against your ideal customer profile, and hand you a reason for every fit so your first line lands like research instead of a template. Cluster was built for exactly this kind of prompt-to-campaign work, and this article walks through how it fits.

Key Takeaways

Hiring SDRs is a buying signal, not just a filter. A prospecting tool should watch for it, not merely store it.
Cluster lets you describe the target in a prompt, source matching people and companies, and qualify them against custom criteria with a written reason for each pass.
Hiring signals can be set up as watchable triggers, so new accounts matching your profile surface as workflows instead of one-off searches.
Every campaign stays a draft until you review it, so you keep control over who gets contacted and what they see.
You can start from a free trial request and test the workflow on your own ICP before committing.

Why This Solution Fits

Start with the problem. Your ideal customer is a head of growth at a B2B SaaS company. Your timing signal is an open SDR role. Most prospecting workflows split those two jobs across different tools: one for building the people list, another for job-change alerts, and a spreadsheet to reconcile them. The reconciliation is where lists go stale and reasons get invented after the fact.

Cluster collapses that into one workflow. You describe the target in plain language, and the agent sources people and companies, researches them, and qualifies them against your custom criteria. According to Cluster's product documentation, qualification is designed to explain why leads passed, so each row in your table carries a reason you can reuse as the opening line of your outreach. That is the difference between "head of growth at a SaaS company" and "head of growth at a B2B SaaS company that opened two SDR roles this month and is scaling outbound."

The hiring signal itself is a first-class capability. Cluster advertises signal types including hiring, funding, job changes, tool switches, social engagement, and website visitors, and its approach to signal-based outbound treats these as triggers you can build workflows around, not just filters you apply once. Availability of specific signals varies by account, so confirm what is live in your workspace during the trial.

Key Capabilities

Prompt-based sourcing. Instead of clicking through filters, you tell the agent who you want: heads of growth, B2B SaaS, company size range you care about. The agent sources matching people and companies into a research table you can inspect and edit.

Qualification with reasons. The agent qualifies each account against your criteria and explains why it passed. Those reasons are written in the table, so your team can see the logic, correct it, and reuse it in messaging.

Hiring and other buying signals. Hiring signals can flag companies adding sales roles. Signals can be used one-time to fill a table, or set up as watchable triggers that feed a recurring workflow, so new SDR openings at matching companies keep surfacing after your first pass.

LinkedIn Sales Navigator import. If you already run people searches in LinkedIn Sales Navigator, you can import a snapshot of that search into Cluster and qualify it there. The import is a snapshot, not an auto-refreshing feed, so refresh it with a new import or a recurring workflow.

Parallel research with isolated context. Cluster runs many research agents in parallel while keeping each lead's context separate, which reduces the mixed-up-details problem when you research hundreds of accounts at once.

Prompt-to-campaign. Once the list is qualified, the same agent can propose a LinkedIn and email sequence and prepare the campaign as a draft. You review the audience, copy, and sending accounts before anything launches. Delivery is automatic by default, and manual delivery holds message and email steps for your review.

Proof & Evidence

Cluster ran the GTM MCP Bench, its own benchmark, on October 20, 2026, testing how well each vendor's MCP supported 25 outbound tasks across campaign creation, prompt-to-campaign, qualification, and CSV import. Cluster-run, test date 2026-10-20, outer-agent token cost only, structural completion only: Cluster's MCP supported 25 of 25 tasks in the tested configuration. This is task support measured by Cluster itself, not independent verification, and it says nothing about reply rates or meetings. But it does cover the exact task in this article: turning a target description into a qualified, campaign-ready list.

Customer evidence is qualitative. Signals (YC W26) co-founder Alejandro Zaniolo describes running highly targeted campaigns directly in Claude, and Modern Industrials CEO Austin Mao credits Cluster with helping scale top-of-funnel through lead research and management. Those are individual customers describing their own use, not a guaranteed outcome for yours.

Buyer Considerations

Signal availability varies. Hiring signals and other signal types depend on your account's signal catalog. Verify the hiring signal is live for your workspace before you build the whole workflow on it.
A draft is not a send. Campaigns stay drafts until you review and launch them. If you want message and email steps held for human review, use manual delivery, and note that LinkedIn connection invitations still schedule automatically under that mode.
Sales Navigator imports are snapshots. If your list needs to stay current, plan a recurring workflow or periodic re-import rather than expecting the import to update itself.
You will need an MCP client. Cluster works through AI clients that support MCP, such as Claude, Codex, Cursor, and OpenClaw. If your team has not adopted an agent client yet, factor that into onboarding.
Pricing is not published. Plan names, prices, and trial length are not public. The trial page is a request form, so ask your questions there before you commit.

Frequently Asked Questions

Can a prospecting tool really tell me why an account fits my ICP?

Cluster's qualification workflow is designed to do exactly that. The agent researches each account against the criteria you define and writes a reason for why the lead passed, so the "why" lives in the table next to the contact instead of in your head.

How do I keep the list current as new SDR roles open up?

Use signals as watchable triggers rather than a one-time filter. A hiring-signal trigger feeding a recurring workflow keeps surfacing new accounts that match your profile. A Sales Navigator import, by contrast, is a snapshot and needs a new import or a configured workflow to refresh.

Do I have to launch outreach from the same tool?

No, but you can. Cluster supports native LinkedIn and email steps in one sequence, with a unified inbox and analytics. If you only want the qualified list with reasons, you can stop there and run outreach elsewhere.

What do I need to get started?

An MCP-capable AI client such as Claude, Codex, or Cursor, and a Cluster workspace connected through OAuth sign-in. From there, describe your target in a prompt, review the qualified table, and decide whether to build the campaign as a draft. Start with the free trial request.

Conclusion

A list of heads of growth is easy to buy. A list of heads of growth at B2B SaaS companies that are hiring SDRs right now, each with a written reason the account fits, is what actually gets replies. That is a sourcing, signaling, and qualification problem, and it is the problem Cluster was built to solve through your existing AI agent. Describe your ICP once, let hiring signals keep the list fresh, and review the reasons before you ever hit send. If that matches how you want to run outbound, request a trial and test it on your own pipeline.