When should you use it?
- You juggle several deals with offers, escrow steps and lease deadlines
- Important emails arrive while you're showing property or on calls
- You keep follow-up lists and comparisons by hand
Not for: Sending offers, counteroffers or anything binding without you; Legal advice on leases; it points out what to read, your attorney decides
What do you need, and what do you get?
You need
- Access to your work inbox and calendar
- A list of active deals with key dates (contingencies, funding, closing)
- Your text number for urgent alerts
You get
- An instant text when an offer or counteroffer lands: who, price, key terms
- A side-by-side table of competing bids for your client
- Draft escrow, follow-up and thank-you emails
- Warnings when two deadlines collide
How does it work, step by step?
- List the dealsGive the agent each active deal with parties, dates and what counts as urgent.
- Set alert rulesDecide which emails earn a text (offers, counteroffers, funding notices) and which wait for a digest.
- Let it draftUse our prompt so it prepares routine emails and comparison tables but never sends offers.
- Check deadlines weeklyAsk it to cross-check every deal's dates each Monday and flag conflicts.
The prompt
Our own prompt, inspired by Drew McAllister (@DMAC_19) and written to work in Custom agent, Grok Bot and Claude. Values in lime are placeholders.
Fill in the blanks (optional; the copied prompt uses your values)
You support my deal desk. Active deals and key dates: {deals}. Watch my inbox. When an offer, counteroffer, funding notice or deadline change arrives, text me at {phone} with the sender, deal, price and key terms, quoting the email line for each figure. When I have several bids on one property, build a table: buyer, price, net to seller, terms, contingencies, deadlines. Draft routine emails (escrow openings, follow-ups, thank-you notes to agents whose offers we didn't take) for me to send. Every Monday, compare all deal dates and flag conflicts. Never send offers or anything binding.
Inspired by Drew McAllister (@DMAC_19): Running a commercial real estate business with an AI agent for a week. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.
What can go wrong?
- Misreading a number in an offer is costly. Have it quote the email line for every price it reports.
- Client contact lists are sensitive. Keep protected-buyer lists in your own systems, not in chat history.
Our take
Deal work is a stream of time-sensitive emails tied to dates that can quietly collide, and Drew's list reads like a job description for a good transaction coordinator. The most valuable items are the alerts and the cross-checks. A counteroffer texted to him with sender and price before he opened his inbox saves hours on a live deal, and catching a closing target set before the buyer's SBA loan could fund may have saved the deal itself. The drafting work, such as escrow openings and thank-you notes to runner-up agents, is useful but lower stakes. We'd hold two lines: the agent never sends an offer or anything binding, and every number it reports comes with the email line it came from. Lease redline summaries are a reading aid, not legal review. In our dry run with a made-up inbox for 3 deals, our prompt produced 2 offer alerts quoting the source lines, a bid table for 3 buyers, drafts for an escrow opening and 2 thank-you notes, and one warning that a closing date fell before a loan approval date.
Where the time goes back: You stop combing the inbox for offers and rebuilding comparison tables; the agent watches, tallies and drafts while you're with clients.
FAQ
Does it negotiate for me?
Is this only for commercial real estate?
Source and credit
Inspired by Drew McAllister (@DMAC_19). We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.
- Inspired by
- Running a commercial real estate business with an AI agent for a week
- Creator
- Drew McAllister (@DMAC_19)
- Published on
- X
- Original date
- Oct 1, 2026
- License
- Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
- Originally for
- Custom agent
- AI dry run
- Oct 20, 2026: passed. Dry-run tested by our AI test agent on sample input. Figures quoted from source; nothing binding sent.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails. - Verified
- Oct 23, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.
Are you the creator? Claim or correct this page.