Claude, set up for a rep

Which plan for which rep

Prices below are what Anthropic's own pricing page listed on 2026-09-03. verified Every Claude fact in this chapter comes from that same pricing page and Anthropic's support documentation, not from any builder-specific source. verified

Team's data behavior is the detail worth knowing before you ask your builder for a seat: chats on Team are never used for training regardless of any toggle, the opposite default from Free, Pro, and Max, which puts the training decision in the rep's own hands. verified

The community file becomes a Project

Your community file from Chapter 01 is the fact sheet Claude should never need reminded of. A Project turns it into standing knowledge instead of something re-explained every conversation. Projects are self-contained workspaces with their own chat history and knowledge base, available on every plan, though Free is capped at 5 projects. verified

1. In claude.ai, open Projects and choose Create project. Name it something recognizable, for example "[Community name] Sales Desk."
2. Open Project knowledge and add the community file: current price sheet, plan list, lot status, and incentive terms, as a file you upload yourself, not an export pulled from the CRM.
3. Add your builder's disclosure requirements from Chapter 05 and Chapter 09 (RESPA AfBA disclosure language, any state-required public report language) as their own file, so Claude checks against the real wording rather than a general guess.
4. Add the fair housing word list from Chapter 04 and Chapter 09, so anything drafted for a buyer or an agent gets checked before you see it.
5. Open Project settings and paste in project instructions. Use the block below as a start and edit the bracketed parts.

You are helping [Rep name], a new-home sales counselor (or OSC) for [Builder's full legal name] at [Community name].

Ground every answer in the attached community file, disclosure list, and fair housing word list before you improvise anything.

Never quote a rate or payment. Point to the affiliated lender or an outside lender for any number tied to financing.
Never promise a completion date. Use "estimated" language only, and only with a date I've given you from the current schedule.
Never state a school assignment as guaranteed. Point the buyer to the district's own boundary lookup instead.
Always name the builder's full legal name, [Builder's full legal name], not a nickname or a community brand name alone, in anything client-facing.
Always add the preferred-lender disclosure line whenever an incentive tied to the builder's affiliated lender is mentioned: state plainly that using an outside lender is allowed and does not forfeit the incentive unless the incentive terms say otherwise, and that I am not required to use the affiliated lender.
Never send an email or text on my behalf. Draft it, then stop and let me send it.
Never write to the CRM or any builder system without me reviewing the change first.
Never work from an exported buyer record or registrant list unless I've told you my builder gave written IT or compliance approval for that specific use.
If a task touches financing eligibility, a completion date, or anything a qualified professional should confirm, flag that before it reaches a buyer or an agent, and that AI was used in drafting it.

That block is written to match the pattern the rest of this guide holds to everywhere financing, dates, and school assignments come up: those are the three ways a rep's own draft can turn into a promise the builder or the lender didn't make.

Connectors that apply

A connector lets Claude read, and with your approval write to, a service you already use. The Google connectors are available on every plan, not just paid ones. verified No builder CRM named in Chapter 02, Lasso, Hyphen CRM, Sales Simplicity, or Sales1440, has an official Claude connector; the honest path is CSV in, drafts out, the same as the export rule in Chapter 02.

Zapier and Make only belong in this list at all if your builder's IT specifically approves connecting a builder CRM through them; absent that approval, treat both the same as any other tool touching buyer data, gated by the same written answer Chapter 02 asks for.

The twelve rep workflows

Trigger, tools, exact steps, what stays human, one per line, with the chapter where the full procedure lives.

1. Community file to Project (Chapter 01). Trigger: you're setting Claude up for the first time, or a new plan or price sheet replaces the last one. Tools: Projects. Steps: create the Project, upload the current community file, add the disclosure and fair housing lists, paste in the project instructions block above, confirm the old price sheet is removed from Project knowledge so nothing stale gets referenced. What stays human: the community file's contents and every fact in it come from you, not Claude.
2. First-reply draft for a web lead (Chapter 03). Trigger: a new lead lands from the builder site, NewHomeSource, Zillow, Realtor.com, Homes.com, or chat. Tools: Gmail connector or your own notes, the Project. Steps: Claude reads what the lead asked for (from the lead-comments field or your own notes, never a bulk export), drafts a personalized first reply referencing the plan or community, and flags anything unverified. What stays human: you confirm current price and availability before sending, and you send it yourself.
3. Appointment confirmation and reminder drafts (Chapter 03). Trigger: an appointment is booked. Tools: Calendar connector, the Project. Steps: Claude drafts a confirmation with the appointment time, community, and what to bring, then a reminder draft for the day before. What stays human: you verify the appointment details against your own calendar and send both messages yourself.
4. Be-back follow-up draft (Chapter 04). Trigger: a visitor leaves without buying and is logged in the traffic log as a be-back. Tools: the traffic log entry, the Project. Steps: Claude drafts a follow-up referencing what the visitor specifically liked or asked about, based on your own notes from the visit. What stays human: you review and send it; nothing goes out from a be-back note Claude wasn't shown directly by you.
5. Traffic log summary for the Monday meeting (Chapter 04). Tools: the week's traffic log, the Project. Steps: Claude summarizes visitor count, registered versus unregistered, agent-accompanied versus not, and be-back status, into a short summary for the Monday meeting. What stays human: you verify the summary against the actual log before presenting it.
6. Incentive explainer inside the rules (Chapter 05). Trigger: a buyer asks what an incentive actually covers. Tools: the Project, with the current incentive terms attached. Steps: Claude drafts a plain-language explanation of what the incentive requires, whether it's tied to the affiliated lender, and adds the preferred-lender disclosure line automatically per the project instructions. What stays human: you confirm the incentive terms are current before repeating any of it to a buyer.
7. Purchase agreement walkthrough script (Chapter 05). Trigger: you're prepping for a contract signing. Tools: the Project, the builder's own agreement template. Steps: Claude drafts a plain-language walkthrough script covering each section a buyer will sign, without drafting or altering any actual contract language. What stays human: the agreement itself, every blank filled, and the signing meeting, none of which Claude touches directly.
8. Agent FAQ and co-op confirmation email (Chapter 06). Trigger: a buyer's agent asks about registration policy or co-op terms. Tools: the Project, with current co-op terms attached. Steps: Claude drafts a plain-language FAQ answer and a co-op confirmation email restating the terms in writing. What stays human: you confirm current co-op terms with your sales manager before the email goes out, since terms vary by community and change without notice.
9. Weekly hotsheet to agents (Chapter 06). Trigger: this week's inventory snapshot is ready. Tools: the community's price and inventory sheet, the Project. Steps: Claude drafts the weekly hotsheet format: new homes, price cuts, homes gone, open houses, and current incentive, built as a forwardable one-page note for agents, following the shape of a working per-rep hotsheet built from a snapshot diff of a builder's own inventory workbook. operator What stays human: you verify every line against this week's actual sheet before it goes to a single agent.
10. Weekly buyer construction update (Chapter 07). Trigger: a buyer under contract reaches a new construction milestone. Tools: the construction schedule you've been given, the Project. Steps: Claude drafts a short, dated progress update in plain language, using only estimated-date language per the project instructions. What stays human: you confirm the actual milestone against the schedule before sending, and never let a draft promise a completion date.
11. Walkthrough prep and punch list summary (Chapter 07). Trigger: a pre-drywall or final walkthrough is scheduled. Tools: the Project, your own walkthrough notes. Steps: Claude drafts a prep checklist before the walk and organizes your handwritten punch list notes into a clean, dated summary afterward. What stays human: identifying every punch list item in person; Claude only organizes what you already found.
12. Review request and referral ask drafts (Chapter 07). Trigger: a buyer closes and receives keys. Tools: the Project. Steps: Claude drafts a short, personal review request and a separate referral ask, referencing the specific home and community. What stays human: you personalize and send each one yourself; no draft goes out as a form letter.

What stays human

• Every send: email, text, CRM entry, contract field. Claude drafts; you send.
• Any quoted rate, payment, or completion date, and any statement about a school assignment.
• Whether an exported buyer record or registrant list may touch Claude at all, gated on your builder's written IT or compliance answer.
• Which Claude plan, connectors, memory, and training settings are turned on.
• Current price, incentive, and co-op terms, verified against the actual sheet every single time, never assumed from last week.
• Signing into any builder CRM yourself, in a browser profile Claude in Chrome uses and nothing sensitive shares.

Do this today

1. Pick a plan from the table above and confirm your memory and training settings match what you decided.
2. Create the Project, attach the community file, disclosure list, and fair housing word list, and paste in the project instructions block.
3. Send the IT and compliance checklist from Chapter 02 today if you have not already, and wait for a written answer before any exported buyer record touches Claude.

Sources

1. claude.com/pricing, retrieved 2026-09-03
2. claude.com/pricing; support.claude.com/en/articles/9267247, retrieved 2026-09-03
3. anthropic.com/news/updates-to-our-consumer-terms, retrieved 2026-09-03
4. support.claude.com/en/articles/10166901-use-google-workspace-connectors, retrieved 2026-09-03
5. zapier.com/mcp; docs.zapier.com/mcp/clients/claude, retrieved 2026-09-03
6. developers.make.com/mcp-server; help.make.com/make-mcp-server, retrieved 2026-09-03
7. claude.com/claude-in-chrome; support.claude.com/en/articles/12012173-getting-started-with-claude-in-chrome, retrieved 2026-09-03
8. support.claude.com/en/articles/12902446-claude-in-chrome-permissions-guide, retrieved 2026-09-03
9. support.claude.com/en/articles/12902428-use-claude-in-chrome-safely, retrieved 2026-09-03
10. support.claude.com/en/articles/9517075-what-are-projects, retrieved 2026-09-03
11. support.claude.com/en/articles/11817273 (memory), retrieved 2026-09-03
12. anthropic.com/legal/aup (Usage Policy, high-risk use and impersonation), retrieved 2026-09-03
13. Operator evidence: a Phoenix buyer's agent who builds inventory tools for builder reps, weekly per-rep hotsheet built from a snapshot diff of a builder's inventory workbook, 2026-09-02

← Previous  ·  All chapters  ·  Next →

STARTER PACK · 7 WORKSHEETS

Get the starter pack as one download.

Keep the whole from-zero sequence together when you are ready to work it.

Email address Send the starter pack →

Instant pack link. Occasional field notes. Unsubscribe anytime.