Anthropic · Technologies
Claude Projects
Claude that already knows your context.
Projects are workspaces that hold your documents, instructions and conversation history, so Claude answers with your context every time instead of starting from zero. On Team and Enterprise plans they are shared, turning individual know how into a team asset. We set them up so they actually get used.
PROJECT LIBRARY · EXAMPLE TEAM
PROJECT
KNOWLEDGE
SHARED WITH
STATUS
Client-Proposals
Templates and wins
Sales
HEALTHY
Brand-Voice
Style guide
Marketing
HEALTHY
Contract-Review
Playbook and precedents
Legal
HEALTHY
Onboarding
Draft docs
People
REVIEW
personal-scratchpad
Duplicated effort
Nobody
RISK
Sample library
healthy · review · risk
In plain terms
Stop re-explaining your business to the AI every morning.
A project holds the context once, and every conversation starts from it. Here is what changes.
Without it
- Every chat starting with the same background pasted in again
- Style guides and templates re-uploaded endlessly
- Each person building private prompt tricks nobody shares
- Answers that ignore how your business actually works
With it
- Documents and instructions loaded once, used every time
- Claude answering in your voice, from your material
- Shared projects the whole team works from
- Institutional knowledge that survives staff turnover
What CG TECH can do with Claude Projects
The work, broken into the parts that matter.
Your documents, standing by
Style guides, templates, policies and reference material live in the project, so every conversation draws on them without a single upload.
context loaded once, used always
Claude briefed like a new starter
Each project carries instructions on tone, format and rules, so outputs land closer to final on the first pass instead of the fifth.
outputs right the first time
Team know how, not personal tricks
On Team and Enterprise plans, projects are shared: the proposal project, the brand project, the review project, each one a working asset the whole team improves.
one team, one context
A knowledge base is a product
What goes in, what stays out, who owns updates and how projects map to your workflows. A stale or bloated project quietly gives worse answers, so we design the library and the upkeep.
projects that stay useful
How an engagement runs
From repeated context to a working library, step by step.
01
Map
We find the repeated context and the workflows worth capturing.
02
Design
Project structure, knowledge and instructions per workflow.
03
Build
Projects live with the teams that own them, tested on real work.
04
Embed
Ownership and upkeep so the library stays current.
Questions we hear a lot
Common questions about Claude Projects
What are Claude Projects?
Projects are workspaces that hold your documents, instructions and conversation history, so Claude answers with your context every time instead of starting from nothing. On Team and Enterprise plans they are shared, which is what turns one person’s know-how into something the team can use.
What belongs in a project?
The context a workflow reuses: style guides, templates, policies, product material and worked examples. Not everything you have, just what makes answers better, and we help you make that cut.
How is this different from just attaching files to a chat?
Attachments serve one conversation. Project knowledge serves every conversation in that workspace, for everyone who shares it, without re-uploading.
Is our project content used to train models?
No. On Team and Enterprise plans, business data, including project content, is excluded from training by default.
Who keeps projects up to date?
Someone has to, or answers drift as the business changes. We set named owners and a simple review rhythm as part of the rollout, because an unowned knowledge base decays quietly.
How many projects should we have?
Fewer than you would think. A project per recurring job works. A project per client or per person turns into a filing problem nobody maintains, and the content goes stale without anyone noticing.
What is a good first project to set up?
Something done repeatedly to a known standard: tender responses, board papers, client reports, onboarding packs. The instructions and reference documents already exist in someone’s head, and a project is where they stop being in someone’s head.
What happens when the source documents change?
Nothing, unless someone updates the project, which is exactly the risk. We set an owner and a review point per project, because a confidently answered question from a superseded policy is worse than no answer.
Ready when you are
Want Claude to know your business? Let us talk.
A discovery session maps your workflows, your context and your quick wins. You keep the plan either way.
What to expect
- A consultant replies within 4 business hours
- Session booked to understand your requirements
- We will provide you with a fixed price quote