# Base for project teams: one source of project knowledge, whatever AI each person uses

On a project, everyone asks their own AI about the same documents and gets a different, unsourced answer, and the decisions live in someone's chat history. Put the project in a Base. Everyone connects the AI they already use, Claude, ChatGPT, Grok or a coding agent, and works from the same documents and the same cited facts; contributors add updates from their AI; and decisions, tasks and context stay on the Base's threads for the whole team.

Updated November 2, 2026. Canonical page: https://createbases.com/for/project-teams

## Three ways project teams use Base

1. Share the project's context. Briefs, specs, research and meeting notes go into one Base, and every teammate's AI answers from it with the quote behind each fact. See [how to share a team knowledge base across AI tools](https://createbases.com/guides/connect-documents-to-ai).
2. Contribute updates from any AI. A contributor's assistant saves a new brief, edits a document in place, or adds implementation notes, and Base keeps every earlier version and rereads what changed.
3. Keep decisions on the record. Threads hold comments, tasks with an owner and a status, and context put on the record, so the next person, or the next AI, can see what was decided and why.

## An illustrative example

This example is illustrative, not a customer's project. A product manager, a designer and an engineer run a launch from one Base, each in a different AI.

1. The product manager asks Claude what customer interviews said about signup and saves the launch brief to the Base.
2. The designer asks ChatGPT what the brief means for the checklist and updates it.
3. The engineer's coding agent reads the brief, builds the signup flow, and saves implementation notes back to the Base, and moves the launch task to review.

## Why project teams choose Base

- One knowledge base for every AI. Any app that accepts a custom MCP connector gets every Base tool the person's role allows.
- Answers agree on the sources. Every fact keeps its quote, and figures that disagree between documents are flagged.
- It keeps itself current: new documents are read on arrival, and a figure a later document updates is marked superseded.
- It gets faster the more the team uses it: on a 31-question evaluation it answered 1.9 times faster with 44 percent fewer tokens.
- Clients and partners join by email with a role, and Pro is $20 a month per workspace, not per seat.

## See an example

Open [the example project kickoff Base](https://createbases.com/examples/kickoff): a brief, scope, timeline, budget, stakeholders and kickoff notes. All names and figures in it are fictional.

## Questions

### Do we all need the same AI assistant?

No. Each person connects their own app to the same Base and signs in as themselves; setup for each app is on [the connect page](https://createbases.com/connect).

### Can our AI assistants edit the documents?

Yes, for contributors and admins. They add documents and new versions, and edit text, Markdown, CSV, Word and Excel files in place. Viewers read.

### How soon does everyone see an update?

Usually within a few minutes. Base reads a new or changed document as soon as it arrives, and every assistant uses it on its next call.

### Can we include a client in the project?

Yes. Invite them to the Base by email as a viewer or a contributor. They do not join your workspace or see your other Bases.

### What does it cost?

Base is free for 2 Bases with 300 credits and no card, and Pro is $20 a month per workspace, not per seat. Reading and connecting an AI are free for everyone on the Base.