Grok Bot real estate prompts: packs, briefs, comps you still list
Listing packs, showing briefs, and CMA drafts from MLS, photos, and your notes. You still list, email buyers, and sign. The Bot does not touch a live listing or a buyer inbox.
In short: This page contains 21 copy-paste ready prompts, organized into 5 categories with a description and pro tip for each. The first 5 prompts are free instantly, no signup needed. Hand-curated and tested by the AI Academy team.
Listing packs
5 promptsNew listing pack from notes and photos
1/21✨ What it does
The Bot builds a listing pack for [ADDRESS] from [MLS DRAFT OR SHEET], seller notes, and photos, with remarks, a shot list, and open questions. You still list the home and send the pack to anyone who needs it.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Build a listing pack for [ADDRESS]. Do not change MLS. Do not email anyone. Sources: [MLS DRAFT OR SHEET], seller notes, [PHOTO FOLDER], [BROKERAGE DISCLOSURES]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not email buyers or sellers, change MLS, or sign anything. - Do not invent school ratings, crime stats, or who should live there. If a source is missing, write unknown. Deliverable: Remarks draft, feature bullets, shot list, missing facts, file path on the computer. Review point: I list. I send the pack.
Pro tip: Name the sheet and the photo folder. "The listing" is how the Bot invents beds and footage.
MLS remarks I will paste
2/21✨ What it does
The Bot drafts public and agent remarks for [ADDRESS] in the style of [EXAMPLE LISTINGS], using only facts on [FEATURE SHEET]. You still paste the remarks into MLS and you still send them to your brokerage if required.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Draft public remarks and agent remarks for [ADDRESS]. Do not save them to MLS. Sources: [FEATURE SHEET], [EXAMPLE LISTINGS], [CHAR LIMITS], [FAIR HOUSING NOTES]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not email buyers or sellers, change MLS, or sign anything. - Do not invent school ratings, crime stats, or who should live there. If a source is missing, write unknown. - No invented square footage, taxes, or school names. Deliverable: Public remarks, agent remarks, character counts, facts used, facts missing. Review point: I paste into MLS.
Pro tip: Attach two live listings you respect. "Write luxury copy" without examples writes brochure sludge.
Photo shot list for the photographer
3/21✨ What it does
The Bot writes a room-by-room shot list for [ADDRESS] from [FLOOR PLAN OR NOTES] and flags gaps against [MUST-HAVE LIST]. You still send the list to the photographer and you still book the shoot.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Shot list for [ADDRESS]. Do not book the photographer. Do not pay a deposit. Sources: [FLOOR PLAN OR NOTES], [MUST-HAVE LIST], existing [PHOTO FOLDER] if any. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not email buyers or sellers, change MLS, or sign anything. - Do not book, pay, or email the photographer. Deliverable: Room order, must-have shots, skip rooms, missing photos vs what we already have. Review point: I send the list. I book.
Pro tip: Say twilight yes or no, and which rooms cannot be shown. Vague lists waste a truck roll.
Open house pack, invite stays mine
4/21✨ What it does
The Bot assembles an open-house pack for [ADDRESS] on [DATE], with a sign-in sheet, talking points, and a neighbor flyer draft. You still host the open house and send the invite yourself.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Open-house pack for [ADDRESS] on [DATE] [HOURS]. Do not email the farm. Do not change MLS. Sources: [FEATURE SHEET], [MLS DRAFT], [FARM NOTES IF ANY], [SIGN-IN TEMPLATE]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not email buyers or sellers, change MLS, or sign anything. - Do not invent school ratings, crime stats, or who should live there. If a source is missing, write unknown. Deliverable: Sign-in sheet, talking points, flyer draft, day-of checklist, open questions. Review point: I host. I send the invite.
Pro tip: Put the hours and the parking note in the brief or the flyer sends people to the wrong curb.
Just-listed flyer and captions
5/21✨ What it does
The Bot drafts a flyer and three social captions for [ADDRESS] from [FEATURE SHEET] and [PHOTO FOLDER], with no invented footage or school names. You still list the home and you still post the copy.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Flyer copy plus 3 captions for [ADDRESS]. Do not post. Do not change MLS. Sources: [FEATURE SHEET], [PHOTO FOLDER], [BRAND VOICE EXAMPLES], [CHAR LIMITS]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not email buyers or sellers, change MLS, or sign anything. - Do not invent school ratings, crime stats, or who should live there. If a source is missing, write unknown. Deliverable: Flyer copy, 3 captions, photo pick per caption, facts used, facts missing. Review point: I list. I post.
Pro tip: Ban school names unless they are on the sheet. Guessing a district is how you eat a complaint.
Showing briefs
4 promptsBuyer tour brief for the day
6/21✨ What it does
The Bot writes a showing brief for [BUYER] touring [ADDRESSES] on [DATE], with order, talking points, and mismatches versus [CRITERIA]. You still run the tour and send any follow-up yourself.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: One-page tour brief for [BUYER] on [DATE]. Do not email the buyer. Do not change MLS. Sources: [CRITERIA], [ADDRESSES], [MLS SHEETS], [PRIOR NOTES], map for order. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not email buyers or sellers, change MLS, or sign anything. - Do not invent school ratings, crime stats, or who should live there. If a source is missing, write unknown. Deliverable: Stop order, why each house, mismatches, questions to ask, links. Review point: I run the tour. I send follow-up.
Pro tip: Drive time and lockbox notes beat vibe paragraphs. The Bot has not sat in that traffic.
Seller prep sheet before showings
7/21✨ What it does
The Bot writes a seller prep sheet for [ADDRESS] before [SHOWING WINDOW], using [FEEDBACK SO FAR] and [STAGING NOTES]. You still send that sheet to the seller yourself.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Prep sheet for the seller at [ADDRESS] before [SHOWING WINDOW]. Do not text or email them. Sources: [FEEDBACK SO FAR], [STAGING NOTES], [FEATURE SHEET], [PHOTO FOLDER]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not email buyers or sellers, change MLS, or sign anything. Deliverable: Do-today list, leave-out list, pet or odor note, draft message I will send. Review point: I send it.
Pro tip: Keep it to ten actions. A 40-item punch list is how sellers stop reading.
Showing feedback rollup
8/21✨ What it does
The Bot rolls showing notes for [ADDRESS] from [FEEDBACK FILE OR INBOX] into themes, objections, and one price or staging question. You still talk to the seller and you still send any update.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Roll up showing feedback for [ADDRESS] since [DATE]. Do not email buyers. Do not change MLS. Sources: [FEEDBACK FILE OR INBOX], [MLS DOM AND PRICE], [ACTIVE COMPS IF ANY]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not email buyers or sellers, change MLS, or sign anything. - Separate quoted feedback from your inference. Deliverable: Theme, quote, count, inferred vs stated, one question for the seller. Review point: I talk to the seller. I send the update.
Pro tip: Quote the note. Paraphrase is how "kitchen felt small" becomes a price cut you cannot defend.
Post-showing notes I will send
9/21✨ What it does
The Bot drafts a follow-up for each stop on [TOUR DATE] for [BUYER], using your notes and [CRITERIA], and flags stops with no notes. You still send those notes from your own account.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Draft follow-up notes for [BUYER] after [TOUR DATE]. Do not email the buyer. Sources: My tour notes, [CRITERIA], [MLS SHEETS]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not email buyers or sellers, change MLS, or sign anything. - No fake personalization. If a stop has no notes, mark missing-notes and skip the flourish. Deliverable: Per stop: keep / maybe / pass, draft, missing-notes flag. Review point: I send from my account.
Pro tip: If you wrote nothing after a house, say so. Fake "loved the light" is worse than a short honest line.
Comp drafts
4 promptsCMA table with blank unknowns
10/21✨ What it does
The Bot builds a comps table for [ADDRESS] from [MLS COMPS VIEW] and [ACTIVE LISTINGS], with adjustments you can defend and blank unknown cells. You still set the list price and send the CMA yourself.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: CMA table for [ADDRESS]. Do not invent a sale price. Do not change MLS. Sources: [MLS COMPS VIEW], [ACTIVE LISTINGS], [SUBJECT SHEET], [DATE RANGE]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not email buyers or sellers, change MLS, or sign anything. - No invented adjustments. Unknown stays unknown. Deliverable: Subject row, comps, adjustments, recommended range, sources, unknowns. Review point: I set the list price. I send the CMA.
Pro tip: Tell it which fields you trust. Sold remarks lie. Price-per-foot without condition is theater.
Expired and withdrawn nearby
11/21✨ What it does
The Bot reviews expired and withdrawn listings near [ADDRESS] in [DATE RANGE] and notes why each failed, using only [MLS] fields you trust. You still decide whether to list and you still send nothing to those sellers.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Review expired and withdrawn near [ADDRESS] in [DATE RANGE]. Do not contact those sellers. Sources: [MLS EXPIRED / WITHDRAWN VIEW], [SUBJECT SHEET]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not email buyers or sellers, change MLS, or sign anything. - Do not email or door-knock those sellers. Deliverable: Address, list-to-expire path, likely reason or unknown, lesson for this listing. Review point: I decide whether to list. I send nothing.
Pro tip: DOM plus price cuts beat "the market was slow." If the reason is not in MLS, write unknown.
Actives in the same band
12/21✨ What it does
The Bot compares [ADDRESS] to actives in [RADIUS OR PRICE BAND] on price per foot, days on market, and concessions, citing [MLS VIEW]. You still list or cut price and you still send the comparison.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Compare [ADDRESS] to actives in [RADIUS OR PRICE BAND]. Do not change MLS. Sources: [MLS ACTIVE VIEW], [SUBJECT SHEET]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not email buyers or sellers, change MLS, or sign anything. - No invented concessions. If the field is empty, write unknown. Deliverable: Table: address, list, $/ft, DOM, concessions, link, where we look expensive. Review point: I list or I cut. I send the table.
Pro tip: Concessions and seller credits belong in the table. Sticker price alone is how you lose a listing meeting.
Price-cut rationale for the seller
13/21✨ What it does
The Bot drafts a price-cut rationale for [ADDRESS] from [DOM], [SHOWING COUNT], and [NEW COMPS], with a range and the cost of waiting. You still send it to the seller and you change MLS yourself.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Draft a price-cut rationale for [ADDRESS]. Do not change the live price. Do not email the seller. Sources: [DOM], [SHOWING COUNT], [FEEDBACK ROLLUP], [NEW COMPS], [ORIGINAL CMA]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not email buyers or sellers, change MLS, or sign anything. - Not advice. Cite the comps. Unknown if a number is missing. Deliverable: Current vs proposed range, comps that moved, showing math, draft I will send, cost of waiting. Review point: I send it. I change MLS.
Pro tip: Give two numbers, not a vibe. "We should reduce" with no new solds is an argument you will lose.
Like these prompts? There are full tutorials behind them.
Learn the workflows, not just the prompts. 300+ easy-to-follow tutorials inside AI Academy — and growing every week.
Offers, inspections, close
4 promptsOffer grid I will walk through
14/21✨ What it does
The Bot builds an offer grid for [ADDRESS] from [OFFER PDFS], with price, dates, contingencies, and holes marked unknown. You still send the response and you still sign nothing.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Offer comparison grid for [ADDRESS]. Do not accept, reject, or counter. Do not sign. Sources: [OFFER PDFS], [LISTING AGREEMENT DATES], [SELLER PRIORITIES IF ANY]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not email buyers or sellers, change MLS, or sign anything. - Do not sign. Do not send a counter. Unknown if a clause is unreadable. Deliverable: Grid: price, net if calculable, dates, contingencies, holes, draft questions. Review point: I counsel. I send. I sign nothing until I mean it.
Pro tip: Read the PDF, not the cover email. Escalation and appraisal gaps hide in addenda.
Inspection punch list from the PDF
15/21✨ What it does
The Bot turns [INSPECTION PDF] for [ADDRESS] into a punch list with severity and a draft request, quoting the report. You still send that request yourself.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Punch list from [INSPECTION PDF] for [ADDRESS]. Do not email the other side. Do not sign. Sources: [INSPECTION PDF], [CONTRACT REPAIR WINDOW], [PRIOR AGREED ITEMS IF ANY]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not email buyers or sellers, change MLS, or sign anything. - Quote the report. Not advice. Do not invent costs. Deliverable: Item, page, severity, draft request language, unknowns. Review point: I send the request.
Pro tip: Quote page numbers. A Bot that "summarizes moisture" without the page is how you fight the wrong repair.
Closing checklist with owners
16/21✨ What it does
The Bot builds a closing checklist for [ADDRESS] closing [DATE] from [CONTRACT] and [LENDER OR TITLE NOTES], with owners and missing items. You still send the reminders and you still sign nothing.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Closing checklist for [ADDRESS] on [DATE]. Do not sign. Do not wire. Do not email parties. Sources: [CONTRACT], [LENDER OR TITLE NOTES], [CALENDAR]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not email buyers or sellers, change MLS, or sign anything. - Do not sign. Do not wire. Stop if a full account or card number appears. Deliverable: Task, owner, due date, missing item, draft reminder I will send. Review point: I send reminders. I sign. I wire.
Pro tip: Wire instructions stay out of chat. If a full account number appears, stop and tell me.
Neighborhood one-pager, sourced
17/21✨ What it does
The Bot writes a neighborhood one-pager for [AREA] from [CITY OR SCHOOL OR TRANSIT SOURCES], citing each claim and marking unknowns. You still send that page to buyers yourself.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Neighborhood one-pager for [AREA]. Cite official pages. Do not email buyers. Sources: [CITY OR SCHOOL OR TRANSIT SOURCES], [AREA NOTES I ATTACH]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not email buyers or sellers, change MLS, or sign anything. - Do not invent school ratings, crime stats, or who should live there. If a source is missing, write unknown. Deliverable: Vibe in my words, commute facts with links, school names only if sourced, unknowns. Review point: I send it if I want.
Pro tip: Primary sources only. A blog "best schools" line is how you steer without meaning to.
Make the real estate Bot durable
4 promptsWeekly listing desk digest
18/21✨ What it does
The Bot writes a weekly desk digest of [PIPELINE VIEW] since [FRIDAY]: new listings, stale actives, and decisions you owe. You still list what needs listing and send what needs sending.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Weekly digest of [PIPELINE VIEW] since [FRIDAY]. Only what needs my decision. Do not change MLS. Sources: [PIPELINE VIEW], [CALENDAR], [PRIORITIES IF ANY]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not email buyers or sellers, change MLS, or sign anything. - Do not post to Slack. Do not email the team. Deliverable: New / stale / closing this week / decisions I owe, each with a link. Review point: I list. I send. I share the digest if I want.
Pro tip: Point at a view name. "My deals" is how it narrates every status ping like news.
Match new listings to a buyer
19/21✨ What it does
The Bot matches new listings in [MLS SAVED SEARCH] to [BUYER CRITERIA] and drafts a why-fit note for each keep. You still send those picks from your own account.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Match [MLS SAVED SEARCH] to [BUYER CRITERIA]. Do not email the buyer. Do not change MLS. Sources: [MLS SAVED SEARCH], [CRITERIA], [PRIOR TOUR NOTES]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not email buyers or sellers, change MLS, or sign anything. - Do not invent school ratings, crime stats, or who should live there. If a source is missing, write unknown. - Skip already-shown addresses. Deliverable: Keep / skip, why-fit, mismatch, draft I will send, already-shown flag. Review point: I send the picks.
Pro tip: Hard filters first: beds, budget, commute. Soft "feels like them" is how you send the wrong house.
Listing-desk Bot description
20/21✨ What it does
The Bot writes a description for a listing-desk Bot named [NAME] that owns packs, briefs, and comps, with a never-do list for MLS edits, buyer email, and signing. You paste that text in; you still list and send every client-facing thing.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Write a Bot description named [NAME] for listing packs, showing briefs, and comps only. Sources: This page, [BROKERAGE RULES], [TOOLS I USE]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not email buyers or sellers, change MLS, or sign anything. - Refuse travel booking, outbound sales sequences, and live MLS edits. Deliverable: Name, job, sources, weekly output, approval line, refuse-list. Review point: I create the Bot from this text.
Pro tip: One job. A Bot that "does real estate" will wander into travel and outbound and burn the week.
Save a listing-pack run as a skill
21/21✨ What it does
The Bot writes the listing-pack run you liked as a skill called [SKILL NAME], including sources, pack layout, and the stop before MLS. You still list from that pack and send it yourself.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Write skill [SKILL NAME] from the listing-pack run we liked. Stop before MLS. Do not email anyone. Sources: The pack from this thread, [FEATURE SHEET TEMPLATE], [CHAR LIMITS]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not email buyers or sellers, change MLS, or sign anything. Deliverable: When to use, steps, sources, approval line, failure if the sheet is empty. Review point: I test on a second address. I list. I send.
Pro tip: Test on a second address before you hang a weekday routine on it. One pretty pack is not a process.
Free tool
Prompt Optimizer
Turn a rough idea into a structured, professional AI prompt.
Frequently Asked Questions
Prompts are the starting line. Tutorials are the finish.
A growing library of 300+ hands-on tutorials on ChatGPT, Claude, Midjourney, and 50+ AI tools. New tutorials added every week.
7-day free trial. Cancel anytime.
Related guides