Prospecting agent for B2B financial services sales teams on Salesforce

What The Prospector does

The Prospector works for the sales team at a 51 to 200 person financial services firm that sells to businesses (for example payments, treasury, lending, or wealth and benefits platforms sold to finance leaders at mid-market companies). It owns the top of the outbound funnel: maintaining the ICP and persona definitions, watching for buying signals, researching and enriching accounts and contacts, drafting personalized first-touch and follow-up sequences inside approved messaging frameworks, and handing warm prospects to the right rep with a research brief. Salesforce stays the system of record. Reps own conversations once a prospect engages, and compliance owns the approved language library the agent writes from. Because the firm wants it built and kept running, the agent ships with monitoring, a weekly tuning cycle, and a named owner on the operator side.

Custom build

The firm runs Salesforce, so a custom Claude build orchestrated with n8n is the better fit than HubSpot Breeze, which is designed around HubSpot data. Claude handles the judgment-heavy work (ICP scoring, research synthesis, persona-specific writing, reply classification) and can be constrained tightly to an approved messaging library, which matters in a regulated industry. n8n connects Salesforce, Warmly, Cognism, FullEnrich, Salesloft, and Chili Piper, and can be self-hosted to keep prospect data in the firm's own environment. Salesloft keeps sequencing, human approval, and activity logging inside a Salesforce-native workflow so every touch is recorded for audit and retention.

What starts it

• A target account shows a buying signal (repeat visits to pricing or product pages, a new CFO or controller hire, funding, expansion, or a relevant regulatory or vendor change)
• A new account is added to a Salesforce target list or moves into an active ABM tier
• A known contact from a past opportunity or closed-lost deal changes jobs or re-engages with content
• An inbound lead is created in Salesforce that matches the ICP but has not booked a meeting
• A weekly scheduled run to refresh priority accounts that have gone 30+ days without a touch

What it reads

• Salesforce (accounts, contacts, opportunities, closed-won and closed-lost history, activity, owner and territory assignments)
• Website visitor and intent signals from Warmly
• Contact and company data from Cognism, with FullEnrich as a waterfall fallback for missing emails and direct dials
• Public sources: company websites, press releases, job postings, annual reports and regulatory filings where relevant
• Approved messaging library and compliance rules maintained in a shared knowledge base
• Sequence engagement data from Salesloft (opens, replies, clicks, bounces, unsubscribes)

When a person takes over

• A prospect replies with interest, a question about pricing, terms, rates, or regulatory matters, or anything beyond booking a meeting: the assigned rep takes over because the agent must not make product, pricing, or compliance claims
• The account is already owned by a rep, is an existing customer, or sits in a named strategic tier: the account owner decides whether and how to engage
• A draft would need a claim, case study, or statistic that is not in the approved messaging library: compliance or marketing reviews before anything is used
• A reply is negative, mentions a complaint, legal concern, or data request (such as a deletion request): the SDR lead or compliance handles it within the defined response window

Rules it follows

• Write only from the approved messaging and proof-point library, never promise returns, rates, savings, or outcomes, and include required disclosures and opt-out language in every email
• Respect consent and suppression rules: check Salesforce do-not-contact flags, regional rules (CAN-SPAM, GDPR, CASL), and global suppression lists before any contact is created or sequenced
• Never contact accounts with an open opportunity, active customers, or contacts touched by a rep in the last 30 days, and cap new contacts per account to avoid flooding a buying committee
• Every research claim must cite a source and be under a set age, unverifiable facts are dropped rather than guessed, and personal or non-business data is never used in personalization
• Enforce daily send limits, domain warmup, and bounce thresholds, pausing sequences automatically if bounce or complaint rates exceed set limits, and log every message for audit and retention

How you know it works

• Meetings booked per week from agent-sourced accounts
• Pipeline created and pipeline value attributed to agent-sourced meetings in Salesforce
• Positive reply rate by persona and signal type
• Draft approval rate without edits (a measure of message quality)
• Rep hours saved on research and list building per week

From pilot to live

1. Pilot (weeks 1 to 4)Lock the ICP, personas, and approved messaging with sales and compliance. Connect Salesforce, Warmly, Cognism, FullEnrich, and Salesloft through n8n. Run the agent for two reps on one segment with every draft human-approved, and review output quality, data accuracy, and compliance flags weekly.
2. Expand (weeks 5 to 10)Add remaining reps and personas, turn on reply classification and Chili Piper booking, and introduce job-change and closed-lost re-engagement plays. Move proven follow-up steps to auto-send while first touches stay approved. Report meetings and pipeline against the pre-pilot baseline.
3. Run and optimize (ongoing)The agent runs across the full team with a named operator owning monitoring, deliverability, and a weekly tuning cycle (prompt updates from rep edits, scoring model refresh from new wins and losses, new signals). A monthly review with sales leadership and compliance covers results, exceptions, and messaging library updates.