We Built a Grok Bot for Realtors. Here It Is.

This summer we did something that took us months of internal argument: we packaged the realtor-facing manager workflow that runs inside Homies—the profile, the skills, the guardrails, the approval behaviour—and published it as a free shared Grok bot template . If you use Grok, you can add it in one tap and put it to work on your book of business today.

Grok bots—xAI’s always-on AI teammates, in beta since August 2026—are more than a saved prompt. Each bot gets a persistent cloud computer with a browser, file system, and terminal; connectors into your services; scheduled tasks; and memory that carries across sessions. And they travel: a bot can be packaged as a template and shared as a link. Ours is listed as Homies AI—a manager assistant for real estate professionals that runs competitive CMAs, follow-up, listings, showings, offers, and content in chat, integrates with your existing CRM, and holds outgoing communications for your approval. xAI runs the model and the runtime; we authored the workflow it executes.

The template is opinionated. It is not a general chatbot with a real estate greeting; it is the specific admin workload that eats a realtor’s week, encoded as skills the bot already knows how to run:

Two design decisions matter more than the skill list. First, the bot proposes and you approve: outgoing messages queue for explicit sign-off, which is the difference between an assistant and a liability. Second, it expects to work against your systems of record—your CRM for contacts and pipeline, your IDX or board-authorized website for listing data. The template ships with no data rights of its own, deliberately. That is the capability-without-custody boundary we argue every real estate AI should respect.

We are also extending what the bot can inherit. On the Homies Tool API we are building board packs: when the first realtor on a board trains a workflow—the local forms choreography, the board-specific showing etiquette—the next realtor on that board inherits the training instead of starting from zero. Secrets never make the trip; passwords, keys, and member IDs are rejected at the API boundary. That work is in development and not yet live, but it is where the template is headed: a bot that gets smarter per board, not just per user.

The argument against shipping this was obvious: we sell an AI team for realtors, and here we were packaging our own manager workflow onto someone else’s platform for free. For a while, that argument won. Every draft of this release died in the same meeting, on the same objection—you are giving away the product.

What changed our minds was realizing the objection had the product wrong. The chat layer—the persona, the skills, the prompt choreography—is becoming a commodity, and pretending otherwise buys us maybe two quarters. What is not a commodity is the layer underneath: the warehoused forms, the executed contracts, the contact and consent records, the board-governed data that a brokerage workflow is legally required to keep, in custody, with retention and audit. That layer lives on the Homies API. It cannot ride along in a shared template, and it should not.

Once you see that split, releasing the template stops being a giveaway and starts being distribution. Every realtor who adds the bot experiences the workflow; the ones whose businesses grow into needing custody, forms, and compliance find that the template already speaks to the API where those things live. We would rather own the layer the law cares about than the layer the model providers are commoditizing anyway.

This is the part of the release we want to be most precise about, because it is the part that governs what the bot can never become. The following stay in warehoused custody on the Homies API, regardless of which chat surface a realtor prefers:

• Forms: official-source real estate forms, their versions, and the completed instances a transaction produces.
• Contracts: executed agreements and the retention obligations that attach to them.
• Contacts and consent: who a realtor may communicate with, on what channel, under what consent—records regulators actually ask for.
• Board-governed data: listing content and feed data that agreements bind to approved applications, not to model context windows.
• Audit trails: what the AI proposed, who approved it, and what committed—the record that protects the realtor.

A chat platform is the wrong warehouse for every item on that list, and not because chat platforms are careless—because custody is a different product. Retention schedules, board data agreements, consent management, and audit are deterministic services with legal owners. The template is designed to call into that layer through the API rather than imitate it. When the bot needs a form, it asks the system that is allowed to hold forms.

The fair question: why a Grok bot and not a ChatGPT configuration, a Claude project, or a self-hosted OpenClaw gateway? We build against all of them—our HomieBench work benchmarks the underlying models directly—and for raw capability the frontier assistants are all remarkable. But out of the box, for the realtor admin workload, they are not close. A shared Grok bot arrives as a finished configuration: skills, connectors, approval behaviour, persona. The others arrive as potential.

Reading the matrix honestly: ChatGPT and Claude can absolutely be assembled into a strong realtor assistant—with custom instructions, projects, connector setup, and real ongoing effort. OpenClaw and Nous Research’s Hermes Agent can be assembled into even more capable ones, if you are the kind of operator who wants to run your own daemon and hold your own secrets, uptime, and incident response. The Grok bot’s advantage is not intelligence. It is that the assembly already happened—we did it, and shipped the result as a link.

That is also why our claim is narrow. We are not saying Grok is the best model, or that a template beats a governed platform. We are saying that if you exclude Homies, there is no comparable out-of-the-box assistant that does the realtor admin job this well, this fast, from a standing start. That was true when we tested it, and it is the reason the template exists.

Free template, expensive habit. Grok Bot access sits behind xAI’s top tiers: the workloads the bot is built for—long contexts, tool calls, recurring routines, its own cloud computer—run on SuperGrok Heavy, which lists at $300 USD per month. (Partner plans and periodic promotions open cheaper routes; budget for the list price.) That subscription alone is double the Homies plan, and the bot only becomes an assistant, as opposed to a well-read intern, once it can reach a CRM and live listing data. Those come from your own subscriptions: a CRM like Follow Up Boss, GoHighLevel, or Lofty, and an IDX or board-authorized website for your feeds.

So the subscription that makes the free template sing costs twice what Homies does on its own—and the full stack lands at $410 or more per month against $150—before you count the hours of configuration the matrix above politely calls “partial.” We are aware of the irony of publishing that arithmetic about our own release. But the numbers are the numbers: for cost against benefit, Homies is still the best play for a working realtor, and the Grok bot is the best thing that is not Homies. Both statements can be true; we shipped the template because they are.

If you are already on a SuperGrok plan, or you want to feel what a configured AI manager does to your week before committing to anything, add the template. It is free, it is genuinely good at the job, and it will not send a message without you. If you get to the point where the bot keeps reaching for things it is not allowed to hold—forms, contracts, warehoused records, board data—that is not a bug in the template. That is the boundary telling you which layer you have outgrown.