Overview

This workflow delivers a complete beta handoff package when Phase 1 development is finished. The client receives one Drive folder with three core artifacts plus a cover email that establishes testing boundaries and next steps.

Before You Start

Phase 1 build is complete per BUILD-CADENCE requirements
Access to Google Drive "99. Claude Code" folder
Live demo deployed on Vercel with password protection
Password stored in 1Password and kickoff doc
All client source materials collected from email threads
Co-founder email for BCC notification

Steps

Create new Drive folder named "<Client> - MVP" and set sharing permissions
Verify live URL format is https://<project>-mvp.vercel.app/ with DEMO_PASSWORD env var middleware
Clone Beta Test Brief template from "99. Claude Code" Drive folder using File → Make a copy
Rename cloned brief to "<Client> — Beta Test Brief — <YYYY-MM-DD>" and move to client folder
Fill in all bracketed placeholders in Beta Test Brief using template schema from assets/beta-test-brief-template.md
Write 15-20 minute recommended demo path with numbered click-by-click steps
Clone Test Tracker Sheet template from "99. Claude Code" Drive folder
Configure four tabs in tracker: Roadmap, Feedback, User testing, Glossary with conditional formatting
Pre-populate User testing tab with all functional workflows set to "Not started" status
Mark blocked workflows as "Skip" with reasons in Notes column
Create "Reference materials" subfolder and move all client-supplied source artifacts
Draft cover email using beta-launch-email-template.md with seven required blocks
Send cover email from build owner with co-founder BCC'd (not CC'd)
Test complete demo path end-to-end to verify all steps work before client access

Quality Check

Client folder contains exactly: Beta Test Brief, Test Tracker Sheet, Reference materials subfolder
Live URL loads with password protection and all functional workflows work end-to-end
Demo path takes 15-20 minutes and never leaves user wondering what to click next
Test Tracker has all four tabs with proper conditional formatting on "Built?" column
Cover email includes all seven blocks: status line, folder pointer, ASK, contents, URL+password, beta definition, client responsibilities
Co-founder received BCC notification without being in reply chain

Common Issues

Password security: Never send demo password in plaintext chat alongside URL - always separate channels
Scattered links: Resist client requests to send individual links via Slack - maintain single folder approach
Demo path testing: If any step in recommended path fails, fix before sending to client to prevent first-impression issues
Template versioning: Always clone from "99. Claude Code" folder templates to ensure latest schema and formatting

Beta Handoff Package Delivery