Brand OS
Brand OS
The biz-side operating system. Brand Engineering · L1 Lead Gen · L2 Client Acquisition · L2 Client Retention · L2 Referral Engine.
Brand OS
The biz-side operating system. For brands running the 0HR Brand Engine.
01
Intake
Tell us about your business — 29 questions, 10 minutes.
02
Foundation
AI builds your strategy — positioning, offers, and playbook.
03
Components
14 deliverables generated — from landing page to nurture emails.
04
Go Live
Published to your domain. POC reviews, approves, we provision.
What lives here
- Rules — Build rules · process · approval gates · do/don't
- Components — Canonical v18 component taxonomy · 9 components · 3 levels
- Templates — Master Template Library (3x3 v18 LOCKED) · 187+ refs · pattern source for AI gen
- Workflows — Install pipeline · LOFI → HIFI lock · per-component approval
- Brands — Live install state per brand · MCM · DH · etc.
- Canonical — Per-component canonical spec (Brand Engineering · L1 · L2)
Operations
- Business Model — Front-End Acquisition · Back-End Retention
- Email Stack — Resend (warm) · Lemlist (cold) · LOCKED 2026-05-25
- Operator Network / Bounties — operators execute bounties per project / month / %
- Memory Protocol — system_state + session_logs
Productized as
- 0HR Studio — Brand OS delivered as a product (DFY / custom)
Sister OS
- Life OS — the personal operating system
How to read this
Brand OS = specs. The actual brand command center (per-brand state, approvals, live ops) lives in the portal at 0hr.app/{brand} — not here. Two different jobs:
| Brand OS (this docs site) | Brand command center (portal) |
|---|---|
| Spec · canonical · locked content | Per-brand state · approvals · live ops |
| MDX · static · publicly readable | React · auth-gated · Supabase-backed |
| What ALL brands share | What ONE brand is doing right now |
Per project_os_vs_portal_audience · LOCKED 2026-05-24.