Build a Solopreneur Knowledge Base With Claude Projects

I used to keep my entire real estate business inside my head. Twelve years of market knowledge about Madeira — which neighborhoods appreciate fastest, which property types attract international buyers, what buyers from Germany ask versus buyers from the UK, the exact wording that moves listings — all of it locked in my skull with no reliable way to transfer it to any tool I was using. Every time I started a new AI session, I was re-explaining myself from scratch. It was like hiring an assistant every single morning who had zero memory of working with you yesterday.

Claude Projects changed that. Not in a vague, theoretical way — in a specific, measurable way that I’ll walk you through step by step in this tutorial. By the end, you’ll have a functioning solopreneur knowledge base inside Claude that actually knows your business, speaks in your voice, and produces usable output without constant hand-holding.

What You’ll Build (and Why It Matters for Solopreneurs)

A Claude Project is a persistent workspace inside Claude that holds a custom system prompt, uploaded documents, and conversation memory — all tied together so every chat inside that Project has full context about your business from the first message.

For a solopreneur, this is the difference between a generic AI assistant and one that already knows your pricing structure, your client personas, your brand voice, your service offerings, and your most common workflows. You stop being a trainer and start being a director.

By the end of this tutorial, you’ll have built:

• A Claude Project with a custom system prompt that captures your business identity
• A knowledge base of uploaded documents covering your services, clients, and workflows
• At least three working sub-prompts for your most repeated tasks
• A test result you can compare against your previous output quality

Prerequisites Before You Start

You need a Claude Pro account. Projects are not available on the free tier. Claude Pro costs $20/month as of 2026. If you’re running a solo business and generating any revenue at all, this is not a meaningful expense.

You also need to spend about 30 minutes before you start gathering the raw material for your knowledge base. Most people skip this and end up with a shallow Project that underperforms. Don’t skip it.

Gather these before Step 1:

• A description of your business, services, and typical clients (even rough notes work)
• 2-3 samples of your best existing writing (emails, proposals, social posts, whatever you produce most)
• A list of your most-repeated tasks that involve writing or research
• Any pricing documents, service packages, or FAQ documents you already have

Step 1: Create Your Claude Project

Log into Claude at claude.ai. In the left sidebar, you’ll see a “Projects” section. Click “Create project.” Name it something specific — not “My Business” but something like “Madeira Real Estate — Robson Consulting” or “Freelance Copywriting — [Your Name].” Specificity here keeps things organized when you eventually build multiple Projects for different parts of your work.

Give the Project a description too. One sentence is enough: “Primary workspace for client communications, property marketing, and market analysis in Madeira, Portugal.”

What the Project Interface Gives You

Once created, you’ll see two main areas: a “Project Instructions” panel (your system prompt) and a “Knowledge” section where you upload documents. Every conversation you start inside this Project automatically inherits both. This is the core mechanism that makes the whole thing work.

Step 2: Write Your Project Instructions (System Prompt)

This is the most important step. Most people write two sentences here and wonder why the output is mediocre. Your Project Instructions are the foundation of your knowledge base — treat them seriously.

Click “Edit” in the Project Instructions panel and build your prompt using this structure:

## Who I Am
[Your name], [business type], based in [location]. I've been [doing X] since [year]. 
I work solo with no staff. My business generates [rough revenue range or client volume] per year.

## My Clients
Primary clients: [describe in 2-3 sentences — demographics, where they're from, what they want, what worries them]
Secondary clients: [if applicable]

## My Services and Pricing
[List your core services with rough pricing. Be specific — Claude uses this to calibrate formality, length, and positioning in output.]

## My Voice and Tone
- [Adjective 1]: [brief explanation]
- [Adjective 2]: [brief explanation]
- I never use [specific phrases or styles you hate]
- My emails are typically [X] sentences long
- I write in [British/American] English

## My Most Common Tasks
1. [Task 1 — e.g., writing property listings for international buyers]
2. [Task 2 — e.g., drafting follow-up emails for cold leads]
3. [Task 3 — e.g., creating monthly market reports]

## Output Rules
- Always write in first person as me, not as "you"
- Match the tone of the specific task I describe
- When I say "draft," give me a complete ready-to-send version, not a skeleton
- Ask me clarifying questions only if you genuinely need them — don't pad responses with unnecessary questions
- Never use [your list of banned phrases]

Fill this in with real specifics. The more concrete you are, the better the output. A vague system prompt produces vague results.

Step 3: Upload Your Knowledge Documents

Click “Add content” in the Knowledge section. Claude accepts PDFs, Word documents, plain text files, and pasted text. You can upload up to approximately 200,000 tokens worth of content per Project — that’s a significant amount of material.

Here’s what to upload, in priority order:

Document 1: Your Voice Samples

Paste 3-5 examples of your best existing writing into a single document. Label each one: “Email to cold international lead,” “Social media post about market conditions,” “Property listing for luxury apartment.” These samples teach Claude your actual voice far better than any instruction you could write.

Document 2: Your Services and Pricing Document

A clean document listing every service you offer, what’s included, and what it costs. Claude uses this to write accurate proposals, answer client questions in your voice, and avoid suggesting services you don’t provide.

Document 3: Your Client FAQ

Every question you get asked repeatedly. Write out both the question and your standard answer. This document alone will save you hours — Claude can draft responses to common inquiries that sound exactly like you wrote them, because the answers came from you in the first place.

Document 4: Your Market or Industry Reference File

For real estate, this is neighborhood guides, typical buyer profiles, current market conditions. For a copywriter, it might be your client niches and typical campaign goals. This is what gives Claude contextual intelligence about your field, not just your business.

Step 4: Build Your Repeatable Task Prompts

Now start a new conversation inside your Project. Test three of your most common tasks with specific prompts. The goal here is to build prompt templates you’ll reuse constantly.

Here are the templates I use in my own Project — adapt them to your business:

PROPERTY LISTING PROMPT:
Write a property listing for the following. Use my standard voice. 
Target buyer: [nationality/profile]
Property type: [type]
Key features: [list 5-8 features]
Price: [price]
Unique selling point: [one sentence]
Length: approximately 200 words for the main description, 
then 5 bullet points for features.

LEAD FOLLOW-UP EMAIL PROMPT:
Draft a follow-up email to a lead who [describe their situation and last contact].
Their main concern was [concern].
My goal in this email is to [specific goal — book call, share a listing, answer a question].
Tone: warm but professional. Length: under 150 words.
Do not use a subject line — I'll write that separately.

MARKET UPDATE PROMPT:
Write a brief market commentary for [month, year] about [specific area or property type].
Key data points to include: [list your data]
Audience: existing clients who receive my monthly email
Length: 250-300 words
Tone: confident, informative, not alarmist
End with one clear takeaway sentence.

Save these templates somewhere you can paste them quickly — a Notion page, a text file on your desktop, anywhere accessible. The combination of the Project context plus a specific task prompt is where the real efficiency comes from.

Step 5: Test, Compare, and Refine

Run three real tasks inside the Project. Then run the same three tasks in a standard Claude conversation with no Project context. Compare the outputs side by side.

What you’re looking for:

Quality Signal	Without Project	With Project
Sounds like you	Rarely on first attempt	Usually on first attempt
Correct pricing / service details	Has to ask or guess	Already knows them
Appropriate length	Often too long or too short	Calibrated to your standards
Correct audience targeting	Generic	Specific to your client types
Edits needed before use	Significant	Minor to none

If the Project output isn’t clearly better, go back to your system prompt and make it more specific. Vague input produces vague output — that’s always the cause.

My Real-World Experience: 6 Months of Running My Real Estate Business Through a Claude Project

I set up my first real Claude Project in February 2026, after about three months of testing various configurations. Before that, I was using Claude regularly but starting every session cold — no context, no memory, just a blank chat where I’d spend the first 10 minutes re-explaining who I am and what I do before getting to the actual task.

My Project now contains seven documents: a voice samples file with examples of my best property descriptions and client emails, a detailed breakdown of Madeira’s key residential areas (Funchal, Calheta, Ponta do Sol, and the northeast), a buyer persona document separating my typical German, British, and Scandinavian clients by what they prioritize and what concerns them, my standard service and fee structure, a common objections FAQ, my social media style guide, and a list of properties I’ve sold in the last two years with brief notes on what worked in each listing.

The single biggest time saving came from property descriptions. In January 2026, before the Project was fully built, writing descriptions for 14 listings took me approximately 4.5 hours across the month — and I still had to do significant edits on most of the AI-assisted drafts because they kept sounding generic or getting Madeira-specific details wrong. In March, with the Project fully operational and my refined prompt template, I wrote descriptions for 11 listings in 55 minutes total. First-draft quality was good enough to send for client review without edits in 8 of the 11 cases.

That’s roughly 3.5 hours recovered in a single month from one task type alone. Across the full month of March — including email drafts, two market commentary pieces, and a batch of Instagram captions — I estimate I recovered about 7 hours compared to my previous workflow. For a solo operator, that’s a meaningful amount of capacity.

The qualitative shift mattered too. My client emails started sounding consistently like me from the first draft, because Claude had actual examples of how I write to clients. I stopped getting that slightly-off-brand feeling where the AI technically said the right things but in a way I’d never say them. The voice samples document did more for output quality than any instruction I could write.

One specific win: I had a German buyer who’d gone cold after three viewings in October 2025. I used the Project to draft a re-engagement email in late January that referenced the specific concerns he’d raised (renovation budget uncertainty), linked to a new listing in his target area, and opened the door for a call without pressure. He replied within 24 hours. We completed the transaction in April. I won’t say the email alone closed that deal — the right property showed up at the right time — but the email quality definitely reopened the conversation.

The Real Limitations I Hit During Testing

Claude Projects do not have memory between conversations in the way many people expect. The Project Instructions and uploaded documents persist, but the actual conversation history does not carry over from one chat to the next. If you discuss something important in Tuesday’s session, Wednesday’s session won’t know about it unless you add that information to your documents or paste it in manually.

This is a genuine friction point for ongoing client management. I wanted to use my Project to track where each lead was in the pipeline, but there’s no way to maintain a living record of client interactions inside Claude itself. I ended up keeping that in a separate CRM and just pasting relevant context into prompts when needed. It works, but it adds a step.

The knowledge document size also has practical limits. My full area guides for all of Madeira run longer than I’d like to upload, so I’ve had to summarize aggressively. Claude sometimes gives slightly less precise location-specific advice than I’d get if I could upload the full documents. Not a dealbreaker, but worth knowing.

And finally: this setup requires real upfront investment. The hour or two you spend building solid Project Instructions and gathering documents is not optional — it’s the entire reason the system works. If you rush through it, you’ll get mediocre results and conclude that Projects aren’t worth it. They are worth it, but only if you do the groundwork.

Troubleshooting Tips When Output Isn’t Clicking

Problem: The output still sounds generic. Solution: Your voice samples document needs more examples. Add at least five real pieces of writing. Labeled samples outperform any amount of instruction about tone.

Problem: Claude keeps asking clarifying questions instead of drafting. Solution: Add a line to your Project Instructions: “When asked to draft something, produce a complete draft first. Ask questions afterward if genuinely needed, not before.”

Problem: Output length is inconsistent. Solution: Specify length in every task prompt, not just in the system prompt. The task-level instruction overrides general preferences reliably.

Problem: Claude ignores specific details from your documents. Solution: Reference the documents explicitly in your prompt: “Using the buyer persona document in this Project, draft a listing description targeting a British retiree.” Direct references activate the right knowledge.

Problem: The Project Instructions feel too long and messy after several revisions. Solution: Every few weeks, rewrite your Project Instructions from scratch based on what you’ve learned. Don’t just patch the old version — a clean rewrite produces better results than accumulated edits.

Practical Summary: What to Do This Week

Day 1: Gather your raw material. Voice samples, services document, client FAQ. Don’t skip this.

Day 2: Create your Project and write your system prompt using the template in Step 2. Upload your documents.

Day 3: Run three real tasks using specific prompt templates. Compare output quality to what you were getting before. Note what’s missing.

Day 4-7: Refine your Project Instructions based on the gaps you found. Add one more document if needed. By end of week one, you should have a setup that cuts your most-repeated writing tasks by at least 50%.

The solopreneur advantage here is real. You’re not building a knowledge base for a team — you’re building one that represents a single person’s expertise, voice, and context. That’s actually easier to do well, and the output quality ceiling is higher because the target is more specific.

Claude Pro costs $20/month. If your first well-built Project saves you even two hours in month one — which is a conservative estimate — you’ve covered the cost several times over by any reasonable measure of your time.

If you want to see exactly what I put in my system prompt and documents, I’ve published the full template I use for my Madeira real estate business — grab it here and adapt it to your own operation.