AI-augmented deal desk (L4)

Deal desk uses agent to summarize the deal, flag risks, suggest terms. Reduces approval cycle from days to hours.

WORKFLOW1Configure Unified Data In…estionManual2Design the Risk Discovery…PromptManual3Automate the Deal Brief G…nerationManual4Implement Human-in-the-Lo…p WorkflowManual5Track Margin and Cycle Pe…formanceManual
5 steps, in order, with the tool that owns each one.
Adoption ladderSix levels from Starter to Rebuilt. This item sits at level 4.L1 StarterOne tool, no workflow changeL2 AssistedAI drafts, humans approveL3 IntegratedWired into CRM and SlackL4 OrchestratedMulti-step, owned, measuredL5 AutonomousAgent runs, human auditsL6 RebuiltThe process itself changes
This playbook belongs at L4 Orchestrated. Running it above your level is how pilots stall.
Measures of successapproval cycle time; marginPROVE IT WORKEDapproval cycle timemargin

The steps

  1. 01

    Configure Unified Data Ingestion

    The Deal Desk Manager must first establish a unified data ingestion pipeline using an orchestration tool like Zapier, Make.com, or Workato. The goal is to trigger the AI agent the moment a 'Quote' is sent for approval in your CRM (Salesforce, HubSpot). • Configuration: Set up a 'New Record' trigger in your CRM directed at the 'Quote' or 'Deal' object where status equals 'Pending Approval.' • Data Mapping: You must pull three distinct pools of data: the Quote Line Items (products, quantities, discounts), the Opportunity Details (close date, competition field, account history), and the most recent 10-15 email communications from the linked Contact. Use an 'Email Search' module to find messages where the 'Subject' contains the Deal ID. • Tooling: CRM API access, a middleware connector, and OpenAI's GPT-4o or Anthropic's Claude 3.5 Sonnet via API. • Who: RevOps Analyst or Systems Admin. • Time: 3-4 hours to map all fields correctly. • Pitfall: Ensure you filter out internal-only emails; only ingest client-facing threads to avoid confusing the AI with internal chatter. • Definition of Done: A successful test run where a JSON payload containing the quote, opportunity data, and email text is sent to the AI environment.

  2. 02

    Design the Risk Discovery Prompt

    Create a System Prompt for your AI agent that functions as a Senior Deal Desk Analyst. This is where you encode your 'Rules of Engagement.' The prompt must instruct the AI to analyze the ingested data for specific 'Red Flags.' • Example Prompt: 'You are a Senior Deal Desk Analyst. Review the attached Quote and Email history. 1) Identify any discounts exceeding our 20% standard threshold. 2) Flag if the client mentions a competitor like X or Y in the emails. 3) Compare current margins against the last 12 months for similar accounts. 4) Assign a Risk Score from 1-10 (10 being high risk) based on aggressive discounting or vague contract language.' • Logic Setup: Use 'Function Calling' or structured outputs to ensure the AI returns a consistent JSON object with fields for 'Risk Score,' 'Risk Summary,' and 'Suggested Terms.' • Who: Deal Desk Manager and RevOps. • Time: 2 hours for prompt engineering and iterative testing. • Pitfall: Avoid generic prompts; you must explicitly list your 'Deal Floor' rules (e.g., 'Never allow Net-60 terms without VP approval') so the AI knows what to flag. • Definition of Done: The AI consistently generates a structured summary that highlights at least 3 specific risks per quote.

  3. 03

    Automate the Deal Brief Generation

    The AI must generate a 'Deal Brief' that lives inside the CRM or a Slack notification, ensuring it provides actionable suggestions rather than just data. This Brief should suggest 'Compromise Terms' to the human approver. • Settings: Configure the AI to output a 'Recommendation' field. If the Risk Score is >7, the recommendation should be 'Escalate to CFO.' If 4-6, 'Approve with Conditions.' If <4, 'Approve.' • Suggested Terms: Instruct the AI to suggest 'give-get' scenarios. For example: 'If the client wants a 25% discount, suggest we require a 2-year upfront payment or a marketing case study clause.' • Formatting: Use Markdown for the brief so it is readable in the CRM 'Description' field or a Slack Block Kit message. • Who: RevOps Lead. • Time: 1.5 hours. • Pitfall: Don't let the AI make the final decision. Ensure its output always includes the phrasing 'Suggested Action' to reinforce that a human must make the call. • Definition of Done: A formatted brief appears in the CRM Approval Request record within 60 seconds of a quote being submitted.

  4. 04

    Implement Human-in-the-Loop Workflow

    Set up a dedicated Slack or Teams channel (#deal-desk-approvals) where the AI posts the Brief. This centralizes the 'Human-in-the-Loop' workflow, preventing the 'Approval Cycle' from stalling in email inboxes. • Tooling: Use the Slack 'Post Message' or Teams 'Send Card' action in your middleware. • Integration: Include 'Approve' and 'Reject' buttons directly in the notification. These buttons should trigger a webhook back to your CRM to update the Quote Status. • Process: The Deal Desk Manager reviews the AI's summary, clicks into the CRM if deeper detail is needed, and then executes the decision directly from the chat app. • Who: Deal Desk Manager. • Time: 2 hours to build the webhook response logic. • Pitfall: Ensure your CRM permissions are set so that the middleware 'Integration User' has the authority to change quote statuses. • Definition of Done: A Deal Desk Manager can approve or reject a quote from their mobile device via Slack/Teams without logging into the CRM.

  5. 05

    Track Margin and Cycle Performance

    To measure the ROI of the AI agent, you must track 'Margin Performance' and 'Cycle Time' in a dedicated dashboard. • Data Capture: Every time a deal is approved, write the following to a custom 'Deal Desk Log' object in your CRM: Final Discount %, AI Calculated Risk Score, Time from Submission to Approval, and Human Override (if the human ignored the AI's advice). • Analysis: Create a report to compare the average margin of 'AI-Assisted' deals against historical benchmarks. Look for a reduction in 'Cycle Time' (the time from Quote Created to Quote Signed). • Cohort Tracking: Monitor these deals over a 6-month period to see if high-risk deals flagged by the AI (but approved by humans) result in higher churn or lower expansion. • Who: RevOps Manager / Data Analyst. • Time: 3 hours for dashboard creation. • Pitfall: Failing to track when a human overrides the AI makes it impossible to 'tune' the AI's prompt later. • Definition of Done: A live dashboard showing a trend line of 'Average Approval Hours' (targeting <4 hours) and 'Average Deal Margin.'

Next playbooks

Unfamiliar terms are defined in the AI and Revenue Dictionary. Related frameworks live in the framework library.

Share this playbook

Posting to Instagram or TikTok? Copy the link, it carries the title, summary and share image.

Arrives weekly by email. Free. Unsubscribe anytime. By subscribing you agree to our Privacy policy and Terms. We never sell or share the list.