I wasted six weeks treating Claude like a fancy search engine. I’d open a new chat, paste in my context, write my prompt, get the output, and close the tab. Then do the exact same thing tomorrow. No memory. No consistency. No time saved. Just me, manually rebuilding the same context wall over and over for every single content task in my real estate business.
Then I actually set up a Claude Project properly. Not a chat. A Project — with custom instructions, uploaded documents, and a structured workflow baked in from the start. That one setup session, which took me about 90 minutes, has saved me somewhere between 3 and 4 hours every single week since. For a one-person operation running out of Madeira, that’s not a small number.
This tutorial shows you exactly how to set up a Claude Project for a content business. Every step. Every setting. Every prompt template I actually use. No theory — just what works.
What You’ll Build by the End of This Tutorial
By the time you finish these steps, you’ll have a fully configured Claude Project that:
- Knows your brand voice without you explaining it every time
- Has your key documents uploaded and searchable (style guides, client briefs, templates)
- Runs consistent outputs across property descriptions, email sequences, social posts, or whatever content type your business produces
- Gives you a repeatable system instead of a random conversation each time
This works for real estate content, freelance writing, marketing agencies, coaching businesses — any content operation where you produce similar outputs repeatedly.
Prerequisites Before You Start
You need a Claude Pro account ($20/month as of 2026) to access Projects. The free tier does not include this feature. If you’re running any kind of content business, Pro pays for itself fast — I use it daily and it’s the single AI subscription I’d keep if I had to cut everything else.
You also need to prepare three things before touching the interface:
- A brand voice document — even a rough one. Two paragraphs describing your tone, your audience, and what you never want to sound like.
- One or two examples of your best content — past articles, property descriptions, email sequences. Whatever your best work looks like.
- A list of your most common content tasks — the things you produce weekly or monthly. Don’t overthink it. Five tasks is enough to start.
Have those ready in text files or Google Docs. You’ll upload them in Step 4.
Step-by-Step: How to Set Up a Claude Project for Your Content Business
Step 1 — Create a New Project
Log into claude.ai. On the left sidebar, you’ll see a “Projects” section. Click “New Project.”
Name it something specific. Not “Content.” Something like “Madeira Real Estate Content” or “Client Newsletter System” or “Property Listings + Social.” You’ll likely build multiple projects over time — vague names become a problem fast.
Give it a short description too. I use descriptions like: “All content for Madeira property listings, client emails, and Instagram. Voice: direct, local expert, no tourist-brochure language.” This description is just for you — but writing it forces clarity before you build anything.
Step 2 — Write Your Custom Instructions (This Is the Most Important Step)
Inside your new project, find “Custom Instructions” or “Project Instructions” in the settings panel. This is where you define how Claude behaves across every conversation inside this project.
Most people write two sentences here and wonder why outputs are generic. Don’t do that. Spend 20 minutes on this section. Here’s the template I use and refine for every project I build:
ROLE:
You are a specialist content writer for [YOUR BUSINESS NAME], a [describe your business] based in [location]. You write content that sounds like [YOUR NAME] — not like a content agency, not like AI.
AUDIENCE:
[Describe your primary audience in 2-3 sentences. Who are they? What do they care about? What language do they use?]
VOICE AND TONE:
- [Adjective]: [brief explanation of what this means in practice]
- [Adjective]: [brief explanation]
- [Adjective]: [brief explanation]
- Never: [list 3-5 things you never want in your content — clichés, corporate language, vague claims]
OUTPUT DEFAULTS:
- Format: [e.g., short paragraphs, no bullet overload, one H2 per 200 words]
- Length: [typical lengths for your main content types]
- Always end with: [e.g., a specific call to action, a question, nothing — whatever fits your style]
CONTEXT YOU SHOULD ALWAYS REMEMBER:
- [Key fact about your business]
- [Key fact about your market]
- [Any recurring details Claude should never get wrong — e.g., your location, your pricing tier, your specialty]Here’s a condensed version of my actual instructions for my Madeira real estate project, so you can see what “filled in” looks like:
ROLE:
You are a content writer for Robson Penassi Consulting, an independent real estate consultancy in Madeira, Portugal. You write like Robson — experienced, direct, local, never like a tourist brochure.
AUDIENCE:
International buyers, mostly from Northern Europe and Brazil, aged 35-60, relocating or investing. They are research-heavy and skeptical of marketing fluff. They want facts, local insight, and honest trade-offs.
VOICE AND TONE:
- Direct: State things plainly. No winding sentences that arrive late at the point.
- Local expert: Reference Madeira specifically — neighborhoods, regulations, terrain, climate. Never generic Portugal content.
- Honest: Include real limitations when relevant. Buyers trust Robson because he tells them what's hard, not just what's beautiful.
- Never: "paradise", "dream home", "don't miss out", passive voice overload, vague superlatives.
OUTPUT DEFAULTS:
- Paragraphs: 3-4 sentences max.
- No more than one bullet list per piece of content unless it's a features list.
- Property descriptions: 150-200 words. Always end with a practical detail (parking, access, nearest town).
CONTEXT:
- Business location: Funchal, Madeira, Portugal
- Specialty: International buyer representation and off-market properties
- Current market context: Prices stabilized in coastal areas in 2026 after the 2023-2024 run-upYour instructions don’t need to be long. They need to be specific. Specific beats long every time.
Step 3 — Set Up Your Project Tools
Claude Projects support a set of tools depending on your plan. In Pro, you get access to:
| Tool | What It Does | Use It For | Enable It? |
|---|---|---|---|
| Web Search | Pulls live data from the web during conversations | Market research, competitor content, current stats | Yes — if your content references current data |
| Document Knowledge | Reads your uploaded files in every conversation | Style guides, templates, briefs, past content | Yes — always |
| Analysis Tool | Runs calculations, processes data | Pricing analysis, content performance data | Optional — useful for data-heavy content |
For a content business, the Document Knowledge tool does the heaviest lifting. Enable web search only if your content regularly references current events or statistics. I keep it on for my market analysis reports and off for property descriptions — descriptions don’t need live data, they need consistency.
Step 4 — Upload Your Knowledge Documents
Inside your project, find the “Add Content” or “Knowledge” section. Upload your prepared files here. Claude will reference them automatically in every conversation within this project.
What to upload for a content business:
- Brand voice guide (even 1 page is enough)
- 3-5 examples of your best existing content — these are your style anchors
- Content templates for your most common formats
- Client or audience profile — who you write for, their pain points, their language
- Any recurring reference info — for me, this is a Madeira neighborhood guide, local regulations summary, and a glossary of terms I use consistently
File format matters. Plain text (.txt) and PDF work well. Heavily formatted Word documents sometimes cause Claude to focus on structure over content. When in doubt, paste text directly rather than uploading a complex file.
Keep individual documents under 10,000 words each. If your style guide is a 40-page monster, break it into focused sections. Claude processes focused documents better than sprawling ones.
Step 5 — Build Your First Prompt Templates Inside the Project
Start a new conversation inside your project and build out your most-used prompt templates. Save these somewhere accessible — I keep mine in a Notion database linked from my project notes.
Here are three templates I use weekly:
Property Description Template:
Write a property description for the following listing. Use the voice from the uploaded style guide. 150-200 words. End with one practical detail about access or nearby infrastructure — not a sales line.
PROPERTY DETAILS:
Type: [apartment / villa / land]
Location: [neighborhood, Madeira]
Size: [m²]
Bedrooms: [number]
Key features: [list 4-6 features]
Price: [€ amount]
Unique selling point: [what makes this different from similar listings]
Any limitations to mention honestly: [e.g., no garage, steep access road]Weekly Market Update Email Template:
Write a 200-word market update email for my buyer newsletter. Tone: like a trusted local advisor sending a personal note, not a broadcast email.
This week's key data points:
- [Stat 1]
- [Stat 2]
- [Observation from the field]
One honest observation about current market conditions — include a trade-off or limitation, not just positive spin.
End with one actionable suggestion for buyers currently searching.Instagram Caption Template:
Write 3 Instagram caption options for the following property/topic. Each caption: under 150 words. Hook in the first line (no "Check out this beautiful..."). Include one specific local detail. End with a question or soft CTA — no "DM me now" language.
Topic/property: [describe]
Target emotion: [curiosity / aspiration / reassurance / urgency]
Any specific detail to include: [optional]Step 6 — Test, Then Refine Your Instructions
Run each of your templates through 3-4 real tasks before you declare the project ready. Compare the outputs against your best existing content. Ask yourself: would I send this as-is, or am I still editing heavily?
When outputs are off, the fix is almost always in the custom instructions, not the individual prompt. If Claude keeps using language that doesn’t match your voice, go back to Step 2 and add a specific “never do this” line. Be surgical. One precise instruction beats a paragraph of vague guidance.
I spent about 3 weeks refining my instructions before they felt stable. That’s normal. The project gets better with use — each refinement you make carries forward into every future conversation.
My Real-World Experience: From 3 Hours to 35 Minutes on Listing Content
In January 2026, I had a busy stretch — 14 new listings to process in one month. In the old workflow, writing descriptions, preparing social content, and drafting the property intro emails for each listing took me roughly 3 hours per listing batch (I’d do 4-5 at a time). That’s about 9-10 hours total just for content on that month’s listings, before I’d even touched market reports or client communications.
I’d set up my Madeira Real Estate Content project the previous November — two months earlier — but this January was the first real stress test of it. I had all 14 property briefs ready in a spreadsheet. I ran them through the project one by one using my property description template. Each description took me about 90 seconds of prompting and 2 minutes of editing. Most needed one small fix — a word that didn’t sound like me, or a detail I’d forgotten to include in the brief.
Then I ran the Instagram captions: 3 options per listing, pick one, light edit. Another 3-4 minutes per listing. The intro emails for buyers on my list who matched each property — another 2 minutes each, because Claude already knows my email tone from the uploaded examples.
Total time for all content on 14 listings: just under 2 hours. That’s roughly 8 minutes per listing for description + social caption + intro email. The previous baseline for the same output was closer to 25-30 minutes per listing when done manually — and that’s not counting the time I’d spend staring at a blank page for the hard-to-describe properties.
The quality was consistent in a way my manual writing never fully was. When you write 14 descriptions in one sitting after a full day of client calls, the 12th one is worse than the 2nd. Claude doesn’t have that problem. Every output started from the same quality baseline, which made the editing pass faster too — I knew what to look for.
One thing I noticed: the project’s value compounds. My instructions in January were sharper than they were in November because I’d added 4-5 refinements from real use cases. By February, I was editing even less. The project was learning what I needed not because Claude has memory in some mysterious AI way — but because my instructions had become genuinely precise about my actual needs.
The cost of all this: $20/month for Claude Pro. I spend roughly 5 hours a month actively working inside my Projects now, down from what used to be 15+ hours of content production. For a one-person business, that extra 10 hours a month goes directly into client work and business development.
Genuine Limitations I Hit During Testing
Claude Projects are not perfect. Here’s what actually frustrated me from real use:
The knowledge base doesn’t update dynamically. If I revise my style guide document, I have to delete the old file and re-upload the new version. There’s no “sync” feature. This caught me twice — I updated my voice guidelines but forgot to re-upload, and Claude kept using the old version for two weeks before I caught it on a client email draft.
Long uploaded documents get inconsistently referenced. I uploaded a 15-page neighborhood guide once. Claude referenced it well for the first few sections and seemed to ignore the latter half in practice. I split it into three separate documents by region — that fixed it. Lesson: shorter, focused documents outperform one long comprehensive one.
Projects don’t carry over to the mobile app cleanly. As of early 2026, the mobile Claude experience for Projects is still behind the desktop web version. I do all my project setup and serious prompting on desktop. Mobile is fine for quick chats, not for structured project work.
You cannot share a project with someone else on a separate account. If you’re a solo operator this doesn’t matter. If you eventually bring in a VA or collaborator, they’d need to be added under a Teams plan — the Pro personal plan is single-user only.
Troubleshooting: When Your Project Outputs Feel Wrong
Problem: Claude keeps ignoring parts of my custom instructions.
Fix: Instructions that conflict with each other get deprioritized. Read your instructions aloud and check for contradictions. Also try moving your most critical rules to the top — Claude weights earlier instructions more heavily.
Problem: Outputs feel generic even with instructions set up.
Fix: Your uploaded example content is probably too polished or too diverse. Pick 2-3 examples that all sound unmistakably like you at your best. More variety = more averaging = more generic outputs.
Problem: Claude references uploaded documents but gets details wrong.
Fix: Add a direct instruction like: “Before writing, state the key relevant facts from the uploaded documents that apply to this task.” This forces Claude to surface its understanding before generating, which catches misreads early.
Problem: Each conversation inside the project still feels inconsistent.
Fix: You’re probably starting conversations with minimal context and relying entirely on the project instructions to carry the load. Add 2-3 lines of specific context at the start of each conversation even within a project. Instructions set the rules; individual prompts set the scene.
Practical Summary: What a Well-Set-Up Claude Project Looks Like
A content business Project on Claude that actually works has six components:
- A specific name and
Robson Penassi
Real estate consultant in Madeira, Portugal. Solopreneur since 2012. Testing AI tools since 2023 to automate his one-person business. Writes about what actually works — and what does not.
More articles by Robson →
