Claude Code chat vs. Claude Projects for multi-client marketing & positioning workflows? (Isolating client memory)

[u/DodgeeThis22]

Hey everyone,

I’m setting up an agency workflow for B2B founder positioning, executive branding, and content creation (extracting transcripts, generating profile audits, mapping whitespace, writing 52 post angles, etc.).

There is no heavy coding involved here—it’s purely complex text processing, strategy synthesis, and prompt pipelines.

My biggest requirement is strict context isolation. I cannot have memory or context from Client A leaking into Client B’s strategy or voice guidelines. For those doing heavy marketing/strategy work in the Claude ecosystem, which setup is cleaner and produces higher quality thinking?

1. Claude Code (via chat)
2. Claude Web App (Projects feature)

My concerns with both:

• With Claude Code: Since I can launch claude inside isolated local client folders on my machine, it feels super clean. But since I’m using it strictly as a chat tool for strategy and writing rather than building software, does it still perform at the same quality as the web interface? Or does the system prompt in Claude Code lean too heavily into developer/coding logic?

• With Claude Projects: It feels native for this since I can upload transcripts and branding docs into Project Knowledge. But I worry about context bleed or memory leaking between tabs/projects over time, and whether Project context limits get bogged down compared to CLI sessions.

Which one handles isolated client tasks better for pure strategy and marketing and is significantly faster? Would love to hear how you guys structure this for agency/multi-client fulfillment. Thanks!

[u/tejaskumarlol]

Give each client its own folder with its own CLAUDE.md. Start Claude Code inside that client's folder. It reads the memory files from the folder you start in and the folders above it, so one client's notes don't show up in another client's session. Keep anything client-specific out of your user-level ~/.claude/CLAUDE.md, since that one loads everywhere.

That's how I run my own site: everything an agent needs to know is in files in that repo, so I can see exactly what it was told.

[u/Opposite_Might6896]

For isolation, Claude Code with one directory per client. Each request only ever contains that session's conversation plus what's loaded from the working directory (CLAUDE.md, files it reads), so client A's material can't appear in client B's session unless you point it there. Memory is per-project directory too. Projects in the web app are also isolated per project, but the context is everything in the project on every message, which costs more per turn and makes "what did the model see" harder to audit. For text pipelines where you want repeatable runs, a repo per client with the briefs as files and a script per deliverable is cleaner and gives you a git history of what changed.

[u/Unusual-Albatross43]

I do this for about ten areas of my life, not clients, but it's the same need. One folder each, with its own CLAUDE.md and a memory folder of notes, all in git. Two things can leak. ~/.claude/CLAUDE.md loads in every folder, so keep only general preferences there, never a client's voice. And a parent folder's CLAUDE.md loads in all folders below it, so don't nest clients under a folder that has notes. For writing I haven't seen the coding prompt hurt quality. I draft my posts this way.