What you'll do: set up your Claude Project so it permanently remembers your business, then run your first content workflow.
โฑ 25 minutesFollow along as I learn โ
๐ธ Instagram ๐ต TikTok โถ๏ธ YouTube ๐ Twitter ๐งต Threads ๐ฆ Bluesky ๐ฅ FacebookFor my first month, every single chat with Claude started the same way. "I run a small business. My audience is..." Copy. Paste. Every time. It was exhausting.
Projects ended that. One 5-minute setup. You tell Claude who you are, what you do, who you serve, and how you write. Every chat inside that Project already knows. You never re-explain again.
It's the feature most beginners skip. It's also the one that makes Claude feel like it works for your business instead of a generic one.
Open claude.ai. In the left sidebar, click New Project. Give it a name (your business name works). Then paste this into the Project's custom instructions and fill in the brackets.
I am [your name], the owner of [business name]. I [what you do] for [who you help]. My tone is [word 1], [word 2], [word 3]. My audience is [describe them in one sentence]. My business started in 2026. Never assume I have years of prior experience.
Save it. Every chat you start inside this Project now begins already knowing your business.
Projects are tools for consistency, but consistency comes from iteration. After Claude drafts something, compare it to your past work. Where's it different? Add that detail to your Project context, then run the same task again. By round 3, the output will feel like yours.
Record a 60-second voice memo about an idea. Transcribe it (your phone does this, or paste the audio note text). Then start a chat inside your Project and run this:
Turn this into a LinkedIn post, an Instagram caption, and a 3-bullet email newsletter section. Match the voice in the transcript. Here's the transcript: [paste it here]
First, teach Claude your voice once. Paste in a few emails you've sent with this prompt:
These are examples of emails I've written. Use them as my voice reference for any email you draft.
Then, any time you need a draft, run this:
Draft an email following up with a prospect I met last week. We discussed [topic]. Keep it under 5 sentences. Sound like me.
Run this one in a fresh chat, not inside your Project. You want neutral analysis, not answers filtered through your own business context.
Research [competitor website URL or business name]. Give me: what they sell, who they target, their pricing if visible, how they position themselves, and 2 gaps I could fill that they're not addressing.
You can drag a file straight into a claude.ai chat and ask questions about it. Claude reads the contents and works from them directly.
Check specific details in any Project output: did it get your service right, your audience, your pricing? AI fills gaps with plausible-sounding guesses.
Your context wasn't specific enough. "I'm a marketing person" is too vague. Claude forgets vague. "I'm a B2B SaaS marketer who focuses on LinkedIn. My audience is technical founders. I write in conversational tone. Here's an example..." is specific. Claude remembers that.
You added context to your Project but didn't give Claude examples of your actual writing. Go back to your Project. Paste in 2-3 emails you've actually sent. Tell Claude: "Match this tone and structure." The difference is immediate.
You forgot the "When NOT to Use AI" lesson. Competitor data is high-hallucination territory. Claude will confidently give you wrong numbers. Before you use it, verify: check their actual website, their LinkedIn, their press releases. Cross-check 3 sources minimum. If Claude's number doesn't match reality, ask Claude to cite where it got that number. It usually can't.
You have too much context, or it's buried. Keep Project context under 500 words. Put your core business details first, examples second. If Claude's not using it, your instructions in the individual message are too weak. Your message context overrides Project context. Make your message specific: "Using what you know about my business..." reminds Claude to check the Project.
The Iteration Habit: Projects are tools for consistency, but consistency comes from iteration. After Claude drafts something, compare it to your past work. Where's it different? Add that detail to your Project context, then run the same task again. By round 3, the output will feel like yours.
3 questions
I share what I'm learning in real time, new workflows, honest reviews, what worked and what didn't.
#BuiltwithSally