The strategic read is simple: Microsoft is dissolving the CRM into the places sellers already work. You don't open Dynamics 365 anymore — pre-meeting briefs, account updates, and case alerts come to you in Teams, and agents log everything back to the CRM without you touching a form.

Salesforce shipped seven job-ready SDR and sales agents in September. Google shipped a universal Gemini agent with coworker identities on the same day as this Microsoft release. OpenAI shipped Dots always-on agents at DevDay. Now the vendor that owns the inbox and the meeting — Outlook and Teams — has put its own SDR agent into public preview, with usage billing switching on November 16, 2026.

Here's what actually shipped, what the full Microsoft sales agent lineup now looks like, what it costs, and where it falls short.

What Microsoft Announced on October 8​

Four things, at different stages of readiness:

1. Thirty pre-built Copilot skills (available now). Packaged skills across Dynamics 365 Sales, Customer Service, and Customer Insights — pipeline summaries, opportunity risk checks, follow-up drafting, segment building. These run inside Microsoft 365 Copilot, so a seller asks in plain language and the skill executes against live CRM data.

2. Dynamics 365 CRM in Teams (public preview). Sellers get pre-meeting briefs, account updates, and deal alerts directly in Teams — no tab-switching into the CRM. This is the "ambient CRM" bet: the system of record becomes a background service feeding the collaboration layer.

3. Sales Development Agent (public preview). The headline item. It researches prospects, writes personalized outreach, manages follow-ups, and hands qualified leads to sellers — the same autonomous SDR category as Salesforce's Hunter agent and the AI SDR tools that have been selling this motion for two years. Copilot credit billing starts November 16, 2026.

4. Service Agent (private preview). Restricted to Microsoft's "Frontier" early-access customers. It fields customer requests across Outlook, Teams, and Office apps and creates CRM cases automatically.

There's also Dynamics 365 Activate, an AI migration tool in public preview since September that maps a competitor CRM environment and recommends a migration path. Point it at your Salesforce org and it builds the move plan — a direct shot at switching costs, the strongest moat in CRM.

Microsoft's proof point for the SDR agent: Adobe's early test, where the Sales Development Agent "helped unlock meetings with more than 10 net-new customers within three weeks of a limited launch." Treat it the way you'd treat any vendor-supplied pilot stat — directionally interesting, not a benchmark. Ten meetings in three weeks is roughly what one competent human SDR produces.

The Full Microsoft Sales Agent Lineup (October 2026)​

Microsoft's agent naming is genuinely confusing — there are at least six, and one is being killed this month. Here's the map:

Two things stand out.

First, the Sales Close Agent retirement is a 30-day rug pull. New instances were blocked September 30; existing ones get removed October 30. Teams that built process around it are being pointed at the Sales Development Agent — a different tool for a different job. This is the risk of building on preview-stage agents, and it won't be the last time. If a vendor agent is in preview, treat it as a pilot, not infrastructure.

Second, the architecture echoes what Outreach did with MCP and what Salesforce did with Claudeforce: the GA Sales Agent is grounded in live Dynamics 365 data via Model Context Protocol. MCP has quietly become the standard plumbing of the agentic sales stack across every major vendor.

What It Costs: The Credit Math​

Microsoft's pricing has three stacked layers, and you need to understand all of them before the November 16 billing switch.

Layer 1 — the CRM seat. Dynamics 365 Sales runs $65/user/month (Professional), $105 (Enterprise), or $150 (Premium). Premium is the agentic tier and bundles 1,000 Copilot credits per user per month.

Layer 2 — the Copilot seat. Microsoft 365 Copilot is $30/user/month (annual), and the GA Sales Agent requires it, on top of a qualifying Microsoft 365 plan.

Layer 3 — agent usage. Copilot credits are $0.01 each pay-as-you-go, or $200 for a 25,000-credit pack. Microsoft's own task tiers: light tasks burn ~100–300 credits ($1–$3), medium ~400–700 ($4–$7), heavy 700+ ($7+). The Sales Development Agent's autonomous workflow — research a prospect, write outreach, manage the follow-up thread — is a medium-to-heavy task every time it runs.

Do the math on Premium's bundled 1,000 credits: at ~500 credits per worked lead, that's two leads per user per month before you're paying overage. A real SDR motion working 150 accounts a month at that burn rate is roughly $750/month per rep in credits alone — on top of the $150 CRM seat and the $30 Copilot seat.

This is the same pattern we flagged with HubSpot's credit model (100 credits/lead against a 3,000-credit allowance) and Agentforce's $0.10-per-action metering: the headline seat price is the entry fee, and the agent usage meter is where the bill actually lives. Every major vendor has now converged on it.

Where This Is Strong — and Where It Isn't​

The distribution advantage is real. Microsoft owns the surfaces where selling actually happens: email (Outlook), meetings (Teams), documents (Office). An agent that drafts the follow-up inside the thread it's replying to, with CRM context already loaded, removes friction no standalone tool can. The futurum framing — Dynamics 365 as an "ambient CRM layer" — is the right read. Demand is there too: 48.6% of CX decision makers plan agentic AI deployment within 18 months.

The gaps matter for outbound teams:

• No native prospecting data. The Sales Development Agent researches from your CRM, public websites, and approved internal sources. There's no bundled contact database, no intent data, no visitor identification. Microsoft assumes the lead already exists in Dynamics 365 — the hard part of outbound is everything before that.
• Frontier-gated rollouts. The Service Agent and the most capable agent features land with Frontier early-access customers first. Mid-market teams are at the back of the queue.
• Preview churn. The Sales Close Agent just got deleted with 30 days' notice. The Sales Development Agent has no published GA date. Building quota-carrying process on it today is a gamble.
• Dynamics 365 gravity. Everything is best inside Microsoft's CRM. The Sales Agent can read Salesforce data, but the deep integrations — Fabric lakehouse joins, Customer Insights segments — are Dynamics-only. This is an ecosystem play, like Gong, Apollo, and ZoomInfo's agent builders, each pulling you deeper into their stack.

What Sales Teams Should Do​

If you're on Dynamics 365: Turn on the 30 Copilot skills now — they're included and they're the lowest-risk win. Pilot the Sales Development Agent before November 16 while usage is free, instrument credit burn per worked lead from day one, and project your real monthly cost before the meter starts. If you were using the Sales Close Agent, migrate this week — it's gone October 30.

If you're on Salesforce or HubSpot: Nothing here forces a move. The Microsoft agents are a reason to stay in the Microsoft ecosystem, not a reason to join it — and Dynamics 365 Activate cuts both ways, since every vendor is now building AI migration tooling to raid everyone else's installed base.

For every team: The bottleneck these agents don't solve is knowing who to contact. The Sales Development Agent executes outreach against leads you already have; it doesn't find the in-market accounts visiting your site or fire on buying signals. That layer — visitor identification, signal detection, and automated first touch — is where MarketBetter sits, and it feeds any CRM agent downstream, Microsoft's included.

The agentic CRM war now has every major vendor on the field: Salesforce, Google, OpenAI, HubSpot, and Microsoft, all shipping autonomous sellers with usage meters attached. Microsoft's edge is that its agents live where your buyers already read email and take meetings. Its tax is three stacked subscriptions plus a credit meter. Price the whole stack before you pilot.

Want the signal layer that makes any of these agents worth running? Book a demo and see how MarketBetter identifies in-market accounts before your competitors' agents ever email them.

Buried under the platform language is the detail that matters for revenue teams: Google is shipping coworker agents — persistent AI teammates that get their own @agents.company.com email address, their own calendar, their own entry in the company directory. You don't prompt them. You email them, schedule them, and assign them objectives like you would a new hire.

And in a week where every vendor is metering agents by the action, the conversation, or the credit, Google said the quiet part: it does not plan per-seat licensing for coworker agents in Workspace.

Here's what launched, how it compares to the agents Salesforce, OpenAI, and HubSpot shipped in the last month, and what a sales team should actually do about it.

What Google Actually Shipped​

The Gemini agent collapses Google's scattered enterprise AI surface — Gemini Enterprise, Workspace AI, Agentspace — into one agent you interact with four ways:

• Chat with it like any assistant
• Assign it objectives and let it plan the work itself
• Schedule it to run recurring jobs
• Trigger it from events — a form submission, an inbound email, a CRM change

The architecture is the real shift. The agent runs persistently in the cloud with shared memory and a personalization graph, so a multi-day job keeps running after you log out. It spawns temporary sub-agents for individual tasks and reports back when done. If you've read our coverage of OpenAI's Dots always-on agents, the pattern is familiar — the industry has converged on "agents that never clock out."

It reaches beyond Google's walls, too. The agent works across Google Workspace, Microsoft 365, and Slack, and connects to enterprise systems including Salesforce, ServiceNow, Jira, Snowflake, and Databricks. For grounding, Google announced a Knowledge Catalog for business definitions — during development, Bloomberg Media reported a 63% lift in SQL query accuracy when queries were grounded in it.

One more surprise: Smart Routing sends tasks across both Gemini and Anthropic's Claude models. Google is routing work to a competitor's model when it's the better fit for the task. That's a pragmatic concession to how enterprises already operate — most teams we talk to run Claude for sales workflows alongside Gemini already.

Coworker Agents: The Feature That Matters for Sales​

Every vendor now sells "digital workers." Salesforce has Agentforce Coworker and the Piper and Hunter SDR agents. OpenAI has Dots. What Google added is an identity model the others don't have:

A coworker agent gets a real Google Workspace account — email address, calendar, storage, directory entry. That sounds mundane. It isn't:

• Reps interact with it like a teammate. Forward a prospect thread to research@agents.company.com and get an account brief back. CC it on a deal thread and it keeps the CRM updated. No new interface to learn — the interface is email, which is where sales lives anyway.
• It can be invited to things. Put the pipeline-review agent on the Monday call invite. Schedule the follow-up agent to sweep stalled deals every Friday.
• IT can govern it like an employee. Provisioning, permissions, and offboarding run through standard identity management. Every action lands in the audit log attributed to the agent, not to whichever human triggered it. Agent identity is cryptographically attested, permissions propagate via OAuth, and an Agent Gateway acts as what Google calls an "AI network firewall."

That last point is why this launch will clear security review faster than most. The number one blocker we see when sales teams try to deploy AI SDRs is not capability — it's that security teams can't answer "who did that?" when an agent touches the CRM. A directory-native agent with its own audit trail answers it.

Sales Workflows This Unlocks​

Concrete plays a Workspace-based sales org can run once this hits GA:

1. An inbound triage agent with its own inbox. Route demo-requests@ to a coworker agent that enriches the lead, checks ICP fit against your Knowledge Catalog definitions, books the meeting, and logs it to Salesforce via the connector. This is the same job Salesforce's Piper does for $2 a conversation — except here it lives in the Gmail stack your team already pays for.

2. Scheduled pipeline hygiene. A recurring agent job that sweeps the CRM every morning for deals with no next step, stale close dates, or ghosted threads, then emails each rep their fix list. Multi-day persistence means it can chase its own follow-ups.

3. Event-triggered account research. New opportunity created in Salesforce → agent builds a brief from the account's website, news, and your internal docs → drops it in the deal folder and calendar invite before the first call. Pair it with the Gemini Skills your team has already written — skills define the playbook, the agent executes it unattended.

4. RFP and security questionnaire grinding. The Commerzbank case Google cited — manual document review cut from 20 hours to one — is the same shape as answering a 200-row security questionnaire from your champion's procurement team.

The common thread: these are jobs sales ops currently does with a patchwork of Zapier, spreadsheets, and interns. An agent with an email address and OAuth-scoped CRM access is a cleaner primitive.

Pricing: The Wedge Google Is Driving​

Google did not announce pricing, and final metering models are undisclosed. But the statement that there's no per-seat licensing planned for coworker agents in Workspace is aimed directly at how everyone else charges:

Treat "no per-seat" with appropriate skepticism — Google will meter something, likely tokens or compute, and undisclosed pricing is a reason to pilot, not to commit. But the strategic intent is clear. Google claims 8 million paid Gemini Enterprise seats across 4,200 companies and nearly 90% of the Fortune 100; it can afford to make agents a retention feature for Workspace rather than a new line item. Per-project spend caps with real-time pause are built in, which is more cost governance than most agent platforms launched with.

How It Stacks Up Against the Last 30 Days of Agent Launches​

October has been absurd. In four weeks we've covered Salesforce's Koa model and AIforce suite, Gong, Apollo, and ZoomInfo all shipping agent builders in the same week, Claudeforce putting Salesforce inside Claude, and OpenAI's Dots. Where Gemini agent fits:

• vs. Salesforce: Agentforce agents are strongest inside the CRM with CRM data. Gemini's coworker agents are strongest around the CRM — email, calendar, docs, research — with Salesforce as one connector among many. If your reps live in Gmail and only visit Salesforce under duress, Google's shape fits better.
• vs. Microsoft Copilot: Microsoft has native-integration advantage in Microsoft-standardized orgs and existing enterprise agreements. Google's counter is cross-application context — one agent spanning Workspace and Microsoft 365 and Slack — plus multi-model routing. If your company runs Office, wait for evidence it works well there.
• vs. point-solution AI SDRs: Vertical sales agents still win on out-of-the-box sales judgment — a universal agent doesn't know what a good discovery question sounds like. Google's industry-specific agents are starting with financial services and legal (in preview); there's no sales-specialized agent yet.
• vs. the model layer: This launch is about orchestration, not model quality. Google's frontier-model story for sales is Gemini 4 Argon, and Smart Routing means the agent may quietly use Claude for some of your tasks anyway.

What Sales Leaders Should Do Now​

1. If you're on Workspace: ask your Google rep for the private beta. The identity and audit model means security review can start now, before GA. Inventory the three workflows above and pick one.
2. If you're on Microsoft: nothing to do yet. The cross-suite claims need proof, and Copilot's agent roadmap is the default path for your stack.
3. If you're mid-evaluation on an AI SDR vendor: finish the evaluation, but add a column for "does Workspace eat this feature by Q1?" Inbound triage and meeting booking are squarely in the blast radius.
4. Watch the metering announcement. "No per-seat" is a direction, not a price. The number that matters is cost per worked lead, and nobody can compute it yet.

The pattern across this entire launch wave — Salesforce, OpenAI, HubSpot, now Google — is that always-on agents with real identity are becoming infrastructure, not features. The teams winning with them aren't the ones with the fanciest agent; they're the ones feeding agents clean signal about which accounts are actually in-market. That's the layer we build at MarketBetter: visitor identification and intent signals that tell your agents — Gemini, Agentforce, or ours — who to work and why. Book a demo to see how signal-fed agents outperform prompt-fed ones.

FAQ​

What is the Gemini agent? A single universal AI agent for work announced by Google Cloud on October 8, 2026 at Gemini at Work. It answers questions, handles knowledge work, creates media, writes and runs code, and executes multi-day tasks persistently in the cloud across web, mobile, desktop, and CLI.

What are Gemini coworker agents? Persistent agents with their own Google Workspace accounts — email address, calendar, storage, and directory entry. Teams interact with them by email or meeting invite, and IT governs them through standard identity management with per-agent audit trails.

When is the Gemini agent available? It's in private beta as of October 8, 2026, with general availability expected around the end of October or early November 2026. Industry-specific agents for financial services and legal are in preview.

How much does the Gemini agent cost? Google has not announced pricing. A company representative said there are no plans for per-seat licensing of coworker agents in Workspace, but the final metering model is undisclosed.

Does the Gemini agent work with Salesforce? Yes. Connectors cover Salesforce, ServiceNow, Jira, Snowflake, Databricks, Confluence, and Microsoft 365/Teams, with OAuth-propagated permissions and action-level audit logging.

Anthropic released Claude Haiku 5.5 on October 7, 2026, and the number that matters is the price: $0.10 per million input tokens and $0.50 per million output — down from $1.00 and $5.00 on Haiku 4.5. That's not a discount. That's a different category of spend. Two weeks after Opus 5.5 cut flagship costs 40%, the budget tier just dropped roughly 75%.

For sales teams, the practical translation: the per-unit cost of high-volume pipeline work — scoring leads, triaging replies, extracting fields, summarizing calls — just fell below the threshold where anyone needs to approve the budget. Scoring your entire 100,000-lead database now costs about as much as one DoorDash order. We ran the math below.

What launched, in 30 seconds​

• Claude Haiku 5.5 is live via API (claude-haiku-5-5) and on AWS Bedrock, Google Cloud Vertex, and Microsoft Foundry.
• $0.10 / $0.50 per million tokens (input/output) for requests up to 100K tokens — a 90% list-price cut from Haiku 4.5's $1 / $5. Anthropic says ~75% cheaper in practice on average workloads.
• Above 100K tokens per request, pricing steps up to $0.50 / $2.50 — still half of Haiku 4.5. More on this trap below.
• 1M token context window (up from 200K) and 128K max output.
• Cache reads at $0.01 per million. Batch API is another 50% off.
• Positioned explicitly for classification, extraction, and routing — adaptive thinking with a medium default effort.
• Benchmarks jumped generationally: OSWorld computer use went from 15.7% → 72.4%, Terminal-Bench agentic coding from 0% → 39.2%, GDPval knowledge work from 735 → 1,620.

The pricing table​

Two things to internalize:

1. The cheap tier has a ceiling. The $0.10/$0.50 rate applies to requests up to 100K tokens. Go over, and the 5x multiplier applies to the entire request, not just the overage. With a 1M context window it's now easy to stuff a whole CRM export into one prompt — and quintuple your bill doing it. For high-volume sales work, chunk requests to stay under 100K. The cheap tier is the whole point.

2. Cache reads cost a penny per million. A production agent re-reading a 20K-token scoring rubric on every call now pays effectively nothing for it. If you structure prompts so stable context caches (the same advice we gave for Opus 5.5), repeated context is a rounding error.

Real cost math: scoring 100,000 leads​

Take the workflow from part 6 of our SDR playbook — building a lead scoring model: score every lead in your database against your ICP with a reasoned 1-100 score and a one-line justification.

Assume per lead: ~2K tokens of input (lead record, firmographics, recent activity), ~100 tokens of output, plus a cached 15K-token rubric.

• Haiku 4.5: 200M input + 10M output ≈ $200 + $50 = ~$250
• Haiku 5.5: $20 + $5 ≈ ~$25
• Haiku 5.5 via Batch API: ~$12.50

Re-scoring your entire database weekly — something nobody did because it cost real money — is now ~$50/month on batch. Same story for the other volume workloads:

At these prices the model cost disappears from the decision entirely. What's left is the part that was always harder: data plumbing, prompt quality, and orchestration — deciding what's worth doing at all. That's been our consistent finding across every AI BDR tool we've ranked: the model is the cheapest component in the stack.

The benchmark that actually matters: computer use went from broken to usable​

Most Haiku 5.5 coverage leads with coding scores. For GTM teams, the sleeper result is OSWorld 2.1: 72.4%, up from 15.7% on Haiku 4.5. That's the "operate an app through screenshots and clicks" benchmark — and 72.4% on a budget model is within shouting distance of what flagship models scored a generation ago.

Why it matters for sales: the surfaces you prospect on often have no API — vendor portals, event platforms, LinkedIn Sales Navigator. Browser-driving agents were previously flagship-only territory because cheap models couldn't reliably click the right thing. A budget model that can operate a browser changes the cost structure of scraping-adjacent workflows — with the usual caveat that a 72% benchmark still means budgeting for failures and human review on anything customer-facing.

The other notable jump: Humanity's Last Exam went from 10.2% to 45.9% (57.4% with tools). This is not last year's "fast but dumb" small model. It reasons well enough to trust with judgment calls like "is this reply a genuine objection or an unsubscribe?"

Haiku 5.5 vs GPT-6 Luna​

OpenAI's budget model GPT-6 Luna matches Haiku 5.5's list price at the low tier, so the comparison comes down to quality and token efficiency:

• Quality: Haiku 5.5 leads on the published benchmarks, including agentic tasks — consistent with what we found when testing Claude against ChatGPT on real SDR workflows.
• Token efficiency: Luna reportedly completes comparable tasks with roughly one-third the output tokens. Identical list price does not mean identical cost per task — a verbose model at $0.50/M output can cost more than a terse one.

Our advice stands: benchmark on your replies and your lead records. For classification and extraction, output lengths are short either way and the difference is noise. For summarization-heavy work, measure tokens per completed task, not price per token.

The subagent pattern: where Haiku 5.5 actually fits​

The architecture Anthropic is pushing — and the one that shows up in launch-customer stories — is a flagship orchestrator delegating narrow tasks to Haiku subagents. Opus 5.5 plans the account research; Haiku 5.5 pulls the revenue line from the 10-K, classifies the tech stack, extracts the org chart.

One practical warning from early multi-agent cost breakdowns: delegation has overhead. In one published example, twenty Haiku 5.5 subagent calls accounted for just 7% of a workflow's total cost — the orchestrator's planning and handoffs consumed the rest. Passing work to a subagent and back can cost several times the work itself. The pattern pays off when the delegated task is genuinely high-volume (hundreds of extractions), not when you're routing a single lookup through three layers of agents.

If you're building this kind of system, the structure matters more than the models — our complete guide to Claude for SDRs covers the workflow design, and the nightly research-run pattern is the natural place to slot Haiku in for the extraction steps.

What to actually do this week​

1. Re-route your volume workloads. Anything currently running on Haiku 4.5, GPT-6 Luna, or a flagship at low effort — triage, scoring, extraction, routing — test on claude-haiku-5-5. The price floor moved; your model routing should too.
2. Keep requests under 100K tokens. Chunk big jobs. The 5x long-context multiplier applies to the whole request, and almost no classification task needs 100K tokens of context.
3. Move overnight jobs to batch. Scoring and enrichment runs that finish by morning get another 50% off — that's the $12.50 full-database score.
4. Re-score things you stopped scoring. Weekly full-database re-scores, re-classification after ICP changes, backfilling old call summaries — jobs that were "not worth the spend" at $250 are impulse purchases at $25.
5. Don't promote it past its weight class. Haiku 5.5 is built for narrow, well-defined tasks. Multi-step account strategy, win/loss synthesis, and anything where a wrong conclusion costs money still belongs on Opus 5.5. The subagent split exists for a reason. And as OpenAI's Dots launch and Gemini 4 Argon showed the same month: every vendor is racing to make the engine cheaper, and none of them are solving what to point it at.

FAQ​

What does Claude Haiku 5.5 cost? $0.10 per million input tokens and $0.50 per million output for requests up to 100K tokens; $0.50/$2.50 above that. Cache reads are $0.01 per million and the Batch API is 50% off. Anthropic estimates ~75% lower cost than Haiku 4.5 on typical workloads.

Is Haiku 5.5 better than GPT-6 Luna? On published benchmarks, yes — Haiku 5.5 leads across the board, including agentic coding and computer use. Luna is more token-efficient on output, which can close the cost gap on verbose tasks. Test both on your own workload.

What's the difference between Haiku 5.5 and Opus 5.5 for sales work? Haiku 5.5 ($0.10/$0.50) is for high-volume, narrow tasks: classification, extraction, triage, scoring. Opus 5.5 ($4/$20) is for multi-step reasoning: account research, territory planning, deal strategy. Production stacks increasingly use Opus as the orchestrator and Haiku for the volume work.

Can Haiku 5.5 do computer use? Yes — 72.4% on OSWorld 2.1, up from 15.7% on Haiku 4.5. Browser-operating agents on a budget model are now viable for internal workflows, though error rates still require human review for anything customer-facing.

Tokens are approaching free. Pipeline isn't. MarketBetter is the orchestration layer that decides what all that cheap inference should actually do — turning signals into a daily playbook of who to contact, why, and what to say. Book a demo →

This is the moment the AI SDR category stopped being a startup niche. The largest CRM vendor on the planet is now shipping named, pre-built AI sales reps as products. If you run a sales team, here's what Piper and Hunter actually do, what they cost, where they're genuinely strong, and where the fine print bites.

The short version​

• Piper (inbound): engages website visitors and inbound leads, qualifies them against CRM data, and books meetings. GA now. This is the Qualified product Salesforce bought for $1.2 billion, rebadged as a job-ready agent.
• Hunter (outbound): researches accounts, prioritizes targets, writes outreach, and works a pipeline "over weeks and months." Pilot now, GA November 2026. It's the first agent on Salesforce's new long-horizon runtime.
• Both require you to live inside the Salesforce (and increasingly Slack) ecosystem. On HubSpot or Pipedrive? These agents don't exist for you.
• Pricing was conspicuously absent from the announcement. The Agentforce commercial units underneath — Flex Credits, per-conversation pricing, user licensing — are where the real math lives.

Where Piper came from: the $1.2B Qualified deal​

Piper isn't new. It's the flagship AI SDR from Qualified, the company Salesforce agreed to acquire in December 2025 and closed on April 1, 2026 — for a consideration of $1.2 billion, $1.1 billion of it in cash, per Salesforce's own 10-Q filing.

Qualified built Piper as an anthropomorphized AI agent that greets inbound website visitors over chat, voice, and video, qualifies them using Salesforce CRM data, and books meetings for human reps. We covered the product in depth before the acquisition in our Qualified review and broke down what customers actually paid in our Qualified pricing analysis — list price around $68K/year for 25 users, with most teams negotiating to $40–50K, and total cost of ownership reaching six figures once you add the required Salesforce stack and services.

What the Dreamforce announcement changed: Piper is no longer a bolt-on you buy from a partner. It's a first-party Salesforce product in the Agentforce catalog, generally available today.

What Piper does​

• Engages inbound leads across your website and inboxes — chat first, with voice and video inherited from the Qualified platform
• Qualifies visitors against live CRM data (firmographics, account history, open opportunities)
• Books meetings directly onto rep calendars
• Routes work to other Agentforce agents when a job crosses roles or systems

Salesforce's proof points: its own internal Piper deployment (live since April 2026) reports a 6% conversion rate and 60+ meetings booked per week, and Asana reported 4x conversation volume from website deployments. Those are vendor-published numbers — treat them as a ceiling, not a floor.

One number worth sitting with: Salesforce says a typical Piper deployment takes 45 days. That's forty-five days of configuration, routing rules, and CRM hygiene before the inbound agent earns its keep. Teams evaluating AI SDRs on "time to first meeting" should price that in.

Hunter: Salesforce's first real outbound agent​

Hunter is the more interesting announcement, because outbound is the harder problem. Inbound agents respond to demand that already exists. Outbound agents have to create it — research an account, decide it's worth pursuing, write something a buyer will actually open, and keep working the account over weeks.

Salesforce's description: Hunter "works a sales pipeline from research to outreach, collaborating with sellers over weeks and months." Concretely, it:

• Researches and prioritizes accounts
• Drafts and sends outreach
• Learns from how your top sellers win
• Pursues quarter-long goals with persistent memory, rather than resetting every chat session

That last point is the technical story. Hunter is the first agent built on Salesforce's long-horizon runtime — the architecture that keeps a plan running over weeks, preserves memory across sessions, and accepts mid-flight steering from human reps. At Dreamforce, Salesforce said other agents will move to this runtime "over time," but at launch, Hunter is the only one.

Status: pilot now, general availability November 2026. Early proof point: Perk, a pilot customer, reported that 60% of its sales pipeline is now built by Hunter. Again — vendor-selected customer, vendor-published number.

If you want the broader context on how Salesforce's agent stack fits together — the Koa reasoning model, Agentforce Coworker, and the AIforce surfaces — we covered that in Salesforce Koa and AIforce: what sales teams need to know and Claudeforce, Salesforce inside Claude.

The pricing question nobody answered on stage​

The September announcement contained no pricing for Piper or Hunter. What exists instead is the Agentforce commercial model underneath:

The break-even math matters: at $0.10 per action, a conversation that takes more than 20 agent actions costs more under per-action pricing than the $2 conversation rate. Inbound qualification conversations — multi-turn, CRM lookups, calendar checks — chew through actions fast.

And that's before the platform underneath. Piper and Hunter require Salesforce — see our Sales Cloud pricing breakdown for what that base layer runs. The pre-acquisition Qualified pattern (list ~$68K, TCO $95K–165K+ with stack and services) is the most honest anchor for what a serious Piper deployment will cost. We'd expect Hunter, as the premium long-horizon product, to land above inbound pricing, not below it.

The lock-in fine print​

Three constraints that didn't make the keynote slides:

1. Salesforce-only, permanently. Qualified always required Salesforce CRM; the acquisition made that dependency permanent and extended it to Hunter. If your CRM is HubSpot, Pipedrive, or Attio, these agents are not an option — full stop. Our Qualified alternatives guide exists precisely for those teams.

2. The roadmap serves Agentforce, not you. Piper's development priorities are now set by Salesforce's platform strategy. Features that made sense for Qualified as an independent company — broader integrations, CRM flexibility — are off the table.

3. Hunter's runtime is a walled garden at launch. The long-horizon runtime is Hunter-exclusive. Custom agents you build on Agentforce don't get persistent multi-week execution yet, and Salesforce gave no delivery date for when they will. You're buying the packaged rep, not the capability.

Named agents are a packaging move — and a smart one​

Give the agent a name and a job title, and buyers stop evaluating a platform and start evaluating a hire. "Should we deploy Agentforce with custom topic configuration for outbound prospecting?" is a six-month committee decision. "Should we hire Hunter?" is a line-item.

Every vendor is converging here. OpenAI shipped always-on Dots agents, Gong launched autonomous pipeline agents, and the entire AI SDR tool market is racing from copilots to named digital workers. Salesforce's edge is distribution: 150,000+ customers who can switch Piper on inside a stack they already pay for.

The open question is quality. An inbound agent with a 6% conversion rate is useful. An outbound agent that sprays mediocre outreach at your best accounts under your domain's reputation is a liability. Hunter "learning from top sellers" is the right idea — whether it works outside pilot conditions is a November question.

What sales teams should actually do​

If you're a Salesforce shop with real inbound volume: Piper is worth a pilot. The Qualified product underneath is mature, and first-party packaging removes integration risk. Budget the 45-day deployment and model costs on conversations, not the sticker.

If you're evaluating Hunter for outbound: wait for GA in November and ask pilot references hard questions — reply rates, meetings sourced, and how much human steering it needed. "60% of pipeline built by Hunter" tells you nothing about pipeline quality.

If you're not on Salesforce — or don't want your outbound brain locked to one vendor: this launch doesn't change your options, it just raises the stakes. The pattern we see across teams comparing these tools (see our MarketBetter vs Qualified comparison) is that the hard part of outbound isn't sending messages — it's knowing who is in-market right now and what to do about them. That's the gap most agent platforms still leave to the human: a dashboard of signals you have to interpret yourself.

MarketBetter takes the opposite approach: it identifies who's actually showing buying intent — down to visitors on your own website — and hands your team a specific playbook of next actions, whether or not Salesforce is your CRM. If you're building the kind of signal-to-meeting motion Hunter is promising, our SDR playbook guide shows the workflow, and you can see the live product in action in 30 minutes.

Book a demo →

Sources: Salesforce Dreamforce 2026 announcements and job-ready agents launch (September 11, 2026); Salesforce FY2026 10-Q (Qualified acquisition consideration); Salesforce and Qualified acquisition announcements; Agentforce published pricing units. Vendor performance claims (Piper 6% conversion, Asana 4x conversations, Perk 60% pipeline) are Salesforce-published figures.

Most Dreamforce coverage treated these as two more logos in a crowded keynote. For sales teams, they're actually one bet: Salesforce is wagering that a smaller model trained exclusively on CRM work will beat frontier models at CRM work, and that the interface to your CRM should follow your reps around instead of making them log in.

Here's what shipped, what it costs, and whether a purpose-built CRM model changes anything for your pipeline.

What Koa Actually Is​

Koa is a reasoning model built by post-training NVIDIA Nemotron 3 Super on a proprietary synthetic dataset modeled on 27 years of Salesforce CRM deployments — scenarios spanning 14+ industries including manufacturing, financial services, healthcare, and travel. Salesforce says no customer data was used in training; the corpus is synthetic workflows (updating opportunities, routing cases, scheduling follow-ups) generated from institutional knowledge, refined with supervised fine-tuning and GRPO reinforcement learning on NVIDIA's NeMo stack.

The headline claim: on Salesforce's internal CRM benchmark, Koa matches or exceeds leading frontier models on CRM actions with three times fewer errors.

Two details worth flagging before you repeat that number in a buying committee:

1. It's an internal benchmark. No third-party validation has been published, and no latency or throughput figures were disclosed. "3x fewer errors" is Salesforce grading Salesforce's homework — plausible (specialized models routinely beat generalists on narrow tasks), but unverified.
2. The trust boundary is the real product. Salesforce owns the model weights and runs post-training and inference entirely inside its own infrastructure. No customer data crosses to OpenAI, Anthropic, or Google during inference. For regulated industries, that single property may matter more than any benchmark.

Pilot customers already running Koa include 1-800Accountant, Baxter Credit Union, Formula 1, UChicago Medicine, and Xero. GA is expected this winter in US regions only.

Why a CRM-Specific Model Is a Big Deal (and Why It Might Not Be)​

The case for: most Agentforce failures aren't intelligence failures, they're action failures — the agent picks the wrong tool, updates the wrong field, or loops on a multistep workflow. A model post-trained on exactly those action patterns should fail less, and since errors in a CRM agent mean corrupted pipeline data, error rate is the metric that matters. It mirrors what we're seeing across the stack: Gong, Apollo, and ZoomInfo all shipped agent builders in the same two-week window, and everyone is converging on the idea that generic chat is over and domain-tuned execution is the game.

The case against: Koa only reasons over what's in Salesforce. Your CRM is a record of what already happened — meetings logged, stages updated, deals closed. The signal that creates pipeline (who visited your pricing page today, which target account just hired a new VP of Sales, who's comparing you against a competitor right now) lives outside the CRM boundary that makes Koa trustworthy in the first place. A model that's 3x more reliable at updating opportunities doesn't help if the opportunity never gets created because the intent signal died in a tool Koa can't see.

That's the structural trade of every CRM-native agent: the tighter the trust boundary, the smaller the world the agent can act on.

AIforce: Salesforce Everywhere Your Reps Already Are​

AIforce is the second half of the announcement, and for day-to-day sellers it's the more tangible one. Salesforce describes it as a live interface layer that takes the data, workflows, business logic, and permissions inside your org and pushes them out to external tools — no migration, existing permissions enforced, zero data retention promised from model providers.

It ships as three surfaces:

We covered Claudeforce in depth when the beta opened — the short version is that pipeline reviews, account research, and opportunity hygiene from a Claude chat window are genuinely useful, with real limits around write actions.

Under the hood, all three surfaces run on the same MCP-based architecture (Salesforce calls it Headless 360), which means agents in Claude, ChatGPT, and Cursor can invoke Salesforce capabilities directly. Add the new long-horizon agent runtime — agents that pursue multi-week objectives like reviving a stalled deal, expected GA in November — and the direction is unambiguous: Salesforce wants to be the system agents act through, not the tab reps click into.

This is the same play HubSpot made with Agent Hub in its Fall 2026 Spotlight, and the same logic behind OpenAI's always-on Dots agents. Every vendor has concluded the CRM UI is where rep productivity goes to die.

What It Costs​

Salesforce disclosed no Koa-specific pricing, which almost certainly means it's consumed through existing Agentforce billing. That model, as of October 2026:

• Flex Credits: $500 per 100,000 credits. A standard agent action burns 20 credits — $0.10 per action. Voice actions burn 30 credits ($0.15).
• Per-conversation: a flat $2.00 per resolved conversation, regardless of complexity. Break-even against Flex Credits is 20 actions per interaction — below that, credits are cheaper.

Run the math on a modest sales motion: 5,000 agent conversations a month at three actions each is $1,500/month at list on Flex Credits — before Sales Cloud seats, before Data 360, before the premium SKUs that AIforce surfaces will likely require once they leave beta. If you're evaluating the full stack, start with our Salesforce Sales Cloud pricing breakdown, because the agent line item sits on top of everything in it.

The pattern to watch: specialized models like Koa are cheaper to run than frontier models, but Salesforce bills you per action, not per token. Efficiency gains in inference don't automatically show up on your invoice.

Should Your Sales Team Care?​

If you're a Salesforce shop: yes, concretely. Agentforce Coworker is GA and effectively free to try if you have Lightning. Put it in front of your ops team this quarter. For Koa, ask your AE two questions when GA lands: whether Koa-powered actions are priced the same as frontier-model actions, and whether you can see per-model error rates on your org's workflows instead of the internal benchmark. If the 3x error claim holds on your data, that's real money in prevented pipeline hygiene cleanup.

If you're not on Salesforce: Koa changes nothing for you directly, but the strategic signal matters. Every major platform now has a domain-tuned agent story — Salesforce has Koa, Google has Gemini 4 Argon with its hallucination-rate pitch, Anthropic's Opus models anchor half the GTM tools shipping this quarter. The buying question has shifted from "which model is smartest" to "which system sees the signals that matter for my pipeline."

Either way: the gap in every CRM-native agent story is the same one. Koa reasons brilliantly over records that exist. It can't see the anonymous visitor on your pricing page, the target account researching your category, or the champion who just changed jobs — the signals that happen before a CRM record exists. That's the layer MarketBetter operates in: identifying in-market accounts and orchestrating outreach from intent signals, then handing clean, qualified context to whatever CRM and agent stack you run. A reasoning model that's 3x more accurate at step twelve doesn't fix a pipeline that loses deals at step one.

If you want to see what signal-to-outreach orchestration looks like in front of your own traffic, book a demo.

The Bottom Line​

Koa is the most credible "small specialized model beats big general model" bet a CRM vendor has made — real training infrastructure, a defensible trust-boundary story, named pilot customers, and a winter GA date. AIforce is the more immediately useful half for sellers, because it meets reps where they already work. Treat the 3x benchmark claim as a hypothesis to test on your own org, budget for per-action pricing that doesn't care how efficient the model is, and remember that the best CRM reasoning in the world only operates on the pipeline you've already managed to create.

If your sales team runs on Google Workspace, this is worth fifteen minutes of your attention. Not because Skills are revolutionary on their own, but because of two things: they finally work inside Gmail, Docs, and Sheets instead of a separate chat window, and Google built them on the same open SKILL.md standard that Claude, Codex, and 30+ other AI tools already use. Write a skill once, run it everywhere your reps work.

Here's what shipped, what dies, and what a sales team should actually do with it.

What Gemini Skills Actually Are​

A skill is a reusable set of instructions that you invoke inline while prompting Gemini — type / or @ in the chat box, pick your skill, and Gemini applies it. Think of it as a saved playbook for a repetitive task, except it travels with you across the Gemini app and most Workspace apps.

The mechanics that matter:

• Inline invocation. No more switching to a separate Gem window. A rep drafting a follow-up in Gmail can trigger a /follow-up skill right there.
• Stacking. Multiple skills can run in a single prompt. Combine a /icp-qualify skill with a /tone-of-voice skill and get output that respects both.
• Auto-invocation. Gemini can detect when a skill is relevant and apply it without being asked. If you have a call-prep skill and ask about an upcoming meeting, it fires automatically.
• Reference files. Skills can carry knowledge files — your pricing sheet, objection-handling doc, ICP definition — so outputs are grounded in your actual playbook instead of generic sales advice.
• Create from chat. Found a prompt that works? Gemini can turn the chat into a skill directly, no blank-page authoring required.

Skills are available on both free and paid Gemini accounts in the app. In Workspace, you need Business Starter/Standard/Plus, Enterprise Standard/Plus, Google AI Pro for Education, or the AI Expanded Access add-on.

The Part Most Coverage Missed: SKILL.md Is an Open Standard​

Here's the detail that makes this more than a feature rename. Gemini Skills use the SKILL.md format — a folder with a Markdown file and a small YAML header — that Anthropic created for Claude and released as an open standard in December 2025. Since then it's been adopted by 30+ tools: OpenAI's Codex, GitHub Copilot, Cursor, VS Code, Gemini CLI, and now the consumer-scale Gemini app and Workspace.

For a sales org, that means skill portability is real for the first time. The account-research skill your ops team writes today isn't locked into Google. The same file structure works in Claude's Docs and Slides integrations, in Codex-based internal tools, and in whatever your team adopts next year. We covered how Claude's Opus 5.5 handles sales workflows — skills written for that world and skills written for Gemini are now the same artifact.

If you've been burned by building automation inside one vendor's walled garden (RIP Gems, and Google's Opal experiment, which is also being phased out), this is the hedge.

Gems Are Being Retired: The Dates That Matter​

Google is not sunsetting Gems overnight, but the clock is running:

The migration preserves names, instructions, knowledge files, and Drive sharing permissions — but migrated skills land as drafts that the creator has to manually activate. If your team has a dozen Gems powering daily workflows and nobody activates the drafts on March 1, those workflows silently stop.

Action item for sales ops: inventory your team's Gems now, rebuild the critical ones as skills during the rollout window, and don't wait for the forced migration. Google's own admin guidance says the same thing.

Five Skills a Sales Team Should Build First​

The teams that got value out of Gems were the ones that encoded their actual process, not generic prompts. Same rule applies, but the inline invocation makes new patterns possible:

1. /call-prep — Pull the prospect's company, role, and recent context into a one-page brief before every meeting. Attach your ICP doc as a reference file so it scores fit, not just summarizes. (Our AI meeting prep guide covers the full workflow.)
2. /follow-up — Your follow-up email structure, tone rules, and CTA conventions. Triggered inside Gmail after a call, stacked with a tone skill.
3. /objection — Reference file: your objection-handling doc. A rep pastes the objection, gets your team's actual counter, not LinkedIn-generic advice.
4. /qualify — Your qualification criteria as instructions. Paste an inbound lead's details in Sheets, get a scored verdict with reasoning.
5. /mutual-plan — Generates a mutual action plan in Docs from deal notes, following your template.

If you have a documented sales process, these take an afternoon. If you don't, start with our SDR playbook template — a skill is only as good as the playbook behind it.

Where Skills Fit in the October 2026 Agent Wave​

Zoom out and Gemini Skills slot into a very crowded month. OpenAI shipped Dots, its always-on agents, at DevDay. Google itself launched Gemini 4 Argon days before Skills. Gong, Apollo, and ZoomInfo all shipped agent builders in the same week, HubSpot restructured its platform around Agent Hub, and Salesforce put its CRM inside Claude.

The pattern across all of it: vendors are racing to let you encode process so agents can execute it. Skills are Google's lowest-friction entry point — no agent builder, no credits math, no new platform. Just instructions that follow your reps around Workspace.

The honest limitation: Skills automate how you respond to work that's in front of you. They don't tell you who to work on. A /qualify skill scores the lead you paste in; it doesn't surface the account that visited your pricing page twice this week. That's the gap between a prompt library and a signal engine.

That second problem — knowing which accounts are in-market and what to do about them today — is what MarketBetter is built for. We identify the companies visiting your site, layer in intent signals, and hand your SDRs a daily playbook of who to contact and why. Pair that with Gemini Skills handling the drafting inside Gmail, and you've closed the loop: signals pick the target, skills write the touch.

Want to see what a signal-driven daily playbook looks like? Book a demo.

FAQ​

When do Gemini Skills launch? Rolling out now: Workspace apps from October 5 (Rapid Release) and October 19 (Scheduled Release), the Gemini app from October 13. Both complete by mid-November 2026.

Are Gemini Skills free? In the Gemini app, yes — free and paid accounts get them. In Workspace apps, you need a Business or Enterprise edition, Google AI Pro for Education, or the AI Expanded Access add-on.

What happens to my Gems? Gems move to Settings on November 17, 2026, then disappear for business users on March 1, 2027 (June 1 for education). They auto-convert to draft skills, but someone must activate each draft.

Can I use my Claude skills in Gemini? Structurally yes — both use the open SKILL.md format (YAML frontmatter + Markdown instructions). Expect minor edits for platform-specific behavior, but the artifact is portable.

Do Skills work in Gmail and Docs? Yes — that's the headline upgrade over Gems. Skills work inline across most Workspace apps via / or @, not just in the Gemini chat window.

The headlines: a rebuilt Breeze Assistant that executes work instead of suggesting it, a self-updating Smart CRM that logs calls, emails, and meetings without rep input, Agent Hub as the single control plane for every AI agent, and a new Revenue Hub that takes over quoting, contracts, and collections.

If you run a sales team on HubSpot — or you're evaluating whether to — here's what's actually in the release, what it costs in credits (the part HubSpot's announcement doesn't dwell on), and where the gaps still are.

The Big Idea: Growth Context​

Everything in the Fall Spotlight hangs off one concept HubSpot calls Growth Context — the combined picture of your business, your team, and your customers that lives in the Smart CRM. The pitch: agents are only as good as the context they operate on, so HubSpot rebuilt the platform to capture that context automatically and score how complete it is.

That's what the new Context Home dashboard does: it shows a completeness score for your CRM data and flags the gaps that will make agents underperform. It's an honest admission wrapped in a feature — AI agents fail on dirty CRMs, and most CRMs are dirty because reps don't log things.

Which leads to the most useful shipment in the whole release.

Self-Updating Smart CRM​

The Smart CRM now captures calls, emails, and meetings automatically and writes them to the record — no manual logging. A Mobile Notetaker transcribes meetings in real time, updates the CRM, and drafts follow-ups. The updated Deal Progression capability pulls commitments and next steps out of transcripts and keeps deal plans current on its own.

This is the feature sales managers should care about most, because it attacks the oldest problem in CRM: the system of record is only as good as the reps' discipline, and rep discipline is terrible everywhere. If HubSpot's capture actually works across your call stack, pipeline reviews stop being archaeology.

The caveat: automatic capture means HubSpot needs to sit in the path of your calls, email, and calendar. Teams running Gong or a separate dialer will need to think about which system owns the transcript — this is the same land-grab we covered when Gong, Apollo, and ZoomInfo all shipped agent platforms in the same week. Everyone wants to be the context layer now.

Agent Hub: One Pane for Every Agent​

Breeze Studio is gone; Agent Hub is the replacement. It gives admins a single view of every agent running across marketing, sales, and service — what's active, what it's doing, what it produced. The rebuilt Breeze Assistant sits on top: you give it a directional prompt ("build a re-engagement play for stalled Q4 deals") and it farms the work out to specialized agents, returning proposals and plans.

For sales specifically, the roster looks like this:

HubSpot's claim: customers using Breeze Assistant generate 2.2x more leads, and its AI sales tools cut time-to-close by nearly half. Treat those numbers the way you'd treat any vendor benchmark — they compare AI adopters against non-adopters, not a controlled test. Teams that adopt AI tooling early tend to be better-run teams to begin with.

Revenue Hub: Quote-to-Cash Moves In-Platform​

The biggest structural change is Revenue Hub (Professional and Enterprise), the evolution of Commerce Hub. It now auto-generates quotes the moment a deal hits the right stage using full deal context, handles contracts directly — create, renew, amend without building a quote first — tracks ARR impact in real time as contracts change, and runs CPQ with standardized pricing across markets and deal types.

The new Revenue Agent watches open invoices and sends personalized collection nudges, following the thread as the conversation unfolds. HubSpot cites a customer (Workleap) going quote-to-signature in under 15 minutes.

For mid-market teams duct-taping PandaDoc, a billing tool, and spreadsheet-based renewals onto their CRM, this is a real consolidation play — the same stack-collapse logic we broke down in the real cost of a B2B GTM stack.

The Credit Math HubSpot Doesn't Lead With​

Here's the part that matters before you turn any of this on: agents bill per completed task in HubSpot Credits, and the allowances are smaller than the ambitions.

Current per-task rates and monthly allowances by tier:

• Prospecting Agent: 100 credits per qualified lead
• Customer Agent: 50 credits per resolved conversation
• Data Agent: 10 credits per answer
• Content Agent: 1,000 credits per content piece
• Allowances: 500 credits/month on Starter, 3,000 on Professional, 5,000 on Enterprise

Do the arithmetic: a Professional-tier team running just the Prospecting Agent gets about 30 AI-sourced leads a month before buying credit packs. One content piece plus a handful of resolved conversations and a Starter allowance is gone in a day. Agent Hub itself doesn't require a separate license, but agents that were free during the Breeze Studio beta now consume credits — so teams that built workflows during the beta are in for a billing surprise.

This is the same pattern we flagged with OpenAI's Dots launch: the agent era is also the metered-pricing era. Per-task billing sounds fair until your agents get good, at which point your bill scales with your success. Model your expected volume before you commit — and if you're already weighing tiers, our HubSpot Sales Hub pricing breakdown covers the base license math.

What's Still Missing for Outbound Teams​

The Fall Spotlight is a strong release for teams whose pipeline already lives in HubSpot. It does much less for the top of the funnel:

Visitor identification is still not native. HubSpot shows you form fills and known contacts. It doesn't tell you which anonymous companies are on your pricing page right now — especially after HubSpot acquired Warmly and the independent-intent landscape shifted. The Prospecting Agent's "40+ buying signals" operate on records already in your CRM.

Signals without prescriptions. Even where HubSpot surfaces intent, the output is a dashboard entry or a drafted email. Someone still has to decide what the play is. The gap between "here's who looks interesting" and "here's exactly what your SDR should do in the next hour" is the gap MarketBetter is built to close: visitor ID, signal scoring, and a daily playbook that tells reps who to contact, through which channel, with what message.

The credit meter changes rep behavior. When every agent action has a visible price, teams start rationing. A platform where prospecting throughput is capped by a credit allowance is a platform where your best month is also your most expensive one.

HubSpot's release confirms the direction the whole market is moving — Salesforce made the same bet with AIforce and Salesforce-in-Claude at Dreamforce: the CRM is becoming an agent substrate, and the winners will be whoever owns the context. If you want the deeper platform evaluation, our HubSpot Sales Hub review and the best Sales Hub alternatives cover the full picture, and AI-native vs traditional CRM explains why the architecture underneath matters.

Bottom Line​

The Fall 2026 Spotlight is HubSpot's best release in years. The self-updating Smart CRM alone justifies the upgrade conversation, and Revenue Hub will genuinely collapse some stacks. But go in with the credit math done, know that the agents only work as well as the context you've accumulated, and understand that HubSpot still tells you who — not what to do next.

If you want the "what to do next" layer — anonymous visitor identification, buying signals scored into a daily rep playbook, without a per-lead credit meter — book a MarketBetter demo and see it on your own traffic.

Here's the twist: you can't use it. Not on the API, not in the Gemini app, not even with a Google AI Ultra subscription. Argon launched exclusively to vetted cybersecurity teams through Google's Fairwind Program, with everyone else waiting on an unannounced date.

So why should a sales leader care about a model they can't touch? Two numbers: Argon leads the benchmark built from real sales, marketing, and ops workflows by roughly 10 points — and it hallucinates at about a third the rate of OpenAI's frontier models. Both matter enormously for revenue teams. Here's the full picture.

What is Gemini 4 Argon?​

Argon is Google DeepMind's new frontier model, announced September 30, 2026. Google positioned it less as a chatbot and more as an execution engine for long-running agentic work: coding sessions, enterprise knowledge tasks, and cyber defense.

The headline spec is a 1-million-token output window — up from 64,000 in earlier Gemini models. Context windows (what a model can read) have been huge for a while; output windows (what a model can produce in one run) have not. A 1M output limit means an agent can plan, execute, and document an entire multi-step workflow — say, researching 200 accounts and drafting tiered outreach for each — in a single uninterrupted pass instead of dozens of stitched-together calls.

That's the same direction OpenAI took with Dots, its always-on agents from DevDay 2026, and Anthropic with Claude Opus 5.5's long-horizon agentic focus. Every frontier lab is now building for delegation, not conversation.

The benchmark that actually matters for revenue teams​

Most model launches lead with coding scores. Argon's coding numbers are good — 77.9% on DeepSWE v1.1, ahead of Claude Opus 5.5 (74.2%) and GPT-6 Astra (74.1%) — but coding benchmarks tell a sales leader almost nothing.

AutomationBench does. It evaluates end-to-end business workflows drawn from sales, marketing, and ops tasks — the closest thing the industry has to "can this model actually run my pipeline follow-up?"

A 10-point lead on a frontier benchmark is rare. And notice the absolute numbers: even the best model completes barely half of realistic business workflows end-to-end. That gap between demo and production is exactly why AI agents are already doing your prospects' research for them but still can't run an unsupervised pipeline.

The hallucination number nobody is talking about​

Artificial Analysis, the independent benchmarking firm, measured hallucination rates across the current frontier:

For coding, hallucinations are annoying — the compiler catches them. For sales, they're fatal. An agent that invents a prospect's job title, fabricates a case-study stat in an outbound email, or misquotes your own pricing doesn't just waste a lead; it burns your domain reputation and your brand.

If the 15% figure holds up in production, Argon becomes the obvious choice for customer-facing agent workflows — emails, call prep docs, proposal drafts — where a made-up fact is a fireable offense. On overall intelligence, Artificial Analysis scored Argon 53 on its Intelligence Index, tying GPT-6 Astra and edging GPT-6.1 Sol's 52, so the accuracy gain doesn't come at a capability cost.

Where Argon is weaker​

It's not a clean sweep, and the gaps are worth knowing:

• Terminal-Bench 4.0: 57.4%, well behind Claude Opus 5.5's 66.4%. If your RevOps team lives in CLI-driven automation, Claude still leads.
• FrontierSWE v2: 55.0% vs GPT-6 Astra's 65.5% on the hardest software tasks.
• DeepSWE caveat: the 77.9% is Google's own number; no independent lab has verified it yet.

Translation: Argon looks like the best business workflow model and a competitive-but-not-dominant engineering model.

Pricing: aggressive, with a deadline​

The $2/$10 intro pricing matches what OpenAI charges for GPT-6.1 Sol, which is clearly the point — Google is pricing its frontier model at its rival's workhorse rates. The 95% cached-input discount is the sleeper feature for sales use: agent workflows re-read the same CRM schemas, playbooks, and account context on every run, so cached input is most of your bill.

No end date for intro pricing has been announced. When access opens, lock in testing early.

Access: the Fairwind bottleneck​

The rollout order:

1. Now: Fairwind Program only — vetted cyber defense teams. (Fairwind launched September 2 with Gemini 3.8 Flash Cyber; Argon joined September 30.)
2. Next: Google AI Ultra subscribers and paid API customers. No date announced.
3. Later: broader developer and enterprise availability.

At launch, Argon was absent from Vertex AI, OpenRouter, Cursor, and GitHub Copilot. Google says the staged rollout is about safety testing frontier capabilities — Argon is unusually strong at vulnerability discovery, which cuts both ways.

For sales teams, the practical read: you are probably 4–8 weeks from being able to build on this. Plan, don't rearchitect.

What sales teams should do this month​

1. Don't rip anything out. Your current stack — whether that's Claude running Salesforce via Claudeforce, Codex-driven GTM automation, or vendor-native agents — doesn't get worse because Google shipped a model you can't access.

2. Make your workflows model-portable. The labs are leapfrogging each other every three weeks. Teams that define their daily SDR playbook as a clear, prioritized task list can swap the model underneath in an afternoon. Teams that hard-wired prompts into one vendor's agent builder cannot.

3. Shortlist your highest-hallucination-risk workflows. Outbound email drafting, proposal generation, competitive battlecards — anywhere a fabricated fact reaches a customer. Those are the first candidates to test on Argon when API access opens, because the 15% vs 51% accuracy gap shows up there first.

4. Budget against intro pricing. At $2/$10 with 95% cached-input discounts, a fully-loaded agent workflow that costs real money on other frontier models becomes nearly free to pilot. Model a 30-day test now so you can start the day access opens.

5. Watch AutomationBench, not DeepSWE. When Argon's competitors respond — and they will, within weeks — judge the responses on business-workflow benchmarks. Coding scores are for engineering blogs.

The bigger pattern​

September 2026 will be remembered as the month the AI-for-sales market split into two layers: the application layer (Gong, Apollo, and ZoomInfo's agent builders, Claude's Docs and Slides for sales collateral) and the model layer, where Google just took the business-workflow crown while locking the door.

The models are converging on the same thesis: long-running, low-hallucination, workflow-executing agents. The differentiator for your team isn't which model you pick — it's whether your signals, data, and playbooks are structured so any frontier model can act on them. That's the work that compounds; everything else is a config change. If you want the blueprint, start with how to go from signal to meeting in 24 hours.

MarketBetter is model-agnostic by design — we tell your SDRs who to contact and exactly what to do next, regardless of which frontier model is winning the benchmark war this month. Book a demo to see it on your own pipeline.

FAQ​

Can I use Gemini 4 Argon today? No, unless you're a vetted cybersecurity team in Google's Fairwind Program. Paid API customers and Google AI Ultra subscribers are next; no date has been announced.

What does Gemini 4 Argon cost? Introductory API pricing is $2 per million input tokens and $10 per million output tokens, rising to $4/$20 after the intro period. Cached input is discounted 95% during the intro window.

Is Gemini 4 Argon better than GPT-6 for sales workflows? On the available evidence, yes: it leads AutomationBench (end-to-end business workflows) 51.3% to GPT-6 Astra's 41.4%, and its measured hallucination rate is 15% versus 51–54% for GPT-6 models. Production results may differ — no one outside Google and Fairwind has stress-tested it.

What is the Fairwind Program? Google's gated-access program for frontier models with strong cybersecurity capabilities. It launched September 2, 2026 with Gemini 3.8 Flash Cyber and gives vetted defense teams early access with reduced safety restrictions for vulnerability research.

Three near-identical announcements in 48 hours is not a coincidence. It's the whole category pivoting at once — and it tells you exactly where the sales stack is going in 2027. Here's what each vendor actually shipped, what's real today versus waitlisted, and how to evaluate any of them without getting burned by a keynote demo.

The 48-hour timeline​

• Sep 30 — Gong announces Mission Callisto at its Celebrate '26 event: Gong Enrich, Deep Mode, and an upgraded Agent Builder with event-triggered Custom Agents.
• Sep 30 — Apollo uses its ApolloNEXT keynote to unveil Builder Studio, the Apollo Intelligence Layer (including GTM Harness agents), and Messaging OS.
• Sep 30 — ZoomInfo announces it has acquired DoubleO.ai, an agent-orchestration startup founded in 2024.
• Oct 1 — ZoomInfo launches Agent Teams inside GTM Studio, built on DoubleO's architecture — live immediately, no new SKU, no new contract.

The same week, Google launched Gemini 4 "Argon" (which tops Zapier's AutomationBench for sales and marketing workflows at 51.3%), and Anthropic revealed it had replaced its own contact-sales form with a Claude-powered agent whose escalated leads convert to opportunities more than twice as often as the old form. The models got good enough, and every vendor jumped at once.

G2 has been tracking the same shift from the category side: five new AI sales categories in two years — AI SDRs (already 400+ products), Agentic GTM Platforms, Revenue AI Platforms, AI Sales Roleplay, and AI Proposal Generators — with AI categories overall growing 152% year over year. "Agentic GTM" is no longer a positioning line; it's a shelf at the store.

What Gong shipped: Mission Callisto​

Gong's launch has three pieces that matter for revenue teams:

Gong Enrich. A built-in enrichment waterfall that searches data providers sequentially until it finds a verified match — and the interesting wrinkle is that Apollo and ZoomInfo are among the enrichment partners. Your call-recording vendor now resells your data vendors.

Agent Builder with event triggers. Gong already let teams run Custom Agents manually. The upgrade is agents that fire automatically when events and conditions you define occur — deal goes quiet, champion stops replying, competitor mentioned on a call. You define trigger, conditions, and actions in a visual editor, or just describe the agent in plain English. Reusable "skills" let you capture how your best team operates and apply it across agents.

Deep Mode + Flows from natural language. Gong Assistant gets a longer-thinking research mode, and can now build Engage Flows from a plain-English request — "build a sequence based on how our top rep follows up after demos."

Availability check: Gong Enrich, the expanded dashboards, and Deep Mode are GA now. The automatically triggered Custom Agents — the actual headline — roll out "later in 2026." If you're evaluating Gong for agentic execution this quarter, you're evaluating a roadmap. Worth knowing before you anchor a renewal on it; see our Gong pricing breakdown for how those negotiations tend to go.

What Apollo shipped: Builder Studio, Intelligence Layer, Messaging OS​

Apollo's announcement is the most ambitious of the three — effectively a re-platforming:

Apollo Intelligence Layer (available now). Two halves. Intelligence Profile keeps a continuously updated view of every contact and account, enriched from multiple sources. GTM Harness is a set of specialized agents and skills for jobs like prospecting, account research, and email deliverability.

Builder Studio (waitlist). Describe a tool in plain English — a web page, a database, an automation — and Apollo builds it. It's the "vibe-coding for RevOps" pitch: instead of buying another point tool, generate it inside Apollo.

Messaging OS (waitlist). Marketing email sends and ad-audience syncing from inside Apollo, pulling marketing and sales under one roof.

The strategy is clear: Apollo doesn't want to be your database with a sequencer bolted on, it wants to be the entire GTM system. The gap between that vision and today's product is the thing to probe in a demo — two of the three pillars are waitlisted. Our Apollo review and pricing breakdown cover what the current platform actually delivers.

What ZoomInfo shipped: Agent Teams​

ZoomInfo moved fastest from announcement to product: acquire DoubleO.ai on Tuesday, launch Agent Teams on Wednesday morning.

How it works. Agent Teams coordinates multiple specialized agents — each with its own role, instructions, and tools — that share context through a workflow. After each step, the system re-evaluates the state of the account to decide what should happen next, rather than marching through a fixed sequence. The example play ZoomInfo leads with: a champion at a closed-won account moves to a CRO role elsewhere → agents detect the move, research the new company, check ICP fit, draft outreach, and route it to the right rep.

The distribution play. Agent Teams is live in GTM Studio with no new SKU and no new contract. That's the sharpest go-to-market move of the week — Gong's triggered agents are "later in 2026" and Apollo's Builder Studio is waitlisted, while ZoomInfo customers could run an agent play the morning of the announcement.

The dependency to understand: agent quality is bounded by data quality. Agent Teams runs on ZoomInfo's own intelligence layer, so your experience will track how good ZoomInfo's data is for your segment — which varies a lot by geography and company size. Our ZoomInfo review and pricing guide go deep on where the data is strong and where it thins out.

Side-by-side: what's actually available today​

What this means if you run a sales team​

1. "Agentic" now describes a maturity spectrum, not a feature. All three vendors use nearly identical language — signals in, actions out, no babysitting. The differences live in what's GA versus demoware, what data the agents stand on, and whether actions actually execute or just generate drafts for humans to send. Make vendors demo on your accounts, not theirs.

2. The stack is consolidating around whoever owns the workflow. Gong reselling Apollo and ZoomInfo data inside Enrich is the tell: everyone wants to be the layer where decisions happen, and everyone else becomes a data feed. When you renew anything in 2027, ask which of your tools is becoming a feature of another one. Our notes on Gong alternatives, Apollo alternatives, and ZoomInfo alternatives are a useful starting map of who competes with whom now.

3. Agents are only as good as the signal layer underneath. A beautifully orchestrated agent play triggered by a stale job change or a misattributed website visit is just automated embarrassment at scale. Before you buy orchestration, audit your signal quality: visitor identification, intent data, CRM hygiene. This is the same lesson from OpenAI's Dots launch and Claudeforce a week earlier — the general-purpose agents are arriving from the model vendors too, and they'll also need clean signals to act on.

4. The Anthropic data point is the one to steal. Forget the keynotes for a second: Anthropic quietly replaced its contact-sales form with an agent, and the leads it escalates convert to opportunities more than twice as often and close about five days faster. One engineer built v1 in weeks. The lesson isn't "buy an agent platform" — it's that speed-to-lead and qualification are the highest-ROI places to deploy agents today.

Where MarketBetter sits in this​

We've been building on the same thesis these three launches just validated: dashboards that show you who are table stakes — the value is a system that tells your team what to do next and then helps do it. MarketBetter watches your signals (website visitors, champion job changes, intent) and turns them into a daily playbook of specific actions per rep, across email and LinkedIn, without a waitlist.

If you're re-evaluating your stack in light of this week, that's exactly the conversation we're built for. Book a demo and we'll show you signal-to-action running on your own ICP.

FAQ​

Is Gong Agent Builder available now? Partially. Manually triggered Custom Agents exist today; the automatically event-triggered agents announced at Celebrate '26 roll out later in 2026. Gong Enrich and Deep Mode are GA now.

Does ZoomInfo Agent Teams cost extra? No — ZoomInfo launched it inside GTM Studio with no new SKU and no new contract required.

What is Apollo's GTM Harness? A set of specialized agents and skills (prospecting, research, deliverability) inside the Apollo Intelligence Layer, which is available now. Builder Studio and Messaging OS, announced alongside it, are waitlisted.

Why did all three launch at once? Frontier models crossed the reliability threshold for multi-step work (Gemini 4 Argon, GPT-6, Claude), G2 formalized the Agentic GTM Platforms category, and nobody could afford to be the vendor without an agent story going into 2027 planning season.

If the last two years were about chatting with AI, Dots are OpenAI's bet that the next two are about delegating to it. Here's what actually shipped, what it costs, where it breaks for sales use cases, and five workflows worth testing this month.

What is a Dot?​

A Dot is a persistent agent inside ChatGPT. Unlike a normal chat session, each Dot:

• Runs on its own cloud computer and browser — it can open websites, fill forms, and use web apps without your laptop being on
• Is powered by GPT-6 Astra, the frontier model OpenAI introduced on September 3
• Connects to 4,000+ apps via OpenAI's connector ecosystem
• Works across surfaces — you can hand it tasks from ChatGPT, text message, email, or Slack
• Handles recurring work — it follows up on open tasks and can delegate pieces to sub-agents

The mental model: less "smart autocomplete," more "contractor with a laptop who never logs off."

It wasn't a flawless launch — one Dot famously had a "slow morning" and failed to respond during the live demo. Always-on doesn't mean always-reliable yet, which matters if you're thinking about putting one in a revenue-critical path.

Dots pricing: what it actually costs​

Notes that matter for budgeting:

• Your first Dot is bundled with Pro and Business Premium — there's no standalone Dot SKU yet
• OpenAI says you'll later be able to buy additional Dots and pay to increase a Dot's speed or monthly workload, but hasn't published those prices
• The Pro rollout currently excludes the EEA, Switzerland, and the UK; Business Premium is listed as available across all supported regions

So the realistic entry price for a sales team is $100–$125 per user per month — roughly what a seat of a mid-tier sales engagement platform costs.

Usage limits: the fine print​

Dots are not unlimited workers. Current published limits:

• Up to 15 active tasks per Pro user
• Aggregate event limits of 30 runs per hour and 720 per day
• An allowance for "deeper work," with extended limits during the first month

For an individual AE managing their own follow-ups, that's plenty. For an SDR team hoping one Dot will run 500 personalized outreach tasks a day — it won't. That's an important constraint before anyone pitches Dots as an AI SDR replacement. (For tools purpose-built for that job, see our best AI BDR tools comparison.)

Everything else at DevDay 2026 that matters for GTM​

GPT-6.1 Sol — a new model at $2 input / $10 output per million tokens, roughly one-fifth of Astra's price at near-Astra quality, with better coding and computer use. If you've built internal sales tooling on the API, this is your new default. OpenAI also claims up to 8x faster token generation in Codex and 6x in the API.

Agents API with computer use — the Agents API (public beta since September 10) got hosted browser access at DevDay. Developers get the Codex harness as a managed service: OpenAI handles sessions, orchestration, and context recovery; your agents can execute code, connect to MCP servers, and delegate to other agents. This is the build-your-own-Dot path for RevOps teams.

ChatGPT Space — a shared environment where teammates and Dots collaborate on files, presentations, spreadsheets, and project context. A new document type called Pages, built for human–agent collaboration, lands in Q4 2026. This is OpenAI's answer to the collaborative-workspace push we covered in Claude Docs and Slides for sales teams.

OpenAI Marketplace (beta) — eligible enterprise customers can apply part of their OpenAI spend commitment toward qualifying partner software. Worth a conversation with your OpenAI rep if you're already on an enterprise agreement.

5 Dot workflows for sales teams to test first​

Keep the limits in mind (15 active tasks, 30 runs/hour) and start with high-leverage, low-frequency work:

1. Morning pipeline brief​

Give a Dot read access to your CRM connector and Slack. Recurring task: every weekday at 7am, summarize deals that moved stages, meetings booked overnight, and contacts who went dark for 7+ days. Deliver to Slack. This is the same pattern we use in our daily SDR workflow with Claude — Dots just make the scheduling native.

2. Pre-meeting research packets​

Dot watches your calendar. Two hours before any external meeting, it browses the prospect's site, recent funding news, and LinkedIn activity, then drops a one-page brief in your inbox. Its own browser means it can do this without your machine on — a real edge over local-only setups like the ones in our Codex prompts for SDR productivity guide.

3. Follow-up enforcement​

Hand the Dot your sent folder. Task: if a prospect hasn't replied in 4 business days and there's no scheduled next step, draft a follow-up in your voice and queue it for approval. Keep a human on send — Dots are too new to give them your sender reputation.

4. Conference and event list building​

Point a Dot at an event's public exhibitor directory and ask for a structured list of companies, booth numbers, and likely ICP fits. Its hosted browser handles the clicking. (If you need this at scale, a dedicated tool is still faster — our free conference scraper does it in minutes.)

5. Competitive watch​

Weekly recurring task: check competitors' pricing pages, changelogs, and release notes; report only what changed. We've caught multiple silent price increases this year doing exactly this — vendors change pricing far more often than they announce it.

The catch: generalist agents still don't know your buyers​

Here's the pattern we keep seeing — first with Claude Opus 5.5, then Salesforce inside Claude, now Dots: general-purpose agents are getting genuinely good at executing tasks you define. What they can't do is tell you which accounts are in-market right now and what to do about them.

A Dot will happily research any account you name. It has no idea that a VP of Sales from your ICP visited your pricing page twice yesterday, or that your champion at a target account just changed jobs. Signal detection — visitor identification, intent data, champion tracking — still has to come from somewhere, and that's the layer MarketBetter owns: it tells your team WHO is in-market and WHAT to do next, then a generalist agent (Dot, Claude, or your own OpenClaw agent) can execute the plays.

One more wrinkle: Dots browsing the web means even more of your buyers' research is now done by agents, not humans. Our own Search Console data shows AI agents are already searching Google with long persona-style prompts — Dots will accelerate that, and your content needs to be legible to them.

Should your sales team buy Pro for Dots?​

Try it if: you're already paying for Pro or Business Premium, your reps lose hours to research and follow-up admin, and someone on the team will own prompt quality for the first month. The bundled first Dot makes the experiment effectively free.

Wait if: you're in the EEA/UK on Pro (not available yet), you need high-volume execution (the run limits will stop you), or you can't tolerate flaky behavior in revenue-critical paths — the demo stumble was a useful reminder that "always-on" is aspirational.

Either way: the direction is clear. Between Dots, the Agents API, and ChatGPT Space, OpenAI is turning ChatGPT into an operating system for delegated work — the same trajectory we're watching in the Claude vs ChatGPT for sales teams race.

Want the signal layer that tells your agents which accounts to work? MarketBetter identifies your anonymous website visitors, tracks champion job changes, and turns signals into specific next actions for your SDRs. Book a demo →

On September 15, 2026, the Salesforce in Claude plugin hit open beta on all paid Claude plans. It's the first shipping product from Claudeforce — the expanded Salesforce–Anthropic partnership announced on August 26 — and it puts 37 prebuilt sales skills inside Claude: meeting prep, account research, deal scoring, pipeline reviews, forecast narratives, and CRM updates that write back to Salesforce after you approve them.

Most coverage treated this as partnership theater between two giants. The practical story is simpler: the hours your AEs spend assembling context before calls and typing updates after them just became a chat message. If your team runs on Salesforce and anyone on it already uses Claude, this beta is worth a structured two-week pilot — not a shrug.

Here's what actually shipped, how to roll it out without scaring your admin, and the one thing Claudeforce fundamentally cannot do for your pipeline.

What Shipped, Exactly​

The facts, stripped of press-release gloss:

• Announced August 26, 2026 as "Claudeforce," with select pilot customers first. Open beta arrived September 15 on all paid Claude plans — no Enterprise-only gate.
• 37 prebuilt sales skills built jointly by Salesforce and Anthropic, covering the daily work of account executives: briefings, account research, call prep, deal-health scoring, post-call opportunity updates, pipeline dashboards with risk flags, and forecast drafts.
• Built on AIforce, Salesforce's enterprise harness that exposes CRM data and workflows through MCP servers and APIs. Translation: no custom integration project. Your admin authenticates once centrally, assigns access to groups, and every action routes through Salesforce's existing permission model.
• Approval-first writes. By default, Claude proposes a change (say, updating an opportunity from your call notes) and the seller approves it before anything is written to the CRM.
• Optional Slack integration pulls deal-channel summaries and account-team threads into the same context.
• More skills land in late 2026, with service, marketing, and commerce skills slated for the following quarter.

Two details matter more than the rest. First, permission inheritance: users can't see records through Claude that they can't see in Salesforce. That kills the most common security objection before it starts. Second, there's no self-service for individual reps — distribution runs through AgentExchange and your Salesforce admin. If you're a rep reading this, your first move is a Slack message to whoever owns your org.

The 37 Skills, Organized by When You'd Use Them​

Salesforce hasn't published the full list, but the skills cluster cleanly around the rhythm of a selling week:

If you've been building this manually with prompts and exports, the table above probably looks familiar — it's roughly the workflow we documented in our complete guide to Claude for SDRs and the AI meeting prep guide. The difference is that the copy-paste tax is gone. Claude reads the live opportunity, the email thread, and the Slack channel itself.

The deal-scoring skill deserves special attention. Scoring "against our process" means MEDDIC, MEDDPICC, or whatever methodology your org runs — applied consistently, on every deal, without a manager spending Sunday night doing it. Forecast narratives similarly compress what is, for most sales leaders, a half-day of spreadsheet archaeology. (If you want to see how far AI forecasting can go beyond narratives, we broke that down in AI sales forecasting with Claude Code.)

How to Roll It Out Without a Committee​

The beta's admin-gated distribution is actually a feature for sales leaders: you can pilot with one pod instead of boiling the ocean.

Setup is five steps:

1. Request access through AgentExchange (Salesforce's marketplace — not the Claude app).
2. Your admin creates one organizational connection. No per-user OAuth dance.
3. Assign access to a pilot group — one team, not the whole org.
4. Optionally connect Slack for deal-channel context.
5. Reps sign in with their own Salesforce credentials, inheriting their existing permissions.

Then run a one-week ramp:

• Days 1–3: read-only. Briefings, account research, call prep. Zero risk, immediate time savings, and it builds trust in the output.
• Day 3: test deal scoring on a handful of live opportunities. Compare against your manager's read.
• Days 4–5: enable approved writes for one rep. Post-call updates are the highest-value, lowest-risk write path because the rep reviews every field change.
• Day 5+: add Slack. Context quality jumps when Claude can see the account team's actual conversation.

Measure one thing: minutes per rep per day spent on prep and CRM updates, before versus after. Sellers routinely lose 60–90 minutes daily to this. If the pilot claws back even half of that across a 10-rep team, that's roughly a full head of selling capacity you didn't have to hire.

One caution: billing is still separate. Your Salesforce contract and your Claude contract don't know about each other yet, and combined pricing hasn't been announced. Budget both lines.

What This Means for the AI-CRM Race​

Benioff's line for the launch — "UI is the AI" — is the tell. Salesforce spent two decades getting people into its interface, and it's now conceding that sellers would rather work where the reasoning happens. That's the same pattern we've tracked all year: Claude Docs and Slides moved deliverables into the conversation; Claudeforce moves the CRM into it too.

For buyers, the practical takeaway is that the "which AI does my stack support" question is collapsing. Salesforce built AIforce to serve any agent through MCP — Claude is simply first. If you're mid-evaluation between assistants, our Claude vs ChatGPT for sales teams comparison covers the reasoning-quality gap that likely drove Salesforce to lead with Anthropic, and the Opus 5.5 breakdown covers the current model ceiling.

It also raises the bar for every point tool charging for "AI meeting prep" or "AI pipeline summaries" as a standalone product. When the CRM vendor and the model vendor ship that natively for the cost of a Claude seat, the standalone version of those features is on a clock.

The One Thing Claudeforce Can't Do​

Read the skill list again. Briefings, prep, scoring, updates, dashboards, forecasts. Every single one operates on deals that already exist in your CRM.

Claudeforce makes your team dramatically faster at working pipeline. It does nothing to create pipeline. It can't tell you that a VP of Sales at a target account visited your pricing page twice yesterday, that a champion just changed jobs, or that an account that ghosted you in Q2 is suddenly researching your category. Salesforce only knows what someone put into Salesforce — and the buyers you most need to reach aren't in there yet.

That's the layer MarketBetter owns: identifying in-market accounts and the anonymous visitors already on your site, then telling your reps who to contact and exactly what to do next — not just summarizing what's already logged. Claude can then research those leads and draft the outreach, but the signal has to come from somewhere. (And no, Claude can't pull this from LinkedIn on its own either.)

The teams winning in 2026 run both layers: signal intelligence to fill the top of the funnel — because outbound isn't dead, it's just evolved — and AI-native execution like Claudeforce to work it without administrative drag.

Want the pipeline-creation layer to pair with your Claudeforce pilot? Book a MarketBetter demo →

FAQ​

What is Claudeforce? Claudeforce is the expanded Salesforce–Anthropic partnership announced August 26, 2026. Its first product, the Salesforce in Claude plugin, entered open beta September 15, 2026 with 37 prebuilt sales skills.

What Claude plans support Salesforce in Claude? All paid Claude plans. There's no free-tier access, and individual reps can't self-serve — a Salesforce admin must enable the plugin through AgentExchange.

Can Claude change my Salesforce data? Only with approval. By default, Claude proposes each write (like an opportunity update) and the seller confirms before it lands in the CRM. Users also inherit their existing Salesforce permissions — Claude can't touch records they couldn't already access.

Does Anthropic train on our CRM data? Anthropic states it does not train on Team and Enterprise data by default.

How much does it cost? There's no combined pricing yet. You pay for Salesforce and Claude separately under existing contracts.

Does this replace an SDR tool or signal platform? No. All 37 skills operate on existing CRM records. Identifying new in-market accounts, website visitors, and buying signals — the pipeline-creation layer — still requires a platform like MarketBetter.

In mid-September 2026, Anthropic quietly killed Claude Cowork as a separate mode, folded it into the main Claude app, and shipped two new surfaces in beta: Claude Docs and Claude Slides. Most of the coverage framed this as an office-suite play against Google and Microsoft.

That's the wrong frame for anyone who carries a quota. The right frame: the most expensive non-selling activity in sales — building documents and decks — just moved inside the AI conversation. Claude's output is no longer text you paste somewhere. The deliverable itself is the output.

We've been running Claude in production GTM workflows since early 2025 (start with the complete guide to Claude for SDRs if you're new). Here's what actually shipped, why it matters more for sales teams than for the "AI office suite" crowd, and five workflows worth stealing this week.

What shipped, in 30 seconds​

• One Claude. You no longer pick "Chat" or "Cowork" up front. Claude decides whether your request needs a quick answer or longer-running agentic work. Existing Cowork chats, projects, artifacts, connectors, and skills carry over.
• Claude Docs (beta, paid plans). Create and edit documents inside a conversation. Real-time co-editing via shareable links, on desktop and mobile. Exports to Microsoft Word or Google Docs.
• Claude Slides (beta, paid plans). Editable presentations you can present directly from Claude, or export as PowerPoint or PDF.
• Rollout: Pro and Max first, staged over the coming weeks across web, desktop, and mobile. Team and Free plans follow. Enterprise orgs get at least 30 days' notice before changes.
• Claude Code stays separate — it remains the terminal/IDE product for engineering work.
• Agentic actions still ask permission by default, with autonomous modes that check in when review is needed.

If you're weighing Claude against the alternative for this kind of work, our Claude vs ChatGPT for sales teams breakdown covers the underlying model differences; this post is about the new surfaces.

The deck tax, quantified​

Every AE knows the routine: discovery call ends, and now you owe the prospect a recap doc, a tailored deck for the champion to forward internally, and maybe a mutual action plan. None of that is selling. All of it eats selling hours.

The pre-Docs workflow with AI already helped, but it had a copy-paste seam running through it:

The seam mattered more than it looked. Reformatting is where the time went, and it's why most reps still hand-built decks even with a Claude Pro subscription. That seam is now gone — with caveats we'll get to.

Five workflows to steal​

1. Discovery call → recap doc before the prospect's next meeting​

Pipe your call notes (or transcript) into Claude and ask for a one-page recap doc: their words for the problem, quantified impact, proposed next steps. Export to Google Docs or share the link directly. Speed is the differentiator here — a recap that lands 30 minutes after the call reads very differently than one that lands Thursday. The prep side of this is covered in our AI sales meeting prep guide.

2. The forwardable deck​

Your champion doesn't buy — they sell internally on your behalf. Build them a 5-7 slide deck in their company's language: their initiative names, their metrics, their org's priorities. Prompt pattern that works:

"Build a 6-slide deck a Director of Sales Ops would forward to their CRO. Their initiative is called [X]. Frame our solution as accelerating [X], not replacing anything. One idea per slide, no jargon."

Then export PPTX and let the champion re-skin it in corporate template if they need to.

3. QBR decks from account data​

QBR season used to mean AEs disappearing for a week of deck-building. Feed Claude the account's usage data, support history, and goals from the last QBR, and have it produce the first full draft — trend narrative, wins, risks, expansion asks. With long-context workflows you can hand it a quarter's worth of raw material in one shot.

4. Mutual action plans as living documents​

MAPs die in attachments. As a shared Claude Doc with a link, the plan becomes the single artifact both sides edit — dates, owners, dependencies. When the buyer updates a milestone, you see it. When they stop touching it, that's signal too.

5. Persona one-pagers at scale​

SDR teams need leave-behinds per persona, per industry. This was never hard to write — it was hard to format twenty times. Now it's a loop: one master prompt, one doc per persona, consistent structure. Pair it with automated lead research so each one-pager cites the pains that segment actually reports.

The caveats (beta means beta)​

• Paid plans only, staged rollout. If you don't see Docs/Slides yet, that's the staging, not you. Team plan admins are waiting on the follow-on rollout.
• Brand control is the open question. Exported decks will need your template applied for anything customer-facing at enterprise. Treat Slides as the content pass; brand polish still happens in PowerPoint for now.
• Data hygiene still applies. A shareable co-editing link is convenient right up until someone pastes another customer's numbers into a QBR deck. Same rules as any AI tool: no cross-customer data in one artifact, and check your org's retention settings before sharing links externally.
• This doesn't replace judgment. Claude will happily produce a confident deck built on a wrong read of the account. Garbage in, beautifully formatted garbage out.

Where this fits in your stack (and what it doesn't solve)​

Docs and Slides compress the asset step of selling. They do nothing for the step before it: knowing who to build the asset for and why now.

A perfect forwardable deck aimed at an account that isn't in-market is still zero revenue. The order of operations that works: signal first (who's on your site, who changed jobs, who's researching the category), play second (what action that signal demands), asset third (the doc or deck that executes the play). That first two-thirds is what MarketBetter does — it tells your SDRs who to target and exactly what to do, so tools like Claude Docs execute plays instead of producing beautifully formatted guesses. If you're building that muscle, start with our SDR playbook template guide.

And if your team is further along the automation curve, the same "asset as output" logic extends to LinkedIn workflows and even forecasting — the pattern across 2026 is consistent: AI stops giving you text about the work and starts giving you the work.

Bottom line​

• If your reps have Claude Pro/Max: turn on Docs/Slides the moment it appears, and standardize the five workflows above. The recap-doc and forwardable-deck plays alone are worth hours per rep per week.
• If you're on Team: it's coming; draft your prompt library now.
• If you're evaluating AI for GTM broadly: this release is another data point that the chat-window era is ending. Assets, actions, and agents are the output now — a shift we've tracked since Claude first connected to real sales tools.

The deck tax funded a lot of late nights. Few will mourn it.

Want the "who and why now" half of the equation solved too? MarketBetter identifies your website visitors, tracks buying signals, and hands your SDRs a daily playbook of exactly what to do. Book a demo →

It's the oldest idea in advertising (trade magazines did this for a century) reborn as the default answer to a cookieless web. In 2026 it's also quietly one of the cheapest ways to put a B2B message in a relevant environment.

Here's how it works, what the current numbers say, and the one structural limit that decides where it belongs in your program.

How Contextual Targeting Works​

Modern contextual engines do four things in the milliseconds before an ad auction:

1. Crawl and classify the page. NLP models read the article — topic, entities, sentiment, even buying-stage cues ("comparison," "pricing," "implementation").
2. Match against your targeting profile. You buy categories ("enterprise software," "supply chain management"), keywords, or custom segments built from example URLs.
3. Apply brand-safety filters. Negative categories and sentiment thresholds keep you off pages you don't want to fund.
4. Bid. If page context matches your profile, your bid enters the auction like any other programmatic impression.

The critical distinction from behavioral targeting: nothing about the person is known or needed. Which is exactly why it survived cookie deprecation untouched.

Why It's Having a Moment in B2B​

Three 2026 realities pushed contextual from fallback to first-class:

• Reach. In cookieless environments, behavioral targeting loses 30–60% of addressable inventory. Contextual keeps 100% — it never needed the cookie.
• Cost. Advertisers report CPCs up to 48% lower and CPMs 20–30% lower than behavioral equivalents, and cookieless CPMs overall run ~22% below cookie-based ones.
• Performance parity. Recent studies put contextual within 5–8% of cookie-based behavioral targeting on CTR and conversion quality — a gap most B2B budgets happily trade for the cost savings.

And B2B is structurally a good fit: long, content-driven research cycles mean your buyers spend months reading exactly the pages a contextual engine can classify. Targeting the content of the research is a decent proxy for targeting the researcher.

Contextual vs. Behavioral vs. Account-Based​

The three aren't rivals — mature programs layer them. Contextual finds relevant environments, account-based ad platforms (see our ABM tools roundup) find target companies, and first-party signals find in-market people.

Where Contextual Fits in an ABM Program​

Platforms like Propensity made contextual a standard channel in omnichannel ABM campaigns — and used well, it plays three roles:

1. Top-of-funnel air cover on a budget. Run category contextual against your solution space so that when your SDR calls, the brand isn't cold. At $3–10 CPMs this is the cheapest awareness you can buy. (For what the full program costs, see our omnichannel ABM cost breakdown.)

2. Intent amplification. When accounts on your in-market list surge on a topic, shift contextual budget onto that topic's content categories. You're betting the surging accounts are reading that content — often a good bet.

3. Competitive adjacency. Custom segments built from competitor-review and comparison URLs put your ad next to the exact moment of evaluation.

The Structural Limit Nobody Puts on the Slide​

Contextual targeting can never tell you who saw the ad or which account is now in-market. It's anonymous by design — that's the privacy feature. Which means:

• No account-level reporting beyond click-throughs
• No signal you can route to an SDR
• No way to know if the CFO who read the forecasting article works at a target account or a student newspaper

That's fine for awareness. It's fatal if awareness is your whole program, because nothing downstream converts impressions into conversations. The teams getting real pipeline from contextual pair it with a capture layer: person-level visitor identification on their own site, so that when the air cover works and the buyer shows up, someone actually knows — and routes the signal to a rep while it's warm.

Ads rent attention. Signals book meetings. Budget accordingly.

FAQ​

Is contextual targeting GDPR-compliant? Yes — it processes no personal data, which is why European budgets adopted it fastest. Standard consent rules still apply to any measurement pixels you add.

What does B2B contextual inventory cost in 2026? Display CPMs typically run $3–15 depending on category competitiveness; premium B2B publications and custom segments price higher. Still consistently 20–30% below comparable behavioral buys.

Can contextual targeting reach specific accounts? No. It targets content, not companies. If you need named-account delivery, that's account-based advertising — compare approaches in our MarketBetter vs Propensity breakdown.

Does contextual work for niche B2B categories? It's actually strongest there. Niche categories have well-defined content universes (trade pubs, analyst blogs, subreddits with display inventory), so classification is precise and waste is low.

Air cover only pays off when you can see who showed up. MarketBetter identifies the visitors your ads send and turns their signals into booked meetings. Book a demo →

In consumer marketing it's a coupon cannon. In B2B it's something more interesting: one of the few ways to build an audience out of verified physical behavior — this device attended that industry event; this device works in that building.

Here's how B2B teams actually use it in 2026, what it costs, and the step most programs skip that decides whether it produces pipeline or just impressions.

How It Works​

1. Draw the fence. GPS/Wi-Fi/Bluetooth-based polygons around target locations — typically 100–300 meters for an office building (tight enough to avoid the coffee shop next door), or the exact footprint of a convention hall.
2. Capture device IDs. Devices that dwell inside the fence during your window get added to an audience segment.
3. Serve and retarget. Ads run on apps and mobile web while devices are in the fence — and, more valuably, for up to ~30 days afterward across their other devices via cross-device graphs.
4. Layer filters. Daypart to business hours (Mon–Fri, 8am–6pm) to bias toward employees over visitors; some platforms layer firmographic data on top.

Accuracy realities: outdoor precision is roughly 5–50 meters depending on device and environment. Good enough for a convention center; do not expect it to separate floor 12 from floor 14 of a shared tower.

The Four B2B Plays​

1. Trade show and conference capture. Fence the venue (and the headline hotels) during show week. Everyone captured is a verified industry attendee — a prequalified audience you retarget for the month after, precisely when follow-up matters. This pairs with the pre-event motion in our conference prospecting playbook: outreach books the meetings, geofenced air cover keeps the brand warm between touches.

2. Competitor's event or booth. Fence a competitor's user conference and spend the next 30 days putting your comparison content in front of their most engaged customers. Aggressive, legal, and common.

3. Competitor and partner offices. Fence competitor HQs to reach their employees (recruiting, or seeding doubt before a renewal cycle) or fence your target accounts' offices as an account-based display channel that doesn't depend on IP resolution.

4. Your own funnel's physical layer. Fence your own event, your roadshow stops, even the steakhouse where you ran the exec dinner — then retarget attendees with the follow-up asset instead of hoping they open the recap email.

What It Costs in 2026​

A single-event fence with 30-day retargeting is typically a $2K–$10K line item — cheap enough to test, which is why it shows up as a standard channel in omnichannel ABM platforms like Propensity. (Full program math in our omnichannel ABM cost breakdown.)

The Honest Limits​

• Device ≠ decision-maker. Your convention-center fence captures the AV crew, the baristas, and 400 vendors along with the buyers.
• No account resolution. You know a device was at SaaStr; you don't know it belongs to the VP of Sales at a target account — most platforms can't close that gap reliably.
• It's still just impressions. Nobody ever geofenced their way directly to a booked meeting. It warms; it doesn't convert.
• Privacy drift. Location data sits in regulators' crosshairs; platform capabilities have narrowed each year and will keep narrowing.

The Step That Turns Location Into Pipeline​

Geofencing's output is an anonymous warm audience. Pipeline starts when a member of that audience does something identifiable — and for B2B, that moment is almost always a visit to your website.

That's the handoff most programs fumble. The event attendee you spent $8 CPM warming clicks through Tuesday morning, browses your pricing page, and leaves — anonymous — unless you have person-level visitor identification running. With it, the sequence completes: fence captures the audience → ads warm it → visitor ID names the ones who show up → the signal routes to an SDR the same day, while the conference is still fresh in memory.

Same principle as every ad channel: air cover doesn't book meetings — the capture layer does.

FAQ​

Is B2B geofencing legal? Yes, using platform-provided opt-in location data. Rules tighten yearly (and several US states now restrict sensitive-location fencing), so keep fences on commercial venues and follow your platform's compliance guidance.

How precise is a geofence? Roughly 5–50 meters outdoors. Building-level targeting works; suite-level doesn't.

How long can you retarget captured devices? Most platforms support ~30-day lookback windows after fence exit — the useful window anyway, since event intent decays fast.

Is geofencing worth it without an event? Rarely as a standalone. Fencing static office buildings produces thin, noisy audiences. It earns its budget around moments — shows, launches, renewal windows — when physical presence actually signals something.

Warming an audience is the easy half. MarketBetter identifies the visitors your campaigns send and hands your SDRs the signal while it's hot. Book a demo →

An in-market account list is the discipline of separating those two groups. Done right, it's the highest-leverage asset in your GTM stack: the same SDRs, the same sequences, the same budget, pointed at accounts that are actually shopping. Done wrong, it's a spreadsheet of companies that "surged" on a topic once and never thought about you again.

Here's the full build process.

What Counts as "In-Market"​

An account is in-market when there's evidence of active evaluation — not just fit. Three signal layers supply that evidence:

The mistake most teams make is building the list from the third layer alone, because that's what their intent vendor sells. Third-party surge tells you an account might be researching the category. First-party behavior tells you a specific person is evaluating you. Weight accordingly.

Step 1: Lock the ICP Filter First​

Intent without fit is noise. Before any signal enters the list, define the firmographic and technographic gate: industry, employee band, geography, tech stack, disqualifiers. An account that surges hard but can't buy (wrong size, wrong region, incompatible stack) should never reach a rep.

This is a filter, not a score. Binary. In or out. The scoring comes later — see our companion guide on how to score an in-market account list.

Step 2: Instrument First-Party Capture​

Your website is the single richest in-market signal source you own, and most teams are blind to it — 97%+ of B2B visitors never fill a form.

• Deploy person-level visitor identification so anonymous traffic resolves to named people at named accounts
• Flag high-intent paths: pricing, integrations, security/compliance pages, comparison pages
• Track return frequency — a second visit within 7 days is worth more than any topic surge

The full setup is covered in our B2B website visitor identification guide.

Step 3: Layer Third-Party Intent — as a Multiplier, Not a Source​

Add topic-surge data on top of the ICP-filtered universe to catch accounts researching the category before they hit your site. Rules that keep it honest:

• Recency: signals older than 14 days are history, not intent. Buying intent decays with a half-life measured in days.
• Repetition: one week of surge is noise; three consecutive weeks is a pattern.
• Relevance: surge on your category and competitor terms, not adjacent topics.

If you're choosing a vendor, our intent data provider roundup covers the trade-offs.

Step 4: Add Trigger Events​

Some accounts enter market because something happened: new VP of Sales, funding round, layoffs at an incumbent vendor, a compliance deadline, a champion changing jobs into a new account. Triggers are the earliest in-market signal that exists — often preceding any research behavior. Pipe them in from job-change alerts, funding feeds, and hiring data.

Step 5: Set Entry, Exit, and Ownership Rules​

A list without lifecycle rules bloats into uselessness within a quarter.

• Entry: ICP pass + at least one strong signal (first-party visit, repeated surge, or trigger event)
• Exit: no new signal in 21-30 days → account rotates out (it can re-enter)
• Ownership: every account that enters gets routed to a named rep within 24 hours — signal-based routing rules prevent the "great list nobody works" failure mode
• Cap: keep the active list at a size your team can actually touch (typically 5-10 accounts per rep per week entering)

The Mistakes That Poison Lists​

1. Static lists. In-market is a state, not a trait. A list built in January is fiction by March. Rebuild continuously or automate entry/exit.
2. Account-level worship. "Acme is surging" is not workable. Who at Acme? Resolve to people or the SDR is cold-calling into a warm account — which is just cold calling.
3. No speed contract. In-market accounts are in-market for everyone, including your competitors. If your motion can't get from signal to meeting inside 24-48 hours, the list's value evaporates before it's worked.
4. Treating intent as a magic bullet. Intent data multiplies a strong ICP and a working outbound motion. It cannot rescue a weak one.

How MarketBetter Automates This​

Everything above can be run manually with spreadsheets and three vendor contracts. MarketBetter runs it as one system: person-level visitor ID (step 2), blended first- and third-party intent (step 3), trigger signals (step 4), and routing rules with SLA timers (step 5) — feeding outreach that's drafted by AI and reviewed by a human before it sends. The list stays live, the exits happen automatically, and every entry ends in an attempted conversation, not a dashboard.

Book a demo to see your own in-market list built from your real traffic.

FAQ​

How big should an in-market account list be? As big as your team can work within the signal window — usually 5-10 new accounts per rep per week. A 5,000-account "in-market list" is a mailing list wearing a costume.

Is intent data enough to build the list? No. Third-party intent alone produces category researchers, not evaluators of you. Blend it with first-party behavior and trigger events, and gate everything through ICP fit.

How often should the list refresh? Continuously. If your tooling forces batch updates, weekly is the minimum viable cadence — intent signals lose most of their value within two weeks.

Most scoring models fail not because the math is wrong but because nobody trusts them — the weights were guessed in a workshop, the score never matches what reps see, and within a quarter everyone's back to gut feel. Here's a model built the other way: start from your closed-won data, keep the dimensions legible, and wire the score to routing so it changes behavior instead of decorating a dashboard.

The Three Dimensions​

Every workable account score combines three things:

Keep them separate. A blended single number hides the difference between "perfect fit, zero activity" (nurture) and "mediocre fit, on your pricing page daily" (call now) — and those demand opposite plays.

Step 1: Calibrate Weights on Closed-Won, Not Opinion​

Pull your last 12 months of closed-won and closed-lost accounts. For each, reconstruct what was observable before the first meeting: firmographics, signals, site behavior. Then ask which attributes actually separated winners from losers.

Every team that does this honestly finds surprises. Common ones:

• First-party engagement outpredicts third-party surge by a wide margin — a pricing-page visit is worth more than a month of topic surge (our buying-signal hierarchy analysis ranks the common signals by closed-won correlation)
• One or two firmographic traits you thought mattered don't
• Negative signals (wrong stack, recent competitor contract, hiring freeze) predict losses better than positive signals predict wins

Recalibrate quarterly. Around three-quarters of B2B teams will run some form of AI-assisted scoring by end of 2026 — but AI calibration on top of unexamined assumptions just automates the guessing.

Step 2: Score Each Dimension 0-100​

A simple, legible structure beats a clever one:

Fit (gate + score). Hard disqualifiers first — wrong size, wrong region, incompatible stack → score 0, exit. Survivors get scored on weighted firmographic/technographic match.

Intent (recency-weighted). Score signals, then decay them: a signal this week at full value, halved next week, gone by week four. Intent has a half-life; a score that ignores decay ranks last month's shoppers above this week's.

Engagement (behavior-tiered). Not all touches are equal. A blog visit is a point; a pricing page is ten; a second pricing visit within a week is twenty; an identified decision-maker doing it is fifty. Person-level resolution matters here — knowing who is on the page is the difference between account warmth and an actual buyer.

Step 3: Convert Scores to Tiers​

Reps don't act on a 73. They act on tiers:

Set thresholds so Tier A matches your team's actual capacity. A tier system that flags 400 "act now" accounts for six reps is a random number generator with extra steps.

Step 4: Wire the Score to Routing​

This is where scoring lives or dies. A score that only sorts a dashboard changes nothing. The score should do things:

• Tier A entry → account routed to a named rep with the triggering signal attached, SLA timer running (routing rules here)
• Tier transitions → notifications, not reports ("Acme moved B→A: 3rd pricing visit this week")
• SLA breach → escalation or re-route

The signal-to-meeting playbook covers the outreach side of the handoff.

The Failure Modes​

1. Opinion-weighted models. If the weights came from a meeting instead of closed-won data, the model encodes the loudest person's intuition.
2. No decay. Scores that only go up produce a leaderboard of accounts that were hot in Q1.
3. Score without routing. If a tier change doesn't move work to a person with a deadline, the model is decorative.
4. Precision theater. Seventeen weighted sub-factors nobody can explain lose to four factors every rep understands. Trust drives adoption; adoption drives revenue.

How MarketBetter Handles Scoring​

MarketBetter scores accounts and people continuously — fit gate, blended intent with built-in decay, person-level engagement — and routes tier changes straight into SDR queues with the evidence attached and outreach drafted for human review. Calibration runs against your actual pipeline outcomes, not a static rubric.

Book a demo to see your accounts scored on live signals.

FAQ​

Account scoring vs lead scoring — what's the difference? Lead scoring ranks individual form-fills; account scoring ranks companies using signals from everyone in the buying committee, including people who never converted. In committee-driven B2B sales, account scoring is the one that matches how deals actually happen.

How many factors should the model use? As few as survive the closed-won analysis — usually 4-7. Every factor you add that reps can't verify against reality costs trust.

How often should scores update? Continuously, or daily at minimum. Weekly batch scoring means your fastest-moving buyers spend their hottest days invisible.

And yet they are almost opposite products.

Propensity is an advertising engine: it builds audiences of in-market accounts and serves them ads across 20+ channels — display, native, CTV, audio, social, direct mail. MarketBetter is a meeting engine: it identifies the people already showing buying signals and routes them into SDR outreach that ends in a booked call.

One warms accounts. The other works them. Here's how to decide which layer to fund — or how to sequence both.

The Short Version​

For the full teardown of Propensity's tiers and hidden contact-data costs, see our Propensity pricing review.

What Propensity Actually Does Well​

Credit where due. Propensity's G2 reviews are strong (4.8/5), and the product delivers on its promise for a specific job:

• Ad activation without a DSP. Most SMB marketing teams can't run programmatic display, CTV, or audio campaigns themselves. Propensity packages that into a flat monthly fee with campaigns live in under 15 days.
• Audience building from intent. It combines Bombora topic surge with website visitor data to build lists of accounts that look in-market, then syncs those audiences to ad channels automatically.
• Channel breadth. Direct mail, geofencing, contextual — channels most B2B teams never touch — are in the box (LinkedIn is gated to the $3,000 tier, Google/YouTube to $4,000).

If your goal is awareness inside a defined account list — making sure the buying committee has seen your name before your rep calls — Propensity does that at a price 6sense can't match.

Where the Model Breaks​

The limits show up when you trace an ad impression to revenue.

1. Impressions don't book meetings. Propensity's output is engagement: lifted account activity, more site visits, better ad recall. Someone still has to convert that warmth into conversations. If you don't have an outbound motion ready to catch the accounts that heat up, you're paying to warm accounts that cool back down. Signal decay is brutal — buying intent has a half-life measured in days, not quarters.

2. Account-level warmth, person-level gap. Knowing an account is surging on "sales automation" doesn't tell your SDR who to contact. Contact data below the $4,000 tier is metered and accrues per campaign — reviewers on G2 flag exactly this. The moment you operationalize, costs stack.

3. Marketing owns it, sales waits. Propensity is a marketing tool. The pipeline conversation still depends on how well marketing hands accounts to sales — the handoff where most ABM programs quietly die.

What MarketBetter Does Instead​

MarketBetter starts from the opposite end: the people already acting.

• Person-level visitor identification. Not "someone at Acme visited" — which person, matched to title, LinkedIn profile, and contact data. See how that works in our visitor identification guide.
• Blended intent ranking. First-party signals (pricing-page visits, return sessions) blended with third-party intent, ranked by the signal hierarchy that actually predicts closed-won.
• Outreach built in. Signals route to SDRs with AI-drafted, human-reviewed email and LinkedIn sequences. The output isn't a warmed account — it's a meeting on the calendar.
• CRM-native. Syncs into HubSpot, Salesforce, or Pipedrive rather than asking you to run pipeline out of a separate ad console.

The philosophical difference: Propensity spends money to create engagement. MarketBetter captures the engagement that already exists — the 97% of visitors who never fill a form, the accounts surging on your category this week — and turns it into conversations now.

Which Should You Buy?​

Buy Propensity if:

• You have a defined target-account list and no way to advertise to it
• Your sales team is already at capacity and marketing's job is air cover
• Brand awareness inside your ICP is genuinely your bottleneck

Buy MarketBetter if:

• Your bottleneck is meetings, not awareness
• You're already getting traffic and signals but converting almost none of it
• You want sales working in-market accounts this week, not after a 90-day ad flight

The honest sequencing answer: if you can only fund one layer, fund the one that ends in a booked meeting. Ads without an outbound motion warm accounts nobody works. Outbound without ads still books meetings — it just works a slightly colder room. Add the air cover once the capture layer is running.

FAQ​

Is Propensity cheaper than MarketBetter? They're in a similar bracket, but they buy different things. Propensity's $2,000-$4,000/month buys ad activation with channel gates and metered contact data. MarketBetter's flat pricing buys person-level identification plus outreach execution. Compare cost per meeting, not cost per month.

Can you run Propensity and MarketBetter together? Yes, and the combination is coherent: Propensity warms your target list with ads; MarketBetter catches the accounts that heat up and books the meetings. Just sequence the capture layer first.

Is Propensity a 6sense replacement? For SMB ad activation, largely yes — at a tenth of the price. For revenue teams that need intent to drive outbound, neither Propensity nor 6sense closes the loop to a meeting. See our MarketBetter vs 6sense comparison and 6sense pricing breakdown.

What does MarketBetter cost? Flat platform pricing with no channel gates or metered contact data. Book a demo for numbers against your account list.

Ready to work the accounts that are already in-market? Book a MarketBetter demo.

Here's the breakdown, a worked example for a 100-account campaign, and the line item almost every ABM budget forgets.

The Four Cost Buckets​

1. Platform: $24K-$150K+/year​

The software that builds audiences, activates channels, and measures engagement.

Watch the gates: on tiered platforms, LinkedIn activation, Google/YouTube, and unmetered contact data often sit in higher tiers, so the sticker price and the operational price diverge fast.

2. Media: The Per-Channel Reality​

2026 benchmark CPMs for B2B-targeted inventory:

Media allocation varies wildly by strategy — ad-led programs put 40%+ of total budget into media; outbound-led programs as little as 10%.

3. Content: The Quiet Budget Eater​

Ads need somewhere to land. Personalized landing pages, one-pagers per segment, case studies per vertical, creative refreshes every 6-8 weeks (B2B audiences are small; frequency burns creative fast). Dedicated ABM content budgets run $80K-$500K/year at the enterprise end. Lean teams can compress this, but zero-content ABM is just retargeting with a fancier name.

4. People: The Forgotten Line Item​

Someone has to run this — audience builds, channel ops, sales coordination, reporting. A fractional marketing ops hire or agency retainer adds $3K-$15K/month. Skip it and the platform becomes shelfware; the data on why ABM rollouts fail is mostly a story about missing owners, not missing tools.

Worked Example: 100 Accounts, One Quarter​

A realistic mid-market omnichannel campaign — display + LinkedIn + CTV + direct mail against 100 target accounts:

~$2,200 per account per year. That's the honest unit cost of omnichannel air cover — before a single meeting is booked.

The Line Item Everyone Forgets: Capture​

Here's the uncomfortable math. That $55K/quarter produces impressions, engagement lift, and warmer accounts. It does not produce meetings. Meetings happen when someone notices an account heating up and reaches out — fast, to the right person, while the interest is live.

Most ABM budgets spend everything on warming and nothing on catching. The engaged visitors hit your site anonymously, don't fill the form (97% never do), and leave. The ad budget warmed them; nobody was watching the door.

The capture layer — person-level visitor identification, in-market account detection, routed outreach with an SLA — typically costs a fraction of the media budget and is the only part of the stack whose output is denominated in meetings. If your budget can't fund both, fund capture first: it monetizes the demand you already have, including demand your ads didn't create.

How to Right-Size Your Budget​

1. Work backward from pipeline math. Needed pipeline ÷ average deal size = deals; deals ÷ win rate = opportunities; opportunities ÷ account-to-opp rate = accounts to target. Budget for that list, not a round number.
2. Tier the spend. Full omnichannel (mail, CTV, 1:1 pages) for tier-1 only; display + LinkedIn for tier-2; contextual + capture-only for tier-3.
3. Cap media until capture works. If in-market accounts currently reach your site and nothing happens, every media dollar is leaking.
4. Measure cost per meeting, not cost per MQL. It's the only metric that survives contact with a sales team.

FAQ​

What's the minimum viable omnichannel ABM budget? Around $40K-$60K/year gets a small program: SMB platform, modest display + LinkedIn media, lean content, part-time ops. Below that, run capture + outbound only and skip paid media.

What ROI should ABM deliver? Programs that survive tie spend to sourced/influenced pipeline at 3-5x minimum. Engagement-lift reporting alone is how programs get cut in the next budget cycle.

Do I need CTV and direct mail? No. They're tier-1 seasoning, not foundations. Display + LinkedIn + a working capture layer outperforms a six-channel program with no one working the signals.

Want the capture layer priced against your account list? Book a MarketBetter demo.

If you've seen older reviews quoting $1,000-$2,000/month, note that pricing has moved up. Here's the current breakdown, what reviewers actually say, and the questions to ask before signing.

Propensity Pricing: The 2026 Tiers​

Billing is monthly with no disclosed annual lock-in — genuinely rare in ABM, where 6sense and Demandbase quote six-figure annual contracts.

At list price that's $24,000, $36,000, or $48,000 a year. Cheaper than enterprise ABM by a wide margin; far from pocket change for the SMB growth teams Propensity targets.

The Costs That Aren't on the Pricing Page​

Three things to pressure-test on the sales call:

1. Contact data is metered below the top tier. G2 reviewers flag added contact-information costs that accrue with each new campaign launch — and "unlimited contact data" only appears at $4,000/month. If your motion is contact-level ABM (Propensity's whole differentiator), model this before assuming the $2K tier is your real price.
2. Channel gating drives upgrades. LinkedIn — the one paid channel most B2B teams actually want — requires the $3,000 Strategic tier. Google and YouTube require $4,000. The tier you'll actually run is probably not the tier on the ad.
3. Media spend is your problem. As with most ABM platforms, the subscription buys the targeting and activation layer. Budget your actual ad dollars on top, and ask explicitly what (if any) media spend is bundled at your tier.

What Reviewers Like​

Propensity holds a 4.8/5 on G2 across roughly 30 reviews, most from small-business users. The consistent themes:

• Speed and ease of use. Campaign setup is fast, with formats ranging from geofencing to 1:1 ABM plays, and implementation measured in days, not quarters.
• Native ad activation without a DSP. Running display and social campaigns against intent-surging accounts from one tool, with no separate ad-tech stack, is the platform's clearest value at its price point.
• Support that acts like an extension of your team. For a small marketing team without RevOps headcount, reviewers describe the Propensity team as doing real operational lifting.
• HubSpot integration with contact- and account-level performance tracking.

Where It Falls Short​

• Thin intent coverage. Reviewers and analysts note Propensity's intent data runs shallower on mid-market and lower-enterprise accounts than 6sense or Bombora. If your ICP is niche, sample the free intent report (top 100 accounts) before buying — that's what it's for.
• Small proof base. ~30 G2 reviews is a thin sample next to established platforms. The 4.8 average is real but easy to move.
• It's an advertising engine at heart. Propensity's channels — display, CTV, geofencing, contextual, paid social — build awareness at target accounts. What it doesn't do is put a rep in front of a specific in-market buyer. Impressions warm accounts; they don't book meetings.

Who Propensity Actually Fits​

Propensity makes sense if you're a 1-5 person marketing team that wants to run multi-channel ABM air cover — ads across display, CTV, and social aimed at intent-surging accounts — without an enterprise contract or a media agency. It's a legitimate budget answer to 6sense and Demandbase for that use case.

It's the wrong tool if your bottleneck is pipeline, not awareness. If the question you're asking is "which specific companies and people are in-market right now, and how do we get a seller in front of them this week," an ad-impression platform is solving one layer down from your problem.

The Signal-Based Alternative​

That second case is where MarketBetter takes a different architectural bet. Instead of spending the budget on impressions at target accounts, it identifies the people already showing intent — person-level website visitor identification, blended first- and third-party intent scoring — and routes them into human-reviewed email and LinkedIn outreach, synced to HubSpot, Salesforce, or Pipedrive.

The practical difference in one line: Propensity shows ads to accounts that might be in-market. MarketBetter starts conversations with the people who already are. Many teams run air cover and outbound together — but if you can only fund one layer, fund the one that ends in a booked meeting. (Full comparison logic in our MarketBetter vs 6sense breakdown — the same reasoning applies here at a smaller price tag.)

FAQ​

How much does Propensity cost in 2026? $2,000/month (Essential), $3,000/month (Strategic), or $4,000/month (Unlimited), billed monthly. Older reviews citing $1,000-$2,000/month reflect earlier pricing.

Does Propensity require an annual contract? No annual commitment is disclosed — pricing is presented as monthly flat rates, unlike most enterprise ABM platforms.

What's the catch in Propensity's pricing? Contact data is metered below the $4,000 tier and accrues per campaign, LinkedIn ads require the $3,000 tier, and Google/YouTube require the $4,000 tier. Ad spend is separate from the subscription.

Is Propensity a 6sense alternative? For multi-channel ABM advertising on a smaller budget, yes. For deep intent data on mid-market accounts, its coverage is thinner than 6sense or Bombora. See our 6sense alternatives roundup for the full field.

What should I compare Propensity against? Other account-based marketing tools for the air-cover layer — and signal-based outbound platforms like MarketBetter if your goal is booked meetings rather than account awareness.

Want to see what person-level intent looks like on your own website traffic before you commit to an ad budget? Book a MarketBetter demo.

Sometime in the past year, a new kind of visitor started showing up in our Google Search Console — one that never clicks, searches in complete sentences, and occasionally types "yes" into Google.

We dug into 90 days of Search Console data (June 27 – September 25, 2026) across our blog, and found that on some pages, the overwhelming majority of search impressions are no longer generated by humans at all. They're generated by AI agents — coding assistants, research agents, and buying copilots — using Google as a tool call.

This post shares the raw numbers, the three distinct query patterns we found, and what it means for anyone doing B2B marketing in 2026.

The page where 89% of "searchers" are machines​

Our guide on scraping conference exhibitor lists for sales prospecting pulled 26,656 impressions over the 90-day window, ranking at an average position of 7.5.

A page with that many impressions in the top 10 should generate hundreds of clicks. It got 50 — a 0.19% CTR.

The query report explains why. Roughly 23,700 of those impressions (89%) came from queries that no human being would ever type:

And then a long tail of near-identical variants, each referencing a specific exhibitor ID: "extract company details from tbse26.mapyourshow.com exhibitor 906394" (836 impressions), "...exhibitor 954105" (634), "...exhibitor 971223" (606), and so on.

Think about what that pattern means. Someone pointed an AI agent at a trade show's exhibitor directory and told it to build a lead list. The agent worked through the directory page by page, and for each exhibitor it hit a wall — so it did what agents do now: it searched Google for help, once per exhibitor, thousands of times. Each search was machine-composed ("extract X from URL Y"), machine-executed, and machine-read.

Every single one of those queries produced zero clicks. The agent read the search results page, took what it needed (or didn't), and moved on. No visit. No pageview. No analytics event. From our web analytics' point of view, none of this ever happened.

The three types of agentic queries we found​

Once you know what to look for, agent queries are easy to spot. Across our Search Console data, they fall into three buckets.

1. Tool-command queries: Google as a function call​

These read like API calls written in English — verb + object + source URL:

• "scrape exhibitor details from [domain]"
• "structured data extraction from [domain]"
• "find company website and phone number from [domain]"
• "get company info from [domain] exhibitor 982044"

The tell: humans search for categories ("conference attendee scraper" — a real human query on the same page, 352 impressions). Agents search for operations on specific resources, often with IDs a human would never memorize, let alone type.

2. Full-sentence buying prompts: the agent as researcher​

Our Qualified review and comparison pages surface a different species — complete, structured buying questions:

• "ai sdr tool that can score replies and push only qualified meetings to my sales team what should i buy"
• "best ai sales agent tools for qualifying inbound leads and booking meetings pricing included"
• "1mind vs qualified vs sable: which is best for smb sales?"
• "alternatives to qualified for enterprise ai sales assistants?"
• "ai agent that can handle inbound leads 24 7 and route them to sales what are the best options"

These are not keywords. They're prompts — requirements documents compressed into one sentence, with constraints ("pricing included", "for smb", "faster to deploy") that a human searcher would split across five separate refinements. Someone asked their AI assistant to shortlist vendors, and the assistant ran the research through Google.

We first wrote about this buyer-side shift in our B2B GEO playbook for AI buying agents. What's new is seeing it at volume in first-party data: vendor evaluation queries that arrive fully formed, get answered from the results page, and convert (or disqualify you) without a click.

3. Conversation leakage: chat turns fired as searches​

The strangest bucket. Scattered through our query report are fragments that only make sense as turns in a conversation with an AI assistant, accidentally routed to Google's search box:

• "yes"
• "more"
• "another"
• "which one should i try first"
• "are there any other alternatives?"
• "can you give me numbers"
• "its not allowing me to paste"
• "devami?" (Turkish for "continue?")

Each of these registered impressions against our pages. "Its not allowing me to paste" is someone talking to their agent mid-task. "Which one should i try first" is a follow-up question after the agent listed tools. These utterances are leaking into Google's query stream — presumably from agent frameworks and browser assistants that pass user input straight to search — and Google is dutifully matching them against indexed pages.

Amusingly, this bucket is the only one that clicks: "more" earned 3 clicks, "another" and "are there any other alternatives?" one each. When there's a human in the loop, even one keystroke deep, clicks come back.

Why this breaks the metrics you report on​

Three uncomfortable implications fall out of this data.

1. Impressions are inflated, and CTR is broken as a quality signal. If 89% of a page's impressions come from agents that structurally never click, that page's "bad CTR" isn't a title problem — it's a measurement artifact. We see the same decoupling on our pricing breakdowns: pages ranking at position 3–5 with six-figure impression counts and near-zero clicks, because the answer gets absorbed upstream — by AI Overviews, by agents reading snippets, by assistants summarizing the SERP. Before you rewrite a title for CTR, read the actual query report and ask who is searching.

2. Rankings now have an invisible audience. Your position 6 result isn't just competing for human eyeballs. It's being read, parsed, and quoted by agents assembling answers for their users. The click never happens, but the influence does — the agent recommends (or eliminates) you based on what it read. This is the core argument for generative engine optimization: the SERP is becoming an API, and your content is the response payload.

3. Your analytics undercount your actual reach. None of these 23,700 agent impressions show up in web analytics, and neither do the recommendations that flow from them. If a buying agent shortlists you from a search snippet and its user books a demo two days later, your attribution model calls that "direct traffic." The dark funnel just got a lot darker — which is exactly why we lean on website visitor identification to recover the human end of these journeys when they finally do land on the site.

What to actually do about it​

This isn't a doom post. Agents reading your content is a distribution channel — one most of your competitors are ignoring. Here's what the data pushed us to change.

Write answers, not teasers. Agents quote what they can extract. Put the direct answer — the price, the step list, the comparison verdict — in the first screen of content, in plain declarative sentences. We saw this work firsthand: our post on Codex's mid-turn steering feature captured thousands of impressions within days of the feature shipping because it answered the exact question people (and their agents) were asking, in the exact words they used.

Structure for machines. Tables, consistent headings, explicit entity names. An agent parsing "best AI SDR tools with pricing" rewards the page that states "Tool X costs $Y/month for Z seats" over the one that says "pricing varies by needs." Our pricing transparency study exists partly because concrete numbers are what both humans and agents are starving for.

Cover the workflow, not just the keyword. The agent queries on our conference post are task queries — the searcher (human or machine) is mid-workflow. Content that walks through the actual task end to end, like our SDR playbook template guide or our guide to automating LinkedIn Sales Navigator with Claude, gets matched against these long operational prompts far more often than thin listicles do.

Expect the buyer's first touch to be an agent. The full-sentence buying prompts above are early evidence of a shift we think defines the next few years of B2B: frontier models are getting good enough to run real GTM work, and buyers are handing them the vendor research. Your "first meeting" increasingly happens between your content and someone else's AI. Make sure your content performs well in that meeting.

Methodology​

All data is first-party Google Search Console data for marketbetter.ai, June 27 – September 25, 2026, web search type, query dimension. We classified queries as agent-generated based on structural patterns: imperative verb + source URL construction, embedded database-style resource IDs, full-sentence multi-constraint prompts, and conversational fragments with no standalone search intent. Ambiguous queries were counted as human. The 89% figure for the conference-scraper page is therefore a floor, not a ceiling.

We'll rerun this analysis as the data grows. If the trend holds, "share of agent impressions" may become a metric worth tracking on every B2B content dashboard.

MarketBetter identifies the companies visiting your site — including the humans who show up after their AI did the research — and tells your SDRs exactly what to do next. Book a demo →