Claude Project: Your Persistent Research Assistant

For Research Analysts

Tools: Claude Pro | Time to build: 1-2 hours | Difficulty: Intermediate-Advanced Prerequisites: Comfortable using Claude for verbatim coding or executive summaries — see Level 3 guide: "Open-Ended Verbatim Coding with Claude"

What This Builds

A Claude Project that acts as your persistent research project assistant for a specific client engagement. Instead of explaining the client, the research question, the methodology, and your coding framework every time you open Claude, your Project has all of this loaded permanently. Every conversation starts from shared context — you just ask your question and get a precise, tailored answer. Over a 3-month engagement, this saves you hours of re-briefing and produces dramatically more consistent outputs.

Prerequisites

• Claude Pro subscription ({{tool:Claude.plan}} at {{tool:Claude.price}}) — Projects require a paid account
• Comfortable with Claude for at least 2-3 basic tasks (verbatim coding, report drafts, etc.)
• 1-2 hours to set up the project context files

The Concept

A Claude Project is like giving a new team member a full onboarding document that they remember perfectly in every conversation. A regular Claude conversation starts blank — you have to explain everything from scratch. A Project starts with your uploaded context files already loaded: the client brief, the research design, your coding framework, the deliverable template, and your brand voice guide. Every conversation in that Project inherits this shared knowledge automatically.

Build It Step by Step

Part 1: Create the Project in Claude

1. Open Claude at claude.ai and sign in to your Pro account
2. In the left sidebar, click + New Project (or look for a Projects section in the navigation)
3. Name the project clearly: "Client Name — Study Name — Date" (e.g., "Brightway Insurance — Brand Tracker Q2 2026")
4. You'll land in the Project workspace, which has a Files section and a conversation area

What you should see: A project workspace with a file upload area on the left and a conversation panel on the right.

Part 2: Upload your context files

This is the key step. Click Add files (or the upload icon) in the Files section and upload these documents:

File 1: Project Brief (1-2 pages) Create a document containing:

• Client name and industry
• Research objective (the exact business question)
• Target respondent description
• Methodology summary (survey type, n, dates)
• Key deliverables (report, deck, topline)
• Timeline and milestones
• Client preferences and sensitivities

File 2: Codebook (if applicable) Your verbatim coding framework for this project — all codes defined with examples. Upload as a simple text or Word file.

File 3: Report Template or Outline The section structure of your deliverable. Even a simple outline helps Claude understand what you're building toward.

File 4: Prior Wave Data (optional) If this is a tracking study, upload the prior wave topline findings. Claude can then compare current findings to prior wave automatically.

What you should see: Files appear listed in the Project's file section. Claude can now reference these in any conversation.

Part 3: Write the Project Instructions

In the Project settings (look for a "Project instructions" or "Custom instructions" option), write a brief brief for how Claude should behave in this project:

You are a research assistant for a market research project called [Project Name].

Context is in the uploaded files:
- "Project Brief" — client background, research objective, methodology
- "Codebook" — the verbatim coding framework for this project
- "Report Outline" — the deliverable structure

How to behave:
- Always refer to the client as "[Client Name]" — never "the client"
- When coding verbatims, always use the codes from the Codebook file exactly as written
- When drafting report copy, match the section structure from the Report Outline
- Flag anything where you're uncertain or need clarification from me
- Keep outputs professional, client-facing, without consulting jargon

What you should see: Instructions saved. Every new conversation in this Project will now start with this context pre-loaded.

Part 4: Test and Refine

Start a new conversation in the Project. Test with a question that requires the uploaded context:

• "Based on the project brief, what's the primary business question we're answering?"
• "Code this batch of verbatims using the codebook" [paste 10 test responses]
• "What section of the report would this finding go in?" [describe a hypothetical finding]

If Claude's answers are inaccurate or miss context from your files, refine the Project Instructions to be more specific about how to use each file.

Real Example: Brand Tracker Project

Setup: You're running a quarterly brand tracker for an insurance client. You create a Claude Project named "Brightway Insurance Brand Tracker Q2 2026" and upload:

• A 1-page project brief with the tracking metrics and client context
• The verbatim codebook (12 codes for the open-ended question)
• The report template (8-section outline with slide descriptions)
• Prior wave toplines from Q1 2026

Input (typical conversation): "Here are 80 verbatim responses to the brand perception question. Code them using the codebook."

Output: Claude returns a table with all 80 responses coded, with [REVIEW] flags on 6 edge cases — no reminder needed about which codebook, no re-explanation of the codes.

A week later: "Draft the awareness section of the report based on these findings" — Claude drafts copy that already knows the section structure, the client name, and the prior-wave benchmarks.

Time saved: Across a 3-month engagement with 5-6 waves of work sessions, the saved briefing time and more consistent outputs add up to 8-12 hours.

What to Do When It Breaks

• Claude gives generic answers that ignore the uploaded files → Check that files are actually in the Project (not just your conversation). Re-upload if needed. Add explicit instructions like "always check the Codebook file before coding."
• Verbatim coding is inconsistent across conversations → Add more examples to the codebook file. The more worked examples in the codebook, the more consistent the coding.
• Claude invents context not in your files → Add to Project Instructions: "Do not invent or assume information not in the uploaded files. Say 'I don't see this in the project files' if you're unsure."
• File content is outdated → Delete the old file from the Project and re-upload the updated version. Claude uses the current file content in each conversation.

Variations

• Simpler version: Skip the Project and just paste your project brief at the start of every Claude conversation — same context, manual each time
• Extended version: Add a "client voice guide" file with sample past deliverables so Claude can match your firm's writing style exactly

What to Do Next

• This week: Set up a Project for your longest-running or most complex current engagement
• This month: Build Projects for your top 3 active clients — experience the difference in conversation quality
• Advanced: Combine with the automated verbatim coding pipeline (Level 4) to create a fully systematic analysis workflow for large tracking projects

Advanced guide for Research Analyst professionals. Claude Projects require a paid Claude Pro subscription.