A Deal Team of Six Still Runs on Single-Player AI

It takes a village to close a deal, but AI in sales is still single-player. An SDR, an AE, a solutions engineer, a manager, a CSM, and a CRO all work the same account. Each of them opens a chat window alone.

Six People Work the Deal, and Six Chats Start From Zero

Every person on a deal team now has AI. The SDR uses it to research the account. The AE uses it to prepare for discovery. The SE uses it to draft the security response.

Each of those chats holds a private slice of the account, and none of it carries over. When the SDR hands the meeting to the AE, the research on the champion's priorities stays in the SDR's chat history. The AE starts again. So does the SE, a week later, when the technical questions arrive.

This is context loss, and it compounds at every handoff. Multiply it across six roles and a long enterprise cycle, and the team spends real hours rebuilding what someone already knew. One breakout group of revenue leaders described the result: "Too many signals across too many tools. None of them wrong. None of them synthesized."

What changes is where the knowledge lives. The account needs one continuously updated picture that every person and every agent works from. Then the AE inherits the SDR's research on day one, and the SE walks into the technical call already knowing what the buyer cares about.

Chat Waits to Be Asked, So It Misses the Moments That Move Deals

Chat answers a question, then waits. That works for tasks a rep already knows to ask about. Deals rarely turn on those tasks.

They turn on events nobody thought to ask about. The champion changes jobs in week six. Product usage drops in an account the CSM is preparing to renew. A new executive joins the buying committee and starts asking about budget.

A revenue leader at a public SaaS company put the gap plainly: "We have great AI tools. They save a few minutes a day. I'm not getting more revenue." Minutes saved on request do not add up to pipeline. The work that moves the quarter is often the work no one asked for.

What changes is who starts the work. Proactive agents monitor every account, identify what needs attention, and act within the permissions leaders set. When the champion leaves, an agent is already mapping the new stakeholders and drafting outreach for the AE to review.

Leaders Set the Playbook but Cannot See Whether It Runs

Revenue leaders write a playbook. They often cannot see whether it runs. The usual way to find out is the forecast call.

A manager asks about a deal in commit and learns there is no confirmed economic buyer. The AE knew, and so did the AE's chat history. The manager did not, because single-player AI is invisible to everyone except the person typing.

That is the larger cost of single-player AI. Leaders lose visibility into execution, so coaching turns into reconstruction. Managers spend the forecast call discovering gaps instead of deciding what to do about them.

In a multiplayer model, the leader writes the rule once. For example: no deal moves to commit without a confirmed economic buyer. The system checks every open deal against that rule, flags the ones that fall short, and puts agents to work closing the gaps.

The manager steps in where judgment matters, such as a stalled negotiation or a champion who has gone quiet. This is the move from insights to enforcement and action. The forecast call becomes a conversation about strategy, because the basics are already handled.

Shared Account Context Is What Gets a Team Past Skills

AI in sales matures in four stages:

1. Chat answers a question, then waits.

2. Skills run repeatable tasks on request.

3. Multiplayer adds collaboration and enforcement between reps, leaders, and agents.

4. Autonomous agents act continuously within your permissions.

The advantage moves to proactive agents. Getting from skills to multiplayer is the hard step. It needs three things: shared account context, a shared place to collaborate, and proactive agents.

The common instinct is to close that gap one use case at a time. A prospecting agent here, a renewal agent there. Each one holds its own partial view of the account, and each one needs its own upkeep.

Samsara looked at that path and chose differently. It picked one persistent account-context layer and a partner over building agents use case by use case. The alternative would have produced fragmented agents with growing maintenance.

The operational lesson is to build the context first. Shared Account Context is a continuously updated understanding of every account. It draws on internal signals (CRM, calls, email, product usage) and external signals (news, people changes, market activity). Every new agent, every new rep, and every leader starts from the same picture.

The Quarter Changes When the Team Works From One Context

Picture an AE's Monday under this model. Priority accounts are already researched. Two deal risks are flagged with a recommended next step, and outreach to a new stakeholder is drafted and waiting for review.

The AE decides what to send, who to call, and how to run the meeting. Agents carried the research and preparation. The AE owns the relationship, the judgment, and the close.

Across the team, the same context flows through every handoff. The SDR's research reaches the AE. The AE's call notes reach the SE and the CSM. The manager sees which deals follow the playbook and which need help, without asking anyone to update a field.

This is the system Actively builds for revenue teams: proactive agents working every account, one Shared Account Context, and the playbook leaders set. Before Actively, Verkada's reps spent 15+ hours a week deciding which accounts to focus on, reading prior interactions, researching, and writing emails.

The results show up in the number. Greenhouse saw pipeline per rep rise 54%, and ramp time was cut in half within 6 months. Ramp's win rate rose 23%.

Samir Joglekar, Chief Revenue Officer at Greenhouse, described the starting point many teams will recognize: "Most AI tools we evaluated were just assistants; our reps still had to connect the dots." Connecting the dots is the work a deal team of six does every day. Whether it shows up in pipeline depends on whether that team works from the same context.

Your team already uses AI every day. The open question is whether it works as a team. Look at the largest deal in your forecast. Count the people on it, then count how many of them share the same picture of the account.