AI Sales Cockpit: Deal Review as a Guided Playbook Instead of a Manager Q&A

What is the Sales Cockpit?

The Sales Cockpit is phase one of agent playbooks — a structured deal review as a guided multi-stage dialogue with the AI coach. Instead of an open chat session, the rep follows a defined path: Discovery, Pain, Champion, Stakeholder Map, Decision Criteria, Proof, Pricing, Close Plan, Handover, Retro, Manager Sync.

Per stage the user picks: voice or chat. On the way to a customer meeting, talk. At the desk, type. Both paths produce the same result — a structured answer per stage that the coach pulls together.

When the agent opens, the cockpit starts automatically. Anyone with an open session sees a resume banner and continues exactly where the last state stopped. No "where were we?", no fresh start.

The 11 Stages

The playbook covers the full arc of a complex B2B deal — from initial need recognition to handover to customer success or the manager sync after closing:

• Discovery — What task does the customer want to solve? Who named the problem?
• Pain — What happens if nothing happens? How high is the cost of standing still?
• Champion — Is there a person driving the change internally? What is their self-interest?
• Stakeholder Map — Who decides, who influences, who blocks? One position per person.
• Decision Criteria — What criteria must the solution meet for a "yes" to be possible?
• Proof — What evidence convinces the buying committee? Pilot, reference, ROI model?
• Pricing — What budget is set? Is there an approved frame?
• Close Plan — What steps lead to closing, with what dates?
• Handover — What does customer success need to know so onboarding starts cleanly?
• Retro — What worked, what took longer than planned?
• Manager Sync — What does leadership need to influence the next deal?

Each stage is its own form set: free text, multiple-choice chips, segmented toggles, computed fields. The coach interprets the answers, asks follow-ups, suggests phrasing — per stage, not across the whole cockpit. That keeps the conversation focused.

Master and Partner — Two Tracks in Parallel

In complex deals, lead sales and partner work on different tasks. The lead drives discovery and champion building. The partner handles the technical solution sketch and decision criteria. Forcing both onto the same eleven stages would miss reality.

The cockpit solves this with two tracks: master and partner. Both roles see different stage sets, both contribute independently. The contributions stay visible — the lead sees what the partner wrote on decision criteria, the partner sees how the lead describes the stakeholder map. Nobody writes in the same field at the same time. The cockpit holds contributions in stage-specific slots — what one person writes survives when the other continues.

In practice: the account partner can run their stages on Wednesday while the lead sales adds theirs on Thursday. By Friday a shared review document exists — both views, one output.

Output: Persistent Markdown Handover

At the end of every cockpit run, a structured markdown summary appears. A file that is copyable, fits into CRM notes, lands on Confluence pages, goes to the manager. No screenshots, no tickets, no back-and-forth.

What it contains: the core answer per stage, the coach's assessment, the open points and the next step. Anyone who picks up the deal in two weeks reads for five minutes and has the state. Anyone who hands the deal to a colleague hands over the document — and the colleague sits at the same level as the previous owner.

The markdown handover is the point where AI coaching stops being a practice tool and starts intervening in the operational sales workflow. The cockpit produces no learning snippets that stay inside the module afterward. It produces deal artifacts the team uses further.

Why This Workflow First

Three reasons the agent playbooks start with the Sales Cockpit:

Deal reviews have the biggest transfer gap. In training, role plays repeat, objection handling drills, discovery questions sharpen. But the review of a concrete deal — where numbers, stakeholders, and decision logic come together — runs in practice without structure. The coach pulls that into a reproducible path.

Manager sync is the most common bottleneck. Leadership wants to know where deals stand without asking thirty reps individually. The markdown output format gives the manager exactly that — state, risk, next step — in a form readable in five minutes.

Multi-stage forms are technically non-trivial. Track resolver, stage-keyed payload merge, resume logic for abandoned sessions, idempotency on markdown render. Building it once cleanly opens the door to further playbooks — customer onboarding, QBR, lost deal analysis. The Sales Cockpit is the template.

What Comes Next

The cockpit is phase one. It covers the deal review workflow fully and runs in the platform today. On the roadmap: further playbook templates for other sales tasks following the same multi-stage pattern — each with own stages, own tracks, own output form.

The structure stays: 11 or fewer stages, voice or chat per stage, markdown handover at the end. Anyone who used the cockpit once knows how the next playbook works.

Try the Sales Cockpit Live

The Sales Cockpit is available as a guided deal review workflow in the VIAVENDO platform today. For a first impression, a walkthrough on a real or anonymized deal — from discovery to manager sync, with real markdown output at the end.

Schedule a walkthrough — we run the cockpit on a deal from the current pipeline context and discuss the master/partner configuration for your sales team.

Further Reading

• Account Development Plan vs. AI Deal Coach — How the AI coach extends the classic ADP instead of replacing it
• Preserving Sales Knowledge: Knowledge Transfer with AI — What happens to experiential knowledge when a senior sales rep leaves