25 posts tagged with "AI & Sales Automation"

A champion changing jobs is the warmest signal in B2B sales. Someone who already bought from you just landed somewhere new, with new problems and new budget. Every champion-tracking vendor — us included — has been telling you some version of that story for two years.

Here's the part of the story nobody leads with: most of the "job changes" these systems detect aren't new. They're old news your CRM was too stale to notice.

We pulled the numbers on one customer's workspace this fall. Of 216 champion job-change signals detected over a 60-day stretch, only 20 involved a role the person had started within the previous 90 days. 98 of them — nearly half — were moves into roles the person had started more than two years earlier. Reps enrolled them in outreach anyway, and real prospects got "congratulations on the new role" emails for jobs they took in 2018.

That's not a warm signal. That's a cold email with a timestamp problem, sent to the exact person whose goodwill you could least afford to burn.

So we changed how the whole pipeline works. As of November 3, a detected champion move becomes a signal — with outreach, owner routing, and email lookup — only when the new role started within the last 60 days. Everything older is still recorded on the champion's history, but nobody gets congratulated for ancient history again.

Most of our customers sell globally. IoT connectivity deals in Germany and Japan, EHS compliance deals across five European markets, logistics deals in Brazil. Their buyers read email in their own language — and reply rates show it.

Until this week, running a German campaign in MarketBetter meant writing your templates in German and trusting the AI to take the hint. It usually did. "Usually" is not a word you want anywhere near your outbound.

So we shipped the obvious thing, and then the less obvious thing that makes it actually trustworthy. In the campaign builder's Voice step — right next to tone and AI Context — there's now a Language control. Pick German, and the campaign's emails are generated in German. All of them. Every touch, every follow-up, for every contact on the list.

The pickable set today: Czech, Dutch, French, German, Greek, Hungarian, Italian, Japanese, Korean, Polish, Portuguese (Brazilian and European), Romanian, Spanish (Castilian and Latin American), Turkish, and Ukrainian. English isn't on the list because the default already handles it — more on that below.

A buyer fills out your demo request form on Tuesday. On Thursday they're back on your site with a real question — pricing, security review, rollout timeline — and they open the chat widget. The first thing your chatbot says to this warm, self-identified, already-in-your-CRM prospect:

"Can I get your email so the team can follow up?"

They already gave it to you. Your CRM knows them. Your marketing automation is mid-sequence on them. The only system on your website that doesn't know they exist is the one talking to them.

We measured how often this happens across our own CRM-connected chatbot deployments: over a 90-day window, 13% of chatbot leads were already a contact in that customer's CRM, and 5% had already submitted a form on that same website. The bot asked every single one of them for their details again.

Today that stops. The MarketBetter chatbot now recognizes visitors who already submitted one of your website forms — and there's a second half to this release that matters just as much: what we deliberately didn't turn on, and the accuracy bar it has to clear first.

Outbound personalization has a last-mile problem. Teams spend real money personalizing the email — the signal, the opener, the proof point — and then the click lands on the same generic homepage every other prospect sees. The one moment a buyer voluntarily gives you their attention, you hand them the brochure.

Today we're shipping personalized landing pages in MarketBetter: for every account in an audience, the platform generates a dedicated page that reads like it was written for that account and looks like it belongs on your website — your fonts, your colors, your buttons, your layout. Not a page-builder template with your logo pasted on. Your actual design, captured from a page you already published.

And because a web page is public in a way an email never is, every page passes a human review gate before it goes live. More on that below — it's the part we sweated most.

Three weeks ago we launched Loops, our sales nurture agent, with a claim that made some people wince: most days, most people get nothing — that's the feature. A loop emails a non-responder only when a genuinely new update fits them, and a second AI can veto any send.

The launch post was about the sending machinery. A month of production taught us something we didn't fully appreciate when we shipped: a nurture agent that mostly stays quiet generates a surprising amount of signal around the sends — in the replies that aren't a yes or a no, in accounts that start moving while they're parked in the loop, and in the rhythm of the loop itself.

This is the follow-up in the same spirit as our Clay field report: here's what we learned, what we changed, and four questions we'd genuinely like your take on. We're still looking for design partners who want to argue with us.

Apollo's developer page now leads with a sentence that would have read as satire two years ago: "Build headless GTM tools, agents, and pipelines on one API." Search, enrich, sequence, and analyze — "no UI required."

That's not a feature announcement. It's a thesis about who the user of a sales platform is going to be. The term borrows from headless CMS — content systems that dropped their front end and became pure APIs because other software, not people, consumed them. Apollo is making the same move with outbound: the app is now one of several front ends, alongside a command-line tool, an MCP server inside Claude and ChatGPT, and 70+ REST endpoints — and Apollo's own numbers say a meaningful slice of its users have already stopped opening the app entirely.

We've been tracking this shift from the other side — AI agents showing up in our own Search Console data, Demandbase coining "B2A marketing" for selling to agents, Attio rebuilding its CRM as a database for agents. Apollo's version is the execution-layer chapter of the same story. Here's what actually shipped, what the published numbers do and don't support, and a concrete play a sales team can run with it this week — plus the part headless execution structurally can't solve.

On October 20, at its GO conference, Demandbase launched three new AI agents — an AEO Agent, a Campaign Agent, and an Audience Agent — and wrapped them in a new acronym: B2A, "business-to-agent" marketing. The pitch, in CEO Gabe Rogol's words: "Marketing to people isn't enough anymore because buyers no longer start with a search. They start with an agent. And those agents are deciding which brands get seen and which get overlooked."

Strip the acronym and the underlying claim is one we can verify from our own Search Console data: AI assistants increasingly sit between your content and your buyer, and they decide what the buyer hears about you. That part is real. Whether you need an enterprise ABM platform to respond to it is the question worth examining.

Here's what Demandbase actually announced, what the release doesn't say, and what a sales team can do about AI-answer visibility this week — including the parts that cost nothing.

On October 14, Attio CEO Nicolas Sharp announced what the company calls the architecture for Agentic Revenue — a rebuild of the CRM's data layer around one idea: "To agents, Attio looks like a database." Four new capabilities shipped with the announcement: a SQL Engine, Postgres-compatible Data Connectors, Agent Scale reads, and a new Activities data type.

Sharp's framing is the sharpest one-liner of the agent-CRM year so far: "In the age of agents, systems of record have never mattered more. They've also never been less prepared for what's coming."

He's right about the problem. Every vendor we've covered this fall — Oracle, Salesforce, Outreach — is bolting agents onto a system of record designed for humans clicking through list views. Attio's bet is different: make the record system itself speak the language agents already know. That's genuinely interesting. It's also, in its most useful form, gated behind a custom-priced Enterprise plan.

Here's what actually shipped, what it costs to reach, and what it does and doesn't change for a sales team.

On October 19, monday.com launched Harmony, a voice AI agent platform that runs sales calls end-to-end — prospecting, discovery, qualification, objection handling, pitching, and a warm transfer to a human rep with a full briefing. It's live now for mid-market and enterprise customers in the US, UK, Australia, and Singapore.

This is a workflow-software company walking straight into the AI SDR fight. And unlike the CRM giants shipping agents that work records already inside the system, Harmony attacks the live phone call — the channel most vendors have been too nervous to automate beyond routine support.

The launch claims are aggressive: roughly 200-millisecond response latency and "a contact rate of up to 70%." The flagship customer story is genuinely interesting — but read closely, it tells you exactly where voice AI works today and where it doesn't. Here's the breakdown.

On October 26 at Oracle AI World in Las Vegas, Oracle announced five new agentic applications for sales and service teams — territory planning, account research briefings, service diagnostics, field capacity planning, and CPQ environment migration. All five run on Oracle Fusion Claw, the "governed agentic execution runtime" Oracle introduced on September 29 with 25 launch applications, bringing its total agentic application count to 75.

That makes Oracle the fourth CRM-scale vendor in two months to ship autonomous sales agents, after Salesforce's Koa model and AIforce suite, Microsoft's Dynamics 365 agent push, and Google's universal Gemini agent.

But Oracle's announcement is interesting for a different reason than the agents themselves. While competitors lead with what their agents can do, Oracle led with how its agents are controlled — named governance artifacts like the "Outcome Receipt," an auditable record of every decision an agent made and why. That's a tell about where enterprise agentic AI is heading in 2027, and it gives every sales leader — Fusion customer or not — a sharper set of questions to ask vendors.

Here's what shipped, how the governance model works, what it costs (short answer: Oracle won't say), and what to do about it.