The Revenue AI Report

GitHub Copilot for everyday autocomplete (L1)

Every engineer gets GitHub Copilot in their IDE. No process, no review board, no shared prompts, just turn it on. The cheapest way to start measuring AI productivity in engineering.

WORKFLOW1Buy seats for the whole t…amGitHub Copilot2Set the floor, not the ce…lingManual3Measure adoption, not out…utGitHub
3 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 successPRs/engineer/week; time-to-first-commit for new hires; % of code suggestions acceptedPROVE IT WORKEDPRs/engineer/weektime-to-first-commit for new hires% of code suggestions accepted

The steps

  1. 01

    Buy seats for the whole team

    Tool: GitHub Copilot

    Don't pilot. At $19/user/month, Copilot Business pays back at <30 min saved per engineer per month. Buy seats for everyone who writes code, including PMs who poke around the codebase. Owner: Eng manager + IT. Time: 1 day for procurement. Pitfall: "pilot with 3 engineers", you'll spend 3 months debating ROI instead of shipping. DoD: every IC has Copilot active in their daily IDE.

  2. 02

    Set the floor, not the ceiling

    Tool: Manual

    Write a 1-page "AI in engineering" doc: (a) Copilot is the team floor, (b) personal use of ChatGPT/Claude is fine for explanations, (c) DO NOT paste customer data or secrets into public chats, (d) reviewer is still responsible for merged code. Owner: CTO or staff eng. Pitfall: writing a 20-page policy nobody reads. Keep it 1 page. DoD: doc is linked from the engineering handbook README.

  3. 03

    Measure adoption, not output

    Tool: GitHub

    Pull the Copilot admin dashboard monthly: active users, suggestion acceptance rate, languages used. Goal in month 1: >80% weekly active. Don't try to measure lines-of-code-per-engineer, it's a vanity metric that incentivizes garbage. Owner: Eng ops. Pitfall: tying performance reviews to Copilot acceptance rate, engineers will accept worse suggestions to game the number. DoD: monthly Copilot adoption report shared in eng all-hands.

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.