Building an AI-native revenue organization

In this guide, we share how revenue leaders can roll out Claude across a sales organization, including the setup decisions, a three-phase rollout plan, and an ROI measurement framework.

In our conversations with revenue leaders, we hear the same challenges: half the team barely touches the AI it already has, the best sellers build skills and prompts that no one else uses, and leadership has no visibility into usage and spend. Meanwhile, sellers gather account context before every call from multiple systems: the CRM, email, call recordings, Slack. That can mean spending thirty minutes on prep for fifteen minutes of conversation.

Individual reps can save time every day when they hand over call prep to Claude, but when the whole team adopts it, the benefits compound. How much a sales organization gets out of Claude depends on what it has built around it: which systems Claude can read and write and whether it has the access and controls to take on more complex work.

Cox Communications reported a 7x return in its first-year of AI investment and cut the cost of validating and enriching sales leads by 86%, bringing accuracy up from 18% to 97%. At Cyera, where 88% of roughly 1,500 employees use Claude weekly, BDRs draft outreach with a skill that’s been built using the top performers’ best work—a quality improvement as much as a time saving.

To help revenue teams get the most out of AI, we put together Building an AI-native revenue organization, a guide to rolling out Claude across sales.

In the guide, we share:

Read the guide here.

Get the developer newsletter

Product updates, how-tos, community spotlights, and more. Delivered monthly to your inbox.