Sanctioned email + meeting assistant (L2)

One approved AI tool for the whole revenue team (e.g. Lavender, Regie, Copilot). Centralized billing, basic usage tracking, prompt library owned by enablement.

WORKFLOW1Execute a two-week vendor…bake-offManual2Centralize billing and us…r accessManual3Build the Enablement-owne… prompt libraryManual4Conduct a team-wide 'Usag… Clinic'Manual5Establish a weekly adopti…n review cadenceManual
5 steps, in order, with the tool that owns each one.
Adoption ladderSix levels from Starter to Rebuilt. This item sits at level 2.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 L2 Assisted. Running it above your level is how pilots stall.
Measures of successReply rate; Meetings booked; Tool adoption %PROVE IT WORKEDReply rateMeetings bookedTool adoption %

The steps

  1. 01

    Execute a two-week vendor bake-off

    Start by selecting two leading AI platforms (e.g., Lavender vs. Regie.ai or Gong Engage vs. Outreach Kai). Appoint a 'Pilot Lead' (RevOps or Enablement Manager) to run a 14-day head-to-head trial. Assign 3-5 high-performing reps to each tool to ensure the data isn't skewed by poor sales fundamentals. • In your CRM (Salesforce/HubSpot), create a custom checkbox or tag named 'AI_Pilot_Group' to track these reps. • Define your primary success metric as 'Positive Reply Rate' rather than just total volume. • Create a simple Google Sheet to track qualitative feedback: 'Ease of Use (1-10)', 'Personalization Quality', and 'Time Saved per Email'. • Owners: RevOps for technical setup, Enablement for rep coaching. • Time Estimate: 2 weeks for the trial + 3 days for analysis. • Pitfall: Avoid choosing a tool based solely on price; if reps find it clunky, adoption will fail regardless of cost. • Definition of Done: A formal 'Decision Memo' comparing the two tools across adoption %, average reply rate lift (aim for >15% improvement), and integration stability.

  2. 02

    Centralize billing and user access

    Once a winner is selected, move all individual 'shadow IT' licenses to a centralized corporate account. Contact the vendor's sales team to negotiate a team-based contract rather than paying 'prosumer' rates on individual credit cards. • Access the 'Admin' or 'Billing' panel of the chosen tool. • In the 'User Management' section, bulk-invite your entire revenue team (SDRs, AEs, and CSMs) using their work emails. • Navigate to 'Settings' > 'Integrations' and perform a Global OAuth sync with your email provider (Google Workspace or Microsoft 365) to ensure all outgoing data is logged. • Set up 'SAML/SSO' if your company uses Okta or Azure AD to streamline logins and improve security. • Owners: Finance/Procurement and RevOps. • Time Estimate: 3-5 hours of admin work. • Pitfall: Forgetting to cancel the original individual subscriptions, leading to double-billing. • Definition of Done: All reps are logged in via SSO, and a single invoice is being paid by the company.

  3. 03

    Build the Enablement-owned prompt library

    The Sales Enablement Manager must now curate a 'Golden Library' of 5-10 prompts or templates for each buyer persona (e.g., 'The CTO', 'The VPC of Operations'). This prevents 'blank page syndrome' and ensures brand consistency. • Use the tool's 'Library' or 'Snippet' function to save these prompts. • Example Prompt: 'Rewrite this email for a busy VP of Sales. Focus on the pain point of [Variable: CRM Data Decay]. Keep it under 75 words and use a soft call to action.' • Include variables like {{first_name}} and {{recent_linkedin_post}} to ensure the AI has specific data points to anchor on. • Version control these by adding a suffix like '_v1.0_2024' so you can track which iterations perform best over time. • Owners: Sales Enablement. • Time Estimate: 8-10 hours of copywriting and testing. • Pitfall: Creating generic 'spammy' prompts that ignore the unique value prop of your product. • Definition of Done: A library of at least 20 vetted prompts is visible to all reps within the tool's interface.

  4. 04

    Conduct a team-wide 'Usage Clinic'

    Host a mandatory 60-minute 'Clinic' to show reps how to use the AI assistant without losing their 'human' voice. Moving to Level 2 maturity means moving away from 'copy-paste' and toward 'AI-assisted editing'. • Demonstrate 'The 3-Minute Rule': Reps should spend 2 minutes researching and 1 minute letting the AI draft/polish. • Show them how to use the meeting assistant feature (e.g., if using Copilot or Otter) to summarize discovery calls into 'Pain', 'Current State', and 'Next Steps'. • Provide a 'Prompts Cheat Sheet' PDF that they can pin to their desktop. • Owners: Sales Enablement. • Time Estimate: 1 hour for the session + 2 hours for material prep. • Pitfall: Focusing too much on tool buttons and not enough on the 'why' (e.g., getting more meetings with less effort). • Definition of Done: 100% of the team has attended the training and successfully sent at least 5 AI-assisted emails in a live 'Power Hour'.

  5. 05

    Establish a weekly adoption review cadence

    RevOps must build a dashboard to ensure the investment is paying off. You need to verify that the tool isn't just being 'used', but is actually driving revenue. • In your CRM or the tool's analytics pane, track 'Tool AU' (Active Users in the last 7 days). • Create a comparison report: 'AI-Assisted Sequences' vs. 'Manual Sequences'. • Look at 'Reply Rate' and 'Meeting Booked Rate'. • Every Friday, post the 'Top 3 AI Prompts of the Week' in Slack to encourage peer-to-peer learning. • If adoption drops below 70%, schedule 1-on-1 sessions with laggards to identify friction points. • Owners: RevOps and Sales Managers. • Time Estimate: 1 hour weekly for review. • Pitfall: Ignoring the quality of replies. If you get 10% more replies but they are all 'unsubscribe', the AI is harming your brand. • Definition of Done: A recurring weekly report sent to the VP of Sales showing adoption % and the delta in bookings between AI users and non-users.

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.