Three vendors announced in the past two days that software agents will now carry a lead from capture to opportunity: SAP in a suite release, Zywave in insurance distribution and Commander in waste hauling.
Three releases, one handoff
On October 21, SAP published its Customer Experience Q3 2026 release notes. The sales section introduces a Deal Qualification Assistant that “automates lead qualification, enrichment, routing, and follow-up activities.” SAP splits the job across named agents. A Deal Qualification Orchestration Agent coordinates the path from lead capture to qualified opportunity. A Lead Enrichment Agent gathers prospect intelligence and company context. A Lead Qualification Agent evaluates fit and engagement signals to prioritize opportunities, and a Lead Conversion Agent manages the transition from qualified lead to sales opportunity. SAP says the capabilities are available to select customers.
A day earlier, Zywave, a technology provider for insurance distribution, described updates to its Apex AI platform in a PR Newswire release. Producers can now build an Ideal Customer Profile contact list inside the AI assistant they already use. The Zywave Apex MCP tool ranks contacts by title fit and known company opportunity signals, and by default it targets the single best contact at each company. Producers choose how many contacts to pursue per company, and every contact carries a note on why it was included.
Advertisement
On October 21, Commander, which sells to waste, recycling and scrap haulers, put out a release about its growth and a leadership appointment. It says its platform surfaces prospects such as new construction, business openings and competitor contract expirations, prioritizes them for each sales rep, drafts outreach and quotes, and manages the pipeline in a CRM built around how hauling companies sell. Commander says it grew annual recurring revenue 300% this year, has identified more than $70 million in new revenue opportunities for customers since January and serves more than 100 waste management companies.
Where the work moves
The three products differ in size and market, but the division of labor is the same. Software now decides which account or contact deserves attention, gathers the context a rep would otherwise look up, and drafts the first message. The human step that remains is the conversation after a prospect responds.
SAP describes the benefit as reduced administrative effort and better lead quality. Zywave describes it as more replies, more meetings and more deals. Commander’s Dave Meizlik, President and COO, put the pitch this way: “We give haulers a sales engine that knows their market, tells reps who to call and why, and does the work of finding and closing new accounts.” All three are vendor claims. None of the releases publishes a conversion rate for the automated steps, and Commander’s $70 million figure counts opportunities identified, which is a different measure from revenue closed.
The structure of SAP’s release is also worth reading. The same pattern, an orchestration agent over specialist agents, appears in its service section (a Case Management Assistant) and its marketing section (a Campaign Assistant), so qualification is one instance of a template SAP applies across the customer lifecycle. We reported on the same direction from another vendor when Microsoft’s Sales Development Agent started consuming Copilot credits on Nov. 16, and our earlier analysis of sales AI moving from single tasks to complete plays traced how vendors bundle steps into sequences.
The routing rules become policy
Once an agent decides which lead is qualified and who receives it, the criteria that used to live in a spreadsheet or a routing table sit inside the product. SAP lists routing as one of the activities the assistant automates. Zywave’s default of one best contact per company is a routing rule too, set by the vendor and adjustable by the producer. We made the case in an earlier column that speed to lead is a routing problem, and agent-run qualification raises the stakes of getting those rules right, because a wrong rule now applies to every lead at machine speed.
In our reading, the vertical examples show where this goes next. Commander and Zywave built for a single industry and ranked prospects on signals specific to it, such as contract expirations and loss data. A horizontal suite agent has to qualify leads for every industry its customers serve, which makes its fit signals more generic. A buyer weighing a suite assistant against a vertical tool is choosing between breadth of integration and depth of signal.
What it means for the sales leader
Treat agent-run qualification as a change to your funnel definition and test it as one.
- Ask each vendor for the qualification criteria in writing, including the fit and engagement signals the agent weighs, and compare them with your current definition of a qualified lead.
- Run the agent beside your existing process on a sample of leads for a full sales cycle, and compare opportunity creation and win rates between the two groups.
- Decide who owns the routing rules once they live in the vendor’s product, and log every change to them.
- Keep a human review on the leads the agent rejects for the first quarter, since a false negative never shows up in a pipeline report.
- Ask for conversion data on the automated steps. Opportunities identified and emails sent measure activity, and only closed revenue measures outcome.
SAP’s agents are available to select customers today, so those buyers can run the comparison this quarter. Teams on other platforms can use the same checklist on the next vendor demo that includes the word “autonomous.”
Source: SAP News Center, “Autonomous CX Arrives: What’s New in SAP Customer Experience Q3 2026”
