Projects are strategist engagements — the top-level container for a piece of brand work. A project scopes everything that belongs to one engagement: discovery answers, sources and findings, insights, decisions, and the deliverables you hand off. Use Projects when you run structured brand work for yourself or a client, rather than one-off generations.
Open Projects from the sidebar, or go directly to /projects. Projects are part of the paid spine (Founder, Strategist, Agency); on Free you'll see an upgrade screen.
A strategy project (here) scopes discovery, sources, insights, decisions, and deliverables. Halo Chat's Start Project is a separate content-brief flow that hands a prompt off to a Halo Studio tool. They are different features.
What a project holds
Capture the brief and starting context for the engagement so workshops and sources have a shared foundation.
Evidence you add (notes, URLs, documents, competitor and audience inputs) is auto-linked to the project's evidence folder.
Synthesize findings into insights, then record the formal decisions that fuel Brand Intelligence.
Build client-facing outputs (presentations, positioning and messaging frameworks) and publish them for review.
How to run a project
On /projects, create a project and pick a type (for example brand foundation or rebrand). Set its status and phase, and optionally link a client workspace for portal sharing.
Open the project to move through Discovery → Sources → Insights → Decisions → Deliverables in one place. Evidence you add here links to this engagement automatically.
Approved decisions become the active context Halo Chat, Halo Studio, and Review read. See Brand Intelligence for how active context works.
Send deliverables to the linked client workspace so reviewers can comment in /portal, then finalize outcomes in Review Center.
Create a project before you start adding sources. When engagements exist, the Sources page asks you to pick one, and Eklipsa keeps each engagement's evidence cleanly separated.