DREAMTEAM — Build Order

What this is

The working spec is organized by bucket. This doc is organized by what ships when.

The headline inversion: the spec leads with the Presentation Deck (Bucket 1), but we don’t build that first. We build the team hub first — Brain² + the multi-agent orchestrator + the workspace intelligence around them. The deck and pitch intelligence are the second slice. Creative Intelligence (Bucket 4) is cut from this plan — parked, not on the roadmap.

The hub is the thing that makes DREAMTEAM a place a team lives, not a deck tool with extras bolted on. Get the operating layer right, then everything else has a home to plug into.

Phase 1 — The Hub

Goal: make the hub for teams. The cloud that knows your whole brain.

This is most of Bucket 3 (Team Workspace), minus the two pitch-room features (see Phase 2), plus the Reimagined Terminal.

Ships in Phase 1:

Brain² — the tiered memory spine (hot / warm / cold, smart cycling, critical-flag protection, sublinear retrieval). Everything else reads and writes through this.
Multi-Agent Orchestrator + Task Board — the runtime that deploys agents/squads against a kanban board. The project-management system. Board population (human / auto-extracted / agent-proposed), swarm visibility, swarm-sizing recommendation, auto-recognition of completion + board dedupe, efficiency lens, privacy gate.
Conversational Agent Interface — two-way voice. Voice in is solved; this adds voice out + turn-taking so you operate the orchestrator hands-free.
Conversational Chat Layer — Claude-style history sidebar, context-drift detection, no-manual-save running doc, auto-route on close. The warm/cold feed into Brain².
Reimagined Terminal — Nate’s terminal idea, shipped as a wrapped web app. The whole hub operates like a terminal: you work in it and it feels like a cloud that knows your entire brain, with room to tweak. See 2026-05-21-dreamteam-conversational-terminal-and-chat-layer.
Meeting Capture — Granola hook or native fallback. Feeds Brain² and (later) pitch briefings + follow-up decks.
Migration & Onboarding — Notion-first one-click import (pages → Brain², databases → task board, teamspaces → workspace structure). How a team arrives with its structure intact instead of a flat dump.

References for Phase 1: Macro and the way Meridian built their hub. Both are a good basis — start there, then expand on both and go deeper than either.

Experience target: operates like a terminal; feels like a cloud that knows your whole brain. Personal, but tweakable.

Surface: web app first (the wrapped-terminal web app).

Phase 2 — Pitch Intelligence + Presentation Deck (built together)

Once the hub exists, build the pitch layer on top of it. Deck and pitch intelligence ship as one coordinated slice — they share the same source, brand presets, and live engine.

Ships in Phase 2:

Presentation Deck — already basically built (parzvl.com/dual-template, adaptive viewer, brand preset system, template marketplace). The work here is adapting it to be team-edible: multi-tenant brand presets, shared delivery, team ownership — not a single-operator tool.
Pitch Intelligence — the live editing engine (the substrate) plus the three layers riding on it: pre-pitch adaptation (before), voice-reactive extension (during), follow-up deck (after).
Invisible Group Chat — moved here from Bucket 3. The team back-channel during a pitch.
Live Performance Dashboard — moved here from Bucket 3, reframed as pitch intelligence. Live pitch-coach signal (slide timer, talk-time balance, room transcript, pacing flags) rendered into the invisible chat surface.

Both relocated features are pitch-room tools — they only matter when a pitch is happening, so they belong with the pitch slice, not the always-on hub.

Cut — Creative Intelligence

Love-the-Work-More AI (Bucket 4) is out of this plan. Parked, not sequenced. The proprietary creative-data moat is a separate, far-future bet that depends on DREAMTEAM being a working product first — it’s not part of the build roadmap and shouldn’t pull focus from the hub and the pitch layer.

Surface order

Web app — first. The wrapped-terminal web app is the primary surface.
Mobile companion — demand-gated. Ship the web app, then figure out if teams actually want mobile; build a compatible companion (shared data layer) if they do.
Desktop app — after mobile.

(The spec said desktop-first; this supersedes it. The web app is the desktop experience day one, accessed in the browser.)

Delta from the spec

What this build order changes vs. DREAMTEAM-Spec:

Build order inverts the spec — hub (Bucket 3) before deck (Bucket 1).
Bucket 4 Creative Intelligence → cut. Out of the plan entirely, parked as a future bet.
Invisible Group Chat + Live Performance Dashboard → relocated from Bucket 3 (Team Workspace) into Pitch Intelligence (Phase 2).
New: Reimagined Terminal added to Phase 1 as a wrapped web app.
Surface priority: Web → Mobile (if demanded) → Desktop (spec was desktop-first).

Created 2026-05-25.