baseA founder messaged me last week. "Should we cancel our outbound stack and just use HubSpot Prospecting Agent?"
I told him to read this first.
30 days inside the product. We built real campaigns and real pipelinet. Here is the job HubSpot Prospecting Agent is excellent at, the job it is dangerous at, and how to tell which one you are actually running.
Depends on the motion you are running. Warm follow-up inside HubSpot, yes. Cold outbound at scale, no. The table below shows why.
Prospecting Agent is the AI SDR layer inside Breeze. It sits on top of HubSpot CRM, researches a contact, drafts an email, sends a sequence, and follows up.
It runs off something HubSpot calls a selling profile. That is where you set the value prop, products, target industries, ICP, CTA, and which user the emails come from. One profile per product.
Two modes. Semi-autonomous waits for your review before sending. Fully autonomous sends on its own. Either way, the agent stops the moment a contact replies or books a meeting.
The thing most reviews miss. This is not a sequence tool with better tokens. Prospecting Agent pulls from CRM data, LinkedIn, the company website, news, and funding rounds, and writes a different email for every recipient. Whether it is worth the credits it burns is what I spent 30 days figuring out.
First profile took me 45 minutes. Second one was faster because I stopped second-guessing the fields. Here is what each step actually looks like.
Sales, then Prospecting Agent, then Set up agent. Breeze auto-pulls a value prop from your website. Read it. Then rewrite it.
The auto-pull is generic by design. The agent inherits every weakness in that copy. Garbage in, narrative-and-preachy out.
I rewrote the value prop, the products, the pain points, the ICP industries, and the personas before I let the agent send anything.
You can send from the contact owner or from a single user. The product page sells contact-owner mode hard.
I tried it. Went back to single-user mode in a week.
Reason: You cannot isolate sender performance. Pick one user. Make sure that user has an active connected mailbox and a configured signature, otherwise the agent silently fails and you find out three days later when nothing has sent.
Drop in the meeting link the agent should push toward. Tag the meeting type so booked meetings categorize correctly in CRM.
I used our intro call. Booked meetings show up in reporting tagged the right way. Matters when you want to attribute pipeline to the agent versus other channels.
You can attach URLs and documents the agent references. Useful, not transformative.
Compared to a real Knowledge Base in a tool built for outbound, the depth is not there. Drop in your overview page and your most relevant case studies. Skip the rest.
Start in semi-autonomous. Always. I do not care how confident you are.
First batch you will edit hard. Less by week two. Almost not at all by week three. The agent learns from edits. If you skip review and go fully autonomous on day one, you leave the entire compounding curve on the table.
Default is 4 days minimum between sends. Cap is 5 emails per enrollment. Reasonable defaults. Also ceilings you will hit fast on cold lists.
Four things genuinely impressed me. I am not soft-selling the wins to set up the criticism.
Every action lands in the contact timeline. Replies route to the HubSpot inbox. Engagement logs automatically.
If your team lives in HubSpot, this is a workflow win you cannot replicate with a third-party tool. The data model wins.
Form submitted. List joined. Pricing page viewed three times in a week. The agent fires the same minute.
That is the classic HubSpot strength.When a prospect signals intent, the agent moves before competitors even know that company is in-market.
Genuine pipeline. Not theoretical.
First batch I reviewed, I edited every email.
Week three I was tweaking maybe one in five drafts. The agent learns from edits.
Skip the review phase and go straight to fully autonomous and you leave the entire compounding curve on the table. Do not skip it.
I built one profile for a HubSpot audit motion, another for full implementations. Different value props, different CTAs, different meeting types.
The agent does not bleed messaging across the two.
Table stakes for any team selling more than one thing. HubSpot got it right.
The honest part.
Prospecting Agent was built for one motion. That motion is not cold outbound. Here is where I hit walls.
The agent uses your connected primary mailbox.
Warm follow-up to known contacts? Fine. Cold outreach to hundreds of unverified addresses? You are gambling your main domain reputation on the agent's sending pace.
No warmup. No rotation. No isolation between cold sends and your real business email.
One bad list and your domain is in the spam folder for three months. Real cold infrastructure does not look like this.
No native LinkedIn outreach.
The agent can set a reminder for a rep to send a LinkedIn message manually. The agent itself does not touch LinkedIn.
Multi-channel sequences across email and LinkedIn book noticeably more meetings than email-only. Picking a single-channel tool in 2026 is a strategic miss.
Default is 3 emails per enrollment. Configurable up to 5. Spacing is at least 4 days.
For warm leads, plenty. For cold outbound, we need flexibility to configure all the emails.
Manual re-enrollment defeats the point of automation.
Every recommended lead burns credits.
Some Sales Hub plans include a monthly allowance. Most teams running real outbound volume blow through it inside two weeks.
Buying more credits is fine. But you are now paying a per-lead variable cost on top of a Hub seat that already costs a few hundred a month. Compare that to flat-priced outbound tools and the math gets uncomfortable at scale.
Out of the box, drafts read like a thoughtful LinkedIn comment.
They open with reflection. Mention the prospect's company in flattering terms. Take three paragraphs to ask for a meeting.
That is not a cold email. A cold email is short. Specific. Asks once.
The agent learns from your edits. But you are doing the rewriting work, which is half the reason you bought an AI SDR in the first place.
Single sender per selling profile.
Push past 100 sends a day from one mailbox and Google starts throttling. Real cold infrastructure spreads volume across many mailboxes and rotates them automatically.
Prospecting Agent has no concept of any of this because it was not designed for cold.
To use Prospecting Agent you need Sales Hub Professional or Enterprise.
If you only want an AI SDR, you are buying a full Sales Hub stack to access the feature.
HubSpot-native teams already have those seats. Fine. Outbound-first teams evaluating tools? The actual cost of entry is the agent plus the Hub itself. Changes the math considerably.
If you are picking between these two for B2B outbound, this is the table that decides it.
Read across the rows. Ask which side matches your motion. The answer is usually obvious.
Pick Prospecting Agent if you are this team:
Three or more describe you? Prospecting Agent earns its place.
The CRM-native flow, the trigger-based enrollment, the timeline integration. None of that is replicated by any third-party tool. Use it.
Outbound-first motion changes everything.
You need infrastructure built for cold sending. Channel coverage that includes LinkedIn. Volume to actually move pipeline.
None of that is what Prospecting Agent does. All of that is what I built Agent Frank to do.
Agent Frank fits if most of these are true:
End-to-end outbound. Multi-channel sequences across email and LinkedIn. Unlimited mailboxes. Unlimited LinkedIn senders in one sequence.
Continuous ICP-based prospecting. You set job titles, locations, industries. The agent finds new contacts on its own.
A real Knowledge Base where you upload product brochures, docs, and website links so every email references your business correctly. 20 plus languages natively.
On infrastructure, this is where the gap is widest.
Agent Frank does not send from your primary mailbox. You bring your own domains and mailboxes, or use Infraforge for dedicated IPs, or pick Megaforge: a premium multi-ESP setup with 20 mailboxes split across Gmail, Outlook, Mailforge, and Infraforge that sends roughly 300 emails a day.
Warmup runs automatically through Warmforge. 2 weeks before sending.
None of that exists in Prospecting Agent because none of that is what Prospecting Agent was built for.
Agent Frank starts with a demo.
From there, my team runs the setup across seven steps. We open a complimentary Salesforge account that becomes Agent Frank's office. We build a Knowledge Base from your brochures and website. We pick infrastructure (your own, Infraforge, or Megaforge) and run 2 weeks of warmup. We set up prospecting (your contacts or continuous ICP-based search). We pick the mode (Auto-Pilot or Co-Pilot), the language, the goals. Then he goes live.
Every account gets a dedicated Account Manager and a shared Slack channel for the actual humans who help you tune the agent.
Agent Frank does not run alone.
Replies across email and LinkedIn land in Primebox, the unified inbox inside Salesforge. Lead sourcing connects to Leadsforge, a search engine across 500M plus contacts with waterfall enrichment. Warmup runs through Warmforge. Infrastructure is Mailforge for shared IPs at scale, or Infraforge for dedicated IPs.
One login. One stack. Built to work together because I built it that way on purpose.
The advertised price is misleading on its own.
The real cost has three layers. The Sales Hub seat. The HubSpot Credits per lead. The infrastructure costs (warmup, deliverability monitoring) that are not included.
Stack them up and the actual cost-per-meeting at scale is higher than most teams expect.
Here is how the cost structure stacks against Agent Frank, which charges flat and bundles infrastructure.
For warm-lead motions inside HubSpot, the credit model is efficient. The agent only fires on real signals.
For high-volume cold outbound, the math swings the other way. Flat pricing with bundled infrastructure (warmup, dedicated IPs, Primebox replies) wins.
Pick the pricing model that matches your motion. That is the only question that matters.
No. HubSpot Prospecting Agent is included in Sales Hub Starter, Professional, and Enterprise editions and runs on HubSpot Credits. Some subscriptions include a monthly credit allowance, but credits are consumed each time the agent recommends a lead, so heavy usage can require buying additional credits.
No. Prospecting Agent is email-only. It can set reminders for reps to send LinkedIn messages manually, but the agent itself does not send LinkedIn outreach automatically. For native multi-channel sequences across email and LinkedIn, you need a tool built for that, such as Agent Frank inside Salesforge.
It can technically send to cold contacts, but the design is built for warm-lead nurture inside the HubSpot CRM. The agent sends from a single connected primary mailbox, has no built-in warmup, no mailbox rotation, and caps at 5 emails per enrollment. For high-volume cold outreach, a dedicated AI SDR with cold infrastructure is a better fit.
HubSpot sequences are template-based and rely on tokens for personalization. Prospecting Agent uses Breeze AI to research each contact (CRM data, LinkedIn, website, news, funding) and write a custom email per recipient. Sequences are faster to set up; Prospecting Agent does deeper personalization but consumes credits per lead.
For B2B teams running cold outbound at scale, Agent Frank inside Salesforge is the closest like-for-like alternative. Both are autonomous AI SDRs that handle research, drafting, sending, and follow-ups. Agent Frank adds LinkedIn, unlimited senders, dedicated cold-email infrastructure, 20+ languages, and a dedicated Account Manager. For a wider list of options, see the AI prospecting tools comparison.
By default, Prospecting Agent sends 3 emails per enrolled contact in fully autonomous mode and can be configured up to 5. Spacing is at least 4 days between sends. The agent stops the sequence automatically when a contact replies or books a meeting.
Salesforge connects with HubSpot through its standard CRM integration, so contact data and engagement can sync between the two. Most teams choose one or the other based on motion: HubSpot Prospecting Agent for warm leads inside HubSpot, Salesforge with Agent Frank for cold outbound at scale.
.png)
.png)
