How Should RevOps Leaders Implement an AI-Native Sales Org?

How do I thread Claude through our existing tech stack without breaking what works?

The cardinal rule of the Dorfman framework is: do not rip and replace. Your existing CRM, call recording platform, contract management system, and enrichment tools represent years of investment, customization, and institutional knowledge. Claude's role is connective tissue—the layer between and around these tools that makes them communicate and share context.

Start with a stack audit. List every tool in use across sales, deal desk, legal, RevOps, billing, and customer support. Identify which already have Claude or AI features embedded. Map each tool's role in the lead journey: enrichment, routing, system of record, call intelligence, contracts, deal coordination, support. Select six tools that form the core architecture of a lead's journey from inbound to closed-won.

For each stage, identify what Claude does that the tools cannot do alone. Examples: pulling historical context from Slack, docs, and call recordings into the account record before AE assignment; generating proposals that check policy and auto-upload to contract tooling; reconciling forecast data across systems before manager review.

What does the Slack-in, ticket-out system look like technically?

The Slack-in, ticket-out model replaces the scattered DMs and approval-chasing that kill deal velocity. Here's the technical design:

1. Input: Reps submit requests via a structured Slack workflow (or a simple message in a dedicated channel)

2. Ticket generation: Claude auto-generates a ticket with structured fields extracted from the request

3. Triage: Claude evaluates the ticket against policy documents, precedent databases, and historical resolutions

4. Resolution path A: Straightforward requests (standard pricing, common redlines, known compliance answers) are resolved autonomously—Claude posts the answer and logs the resolution

5. Resolution path B: Complex requests are escalated to the right human with all relevant context pre-assembled from CRM, email, call recordings, and Salesforce

6. Notification: The requesting AE receives a status update so they can set customer expectations

As RevOps, you own the policy and precedent documents that power autonomous resolution. Keep them current—Claude's triage quality is only as good as the governing documents it references.

How do I build and maintain the five core Sales Skills?

Skills are combinations of MCP connectors and Claude prompts. Your job is to build the connector infrastructure and work with sales leadership to define the prompt logic.

For Morning Brief: connect calendar, email, Slack, CRM, call recordings, and marketing event data. Define the synthesis logic—what gets prioritized, what constitutes an actionable item, and what format the output takes. Schedule delivery to each rep's Slack or inbox at a fixed time.

For Call Prep: build a shortcut-triggered workflow that pulls stakeholder research, historical context, competitive landscape, and public signals. The output is a one-pager delivered before each call.

For Customer Follow-Up: connect email, call recordings, CRM notes, and Slack. Claude extracts action items, drafts responses, deposits them in the rep's email client, and flags outstanding items for the next morning's brief.

Critically, Skills are living artifacts. Assign ownership, review usage data weekly, and update them as products, competitors, and processes change.

How do I measure whether the AI-native transformation is working?

Track five primary metrics: deals per AE per quarter, new-hire ramp time to first close, percentage of enterprise logos through self-serve, average support function response time, and forecast accuracy. Secondary metrics include Skill adoption rates, 24-hour follow-up completion rates, and new processes encoded per week through the AGI Pills loop.

Build dashboards that compare all metrics to pre-implementation baselines. The compounding nature of the AGI Pills loop means improvements should accelerate over time, not plateau. If they plateau, look for un-encoded manual processes or Skills that have become stale.