Archbee onboarding

Archbee sends 7 emails across 6 days, beginning with a welcome email on day 0 and continuing with one email on each following day. That steady rhythm makes the sequence feel like a guided course rather than a set of unrelated product announcements.

The opening email, “Welcome to Archbee (we promise not to document your every move)!”, frames the series as a “Your 7-Day Learning Journey Starts Now”. It asks the reader to log in and explore, then the next emails turn that invitation into specific actions: create a Space, try collaborative documentation, assign a reviewer, connect a repository, use Ask AI, and manage documentation at scale.

The Multiplayer email and the Review System email use the exact same subject, “Time to document like it’s a group project due tomorrow.”, and the exact same preview text, “Day #3 Real-Time Collaboration with Multiplayer Mode”. The earlier email teaches real-time editing, presence indicators, and inline comments. The next email shifts to assigning a reviewer, even though its subject and preview still point to the previous lesson.

That reuse creates a recognizable editorial pattern: keep a memorable hook while changing the action inside the email. It also makes the preview text a weak guide to the second lesson. If you repeat a label, update the supporting copy or make the shared hook intentionally broad enough to fit both messages.

The content follows a clear progression. The welcome email introduces the journey; the Spaces email covers organizing, publishing, and custom branding; the Multiplayer and Review emails move into team workflows. The Docs as Code email then asks readers to connect GitHub or GitLab for version control, followed by an Ask AI feature tip about answering questions and reducing scrolling. The final onboarding email brings the story to variables, snippets, and portals for managing large documentation systems.

Every email is personalized and has one call to action, which keeps each lesson focused on a single next step. The Multiplayer email is the only plain-text message, giving the collaboration lesson a more direct conversational treatment. The Docs as Code, Ask AI, and final scaling emails use blue, creating a visual shift for the later feature-focused part of the journey. A reusable pattern is to teach one product job per email, move from basic setup to advanced operations, and attach one concrete action to every lesson.