Your First 30 Days of AI: The Activation Playbook [63]

This episode of Leading Pre-Sales features hosts Nate and Ava discussing how SE leaders should approach AI adoption in their first 30 days. The conversation begins with a critical observation: most teams don't actually have a corporate AI strategy; instead, individuals autonomously adopt multiple tools, creating shadow IT situations with 9+ different AI tools in use simultaneously. Leaders often frame this as an enablement problem when it's actually a leadership decision-making gap.

The four key decisions presented are:

1. Environment Selection: Rather than choosing the cleverest tool, leaders should select the one closest to corporate and data requirements. Critically, legal and data protection officers must be involved from day one—not to approve decisions, but to help design guardrails collaboratively. This reframing (from "approval" to "design partnership") significantly accelerates organizational responsiveness.

2. Data Access Priority: Nate and Ava establish a counterintuitive ordering: email first, then calendar, then CRM. They argue email contains the richest deal context (6+ weeks of communication threads) and enables better prep sheets than prompts on blank pages. However, they acknowledge the risk: bad CRM data will be confidently repeated and beautified by AI. The solution is scoping pilots to regions or segments with strong data hygiene first, which builds organizational permission for broader rollout.

3. Full-Day Bootcamp (Split in Half): Morning sessions cover personal use; afternoon covers environmental and data use. Critically, SEs and AEs must attend together, not in separate tracks. The value isn't content delivery—it's AEs understanding the four hours per week SEs currently spend on specific tasks. Some leaders expand this to include partner companies, running regional sessions for scale.

4. Bi-Weekly Rhythm with Named Ownership: A 30-minute open call where team members demonstrate builds ("hot seat") and receive feedback. Crucially, this should be run by a named owner in RevOps, not the leader. This delegation compounds over time and is the step most leaders skip.

The discussion also addresses sustainability: builds must be tool-agnostic, documented in plain markdown, and stored in shared repositories. Weekend hero solutions that only work on personal machines with personal logins don't qualify for inclusion. A single named owner must oversee the repository, or it becomes abandoned by autumn.

The episode concludes with a concrete action plan: block two hours to write down four decisions (one environment, three data sources in order, one bootcamp date, one recurring call owner), then distribute before perfection. A fifth addition: one protected hour weekly for learning with explicit sources listed, because "opting out isn't neutral—it's falling behind slowly."