How I Built a 6-Figure Agency Using Claude Projects

I ran a one-person real estate consultancy in Madeira for over a decade before I figured out something that most freelancers never do: the bottleneck was never the work itself. It was the context. Every client call, every new listing, every market report — I was rebuilding the same mental scaffolding from scratch. Claude Projects changed that for me in a way no other tool has, and by mid-2026 I had effectively built what functions as a small agency operation without hiring a single person.

This is the exact workflow I used. The results, the dead ends, and the one thing I’d do differently if I were starting over today.

The Problem That Was Quietly Killing My Productivity

For years I managed everything myself — client intake, property descriptions, buyer newsletters, WhatsApp follow-ups, Instagram captions, market analysis reports. It was manageable. Until it wasn’t.

By late 2023, I was spending roughly 14 hours a week on content and communications. Not doing deals. Writing about deals. I tested ChatGPT, Gemini, a handful of writing tools. They helped at the margins. But every conversation started cold. I’d paste context, explain who my client was, describe the Madeira market — then get a decent output that still needed heavy editing because the AI had no idea how I actually operated.

The real problem wasn’t generating words. It was that I had no persistent system. Every AI session was a new employee with amnesia.

What Claude Projects Actually Does (and Why It’s Different)

Claude Projects, part of Claude’s Pro plan at $20/month, lets you create separate project workspaces where you upload documents, set instructions, and have Claude retain that context across every conversation inside that project.

That sounds simple. The implications aren’t.

When I upload my brand voice guide, my standard property description template, a PDF of the current Madeira market data, and my client intake notes into a single project — every conversation I start inside that project already knows all of it. I don’t re-explain. I don’t re-paste. I just work.

For a solo operator, that’s the closest thing to having a trained assistant who never forgets a briefing.

The Projects I Built and What Each One Does

I currently run six active Claude Projects. Each one functions like a different department of a small agency:

• Listings Project: Contains my property description templates, Madeira neighborhood guides, standard photography brief, and Portuguese/English terminology reference. I feed it raw listing notes and get publication-ready descriptions in both languages.
• Client Comms Project: Holds my tone-of-voice guidelines, common buyer/seller objection scripts, and a FAQ document I’ve built over 14 years. I use it to draft emails, WhatsApp follow-ups, and offer letters.
• Market Reports Project: Loaded with current transaction data, INE housing statistics, tourism occupancy figures for Madeira, and my own quarterly observation notes. It produces first drafts of market reports I send to investor clients.
• Social Media Project: Contains my Instagram content calendar format, best-performing captions from the past 18 months, and brand hashtag strategy. I batch 30 days of captions in about 90 minutes.
• Lead Nurture Project: Email sequences, SMS templates, my typical sales timeline for foreign buyers in Madeira. Drafts entire follow-up sequences from a single intake note.
• Admin Project: Standard contracts language reference, NHR tax regime summaries for clients, Golden Visa update notes. Helps me draft FAQ responses and client briefing documents quickly.

My Real-World Experience: From Solo Consultant to Agency-Style Output

Here’s the specific moment I knew this workflow had actually worked.

In February 2026, I had a week where three separate investor clients requested full market reports simultaneously. Two were British buyers evaluating long-term rentals in Funchal. One was a German client comparing Madeira to the Algarve. Normally, writing three custom market reports would take me the better part of two full working days — roughly 10 to 12 hours of focused writing, research cross-referencing, and editing. I’d done it before and it nearly killed a weekend.

This time, I opened my Market Reports Project. My context was already loaded: Q4 2025 transaction data I’d uploaded the previous month, INE rental yield figures, my own notes from two site visits in January, and a report structure template I’d refined over six months. I wrote three prompts — one per client, each about four sentences — describing the client profile, their budget range, the specific neighborhoods they’d shortlisted, and the tone I wanted (conservative for the German client, opportunity-focused for the British buyers).

Claude produced three solid first drafts in under 20 minutes total. I spent another 90 minutes editing, adding my own observations, and customizing the conclusions. Total time: just over 2 hours for three reports that would have taken 10 to 12 hours in 2024. That’s roughly 8 to 9 hours recovered in a single week from one type of task.

What made it work wasn’t just Claude’s writing ability. It was the fact that the project already contained my framing for the Madeira market, my client communication style, and my report structure. I wasn’t prompting a general AI. I was prompting something that already knew how I think about this market.

I also use the Listings Project every week. In March 2026 I had 11 active listings. Writing descriptions in Portuguese and English used to take me about 25 minutes per listing — that’s over 4 hours. With the project loaded, I was averaging under 8 minutes per listing, including my edits. Total time that month for 11 listings: roughly 90 minutes. Time saved versus my old process: approximately 2.5 hours. Across a year, that compounds fast.

The lead nurture project has been the quietest win. I used to write follow-up email sequences manually, sometimes days after initial contact because I kept deprioritizing it. Now I paste in a client intake note and get a 5-email sequence in about 4 minutes. I review, adjust the personalization, and schedule it. My response-to-sequence time went from 2 to 3 days down to the same day, almost every time.

The Exact Setup Process I Used to Build Each Project

Getting a Claude Project working well takes about 2 to 3 hours of setup. Most people skip the setup and then wonder why outputs aren’t good. Don’t skip the setup.

Step 1 — Write a Project Instruction Document

This goes in the “Project Instructions” field at the top of each project. Mine run about 300 to 500 words. I include: my role and business context, the specific output format I want, tone guidelines, what I never want it to do (e.g., invent transaction data, use generic European market language instead of Madeira-specific detail), and a reminder of my target audience for that project.

Step 2 — Upload Your Reference Documents

Claude Projects lets you upload PDFs, Word docs, and text files. I upload: past examples of my best work in that category, data sources I reference regularly, templates and structure guides, and any client-specific background documents when starting a client-specific thread.

Step 3 — Run a Test Conversation and Refine

I start a test conversation inside the project and ask Claude to produce a sample output. Then I review what’s wrong — usually the tone is slightly off, or it’s missing a structural element I care about. I add that correction to the project instructions. I do this two or three times before I use the project for real work.

Step 4 — Refresh Documents Monthly

Data goes stale. I schedule 30 minutes on the first Monday of each month to update any market data or transaction figures in my projects. This keeps outputs accurate and means I’m not manually correcting outdated references in final drafts.

How This Compares to Other Approaches I Tried

Approach	Context Retention	Monthly Cost	Setup Time	Output Quality (My Use)
Claude Projects (Pro)	Persistent across sessions	$20	2–3 hrs per project	High — context-aware
ChatGPT Custom GPTs	Session-limited without memory add-on	$20	1–2 hrs per GPT	Medium — less nuanced writing
Standard ChatGPT/Claude (no projects)	None — resets each session	Free–$20	0 (but re-paste every time)	Medium — generic without context
Notion AI	Limited to current page	$10 add-on	Minimal	Low for complex outputs
Hiring a VA	High — if well-trained	€800–€1,500+	Weeks of onboarding	Variable

The VA comparison is the one I keep coming back to. I looked at hiring a part-time assistant twice in the past three years. The cost, the training time, and the coordination overhead never made sense for a one-person operation at my volume. Claude Projects at $20/month isn’t a replacement for every VA function — but for content and communications, it covers 80% of what I’d have hired for.

What Claude Projects Does Not Do Well

I want to be direct about this because I see a lot of enthusiastic coverage that skips the limitations.

Document size limits are a real friction point. Claude Projects has limits on how much you can upload per project. I hit this with my Market Reports Project when I tried to load two years of quarterly data PDFs alongside current reports. I had to selectively trim documents and keep only the most recent data, which means I sometimes miss historical comparisons I’d otherwise include. It’s manageable but it’s a genuine constraint that shapes what the system can do.

It doesn’t pull live data. If I want current property listings from the Madeira market, Claude can’t go get them. I have to manually update my reference documents. For a market that moves fast in certain micro-segments — Funchal centro, for example — there’s always a lag between reality and what my project knows.

Complex multi-step reasoning sometimes drifts. When I ask for outputs that require balancing several constraints simultaneously — say, a report for a client with unusual tax residency requirements combined with a specific financing structure — I sometimes get confident-sounding answers that subtly miss one of the constraints. I’ve learned to prompt in stages rather than expecting a single prompt to hold all the variables cleanly.

It’s not a CRM replacement. I made the mistake of thinking I could manage client tracking inside a Claude Project by keeping notes there. It doesn’t work. Claude isn’t building a searchable database of interactions — it’s holding context for conversations. Keep your CRM separate.

What I’d Do Differently Starting Today

I spent the first two months using Claude Projects too casually — opening sessions inside the project but still writing long context paragraphs in each prompt out of habit. I was duplicating effort. The shift that actually changed my output speed was writing tight, task-specific prompts and trusting the project context to fill in everything else.

If I were starting over in 2026, I’d set up the project instructions more carefully before doing any real work. The 3 hours I invested in each project instruction document paid back in the first week. The projects I rushed — my Admin Project, specifically — still produce outputs I have to edit more heavily. The quality of your project instructions directly determines the quality of your outputs.

I’d also connect the workflow to my scheduling tools earlier. Right now I batch social media captions in Claude and then manually paste them into my scheduling tool. That’s a step I keep meaning to automate through Make.com but haven’t yet. Leaving it on the table.

Practical Summary: How to Build Your Own Agency-Style Workflow

1. Audit your recurring tasks. List every content or communication task you do more than twice a month. Those are your project candidates.
2. Start with one project, not six. I built six over about four months. Start with the task that costs you the most time right now.
3. Write project instructions seriously. Treat it like a brief to a new contractor. Include context, format requirements, tone, and hard rules about what to avoid.
4. Upload your best existing work as examples. Claude learns from examples better than from abstract instructions. Show it what good output looks like in your voice.
5. Schedule a monthly document refresh. Stale data is the main reason outputs start degrading over time.
6. Keep your CRM and your Claude Projects separate. One is for conversations and content. The other is for relationship tracking.

The honest outcome after 14 months of running this: I recovered roughly 6 to 8 hours per week across all six projects. That’s time I now spend on client relationships and viewings — the parts of this business that actually require a human in the room. My output volume roughly doubled. My content quality improved because I stopped rushing. And I’m still doing this alone, which is how I prefer it.

Claude Pro costs me $20/month. The time it saves me every week is worth several times that — and I say that as someone who was skeptical of AI tools until I actually tested them systematically.

If you’re a freelancer or solo operator thinking about whether Claude Projects is worth setting up, the honest answer is: yes, but only if you do the setup properly. Half-built projects give you half the value. Do it once, do it right, and it runs itself.

If you want to see exactly how I structured my Listings Project instructions — including the full template I use for bilingual property descriptions — subscribe to the Solo AI Kit newsletter. I share the actual documents, not just the concepts.