There's a gap between using Claude to write a listing description and using Claude to run the operational side of your business. This workshop is the bridge.
We treat Claude not as a writing assistant but as an operational counterpart — a system that holds context across days, flags slippage, and keeps your follow-up tight without you babysitting a CRM.
What we cover
- Project architecture: one Project per active listing, one per buyer pipeline, one per sphere — with custom system prompts that change Claude's behavior per context.
- The "60-second debrief" pattern: every showing, every call, every offer round captured into the right Project with a structured summary you can search later.
- Weekly review prompts that summarize what moved, what stalled, and what you committed to but never did.
- File hygiene: when to upload, what to upload, and what to never upload (legal and privacy boundaries).
- Handoff patterns: how to brief a TC, a stager, an inspector, or a lender from a Project's context in one paste.
How the time breaks down
First hour: Project architecture and system prompts. Middle hour: debrief and weekly-review patterns against real pipelines. Final hour: cross-context handoffs and the small habits that compound.
Who shouldn't take this
If you're still in your first month of Claude, take Claude Basics first.