Day one AI setup for new hires (L1)

Every new revenue hire leaves week one with the sanctioned assistant provisioned, the notetaker joined to their calendar, the prompt library bookmarked, and the acceptable use rules signed. Adoption is an onboarding problem before it is a change management problem.

WORKFLOW1Add AI to the provisionin… checklistNotion2Teach three jobs, not the…toolLoom3Sign the acceptable use o…e pagerManual4Check at day thirtySlack
4 steps, in order, with the tool that owns each one.
Adoption ladderSix levels from Starter to Rebuilt. This item sits at level 1.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 L1 Starter. Running it above your level is how pilots stall.
Measures of success% new hires provisioned in week one; day 30 active usage; time to first AI assisted deliverablePROVE IT WORKED% new hires provisioned in week oneday 30 active usagetime to first AI assisted deliverable

The steps

  1. 01

    Add AI to the provisioning checklist

    Tool: Notion

    The assistant licence, the notetaker, and the prompt library go on the same IT checklist as email and CRM. If it is requested later, it is requested never. Owner: enablement plus IT. DoD: three AI items appear on the standard provisioning list.

  2. 02

    Teach three jobs, not the tool

    Tool: Loom

    Cover exactly three jobs a new rep does weekly: account research, call recap, follow up email. Tool tours teach nothing. Job walkthroughs stick. Owner: enablement. DoD: three short recordings exist and are linked in onboarding.

  3. 03

    Sign the acceptable use one pager

    Tool: Manual

    What may be pasted, what may not, which tools are sanctioned, who to ask. One page, signed in week one, not a policy PDF nobody opens. Pitfall: a legal document instead of a usable rule sheet. DoD: signed page stored with onboarding records.

  4. 04

    Check at day thirty

    Tool: Slack

    At day thirty, verify actual usage rather than asking how it is going. If a new hire has not used the assistant in the last week, that is an enablement miss to fix now. Owner: hiring manager. DoD: day thirty usage check recorded for every new hire.

Tools in this playbook

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.