Projects, rollups, and one place to look.

Projects are workspaces

A project (you'll see it as an "app" in plans) is one product, brand, or site: its own widget, inbox, knowledge base, CRM pipeline, automations, and team permissions. Everything customer-facing is scoped to a project.

HQ — the account rollup

HQ sits above projects and answers "where do I go first?" It aggregates signals across every workspace: open conversations, support pressure, pipeline stalls, and the top recommended action per project. If you run one project, HQ is quiet; if you run five, it's the difference between an operation and a tab farm.

Overview — the daily picture

Each project's Overview shows the current focus, the evidence behind it, and the top recommended actions. It's the page you open at the start of the day instead of checking four inboxes and a spreadsheet.

Work — the follow-through

Recommendations only matter if they ship. Work is the execution lane: initiatives, drafts ready for review, and the approve/edit/dismiss loop. Things enter Work from conversations, stalled deals, and knowledge gaps — and leave shipped.

Using the layers well

• HQ for prioritization — pick the project; don't context-switch by mood.
• Overview for clarity — one screen: focus, evidence, next actions.
• Work for follow-through — approve drafts, don't write from scratch.

Permissions across layers

Team members get per-project access (support, sales, knowledge, settings areas). HQ visibility is an account-level view — founders and operators see the rollup; specialists see their workspaces.