Activity
Mon
Wed
Fri
Sun
Jun
Jul
Aug
Sep
Oct
Nov
Dec
Jan
Feb
Mar
Apr
May
What is this?
Less
More

Memberships

Clief Notes

31.5k members โ€ข Free

2 contributions to Clief Notes
๐Ÿ† WEEKLY COMP #4: THE AGENCY ๐Ÿ†
๐Ÿ’ฐย $325 CASHย ๐Ÿ’ฐ That's a full year of Premium. Win this and your membership pays for itself. But the real prize this week isn't the cash. Keep reading. ๐Ÿ“‹ย THE CHALLENGE You just got hired again. Meet Diana, owner of a 4-person boutique real estate team in Austin. 60-80 transactions a year, mostly residential, mix of buyers and sellers. ๐Ÿ“Ž Download the full client brief attached to this post. Short version: She doesn't want software. She wants aย systemย she can teach her team to use in a week. Your job is to build the AI operating system for her team. This isn't one specialist. This is a small team of AI specialists organized into a multi-folder ICM architecture, with a clear handoff protocol between them. ๐Ÿ—‚๏ธย WHAT YOU'RE BUILDING Last week was one specialist. This week is a team of them. Required folders: ๐Ÿ“ย 00_orchestrator/ย โ€” The router. Where every request starts. Decides which specialist gets the job. ๐Ÿ“ย 01_lead_qualifier/ย โ€” First contact with new prospects. Captures intent, budget, timeline. ๐Ÿ“ย 02_property_research/ย โ€” Deep research on specific properties or neighborhoods. ๐Ÿ“ย 03_client_communication/ย โ€” Drafts emails, texts, follow-ups in the voice of the agent. ๐Ÿ“ย 04_transaction_coordinator/ย โ€” Handles the deal once it's live. Checklists, deadlines, document tracking. Each folder must include: - ๐Ÿ“„ identity.md - ๐Ÿ“ rules.md - ๐Ÿ’ฌ examples.md - ๐Ÿ”— handoff.md (NEW for Week 4 โ€” how does this folder pass work to another folder?) - Plus a root-level README.md explaining the architecture, the typical flow, and how to onboard a new team member. ๐Ÿ”ฅย WHY THIS ONE IS DIFFERENT Weeks 1, 2, and 3 were warmups. This is the comp where the work you ship genuinely starts to look like the real thing. The handoff protocol is the test. Anyone can build five folders. The hard part is defining what each one needs from the previous one and what it passes to the next one. That's where multi-agent systems actually live or die.
4 likes โ€ข 6d
๐Ÿ› ๏ธ What you built I built the multi-agent real estate operating system for Diana's Austin team, as requested, using Claude Code. Repo: https://github.com/ivancalvo-dbxs/2026-skool-clief-weekly-4 ๐ŸŽจ Two design decisions you made and why - Database folder: A database is always required to evaluate and test the interactions. YOU CAN'T MAKE APPS WITHOUT DATABASES ๐Ÿ”ฅ๐Ÿ”ฅ๐Ÿ”ฅ. - Commands: Each agent can be invoked with a command (i.e.,/qualify-lead /research-property) in case someone wants to skip the router, isolated executions or just unity testing (FREE WILL FOR USERS). โž• Things you'd add if you had another week - Print the results as HTML or Markdown in the browser. Non-technical users would appreciate having this available because the CLI can be intimidating sometimes. - Real DB integration. Databricks Lakebase would have been my choice ๐Ÿ”ฅ. - Real Gmail integration.
Welcome to Clief Notes. Here's where to start.
1. Watch the intro video and introduce yourself in the intro post here 2. Start with The Foundation (free course). Concepts, folder architecture, prompting framework. Everything else builds on this. 3. Check in at the bottom of each lesson. Polls, discussion posts, other members working through the same stuff. Use them. 4. When you're ready to build real things, move to Implementation Playbooks (Level 2). When you're ready to build your own tools, Building Your Stack (Level 3). 5. Post your work. Ask questions. Help others when you can. What are you here to build?
Poll
5516 members have voted
0 likes โ€ข 6d
Hello everyone! Happy to be here. I 100% agree with the takes that Jakes have on AI. Let's build awesome projects together!
1-2 of 2
Ivan Calvo
1
1point to level up
@ivan-calvo-7204
Lead Scale Solutions Engineer at Databricks

Active 6h ago
Joined May 12, 2026
Powered by