By the end of this install you have two things on the table: a one-page rollout plan your company can act on this quarter — business case, seat count, governance answers already filled in — and, if you have the authority or the seats already exist, a live shared workspace where your first team deliverable runs on real data. This is the install where the Two-Lane Rule resolves: everything you've been running scrubbed and pasted in Lane A moves onto a company workspace with contractual no-training, and the workarounds retire.
Every scrubbing step, every manual paste, every "I can't connect that" from Installs 1–8 was you collecting evidence. Today you spend it.
Prerequisites
- Working components from earlier installs — at minimum your voice skill (1), one running workflow (2 or 7), and ideally a team skill (8). These are your receipts.
- Your hours-back number from Install 5, if you measured it.
- A rough list of who would get a seat (start with 5–8 people, not the whole org).
- 15 minutes.
Build steps
-
Write the business case from your receipts. Not a memo about AI — a memo about hours and risk. Paste this, filled in:
Draft a one-page business case for moving our team onto Claude Team [or Enterprise]. Audience: [my manager / IT / finance]. Inputs: hours I now save weekly from workflows I built myself: [X hours]; the recurring deliverables I would move to a shared workspace: [weekly report, meeting follow-ups, SOP skills — list yours]; pilot group size: [N seats]; current risk: team members are already using personal AI accounts with no contractual data protection. Structure: the problem (shadow AI use + hours lost to manual work), the fix (a company workspace where data is contractually never used for training), cost [seats × list price], payback in hours at [average loaded hourly cost], and the two governance guarantees IT will ask about first. Under 400 words. No hype — this reader deletes hype. -
Answer the governance questions before anyone asks them. This is what separates your pitch from every "can we get AI?" request IT has already declined. Work through the governance checklist (second download below) — training terms, data retention, access control, offboarding, connector policy, incident path — and paste your answers into the plan. Arriving with this filled in is the whole trick: you're not asking IT for permission, you're handing them a completed review.
-
Choose the plan. Team covers most cases: contractual no-training, shared Projects, central billing. Choose Enterprise when IT requires SSO, domain capture, audit logs, or compliance certifications — put the question to them exactly that way and let their answer pick the tier.
-
Stand up the workspace — one shared Project per recurring deliverable. This is the structural decision that makes the workspace useful instead of an empty chat room. Create the workspace, invite the pilot group, then create your first shared Project: the weekly report from Install 7. Set its Project instructions with this:
This Project produces our weekly [board/team] report. Its knowledge contains the Report Spec, our report format, and writing-voice notes. Anyone in this Project may generate the weekly draft using the saved reporting prompt. Rules: numbers come only from connected sources or pasted data — never estimated; write [MISSING: name] where data is absent; every draft is reviewed by [owner] before it is sent. If someone asks to change the format itself, do not change it — direct them to [owner].Repeat the pattern: one Project per deliverable — the report, the SOP skill from Install 8, meeting follow-ups. Deliverables get Projects; ad-hoc questions stay in personal chats.
-
Standardize the outputs, leave the working styles loose. Standardize: report formats, SOP skills, Project instructions, the never-paste list, connector policy. Leave loose: how individuals prompt, draft, and explore. Teams adopt tools that make their output consistent and their process free — mandate the second half and adoption dies.
-
Migrate the work lane, then retire the workarounds. Move each Lane A workaround to its full version: the Reporting Machine's paste step becomes a live connector; the SOP skill's anonymized examples become real ones — inside the workspace only. Your personal Claude stays exactly as Install 0 configured it: personal calendar, personal email, training off. The lanes don't merge; the work lane finally gets its own road.
The Two-Lane note
Lane A (you don't control the budget): the plan is the component. You leave this install with the business case and the completed governance checklist — a proposal someone with a budget can approve without further homework. Until it's approved, keep running the Lane A variants from Installs 1–8 exactly as built: scrubbed, pasted, personal-data-only. Lane discipline holds until the day the workspace exists; it is never the thing you relax to save time.
Lane B (workspace exists or you can create it): skip the pitch and run steps 3–6 today. Your job shifts from advocate to administrator: pilot group in, first two shared Projects live, and a 30-day check where each pilot member names one deliverable they've moved in — the plan template below includes it.
Component shipped
You now have a rollout plan with the governance homework already done, and — on Lane B — a shared workspace with your first team deliverable running in it. Tomorrow morning: send the one-pager to the person who owns the budget, or send the pilot group their invite links.