The Revenue AI Report

Claude for Work shared projects (L2)

A whole team standardizes on Claude for Work (Projects + shared knowledge). PM, design, and eng all chat to the same context, product specs, design docs, codebase snippets, instead of copy-pasting into 5 different chats.

WORKFLOW1Buy Claude for Work seatsClaude for Work2Create 3 anchor ProjectsClaude Projects3Weekly Project hygieneManual4Roll to next squad after … weeksManual
4 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 success# of shared Projects in use; hours saved per IC per week; % of cross-functional docs that originated in ClaudePROVE IT WORKED# of shared Projects in usehours saved per IC per week% of cross-functional docs that originated inClaude

The steps

  1. 01

    Buy Claude for Work seats

    Tool: Claude for Work

    Start with one squad (PM + design + 4 engineers). Claude Team is $30/user/month for Projects, shared knowledge base (up to 200K tokens per Project), and SSO. Get billing through finance, not personal cards, you want centralized audit and offboarding. Owner: Ops + first squad lead. Pitfall: letting people keep using personal Claude accounts, context fragments, IP risk. DoD: 1 squad fully on Claude for Work with SSO.

  2. 02

    Create 3 anchor Projects

    Tool: Claude Projects

    For the pilot squad, create exactly 3 shared Projects: 1) "Product spec drafting", knowledge: PRD template, brand voice, customer-interview transcripts. 2) "Engineering, current sprint", knowledge: relevant code files, architecture doc, recent PR descriptions. 3) "Customer support triage", knowledge: docs site, escalation playbook, last 30 days of tickets. Each Project has a 1-paragraph system prompt about its purpose and tone. Owner: squad lead. Time: 1 day to set up. Pitfall: creating 20 Projects on day 1, nobody knows which one to use. DoD: every squad member has used all 3 Projects in their first week.

  3. 03

    Weekly Project hygiene

    Tool: Manual

    Every Friday, the squad lead spends 20 minutes: archive Projects that haven't been touched in 2 weeks, refresh the knowledge base of active Projects (delete stale specs, add new docs). Without hygiene, Projects fill with garbage and people abandon them. Owner: squad lead. DoD: each active Project has a knowledge-last-updated date <14 days old.

  4. 04

    Roll to next squad after 4 weeks

    Tool: Manual

    Run a 30-min retro with the pilot squad: what Projects became indispensable, which fell flat, what they wish Claude could do. Use that to template the rollout to the next squad, don't copy Projects 1:1, let the new squad design their own with the pattern. DoD: second squad live by week 5, with their own 3 anchor Projects.

Tools in this playbook

  • Claude for Work
  • Claude Projects
  • Manual

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.