BUILD WEEK REVIEWER GUIDE

Test the product, not a slide deck.

The public demo is open, resettable, and filled only with fictional European sample data. This guide separates working features from deliberate Build Week boundaries.

FAST PATH7–10 minutes

No account. No card. No setup for the web path.

RECOMMENDED TEST PATH
01

Experience one day

Open Day 18, complete the current move, save an energy score, add a fictional journal note, and ask the GPT‑5.6 coach a question.

Participant journey
02

Inspect team support

Open Team Studio. Compare progress and support signals, then verify that journal and coach text never appear.

Team Studio
03

Preview tailored content

Review Days 1–3 for a manager promoted inside the same company and city, including original illustrations and external learning resources.

First three days
04

Reset safely

Use Reset demo in the participant view. Only fictional demo records are restored; no external account is changed.

01
REAL PARTICIPANT SUBSCRIPTION

Start a personal journey in Telegram

Open the First 90 bot ↗

  1. Open the bot privately and tap Start or send /start.
  2. Answer six short questions: name, role, company context, city context, European city, and work mode.
  3. Early access accepts People Manager as the role.
  4. Receive the first tailored Day 1 focus immediately.
  5. Try /today, /mood 4, /pause, and a plain-text private journal note.
02
TELEGRAM GROUP MODE

Add the bot to a reviewer admin chat

Create or open a Telegram test group, add the First 90 bot, then send these commands. Group mode exposes only fictional aggregate demo information and content previews.

/adminCapabilities and live links/metricsAggregate journey health/rolesContent-ready role and contexts/preview 1Day 1 tailored capsule preview/preview 2Day 2 tailored capsule preview/preview 3Day 3 tailored capsule preview/privacyVisible and private data boundary

Plain text sent in a group is never stored as a participant journal entry. Personal onboarding must happen in a private bot chat.

03
ADMIN EXPERIENCE

What works in Team Studio

TEST NOW
  • Aggregate participant and activity metrics
  • Energy trend and support-risk labels
  • Progress by 30-day phase
  • Fictional participant table
  • Service status and content coverage
  • Separate operational admin guide
PRIVACY CHECK
  • No journal answers
  • No GPT‑5.6 questions or answers
  • No raw Telegram messages
  • No employee ranking
  • No automated employment decisions
  • No billing data

The Build Week Studio is read-only. Content stays reviewable and versioned in the public repository.

04
CONTENT-READY SCOPE

One role, complete depth

People Manager is the content-ready role in this release: 90 days and 270 universal touchpoints. Personalization supports same or new company, same or new city, and office, hybrid, or remote work.

Days 1–3 also have enhanced content for an internal manager staying in the same city. Sixteen seeded European cities provide valid IANA time zones for delivery.

Additional roles are a content-expansion track, not simulated coverage.

05
HONEST DEMO BOUNDARIES

What is deliberately not in Phase 1

  • No payment gateway: early access is free; secure hosted checkout belongs to Phase 2.
  • No self-service content editor: Build Week content is versioned in code and Studio is read-only.
  • The public web participant is fictional and resettable; a personal Telegram subscription stays in Telegram.
  • Without an OpenAI API key, the coach uses a clearly labeled deterministic fallback.
  • Only People Manager has a complete reviewed journey today.

Start with the real journey.

Then inspect the team view and privacy boundary.

Open participant demo ↗