Claude Projects for real estate agents: stop repeating yourself every chat
If you explain your business to Claude at the start of every chat, a Project fixes that. Set your details, voice and rules once, and every chat inside it already knows them.
You're explaining your business to Claude every single time. Stop.
If you've been using Claude for a few days, you've probably noticed a pattern. You open a new chat, and before you can ask for anything useful you're typing the same background again. Who you are. Where you work. What you sell. How you like things written. What it must never do.
Then you close that chat, open a new one tomorrow, and do it all again.
There's a better way, and it's built into Claude. It's called a Project.
What a Project actually is
A Project is a space in Claude that remembers who you are. You put your business details, your voice and your rules in once, and every chat you start inside that Project already knows them.
Think of it like briefing a new assistant. You wouldn't re-explain your whole business to them every morning. You'd tell them once on day one, and from then on they'd just get on with it. A Project gives Claude that same day-one briefing, and it keeps it.
A Project usually has two parts:
- Instructions. A short written briefing that applies to every chat in the Project. Who you are, how to write, what the rules are.
- Files. Documents you add for Claude to refer to across those chats. Optional, and worth keeping tight, which I'll come back to.
Inside the Project you can start as many chats as you like. Each one starts with the briefing already in place.
Why this matters in an agent's week
So much of what we ask Claude to do depends on context. A listing description, a follow-up email, a social post, an appraisal summary. All of them come out better when Claude knows where you work, who you're writing for and how you sound.
Without a Project, you either retype that context every time or skip it and get something generic. Generic is the problem. It reads like it could have come from any agent in any city, and you end up rewriting it yourself.
With a Project, the context is already there. You can open a chat and just say "write a follow-up to someone who came through the open home on Saturday", and Claude already knows your area, your tone and your rules.
It also means your rules stay consistent. If you've told it never to make up a price, that rule is in place for every chat in the Project, not just the ones where you remembered to say it.
If you did yesterday's episode on making Claude sound like you, this is where that work earns its keep. Your voice notes belong in your Project instructions, so they apply everywhere.
The Day 4 prompt
This one is a little different. It's not something you paste into a chat. It's the starting text for your Project instructions.
I'm a real estate agent with eXp Realty in Adelaide's north-east. I sell family homes in suburbs like Redwood Park, Modbury and Golden Grove. Write in plain Australian English, warm but direct. Never invent prices, dates or facts; ask me if you don't know.
It's short on purpose. Four sentences, and each one is doing a job.
"I'm a real estate agent with eXp Realty in Adelaide's north-east." This tells Claude who you are and where you work. Swap in your own brokerage and area. Now it isn't guessing whether you're in Sydney, Texas or London.
"I sell family homes in suburbs like Redwood Park, Modbury and Golden Grove." This tells it what you sell and who you're likely writing for. Use your own suburbs and property types. If you mostly sell units to investors, say that instead.
"Write in plain Australian English, warm but direct." This sets the voice. Australian spelling, no American phrasing, and a tone that fits how agents actually talk to clients. Change the adjectives to match you.
"Never invent prices, dates or facts; ask me if you don't know." This is the most important line. Claude is good at filling gaps, and in real estate a filled gap can be a wrong price, a wrong settlement date or a feature the property doesn't have. This line tells it to stop and ask instead. Keep it, whatever else you change.
Once this is in, you can add to it over time. Your sign-off. Words you never want used. How you format emails. Treat it as a living briefing, not a one-off.
Try it yourself
This takes about five minutes.
- Open Claude and find Projects. In the Claude app or on claude.ai, look for Projects in the sidebar. Availability can depend on your plan, so if you can't see it, check your plan details.
- Create a new Project. Call it something clear, like "My Real Estate Business".
- Open the Project instructions. There's a place in the Project to set instructions. That's where your briefing goes.
- Paste the Day 4 prompt and change the details to match your business. Your brokerage, your suburbs, your property types, your voice.
- Save it, then start a new chat inside the Project. Ask for something ordinary, like a short email to a buyer after an inspection. Don't give it any background.
- Read what comes back. Check it's used Australian spelling, sounds like you and hasn't made up anything it couldn't know. If it asks you a question instead of inventing a detail, that's the rule working.
- Compare it. Start a normal chat outside the Project and ask the same thing. Put the two side by side. You'll see what the briefing is doing.
If something in the result isn't right, don't fix it in the chat. Fix it in the instructions, so every future chat gets the improvement too.
Keep the Project tight
The same safety habits from Day 1 apply here, with a Project-shaped twist.
- Be careful what files you add. Anything you add to a Project is available to every chat inside it. Start with general material, like a style guide or a description of your services, not client files. As agents we hold a lot of personal information, and the rules for handling it depend on where you work. If it isn't in the Project, Claude isn't reading it.
- One Project per purpose. It's tempting to build one giant Project for everything. A focused Project with a clear purpose gives cleaner results, and it's easier to see what's in it.
- When you give it a job with your files, still use one narrow folder. A Project briefing doesn't change that. Add the one folder for the job, never your whole computer.
- Keep approvals on for anything that sends, spends or deletes, so nothing goes out or disappears without you saying yes.
- End bigger jobs with "show me your plan first". Even with a good briefing, you want to see what it intends to do before it does it.
Your instructions are a good place to put these rules too. A line like "always show me your plan before changing any files" will apply to every chat in the Project.
Where to go from here
A Project is one of the simplest changes you can make, and it changes every chat after it. Set it up once, then keep improving the instructions as you notice what Claude gets wrong or what you keep having to repeat.
If you find yourself typing the same thing into a chat twice, that's your signal. It belongs in the Project.
Missed yesterday? Day 3: Make it sound like you
Every prompt from the series is on my free prompts page, with a new one each day as the episodes go up, ready to copy.