Claude Project: Build a Shared Team Knowledge System for Your Leasing Office

What This Builds

A shared Claude Project that acts as your entire leasing office's institutional memory: not just a drafting tool, but a searchable knowledge base containing your policies, scripts, objection rebuttals, resident history context, and communication templates. Any team member can ask it a question and get an accurate, on-brand answer instantly. New team members onboard in hours instead of weeks.

Prerequisites

• Claude {{tool:Claude.plan}} subscription ({{tool:Claude.price}}; Projects require the paid tier)
• Your key leasing documents: community policies, pet addendum, parking addendum, lease FAQ, renewal scripts
• The building blocks from the Level 3 Claude guide (basic Project setup familiarity)
• 1 hour to gather and organize your community documents

The Concept

Most leasing offices have their knowledge scattered across binders, email threads, sticky notes, and the memory of whoever has worked there longest. A Claude Project with your documents uploaded becomes a shared, searchable, always-available knowledge base. Ask it "What's our policy on early lease termination?" and it answers from your actual lease addendum, not from general knowledge. The entire team asks it the same questions and gets consistent answers, which means consistent information to prospects and residents.

Build It Step by Step

Part 1: Gather and organize your leasing documents

Before building, collect these documents in digital format (PDF or Word/Google Doc):

Essential uploads:

1. Community Fact Sheet / Property Overview (unit types, amenities, pricing ranges)
2. Pet Policy Addendum (breeds, weights, deposits, pet rent)
3. Parking Addendum or Policy (options, costs, waiting lists)
4. Application Requirements & Qualification Criteria
5. Move-In Checklist and Welcome Materials
6. Current Lease Renewal Script or FAQ
7. Online Review Response Guidelines (if your company has them)
8. Common Prospect Objections and Rebuttals (create this as a Word doc if you don't have it)

Nice to have:

• Floor plan descriptions with square footage for each unit type
• Local neighborhood guide (restaurants, transit, schools, parks)
• Current specials and marketing materials

Format tip: PDFs work well; Google Docs can be exported as PDF. Don't upload image files (photos). Claude reads text, not photos.

Part 2: Create the Project and configure it for team use

1. Log into Claude at {{tool:Claude.url}}
2. Click Projects in the left sidebar → Create project
3. Name it: "[Community Name] Leasing Office: Knowledge Base"
4. Click Edit project instructions

Write instructions that set the scope for team use:

You are the official AI knowledge assistant for [Community Name]'s leasing team.

## Your Purpose
You help leasing consultants answer questions, draft communications, and
onboard new team members — all grounded in [Community Name]'s actual policies
and materials, which are uploaded in your knowledge files.

## Priority Order for Answers
1. If the answer is in an uploaded document: quote or summarize directly from it
2. If the answer is not in documents but is a general leasing best practice: answer and note the source
3. If the answer requires a management judgment call: say "This needs manager approval — I can help you draft the question to ask."

## What You Help With
- Policy questions: "What's our policy on X?"
- Communication drafting: prospect emails, resident letters, review responses
- Objection scripts: "How do I respond when a prospect says X?"
- New team member training: explaining our processes and community details
- Compliance questions: flag anything that should go to management or legal

## Tone
Match the question type: formal for policy questions, warm and on-brand for
prospect/resident communications. Never guess on legal or compliance questions
— always recommend manager or legal review.

## Community Details (key facts — full details in uploaded documents)
[Paste your core community details here as a backup reference]

Part 3: Upload all your documents

1. In the Project view, look for the Files section (usually a paperclip icon or "Add files" button in the left panel)
2. Click Add files and upload each document you gathered in Part 1
3. Wait for each upload to process (you'll see a checkmark when done)
4. After all uploads, test by asking: "What is our pet policy?" Claude should answer from your actual policy document, not from generic knowledge

What you should see: Accurate, document-specific answers that reference the correct breeds, weights, deposits, and pet rent from YOUR policy.

Troubleshooting: If Claude gives a generic answer instead of document-specific, try: "Based on our uploaded pet policy addendum, what breeds are restricted?" Being specific about the document source helps Claude reference it accurately.

Part 4: Build your objection rebuttal library

This is the most valuable piece most leasing offices don't have in writing:

1. In a new Project conversation, type:

I'm going to give you our top 10 most common prospect objections. For each one,
write a natural-sounding, confident rebuttal that fits [Community Name]'s
communication style. Ground each rebuttal in a real benefit or amenity from our
community fact sheet.

Objections:
1. "The rent is higher than other places we've looked at."
2. "The unit is smaller than we thought."
3. "We want to think about it / we're not ready to decide."
4. "We're also looking at [competitor neighborhood or property]."
5. "We'll need to break a lease to move here."
6. [Add your top 5 local objections]

1. Review the output and refine each rebuttal with your actual experience of what works
2. Save this as a Google Doc titled "Objection Rebuttals: [Community Name]" and upload it to the Project
3. Now any team member can ask: "How do I respond when a prospect says our rent is too high?" and get a calibrated, community-specific answer

Part 5: Create an onboarding conversation for new team members

Build a structured onboarding flow by typing this into the Project:

Create a new leasing consultant onboarding guide for someone starting at
[Community Name] next week. Cover:
1. The top 10 things they need to know in their first week
2. How to handle the 5 most common prospect interactions
3. Our community's biggest selling points (draw from the uploaded fact sheet)
4. Our pet and parking policies (summary only)
5. What to do when they don't know the answer

Format it as a quick-reference card they can keep at their desk.

Save this output as a printed document for your welcome packet.

Real Example: New Leasing Consultant, Week One

Setup: Your Claude Project has all community documents uploaded and the objection rebuttal library saved.

Monday: New consultant Jordan starts. Instead of shadowing for 2 weeks, you share the Project link and have them spend 2 hours asking the AI questions: "What's our pet policy?" "What do I say when someone says it's too small?" "Walk me through the application process."

Wednesday: Jordan is on a tour. Prospect asks about the lease break policy and they're not sure. That evening: "What's our early termination clause?" Claude answers from the actual lease addendum. Jordan emails the prospect the correct info before 9am Thursday.

Friday: Jordan handles a negative Google review solo. They ask the Project: "Help me write a response to this review: [paste review]" and get an on-brand draft in 30 seconds that sounds like it came from a 5-year veteran.

Time saved: New consultant productive in 3 days instead of 3 weeks. Quality benefit: Consistent, accurate information to every prospect and resident.

What to Do When It Breaks

• Claude answers from general knowledge instead of your documents → Add to your instructions: "Always prioritize uploaded documents over general knowledge. If a document is relevant, quote from it." Then ask specifically: "Based on our uploaded pet policy, what is the deposit amount?"
• Team members get inconsistent answers → Check if your instructions are specific enough about what "accurate" looks like; add example questions and ideal answers to the instructions for calibration
• Documents are outdated after a policy change → Delete the old document from the Project files, upload the new version, and update your instructions if key details changed. Set a quarterly reminder to audit
• New team members don't know how to use it → Build a one-page "How to Use Our Leasing AI" guide and include it in your welcome packet

Variations

• Simpler version: Start with just the Pet Policy and Application Requirements uploaded. These are the two most-asked-about policies; you don't need every document on day one
• Extended version: Build a second Project specifically for resident relations (separate from prospect leasing). Upload your lease, maintenance request procedures, and renewal escalation process

What to Do Next

• This week: Create the Project, upload your 5 core documents, and test policy questions with your team
• This month: Upload the objection rebuttal library and use it to train new team members; track whether policy question consistency improves
• Advanced: Coordinate with your regional manager to build a portfolio-wide version that all properties under your management share, with community-specific addendums for each property

Advanced guide for leasing consultant professionals. These techniques use more sophisticated AI features that may require paid subscriptions.