The Setup Shouldn’t Feel This Confusing
The person asking the question sounded almost apologetic, which is funny because their problem is painfully normal now. They had built custom agents elsewhere that knew the company’s projects, goals, target audience, and brand voice. Then the company moved to Claude, and suddenly the whole thing felt less obvious. Do you use persistent memory? Do you upload a markdown file every time? Do you need a developer? The short answer from people who’ve actually tried it was pretty clear: stop trying to recreate an assistant. Build a workspace. Claude wants Projects, not scattered chats with a bunch of context duct-taped on top.
That difference matters more than it sounds. Chat-based tools often make people feel like they’re training a little personality that follows them around. Claude, at least in this marketing use case, seems to work better when treated like a folder with a brain. Put the brand voice, audience, offers, campaign goals, and examples in one place. Then keep working inside that place. One commenter called Claude “workspace/document based” rather than “assistant-based,” and that’s probably the mental switch that stops the whole thing from feeling broken.
Projects Are the Answer, But Not One Giant Messy Project
The most repeated advice was almost suspiciously unanimous: use Claude Projects. Not persistent memory. Not a new upload every time. Not a 90-line prompt pasted into every chat like some cursed ritual. Create a Project, put the brand context in the instructions, upload a few supporting files, then start new chats inside that Project. Several people said this is the closest non-developer version of what custom agents were doing before. One person even said every conversation inside the Project inherits the context automatically, which is exactly the kind of boring magic marketers actually need.
The better advice went one layer deeper: don’t make one massive “Marketing” Project that tries to do everything. Make separate Projects for separate workflows. One for marketing content. One for sales outreach. One for paid media. One for newsletters. One for reporting. That keeps the context tight, and Claude doesn’t have to guess whether it’s writing a landing page, analyzing campaign data, or drafting a cold email. A few people warned that too much context makes the output mushier, not smarter. That’s the part nobody wants to hear. More files don’t always mean better answers.
Brand Voice Lives in Examples, Not Vibes
A lot of people think brand voice means typing “smart, friendly, confident, concise” into a box and calling it a day. That’s cute. It’s also why the output comes back sounding like every SaaS homepage ever written. The stronger advice was to treat Project Instructions like a mini brand brief. Who are you? Who do you sell to? What are the current goals? What words should Claude avoid? What should it never open with? What does “on brand” actually look like in the wild?
The comments kept coming back to examples. Paste in two or three pieces of existing work that actually sound right, then tell Claude to match that voice. One marketer said the examples matter more than adjectives because Claude pattern-matches from real writing better than from abstract descriptions. That’s the sharpest lesson here. Don’t tell it your brand is “bold.” Show it the piece where the opening line punches, the body stays clear, and the CTA doesn’t sound like it was assembled in a conference room. Claude can imitate structure and rhythm, but only if you give it something real to hold.
Persistent Memory Is Not the Brand Brain
There was also a clean split on persistent memory. People didn’t say it was useless. They said it’s the wrong foundation for this job. Persistent memory is better for personal preferences, your role, recurring habits, or broad context that should follow you across chats. Brand voice should live inside Projects, because brand work needs boundaries. The newsletter Project should not behave exactly like the sales outreach Project. The paid media Project should not write like the founder’s thought-leadership ghostwriter. Scope is the point.
That’s where some of the frustration comes from. People expect memory to be the magical “remember everything” layer. But for marketing, remembering everything is often the problem. You need Claude to remember the right things for the right task. One commenter said Projects are more deliberate and scoped, and that’s the better foundation. Another said regular chats feel broken once Project-first thinking clicks. That sounds dramatic until you’ve spent a week re-explaining your target audience, your product positioning, and the five phrases your CEO hates. Then it sounds like mercy.
The Trap Is Overloading It
The most useful warning was about instruction length. One commenter claimed that once the instruction field gets too long, the rules buried near the bottom can start fading into background noise. Whether the exact word count is universal or not, the instinct is right: stuffing every brand thought into instructions is not strategy. Put the most important rule first. Keep the instructions sharp. Use uploaded files for reference material. Don’t make Claude dig through a manifesto just to remember not to use a banned phrase.
There’s another small but powerful trick buried in the comments: negative instructions. Claude may be especially good at following “don’t do this” rules. Don’t use these words. Don’t open with a question. Don’t sound corporate. Don’t over-explain. Don’t invent product details. For marketers, that’s gold, because brand voice is often defined by what gets cut. The best creative teams know the forbidden moves as well as the approved ones. Claude apparently behaves better when those lines are drawn clearly.
The emotional core of this whole discussion is simple: people aren’t dumb for being confused. The setup really is less obvious than it should be. But the fix isn’t a developer workflow or some elaborate automation stack. It’s a cleaner operating system for your marketing brain. Build one Project per workstream. Keep the instructions short and brutal. Upload the right examples. Add current campaigns, audience notes, offers, and brand rules. Then stay inside the Project when you work.
Claude won’t magically become your best strategist just because you gave it a folder full of PDFs. It still needs review. It still needs reminders. Sometimes it’ll drift. But when the setup is clean, it can stop behaving like a forgetful intern and start acting like a useful writing partner. Not perfect. Not psychic. Useful. And for a marketing team drowning in context, that’s more than enough.