A non-developer agency questions moving from Claude Projects to Code
A small agency owner currently uses to create a separate workspace for each client. Each workspace holds the client’s brand voice, design materials, rules, and work guidelines for campaigns, , , and related tasks.
The main benefit is that each client’s context stays separate. Colleagues are pushing for a move to Claude Code for long-term use, but the benefit is unclear from a non-developer workflow.
The main concerns are whether client context can be separated easily in a code-like setup, and whether and designs are harder to manage there than in Claude’s normal interface. The practical question is whether the current setup is already good enough or whether Claude Code would create a major workflow upgrade.
Key points
- is being used to keep each client’s work and context separate.
- The workflow includes brand voice, design materials, rules, and guidelines.
- The main doubt is whether Claude Code handles separate client context clearly for a non-developer.
- may be easier to manage in Claude’s normal interface than in a code-like environment.
- The best tool depends on the actual workflow, not on which tool sounds more advanced.