Logline
A five-episode build-in-public arc. Professor High reveals one piece of an upcoming Phase 2 app feature each week — the problem, the data, the hard choice, the sneak preview, and finally an open beta. By the time we ship, the audience has already met the feature.Concept
Most product launches are a single press release dropped into a void. This arc treats product development like a serialized show. Each week of the arc Professor High pulls back one layer of an upcoming Phase 2 feature: what was broken in Phase 1, what the user research said, the architectural tradeoff we wrestled with, a working sneak preview, and finally an open beta CTA. Why serialize a launch instead of dropping it: a one-shot launch gets one swing at attention. A five-week arc gets five. Each episode hands the audience a reason to feel like an insider — they saw the problem before the solution, they saw the tradeoff before the answer. By episode 5, the people who watched the arc are not “users we acquired.” They are “users we onboarded over five weeks.” That difference shows up in retention. A season versus a one-off: a one-off feature post is marketing. A season is a story about how the product is made, with the feature as the payoff. The arc only runs when there is a real Phase 2 to reveal. We do not fake it.Why It Works
Audience hook
The audience feels like insiders. They watch the feature get built, not advertised.
Brand fit
Professor High is a researcher. Showing the research is on-character. Showing tradeoffs is on-character. This arc is just his voice applied to product.
Serialized payoff
Pre-launch demand is built, not bought. By episode 5 the beta waitlist is full of people who already understand what they are signing up for.
Arc Structure
| # | Working Title | Brief |
|---|---|---|
| 1 | The Problem | Honest episode about what was not working in Phase 1. A specific user complaint, a specific gap in the experience, a specific thing the team kept getting wrong. No spin. By being candid about the problem, the arc earns the right to talk about the solution. Ends on the question: what would we have to build to fix this? |
| 2 | What the Data Said | The research episode. What did user interviews say. What did the database show. What surprised the team. Show the actual numbers — sessions per week, drop-off points, the percentage of users who never made it to the feature that mattered most. Data first, conclusions second. |
| 3 | The Hard Choice | The tradeoff episode. Every product decision is a tradeoff and most teams hide that. We show ours. The architectural choice we made, what we gave up to make it, why the alternative would have been worse. This episode builds trust more than any other in the arc. |
| 4 | First Look | The sneak preview. Working feature, real screen recordings, Professor High walking through the flow. Not a polished demo — a working build. The audience sees what they are about to get. Ends with: “Beta opens in seven days.” |
| 5 | Open Beta | The launch. Beta access opens. First 1000 users get in. Cross-platform coordinated drop. The arc closes with a thank-you to the audience who watched the build. |
Format Per Episode
- Runtime: TikTok 30-45s teasers per episode. Instagram carousel with screenshots and quotes from the data. YouTube long-form walkthrough at episode 4. X thread on the launch day for episode 5.
- Beats: Cold open referencing the previous episode’s reveal (5s) -> the new layer (30s) -> what it means for the user (15s) -> next-reveal date stamp (5s).
- Reused elements: The “Phase 2 Reveal” lower-third badge. A consistent screen-recording frame and color treatment. The “Next reveal: [date]” outro card. Founder or PM cameo possible in episodes 2 and 3.
Platforms
| Platform | Role | Notes |
|---|---|---|
| TikTok | Primary | Weekly 30-45s teasers. The home of the arc. |
| Companion | Carousels per episode with screenshots and data charts. Saves and DMs are the leading indicator. | |
| YouTube | Showcase | Episode 4 walkthrough lives here as the long-form anchor. |
| X | Launch | Episode 5 launch thread. Threads are how product launches still travel on X. |
| Web | CTA | A single landing page for beta signup, updated every episode with a fresh teaser. |
Cadence
Five-week arc. Run twice per year, only when there is a real Phase 2 milestone to reveal. Never on a fake timeline. The credibility of the arc depends on the beta actually opening on episode 5.Production Notes
- Recurring Phase 2 Reveal branding in the lower-third of every episode. Same color treatment across the arc.
- All screenshots from the actual product. No mockups. Mockups are obvious and they break trust.
- Founder or PM cameo possible for episodes 2 (data) and 3 (tradeoff). Their voice on tradeoffs lands harder than Professor High’s.
- Every episode ends with a hard date stamp: “Next reveal: [date].” The audience learns to expect the next drop.
- Beta signup link in bio across all platforms from episode 1. Conversion compounds across the arc.
Hashtags & Discovery
#buildinpublic #cannabisapp #highiq #thisiswhyimhigh #productdesign #cannabistech
Pin a fixed hashtag for the arc (e.g., #Phase2Reveal) so the audience can binge the run after launch.
Success Metrics
- Beta waitlist signups per episode: Each episode should add measurable signups. Episode 4 (the sneak preview) should be the biggest spike before launch.
- Episode-over-episode retention: Episode 5 views should equal or exceed episode 1. If not, the arc lost the audience somewhere in the middle.
- Beta activation rate: Of the first 1000 beta users, what percentage activated in week 1. Above 60% means the arc set expectations correctly.
- Comment quality: Look for “I have been waiting for this” and “this fixes my exact problem” — those are the arc working as intended.
Pillar
Primary: Product & App Features. Secondary: Community & Engagement.Status
concept
Related
Scan This
The recurring product-feature show. Phase 2 Reveal is the launch arc that feeds it.
The TIWIH Label
Another product-pillar show. Pairs naturally with reveal arcs.