01
Northstar
- Context
- Access
- Projects
- History
Isolated client HQ
ProductsUse case · HQ for agencies
Give every client their own AI operating system.
Keep every client's context, credentials, projects, and history separate - while your agency reuses the methods that make delivery excellent.
Start free. Build one client workspace. Invite your team when it is ready.
Your agencyShared methods
02
Fieldwork
- Context
- Access
- Projects
- History
Isolated client HQ
03
Common Ground
- Context
- Access
- Projects
- History
Isolated client HQ
Reuse the method. Never mix the client.
One agency system
Every client in its own lane
Every project keeps its memory
The agency AI trap
Individual leverage becomes organizational debt.
The visible problem is slow onboarding. The deeper problem is that the agency does not own the system producing its work.
The method lives with one person.
Your strongest operator becomes the prompt library, quality gate, and help desk for every account.
The client truth is everywhere.
Drive, Slack, task tools, calls, decks, local files, and chats each hold a different part of the account.
Every handoff starts from zero.
A new teammate inherits files and meetings, not the decisions, corrections, and working history behind them.
Access moves through DMs.
API keys and tool setup get copied around because the workflow cannot travel without the credential.
The operating model
Build the agency once. Run it for every client.
HQ separates what should stay private to the client from what should compound across your agency.
- 01Agency owner
Create an isolated client HQ
Give each client a deliberate boundary for knowledge, projects, people, agents, and access.
- 02Account lead
Add the client truth once
Bring in the approved brand, product, customer, history, goals, examples, and decisions.
- 03Operations / IT
Connect approved systems
Let authorized people and agents use APIs, MCPs, data, and tools without pasting keys into chats.
- 04Functional expert
Install the agency method
Reuse the skills and specialist workers that encode how your agency does its best work.
- 05Team + agents
Build the work together
Teammates and agents contribute to the same project, whether the result is a deck, report, brief, portal, or plan.
- 06The client HQ
Keep every correction
Feedback, decisions, deliverables, and open loops stay with the project for the next person and the next run.
The boundary
Reuse the method. Never mix the client.
Your agency's strategy, reporting, research, and production methods can travel. Client knowledge, credentials, project history, and outputs stay where they belong.
Shared agency layerSkills · Workers · Quality gates
Client 01Northstar
Context · Access · Projects · History
IsolatedClient 02Fieldwork
Context · Access · Projects · History
IsolatedClient 03Common Ground
Context · Access · Projects · History
IsolatedBeyond a shared chat
AI can make the output. HQ gives the work a home.
What mattersNative AI sessionAgency running on HQ
Context
Lives in the current chat and operator
Belongs to the isolated client HQ
Method
Copied between prompt docs and accounts
Maintained once as a shared agency capability
Access
Local setup or credentials passed by hand
Granted to authorized people and agents
Collaboration
Separate outputs merged by a project owner
One project resumed by teammates and agents
Handoff
Reconstruct the decisions behind the files
History, feedback, artifacts, and open loops persist
Multiplayer deliverables
The whole team builds from the same client truth.
Strategy deck
Shared sources · prior decisions · review history
Weekly report
Shared sources · prior decisions · review history
Creative brief
Shared sources · prior decisions · review history
Client portal
Shared sources · prior decisions · review history
Already happening
Goodo Studios × HQOne giant prompt document became a system the studio shares.
Goodo Studios moved its AI work into a centralized HQ system with isolated per-brand workspaces. Teammates inherit the setup, reuse workflows, resume projects, and build tools from shared context - without putting every brand in the same lane.
Read the Goodo Studios storyBefore HQOne doc of prompts, copied by hand
With HQWhole studio, isolated per brand
What compounds
Scale the system, not the context chase.
- 01
Onboard a client into a working system, not an empty folder tree.
- 02
Bring a teammate into the client's history without a chain of catch-up calls.
- 03
Reuse the agency method while keeping every client's inputs and outputs separate.
- 04
Collaborate on reports, decks, briefs, portals, and plans from one durable project state.
- 05
Let authorized teammates and agents use connected tools without passing raw keys around.
- 06
Improve the system once and make the improvement available across the team.
Your first win
One client. One shared skill. Two teammates working from the same system.
You do not need to migrate the whole agency. Start with one client workflow and prove that the context, method, and output can move between people without starting over.
Create your first client HQ- 1
Create one client workspace.
- 2
Add one canonical client context file.
- 3
Create or install one agency skill.
- 4
Invite a second teammate.
- 5
Use the shared skill to save one reviewable client output.
Control stays visible
Built for client trust, not black-box automation.
Separated clients
Each client has a deliberate company and workspace boundary.
Governed access
Tools and secrets are deliberately connected and granted.
Bounded agents
Agents have known jobs, inputs, outputs, permissions, and history.
Human review
Important client work remains reviewable before it leaves the system.
Start with one client
Client context should outlast every chat, tool, and handoff.
Give the work a home your agency owns - and give every teammate a better place to start.