Tool Guide

Working with Claude

Claude is wired into everything on this platform — the company brain, the document drafters, and the code the tools are built from. It doesn’t just answer questions: you can tell it things and ask it to make changes, and it carries them out. This guide covers the three ways to put it to work.

01The brain — ask it, and update it

The Henry Brain is the shared company knowledge base: people, properties, deals, playbooks, and how-we-do-things — built from Henry Group’s files and email, readable by everyone on both sides of the house. In Claude (claude.ai) with the Henry Brain connector on, just ask:

Ask “What do we know about Hampden Plaza?”  ·  “What’s our standard TI allowance on new leases?”  ·  “Who handles vendor COIs?”  ·  “How do I stage a Mailchimp campaign from the CRM?”

The brain is read-write. When something new happens, tell Claude and it records it — properly filed, dated, and attributed — so the next person who asks gets the current answer:

Update “Record that the Johnstown Plaza roof bid came in at $84k from Arvada Roofing”  ·  “File what we learned on the 300 S Logan listing”  ·  “That’s out of date — the insurance carrier changed to Westfield; fix it”
  • Corrections are how the brain stays right. If an answer is stale or wrong, say so in the same chat — Claude updates the page and notes what changed.
  • It keeps its own rules: facts carry dates and sources, nothing secret (passwords, bank details, SSNs) is ever written, and raw files stay where they live — the brain stores the distilled fact plus a pointer.
  • Wrapped up a piece of work? Ask Claude to “crystallize” it — a dated digest lands in the brain so a teammate can pick up where you left off.

02Drafting documents

Claude drafts LOIs and purchase contracts on request — “Draft an LOI for Bright Crown Massage at 10005 E Hampden Ave” — pulling county records and the brain the same way the Transaction Management tool does, and replying with a download link (good for about 24 hours). It only drafts when you ask, and nothing is ever sent on your behalf. Details in the transactions guide.

03Reading the code — the GitHub connector

The tools themselves are code, stored in GitHub — the industry-standard home for software, where every change is tracked, attributed, and reversible. With the GitHub connector on in claude.ai, Claude can read that code and explain it in plain words:

Ask “Why does the CRM require a tag on every new contact?”  ·  “What exactly happens when I press Stage in Mailchimp?”  ·  “Which counties does the property search cover?”

Reading is chat’s job; changing the code happens in Claude Code — next section.

04Changing the tools yourself

Want the CRM in a different color, a column renamed, a new clause in the LOI template’s defaults? You don’t file a ticket — you describe the change to Claude Code (Claude’s builder — at claude.ai/code in the browser, or the terminal app for the technically inclined) and it does the work. Each tool lives in its own repository under github.com/HenryGroupRealEstate:

ToolRepositoryWhen a change is merged
CRMHenryGroupRealEstate/crmGoes live on crm.hre.realzono.com automatically, ~2 minutes
Transaction ManagementHenryGroupRealEstate/contract-drafterGoes live on tc.hre.realzono.com automatically, ~2 minutes
This portalHenryGroupRealEstate/hubDeployed by RealZono after merge
  1. Open Claude Code on the repo At claude.ai/code, connect your GitHub account once, then pick the repository (say, crm).
  2. Say what you want, in plain words “Make the CRM’s design scheme blue.”  “Rename the ‘Pitching’ status to ‘Proposal’.”  “Add a fax label option for emails.” Claude finds the right files, makes the edits, and explains what it changed.
  3. It opens a pull request A pull request (PR) is a proposed change waiting for approval — nothing is live yet. Claude writes up what it did and why.
  4. Review and merge Read the PR summary (ask Claude to walk you through it if anything’s unclear), then press Merge. For anything beyond cosmetics, have a second set of eyes — or RealZono — look first.
  5. It ships itself Merging to the CRM or Transaction tool deploys to production automatically — reload the site a couple of minutes later and your change is live.
Fair game vs. ask first Colors, wording, labels, layout, defaults — go for it. Anything touching sign-in, the database, money, or integrations (Mailchimp, email intake, county data, the brain) deserves a message to RealZono first. And every merge is reversible: the full history is kept, and RealZono can roll production back in one click — so a bad color choice is never a crisis.

05Getting set up

Everything in §1–§3 works from claude.ai with the connectors switched on. To change the tools (§4) you need, one time:

  • A GitHub account (free, github.com) — then ask RealZono to invite it to the HenryGroupRealEstate organization with access to the repositories.
  • Claude Code — sign in at claude.ai/code with your Claude account and connect GitHub when prompted.
  • That’s it — no passwords or keys change hands. The deploy pipeline already holds its own credentials.

Questions, access requests, or something looks wrong after a change → RealZono (nick@realzono.com).