Knowledge Hub

The HQ Knowledge Hub

Plain-English guides to HQ, from your first install to rolling it out across your whole team.

On this page

How HQ Works

How to Structure HQ as a Solo Operator

5 min read Updated Nov 2026

One person running a business, or a few of them, with nobody else in their HQ yet. The setup that fits one person, in the order you'd do it.

Give each business its own company#

The first decision is how many companies to make, and the answer is one per business. If you run two brands, or you do client work, each one gets its own company with /newcompany, and HQ keeps them apart. A company holds everything that belongs to that business, which is its documents, its projects, its rules, its credentials and its connected apps.

Your personal space is the other place things can live. It holds what follows you across businesses, which is your preferences, your standing rules, private notes and the helpers you use everywhere. It isn't a catch-all, so if a file is about the business, it goes in the business.

When you're unsure whether something needs a new company, look at the audience. New people or a new business means a new company, and new work for the same business means a new project inside the company you already have. The wall matters even when you're alone, because a company syncs to its own storage as a whole and a key saved in one company is used only inside it. Keep that boundary clean now and it holds when you add a teammate or a client later. If you run several brands under one parent, Setting Up HQ for Multiple Brands covers the two ways to lay that out.

Know the five folders inside a company#

Every company has the same set of folders. These five are the ones you'll use, and each one has one job.

  • knowledge/ is what the business knows, such as the brand guide, the pricing sheet, call notes and customer research.
  • projects/ is the work in flight, with its plans, deliverables and decisions.
  • policies/ is the standing rules HQ follows for this business.
  • skills/ is the processes you've saved so you can run them again.
  • workers/ is where specialist setups and their routing live, and you won't need it on day one.

You don't have to do the filing yourself. Describe what you're saving and HQ puts it in the right folder, and when you need it back you ask for it by what it is ("the pricing sheet", "the skill that turns videos into clips") rather than by where you think it lives. That's also why the folder tree can stay shallow. More on how these pieces fit in Companies, Projects, and Repos.

Bring in the documents you already have#

Your business already has a memory. It lives in a Drive folder, a Notion workspace, a stack of local documents and a repo or two. Tell HQ where each of those lives and which company it belongs to, and let HQ bring the documents in and file them. Don't wait for a cleanup project first, because HQ can organize as it goes.

Then test it with a real question, something like "what did we quote the last client for a rebrand?" If the answer comes back right, the import worked. If it doesn't, you've found the first thing to fix, and the section on misses below covers how.

Connect the tools where the work happens#

Documents aren't enough when the current numbers live in your store, your billing tool or your CRM. Two commands cover this. /hq-secrets stores an API key once, encrypted, and your tools use it when they run without showing it back in chat. /hq-integrations connects apps through a hosted MCP server or an API key, Slack and Google Calendar and a CRM among them, so HQ reads live data instead of a copy you pasted last month. Secrets vs. Integrations explains which one a given tool needs.

Close every session so the work sticks#

The working files inside a session are disposable, so anything you want to keep has to be moved somewhere durable before you close. Four commands do that. /handoff at the end of a session saves where you were so the next session picks up from there. /checkpoint saves the same thing partway through long work. /learn turns a correction you just made into a standing rule, and /journal keeps a note of what you found out. There's more on this rhythm in Sessions and Handoffs.

Keep the structure light, and fix misses as they come#

Once the pieces above are in place, resist the urge to build more. Deep trees and naming debates are work that doesn't improve how well HQ finds things, and there's almost no sunk cost in structure anyway.

When a search misses, you ask HQ to audit why. It checks whether the file is in the right company, whether it's indexed and whether the document itself is any good, then it moves or renames what matters and you ask the question again. The answer you get back is the test, not how the folders look, and a fix takes a few minutes rather than an afternoon.

Skip the team features until there's a team#

Skip groups and per-path access grants. You're the only person, so you can already see everything. Skip workers until there's a process you run more than once a week.

When the first teammate arrives, add them to the company and decide whether everyone sees the whole vault or you grant access by group. Their AI tools inherit their access, so if they can't see a file, HQ can't find it for them. That's an access problem, not a filing problem, and the fix is a grant, not a move. Permissions in HQ walks through the options.

Your first session#

  1. Create one company per business with /newcompany.
  2. Tell HQ the three or four places your business's documents live, and which company each belongs to.
  3. Store the keys you use most with /hq-secrets, and connect one app with /hq-integrations.
  4. Ask one real question and fix whatever it exposes.
  5. End the session with /handoff.