Frequently Asked Questions About Dorfman AI-Native Sales Org Build
21 answers covering everything from basics to advanced usage.
// Basics
What does 'Claude as connective tissue' actually mean?
It means Claude's role is to make all your existing tools talk to one another, create a seamless customer journey, and handle everything in between and around those tools. Instead of being the seventh app in your stack, Claude sits across enrichment, routing, CRM, call intelligence, contracts, and support — pulling context and threading them into one coherent experience.
What are the four constraints I need to map first?
The four immovable parameters are: (1) demand volume you cannot staff for, (2) Claude and AI capabilities already inside your stack, (3) cross-functional dependencies like legal, deal desk, RevOps, billing, and CS that must scale alongside sales, and (4) your headcount growth ceiling and the culture bar you refuse to drop. Every subsequent decision is made inside these constraints.
What are the five core Sales Skills and what does each do?
Morning Brief delivers three prioritized daily actions. Call Prep outputs stakeholder research and discovery questions before each call. Customer Follow-Up extracts action items and drafts responses within 24 hours. Competitive Intel generates dynamic battle cards tailored to the specific deal. Create an Asset produces on-brand custom collateral on demand. Together they're packaged as the Sales Plug-in.
Can I apply this without Anthropic's Claude specifically?
The framework is built around Claude as connective tissue and uses MCP connectors to thread it through your stack, so the specific capabilities described map to Claude. The underlying principles — connective tissue not a seventh tool, two funnels, encoding top-rep behavior as Skills, Slack-in ticket-out — are transferable, but the Skills and Plug-in architecture assume an AI layer with MCP-style connectivity.
// How To
How do I conduct a top-rep behavior audit?
Interview and observe your highest-performing reps to document their specific pre-call research process, follow-up discipline, competitive positioning habits, and collateral creation approaches. These observations become the raw inputs for Skills. The goal is to capture what the best reps do differently so you can encode it as the baseline behavior for every rep, not just top performers.
How do I set up the self-serve funnel without cannibalizing my AE deals?
Define clear qualification signals — firmographic and behavioral data — that distinguish self-directed buyers from complex, high-ACV opportunities needing a human AE. Route smaller or more self-directed buyers into an AI-guided enterprise path through purchase and onboarding, while complex deals go to BDRs. Launch as an MVP first, then track the percentage of new enterprise logos coming through self-serve.
How do I build the Morning Brief Skill?
Configure a single daily prompt that pulls from calendar, email, Slack, CRM, call recordings, marketing events, and centralized initiatives, then delivers three prioritized actions to each rep's Slack or inbox at a fixed time every morning. Use MCP connectors to link the data sources and encode your prioritization logic so the brief surfaces what matters most today.
How do I set up the Slack-in, ticket-out workflow?
Make Slack or Teams the single front door for every support function. When a rep submits a request, Claude auto-generates and triages the ticket, then either resolves it autonomously from precedent and policy documents or escalates to the right human with context pre-assembled from CRM, email, call recordings, and Salesforce — notifying the AE of status throughout.
// Troubleshooting
My AI-generated collateral looks generic and off-brand. How do I fix it?
Encode your brand standards directly into the Create an Asset Skill so output is never generic 'AI slop.' Every asset must be tailored to the specific deal stage, stakeholder profile, and customer needs, and designed to help win. Feed the Skill your brand guidelines, tone, visual standards, and proof points so it produces on-brand collateral by default.
My forecast calls are still just data-gathering. What went wrong?
You haven't let Claude handle reconciliation in advance. Claude should reconcile data across all systems before the call so managers and AEs walk in with clean numbers. That frees the forecast call for discussion, deal strategy, and identifying where AEs need help — not for chasing down which number is correct across three different tools.
I added Claude but I still have six siloed experiences. Why?
You bolted Claude on as a seventh standalone tool instead of using it as connective tissue. The fix is to thread Claude through each stage of your existing six-tool lead journey — enrichment, routing, CRM, call intelligence, contracts, support — so it pulls and shares context across them. Coherence across your stack is the goal, not another app.
My supporting functions became the new bottleneck. How do I prevent that?
Sales is not an island. If you scale only the AE layer, deal desk, legal, RevOps, billing, and CS become the choke point. Give every supporting function the same elasticity by routing all their requests through the Slack-in, ticket-out workflow so Claude triages, resolves, or escalates — ensuring support scales at the same rate as sales capacity.
// Comparisons
How does this compare to hiring more BDRs and AEs?
Hiring adds capacity linearly and slowly — recruiting pipelines can be months deep, and scaling headcount to hit demand often forces you to lower your bar. The Dorfman build amplifies the people you already have and adds a self-serve funnel that generates ACV with no human AE, giving nonlinear capacity gains while protecting your recruiting standard and culture.
How is a Skill different from a generic ChatGPT prompt?
A generic prompt is a one-off instruction. A Skill is an encoded best practice built as a combination of MCP connectors and Claude prompts that replicates a top rep's behavior at scale, pulls live context from your actual systems, and is packaged into the Sales Plug-in issued to every rep. It's a living, reusable artifact — not a copy-pasted prompt.
How does dynamic coaching compare to a static sales methodology?
A static methodology is set quarterly and quickly goes stale in a fast-moving market. Dynamic coaching surfaces six calibrated coaching moments per week per rep using Claude, recalibrated to current business priorities, the live competitive environment, product changes, and deal patterns. What mattered last month may be irrelevant this week — dynamic coaching keeps guidance aligned to what's happening now.
How does the Two-Funnel doctrine differ from traditional PLG plus sales?
Traditional models often treat self-serve as a lower tier or a consolation path. The Two-Funnel doctrine treats the AI-qualified self-serve funnel as a distinct, equally important revenue path — getting the right buyer to the right plan at the right time. It's not about routing everyone to a human; it's about matching each buyer to the funnel that serves them best.
// Advanced
How do I know which six tools should form my core architecture?
List every tool in use across sales, then mark each tool's role in the lead journey — enrichment, routing, system of record, call intelligence, contracts, deal coordination, support. Choose the six that carry a lead from inbound to closed-won. Do not add new tools; the discipline is building coherence across what you have, with Claude threading them together.
What is closed-won governance and how do I implement it?
Closed-won governance is a one-Skill-per-step checklist Claude works through at deal close to ensure every cross-functional requirement — provisioning, billing, terms of service, onboarding enrollment, org mapping, invoicing — is completed without administrative gaps that create a poor customer experience. Implement it as a governed sequence where each step is a discrete Skill invocation tied to the closed-won checklist.
How do I keep Skills from going stale over time?
Treat Skills as living artifacts, not one-time builds. Track which Skills are being used and where AEs are still doing manual work — those gaps are your next encoding candidates. As the business evolves, revisit Skills so what was the top priority last month gets updated. The AGI Pills loop feeds continuous improvement back into the Skills library.
What should a sales leader's job become in an AI-native org?
Systems design. The sales leader's job is no longer purely deal strategy — it's thinking about the entire customer and AE journey as a system and identifying where Claude accelerates each stage. You become responsible for the architecture of the two funnels, the Skills library, the support-function front door, and the coaching layer, not just individual deal tactics.
How do I measure whether the AI-native build is working?
Track the percentage of new enterprise logos coming through the self-serve funnel as your primary health metric there. For the sales funnel, monitor AE capacity per rep, ramp time to first close for new hires, deal velocity through cross-functional approvals, and Skill adoption rates. Rising self-serve ACV, compressed ramp, and faster approvals signal the system is compounding.