Teammate
Adds the market brief
ProductsUse case · Multiplayer AI projects
Every AI chat ends. Your project context should not.
Build decks, reports, briefs, research, and working software with people and agents contributing to one durable project memory.
Start free. Create one project another teammate can resume without a rebrief.
The durable projectContext, sources, decisions, history
Shared in HQLaunch planning project
Agent
Builds the analysis
Leader
Reviews and decides
The artifact moves forward. The context behind it stays with the project.
One shared project memory
People and agents can resume
Nothing important is buried in chat
The chat-shaped project
AI makes the first draft faster. Collaboration still starts over.
Teams can generate more artifacts than ever, but the reasoning, source material, corrections, and remaining work are trapped in separate conversations.
The project is split across chats.
Each person holds a different fragment of the brief, research, decisions, and model history in an interface no one else can fully resume.
The final file loses the story.
A deck or report survives, but the evidence, tradeoffs, rejected options, feedback, and open questions behind it disappear.
Handoffs become rebriefs.
A teammate or agent can receive the latest file, yet still needs someone to reconstruct what happened and what should happen next.
Improvements do not compound.
Every new project repeats the same research, setup, framing, and corrections because the working system was never preserved.
The multiplayer project
Make context the shared surface - not the chat window.
HQ keeps the project state durable so the next person or agent can continue the work instead of recreating it.
- 01Project lead
Create the project around an outcome
Define the deliverable, owner, audience, constraints, success criteria, and open questions in one shared project home.
- 02The team
Bring in the source context
Attach the company knowledge, files, research, examples, meetings, decisions, and connected systems the work should use.
- 03People + agents
Contribute from the best tool
People and agents can work from supported AI interfaces while drawing from the same project and company context.
- 04Project HQ
Save artifacts with their history
Keep the deck, report, brief, research, or app alongside the decisions and corrections that shaped it.
- 05Next contributor
Hand off without the rebrief
The next contributor can see what is true, what changed, what remains open, and where to continue.
- 06The company
Reuse what should compound
Turn the best project methods, templates, and lessons into shared skills for the next project.
Beyond shared chat links
The deliverable is only one part of the project.
HQ preserves the operating context around the artifact so collaboration can continue after the original conversation ends.
The layerSeparate AI chatsWith HQ
BriefRepeated or reinterpreted in every conversationMaintained once as part of the shared project
SourcesUploaded ad hoc and forgotten with the threadStay attached to the work and its decisions
ContributorsWork in isolated chats and merge outputs laterPeople and agents resume one durable project state
FeedbackScattered in comments, calls, and follow-up promptsCorrections remain available to the next contributor
HandoffShare the latest file and schedule a rebriefShare context, artifacts, open loops, and history together
ReuseCopy the final artifact and start againPromote the method and learnings into company capability
What teams can build together
One project state. Many contributors. Reviewable artifacts.
HQ works best where the output matters and the context behind the output matters just as much.
Decks
Narrative, source evidence, examples, feedback, speaker notes, and final presentation.
Reports
Connected data, analysis method, recurring format, decisions, and published output.
Briefs
Goals, constraints, audience, research, references, drafts, and approvals.
Research
Questions, sources, synthesis, disagreements, citations, and decision implications.
Portals and pages
Project context, content, design decisions, implementation, and published artifact.
Plans
Company goals, options, assumptions, owners, decisions, workstreams, and progress.
What changes
Project memory becomes infrastructure.
- 01
Let a teammate or agent continue important work without a live rebrief from the original operator.
- 02
Keep decks, reports, briefs, research, and apps connected to the evidence and decisions behind them.
- 03
Move between supported AI tools without splitting the company project into unrelated histories.
- 04
Make feedback and corrections available to the next contributor instead of burying them in chat.
- 05
Preserve open loops so unfinished work is explicit and resumable.
- 06
Turn successful project methods into shared skills the next team can start from.
Your first win
Finish one artifact without losing the project.
Choose a live deliverable with at least two contributors. Prove that the second person can resume from the project itself, not from a private briefing.
Start a shared AI project- 1
Create one HQ project around a real deck, report, brief, or plan.
- 2
Add the canonical brief, sources, examples, and current decisions.
- 3
Have the first contributor create and save a reviewable artifact.
- 4
Ask a second teammate or agent to resume and improve it.
- 5
Save the feedback, decision, and next open loop with the project.
Durable, bounded context
Project memory stays where it belongs.
Durability only helps when the company can define the boundary, ownership, and access around the work.
- Keep company work inside its company HQ and client work inside the intended client boundary.
- Choose which people and agents can access or contribute to the project.
- Use approved connected systems without copying credentials into project files or prompts.
- Preserve company-owned history without claiming access to unrelated private conversations.
The durable asset is not only the final file. It is the context, sources, decisions, methods, corrections, and open loops that make the file useful.
Keep the whole project
Build with AI together, without starting over.
Start one shared project, save one useful artifact with its context, and let the next contributor move it forward without reconstructing the past.