Your firm has years of institutional knowledge locked inside SOW templates, project intake checklists, client briefs, and internal policies. When a new team member needs to draft a memo, they ask someone. When the operations manager needs the right document request list, they dig through folders. When a founder or principal needs to remember how you handled a similar project two years ago, they rely on memory.

Claude Projects fixes this. You upload your firm's key documents into a persistent workspace, write custom instructions that tell Claude how your firm operates, and anyone on the team gets answers grounded in your actual work product -- not generic internet knowledge.

This guide walks you through it, step by step.

What Is a Claude Project?

A Project is a persistent workspace inside Claude where you upload documents and write custom instructions. Every conversation started inside that Project has access to those documents and follows those instructions. Think of it as giving Claude a filing cabinet of your firm's most important materials, plus rules about how to use them.

• Available on Claude Pro ($20/month) and Team ($30/month per seat) -- Team plans let you share Projects across your firm
• Supports PDFs, Word docs, text files, and spreadsheets -- the formats your firm already uses
• 200K token context window -- enough to hold dozens of documents at once
• Custom instructions -- tell Claude your firm's tone, terminology, and rules

Step 1: Decide What Goes In

Before you touch Claude, make a list of the documents your team reaches for most often. You are not trying to upload everything. You want the 15-25 documents that drive 80% of your daily work.

For a tech agency or MSP, that might be:

• SOW templates (project-based, retainer, managed services)
• New client project intake checklist
• Deliverable checklists by service type (web development, managed IT, software integration)
• Review note templates and common change order language
• Firm billing and utilization policies
• Client onboarding and offboarding procedures

For a software company:

• Proposal and SOW templates
• Client intake questionnaires by service line
• Deliverable checklists and quality standards
• Standard engagement terms and scope guidelines
• Internal methodology and process docs

The rule: if someone asks "where's the template for X?" more than twice a month, it goes in the Project.

Step 2: Organize Before You Upload

Claude reads your uploaded documents, but it does not organize them for you. A little structure up front saves confusion later.

Name files clearly. Rename "Template_v3_FINAL_final2.docx" to "SOW-Template-Managed-Services-Monthly.docx." Claude uses filenames as context, so clear names help it find the right document faster.

Group by function. Projects are flat (no folders), but if you have five SOW templates, add a prefix: "SOW-ProjectBased.docx," "SOW-Retainer.docx," "SOW-ManagedServices.docx." This helps Claude distinguish between them.

Remove sensitive data. Do not upload documents with client Social Security numbers, bank account details, or other personally identifiable information. Use anonymized or template versions.

Keep documents current. Upload the latest version of everything. Outdated documents create outdated answers.

Step 3: Create the Project and Upload

The setup takes about ten minutes:

1. Open claude.ai and sign in with your Pro or Team account
2. Click Projects in the left sidebar
3. Click Create Project and give it a clear name -- "Firm Knowledge Base" or "Tax Engagement Standards"
4. Click Add Content and upload your documents
5. Wait for Claude to process them (a few seconds per file)

Now for the step where the real value shows up.

Step 4: Write Your System Prompt

The system prompt is a set of instructions that Claude follows in every conversation within this Project. It is the difference between a generic AI assistant and one that sounds like it works at your firm.

Here is a starting template for a tech agency or MSP:

You are an internal assistant for [Firm Name], a [tech agency / software company / MSP] serving [describe your client base].

When answering questions:
- Reference the uploaded firm documents before using general knowledge
- Use our firm's terminology and conventions
- Match our firm's professional but approachable tone
- Always note which uploaded document you are referencing
- If you are not sure about firm-specific policy, say so clearly rather than guessing

Firm details:
- Service areas: [list them]
- Peak delivery periods: [dates]
- Review process: [describe briefly -- e.g., "All SOWs require founder or principal sign-off before sending"]
- Naming conventions: [anything specific -- e.g., "We use project numbers in format YYYY-ClientName-###"]

When drafting documents:
- Follow the formatting in our uploaded templates
- Include standard disclaimers from our SOW and service agreement templates
- Use [state] jurisdiction requirements unless told otherwise

Write it in plain language. No special formatting or technical commands needed. Just tell Claude what your firm does, how you work, and what to prioritize.

Be specific about what matters. If every SOW must include a limitation-of-liability clause, say so. If your firm always requires a change order before out-of-scope work begins, spell that out. Claude follows instructions well, but only the ones you give it.

Step 5: Test With Real Questions

Before you roll this out to your team, test it yourself with questions your people actually ask:

• "What documents do we need to request for a new managed services client?"
• "Draft a SOW for a web development project with a monthly retainer."
• "What's our policy on billing for out-of-scope work?"
• "Summarize our project kickoff procedures."

Check the answers against what your firm would actually say. If something is off, adjust your system prompt or upload an additional document. This usually takes two or three rounds to dial in.

Step 6: Roll It Out to Your Team

Adoption makes or breaks any new tool. Here is what works at firms like yours:

Start with one person. Your operations manager or a tech-comfortable team member is your best bet. Let them use the Project for a week before anyone else. They will find gaps you missed and become your internal expert.

Show, don't tell. Sit with two or three team members for 15 minutes each. Show them how to open the Project, ask a question, and verify the answer against a source document. People trust tools they have seen work.

Pick one workflow first. If your biggest time sink is assembling document request lists for new clients, start there. Once the team sees Claude pull the right list in seconds instead of five minutes of folder-hunting, they will find their own uses.

Keep it updated. When your firm changes a policy or updates a template, update the Project. Assign one person -- your AI champion -- to own this. A stale Project loses the team's trust.

Common Mistakes to Avoid

Uploading too much at once. Start with 15-25 documents. A focused Project gives better answers than one stuffed with every file on your server.

Skipping the system prompt. Without custom instructions, Claude is a generic assistant. With them, it becomes your firm's assistant. The system prompt is the highest-value ten minutes of this entire setup.

Not telling the team it exists. Mention it in your next team meeting. Pin it in Slack. Put a link in your internal wiki. The best-built Project is worthless if nobody uses it.

Treating AI answers as final work product. Claude prepares the first draft. Your team members review and approve -- the same quality control you already apply to new team member work. The job moves from doing to reviewing.

What This Looks Like in Practice

A 12-person tech agency uploads their SOW templates, project intake checklists, review note formats, and billing policies. During a busy delivery sprint, a team member asks: "What do we need from a new managed services client before kickoff?" Instead of interrupting the operations manager or digging through folders, they get a list pulled from the firm's own template -- in seconds. The founder asks Claude to draft a SOW for a new software integration client. Claude produces a draft based on the firm's actual template, with the right disclaimers already included. The founder reviews and adjusts instead of drafting from scratch. Over a busy quarter, this adds up to hours saved per week across the team.

Get Started

Two ways to move forward:

Do it yourself: Follow the steps above. You can have a working Claude Project for your firm in under an hour.

Get help: Schedule a free call to see exactly where Claude fits your firm's workflows, or book a free consultation and we will walk through your setup together. Our team has hands-on experience with agency and software company workflows -- we know the documents, the delivery requirements, and the processes that matter in tech services.