Why ICP Fit Isn’t Enough for Effective Sales Prospecting

In a recent LinkedIn post, Nick Palasz discusses how sales teams can look beyond ideal customer profile (ICP) fit to identify prospects with a meaningful reason to engage. This article reports on Palasz’s post and examines the workflow he describes; it is not written by him.

“Just because someone fits your ICP doesn’t mean they’re ready to buy.”

Moving from list building to buying signals

Palasz argues that matching a prospect’s job title and company to an ICP is only an initial filter. As he explains in the post, those details alone do not establish why someone would want to speak with a seller. His proposed approach adds company research and potential buying signals before outreach begins.

According to Palasz, this distinction addresses a common weakness in prospecting: teams may have contact details but lack a specific, evidence-based reason to start a conversation. He frames finding that reason as the central work, rather than simply locating a prospect’s LinkedIn profile.

Four agents, one connected workflow

Palasz says he built a Claude Code Sales Department made up of four specialized agents. Each has a separate role, and its findings inform the next stage of the process.

• Account Finder: identifies companies matching an ICP using approved data sources.
• Researcher: investigates companies, identifies possible buying signals, and flags prospects that may not be a fit.
• Message Writer: uses the research to draft personalized outreach tied to problems the offer can address.
• Follow-Up Planner: uses prospect responses to prepare relevant next steps.

As Palasz notes, the handoffs are meant to preserve context across the sequence: the researcher does not restart from scratch, the message writer receives prospect context, and the follow-up planner can account for the conversation so far.

“Your sales team reviews the output and decides what actually gets sent.”

Human review remains part of the system

That review step is a central feature of Palasz’s description. The agents prepare research, messages, and follow-up suggestions, while the sales team retains the decision about what to send. The post presents the setup as a way to support a research-driven workflow, not as a replacement for salesperson judgment.

A library for getting started

Palasz says the free library includes setup instructions, ready-to-use Claude Code prompts, agent handoff rules, and review checkpoints. He positions the materials as a starting point for teams that want to build the workflow without beginning with a blank page.

In Palasz’s view, better prospecting depends on connecting account fit with context about why a conversation could be useful. His post’s core argument is that automation can help organize that work, while human review determines which outputs merit action.