Product overview

One operator system, multiple entry points.

HAL is designed so teams can start where they feel the pain first, then grow into the full operator model as more context flows into the system.

What the product looks like

The UI is organized around one decision path.

Account-level HQ sets attention order. Project Overview explains what matters now. Work, Inbox, and CRM give each lane a focused execution surface.

Account

HQ

Cross-project attention order, risks, and founder brief.

Project

Overview

One active focus lane with a clear why-now explanation.

Execution

Work

Approved actions, initiatives, and prepared drafts.

Signals

Inbox + CRM

Support and sales evidence keep the loop grounded.

Adopt HAL one capability at a time

Module-level pages still matter.

Some buyers will enter through a specific capability. HAL still supports that. These pages explain the modules in their own right while showing how they fit the bigger operator model.

  • Inbox for conversation handling and customer signal capture
  • CRM Pipeline for founder-led sales workflow
  • Knowledge Base for grounding AI and self-serve support
  • Help Articles for public support content
  • Statistics for operational visibility
Next steps

See the product through your team’s lens.

Jump into use cases if you want an outcome-first view, or go deeper into the docs if you want to understand the product model and setup details.