Getting started
Use HQ & workspaces, operator loop, operating context, and widget setup to get the product aligned with the way your business actually runs.
Docs
Documentation for the operator product, not just the widget.
HAL connects HQ, project Overview, Work, support, CRM, knowledge, API, and hosted HTTP MCP into one operating system for small teams. Start with the concepts, then move into setup.
Start here
The fastest path is to understand the product model first, then configure the surfaces you need. HAL is strongest when support, sales, and Work share context instead of living in separate tools.
HQ & workspaces
See how account HQ, project Overview, and Work fit together.
Operator loop
Understand focus lanes, recommendation runs, approvals, and feedback.
Operating context
Set goals, motion, constraints, and the metric HAL should optimize around.
Widget
Install the customer-facing widget and connect inbound signals.
CRM
Manage pipeline, company context, and founder-led sales activity.
MCP
Connect external AI clients through HAL's hosted HTTP MCP endpoint.
Documentation map
Product areas
Support, help center, CRM, knowledge base, team setup, and approvals all work better when they share the same context and feedback loop.
Platform access
Use the REST API for integration and the hosted MCP endpoint for AI clients that should read or act through HAL.
Current product boundaries
Approval-gated AI
The Manager recommends, drafts, and organizes work. It does not autonomously execute external actions without approval.
HTTP MCP only
HAL exposes a hosted HTTP MCP endpoint. There is no local stdio transport to install and run on your machine.
No customer revenue ingestion
HAL does not yet ingest Stripe or other customer finance data as a live business signal.
Next step
Set up the operator model before you optimize the details.
Start with HQ, Overview, Work, and operating context. Then connect the widget, CRM, and API surfaces that feed the loop.