Keep project scope clear
Use projects to separate products, initiatives, or business lines that should not share a single focus lane.
Team
Invite the team without losing clarity about who owns what.
HAL is designed for small teams, so team setup should reinforce visibility and follow-through rather than create another layer of process.
Where ownership shows up
- Inbox assignments and support follow-up
- CRM record ownership and pipeline movement
- Approved work and drafts inside Work
Recommended setup
Use HQ for founder visibility
HQ should stay readable even as more teammates start using project-level surfaces.
Review feedback patterns
Edits, dismissals, and completions are signals about how the team actually works.