DEV Community

yuki yama
yuki yama

Posted on

Realtor Buyer Tour Packets on Autopilot: $500–$2,000/Month with Manus AI

#ai #sidehustle

Realtor Buyer Tour Packets on Autopilot: $500–$2,000/Month with Manus AI

Please note: All earnings mentioned are illustrative simulations.

Goal: Build a Manus AI workflow that ingests a realtor’s buyer intake (Google Form + agent-provided MLS PDFs/CSV or public listing links), auto-extracts key facts, computes a driving route and ETA table via Google Maps, summarizes highlights, nearby schools/amenities, light comps, and a disclosure checklist, then outputs a branded PDF and emails/SMS the itinerary to both client and agent. Target: ~10 minutes per packet, $49 per tour or $199/month for up to 8 tours.

What you will use

Summary of the workflow you’ll build

  • Trigger: New agent intake (Form submit) or email with MLS PDFs/CSV or public listing links.
  • Parse: Extract addresses, MLS IDs, prices, beds/baths, square footage, lot size, features, remarks.
  • Route + ETAs: Build an optimal route from meeting location with estimated arrival/departure times.
  • Local insights: Top nearby schools and amenities per property.
  • Light comps: Quick median price/$ per sq. ft. and days-on-market from provided CSV or links.
  • Compliance: Disclosure checklist tailored by state.
  • Deliverable: Branded PDF tour packet + email/SMS itinerary to client and agent.
  • Optional: Post-tour follow-up summary automation from agent’s notes.

Step 1: Create the intake form that seeds everything

  • Build a Google Form capturing:
    • Agent name, email, phone
    • Client name, email, phone
    • Showing date window (start/end), meeting location, time buffer per stop (default 15–20 minutes)
    • Property list: MLS numbers and/or public links (Redfin/Zillow/broker site)
    • Uploads: PDFs (MLS flyers), CSV of comps (optional), disclosures (if any)
    • Notes: Special buyer preferences, constraints (must see X first, avoid tolls, etc.)
  • Set Form responses to log to Google Sheets.
  • Foldering: Create a Google Drive folder “Buyer Tours.” Subfolders per client: “ClientName_Date.” Ensure Form File Uploads land there.

Step 2: Capture emailed MLS packets and normalize files

  • Agents often email MLS PDFs or CSVs. Do both:
    • Gmail label “BuyerTours” for relevant threads.
    • Auto-forward to Mailparser. Configure a mailbox to:
    • Save attachments to Drive (into the right client subfolder).
    • Extract listing URLs from the body and output as structured JSON.
    • Use Zapier or Make to:
    • Watch the Form’s Google Sheets row or the Mailparser webhook.
    • Append normalized file/URL lists to the same Google Sheets row.
  • Naming convention: “ClientLast_First_YYYYMMDD_Property1-6.pdf” and “ClientLast_First_intake.json”.

Step 3: Stand up your Manus project and baseline schema

  • Sign up with this invitation link so you get access to the latest features: https://manus.im/invitation/OJF7FVBNBC14H?utm_source=invitation&utm_medium=social&utm_campaign=copy_link
  • Create a new “Buyer Tour Packet” workflow. Inputs:
    • agent_name, agent_email, agent_phone
    • client_name, client_email, client_phone
    • showing_date_start, showing_date_end, meeting_location
    • dwell_minutes_per_property (default 15)
    • property_sources: array of items, each with either mls_pdf_url, csv_url, or public_listing_url
    • state_abbrev (for disclosures)
  • Define a structured extraction schema for properties (this ensures consistent outputs):
    • address_full
    • mls_id
    • list_price
    • beds
    • baths
    • sqft
    • lot_size
    • year_built
    • hoa_fee
    • days_on_market
    • remarks_highlights
    • must_know_disclosures (from agent-provided docs)
    • listing_link (if provided)
  • In Manus, add:
    • File-to-Text step for PDFs/CSVs with OCR on for scanned docs.
    • HTTP fetcher step for public links, with DOM-to-text conversion.
    • LLM “Extractor to JSON” step using the schema above. Prompt instruction example:
    • “Given MLS PDFs, CSVs, and public listing pages, extract normalized property facts into the schema. If a field is missing, leave null. Consolidate duplicates. Preserve addresses exactly as stated. Estimate mls_id if clearly labeled.”

Step 4: Build the route and ETA table via Google Maps

  • You will generate an ordered route and timestamped schedule with the Google Maps Platform.
  • Get a Google Cloud project and enable Directions API and Distance Matrix API. Also enable Places API for schools/amenities.
  • Manus step: after extraction, you’ll have a list of addresses. Add an HTTP request step to Google Maps Platform Directions API:
    • Origin: meeting_location from intake.
    • Waypoints: property addresses (optimize:true if your agent allows reordering by drive time).
    • Departure_time: showing_date_start (UNIX timestamp). Traffic model: best_guess.
  • Parse response to capture sequence order, travel times between stops.
  • Compute arrival/departure schedule:
    • Initialize t0 = showing_date_start.
    • For each stop i: arrival_i = t0 + drive_time_i; depart_i = arrival_i + dwell_minutes_per_property; set t0 = depart_i.
    • Output a compact table per property: Stop #, Address, ETA arrival, Est. depart, Drive time from prior stop.
  • Also generate a sharable Google Maps route link so the agent/client can navigate on mobile:
    • Construct a dynamic URL with origin and waypoints.

Step 5: Nearby schools and amenities per property

  • For each property address, use Google Maps Platform Places API Nearby Search:
    • Categories to pull: school, supermarket or grocery, restaurant, park, transit_station.
    • Radius: 1600 meters (about 1 mile) or 3200 meters (2 miles) depending on urbanity.
    • Return the top 2–3 by rating and proximity. Include name, type, rating, and distance by drive time or walking.
  • Add an LLM summarizer step in Manus to produce one-paragraph “local highlights” per property:
    • “Summarize school options and 2–3 notable amenities nearby. Keep to 3–5 bullet points, include ratings and approximate travel times.”

Step 6: Light comps in minutes

  • Best source: agent-provided MLS CSV. Your Manus workflow should:
    • Convert CSV to structured rows.
    • Filter to last 90 days within 0.5–1.0 miles, similar beds/baths/sqft.
    • Calculate medians: price, price/sqft, days on market.
    • Highlight 3 closest comps with address, date sold or status, and $/sqft.
  • If CSV is not provided:
    • Accept public links the agent shares with permission and in line with those sites’ TOS.
    • Or request the agent export 10–20 comps from their MLS to CSV for better reliability.
  • Keep the comp section light—2–3 bullets plus a small 3-row list. This is a tour aid, not an appraisal.

Step 7: Disclosure checklist (state-aware)

  • Create a small YAML or JSON map in your Manus workflow keyed by state_abbrev with common checklists. Example items (confirm with broker/state rules):
    • Agency disclosure, property disclosure, lead-based paint (if pre-1978), radon, mold, wire fraud advisory, fair housing, local addenda.
  • The Manus logic selects the right set for the state and merges with any must_know_disclosures found in paperwork.
  • Add a disclaimer: “This is not legal advice. Always consult your broker/attorney.”

Step 8: Assemble a branded PDF packet
Two fast paths:

A) Google Docs template (recommended for full automation)

  • Create a Google Docs template branded with the agent’s logo/colors.
  • Use placeholders like {{client_name}}, {{agent_name}}, {{tour_date}}, {{route_table}}, and a repeating section for properties: {{#properties}}...{{/properties}}.
  • With Zapier or Make, add a “Create Doc from Template” action after Manus outputs the final JSON.
  • Fill placeholders with Manus JSON. Convert the Doc to PDF automatically and save in Drive in the client folder.
  • Embed the dynamic Google Maps link. Add quick QR code if desired.

B) Canva Pro (best for highly designed outputs)

  • Use Bulk Create with a CSV from Manus JSON. This can produce beautiful layouts.
  • Note: This may require a semi-manual export unless you connect via a middleware. For fully hands-off, prefer Google Docs + PDF.

Step 9: Email and SMS the itinerary

  • Email via Gmail:
    • Subject: “Buyer Tour Itinerary: [Date] – [Client Name]”
    • Body includes:
    • The ordered property list with ETA arrivals/departures.
    • Google Maps sharable route link.
    • Button/link to the PDF tour packet in Drive or as an attachment.
    • Send to agent and client. CC any team coordinator.
    • Implement with Zapier/Make Gmail actions right after PDF creation.
  • SMS:
    • Use Twilio or another SMS gateway in your automation layer to send a short text with:
    • “Your tour tomorrow at 9:30 AM. First stop: 123 Main St. Route link: [short URL]. PDF in email.”
    • Trigger SMS 24 hours before and 1 hour before start time.
    • If you prefer a no-code path, Zapier SMS works in limited regions; otherwise Twilio is global.

Step 10: Optional post-tour follow-up summary automation

  • Right after the tour, send the agent a link to a 2-minute Google Form capturing:
    • Property-wise thumbs up/down, notes, repair concerns, “Offer?” yes/no/maybe, next steps.
  • Or allow SMS reply with bullets; parse via Mailparser or a webhook and pass to Manus.
  • Manus condenses notes into a clean “Post-Tour Recap” with:
    • Top 3 favorite homes and why
    • Key objections
    • Action items and timelines
  • Email the recap to the client and agent; add a new row in Google Sheets for CRM tracking.

Execution detail inside Manus (what each block does)

  • Trigger block: Webhook from Zapier or Make carrying the Google Sheets row and normalized file/URL list.
  • File ingestion: For each mls_pdf_url or csv_url, fetch, OCR, normalize tables.
  • Link ingestion: For each public_listing_url, fetch HTML, convert to text, remove boilerplate.
  • Property extractor: LLM-to-JSON with strict schema. Deduplicate addresses. Flag missing essentials.
  • Routing: HTTP requests to Google Maps Platform Directions/Distance Matrix. Compute schedule.
  • Nearby: HTTP requests to Google Maps Platform Places Nearby Search by category. Reduce to top items.
  • Summaries: LLM summarizers for each property and overall tour.
  • Disclosures: State mapping + merge with extracted items; add standard advisory text.
  • Output: Single JSON payload that your doc templating step consumes. Include:
    • client/agent info
    • ordered properties with facts, highlights, schools/amenities, comps
    • route table and link
    • disclosure checklist

Time benchmarks

  • One-time setup: 4–8 hours depending on template design and how many states’ disclosures you pre-load.
  • Per tour run time (after setup): 8–12 minutes of your time to glance at data quality, tweak order if needed, and approve send. Manus + APIs do the rest within 1–3 minutes.

Pricing and earnings

  • Offer two plans:
    • Per-tour: $49 per tour (up to 6 properties; +$5 per additional stop).
    • Subscription: $199/month for up to 8 tours; $29 per additional tour; priority turnaround.
  • Optional onboarding fee: $99 to brand their templates, logos, and disclosures.
  • Realistic earnings scenarios:
    • Conservative: 5 agents on subscription averaging 6 tours/month each → 30 tours. Revenue ≈ $995 (5 × $199) + $0 overages if within cap.
    • Mixed: 4 subscribers (32 tours) + 10 ad-hoc tours → $796 + $490 = $1,286.
    • Aggressive: 8 subscribers (64 tours) + 12 ad-hoc → $1,592 + $588 = $2,180.
  • Costs (typical monthly):
    • Google Maps Platform: $200 free credit often covers 100–200 tours. Past that, expect roughly $0.40–$1.20 per tour for Directions + 10–20 Places calls.
    • Mailparser: ~$39/month.
    • Zapier or Make: $20–$49/month depending on volume.
    • Misc: Storage/email negligible.
  • Even at 20–40 tours/month, margin stays high because each packet takes ~10 minutes of your time.

Prospecting: land 5–10 local agents in 2 weeks

  • Build a 1-page sample packet using a real local buyer scenario (use public listings).
  • Identify prospects:
    • Pull 50 producing agents from Zillow/Redfin/your MLS’s top-100 list.
    • Prioritize those who post multiple buyer tours per week on social or have active buyers on their site.
  • Cold email script:
    • Subject A/B test:
    • “I’ll build your buyer tour packets in 10 minutes (route + schools + PDF)”
    • “Your next tour: route, ETAs, schools, comps—done for you”
    • Body:
    • “Hi [Agent], I help agents cut prep time from 60–90 minutes to ~10 with an AI workflow that turns your intake + MLS PDFs/links into a branded tour packet: route with ETAs, nearby schools, light comps, and a disclosure checklist. $49 per tour or $199/mo (8 tours). Sample attached for [Neighborhood]. If I can do one free packet for your next tour, would you try it? If it saves you time, we’ll set you up for ongoing. – [Your Name], [Phone]”
  • DM/Script for calls:
    • “Quick question—how long does a buyer tour packet take your team? I can deliver a polished PDF with maps, ETAs, schools, and comps in 10 minutes. Can I comp your next tour? If it doesn’t save you an hour, I’ll buy your coffee.”
  • Follow-up cadence:
    • Day 2: Send sample video walk-through (2 minutes) showing how the agent just drops links and gets a packet.
    • Day 4: “Tour coming up? I can turn it around same day.”
    • Day 7: “Last nudge—free first packet still open.”
  • Onboarding steps per new agent:
    • Get logo/colors and headshot.
    • Confirm preferred dwell time (15–20 min) and meeting location default.
    • Choose school/amenity categories to highlight.
    • Confirm state for disclosures and broker-required advisories.
    • Collect their Google account for shared Drive folder access.

Quality control checklist per packet (2 minutes)

  • Addresses clean and geocoded.
  • Route order respects any agent preferences (e.g., “See 45th Ave first”).
  • Schools/amenities look relevant (ratings/distance reasonable).
  • Light comps summary has medians and 2–3 solid comps (from CSV).
  • Disclosure checklist present with correct state.
  • PDF branding and page breaks look tight.
  • Email/SMS preview looks correct; route link opens cleanly on mobile.

Concrete data fields and tokens you should include in your template

  • Cover
    • “Buyer Tour for [client_name]” – [tour_date], compiled by [agent_name], [agent_phone]
    • Route link QR code or URL
  • Per property
    • Address, MLS ID, list price
    • Beds/Baths, Sq. Ft., Lot Size, Year Built, HOA
    • Days on Market
    • Highlights (3–5 bullets)
    • Schools/Amenities (3–6 bullets with ratings/times)
    • Light comps (median $/sqft; 2–3 nearest comps)
    • Disclosures to review (bulleted)
    • ETA arrival/departure for this stop
  • Final page
    • Full route and ETA table
    • Agent and brokerage disclaimers
    • Next steps

Building the middleware glue with Zapier or Make

  • With Zapier:
    • Trigger: New row in Google Sheets from Form response.
    • Action: Retrieve files from Drive and links from Mailparser.
    • Action: Webhooks by Zapier → POST to Manus workflow webhook with payload.
    • Action: Poll for Manus job completion (or receive webhook).
    • Action: Google Docs → Create from Template with Manus JSON.
    • Action: Convert to PDF and store in Drive.
    • Action: Gmail → Send emails with PDF/links to agent and client.
    • Action: SMS (Zapier SMS or Twilio) → Send itinerary text.
  • With Make:
    • Same structure with HTTP modules, Google Docs, Gmail, and Twilio modules; easier iterative mapping for the JSON.

Route and Places API usage notes to keep costs low

  • Batch Places calls: restrict fields to name, rating, user_ratings_total, geometry/location; compute travel time once with Distance Matrix for all selected places.
  • Limit results: top 2 schools and top 1–2 of each amenity type.
  • Use the $200 monthly credit on Google Maps Platform. With careful batching, many users stay within the free tier for dozens of tours per month.

Compliance and boundaries

  • Do not scrape behind MLS logins; rely on agent-provided PDFs/CSVs and public links with permission and in line with site TOS.
  • This packet is informational; it is not an appraisal or legal document. Direct clients to the agent/broker for official guidance.
  • Store data securely; use least-privilege sharing on Drive folders.

Turn this into a sellable productized service

  • Positioning: “10-minute buyer tour packets: routes, ETAs, schools, and light comps—ready for clients.”
  • SLAs: Same-day for requests before 2 pm; next-morning otherwise. Rush fee: +$20.
  • Add-ons:
    • “Offer Comparison” one-pager for shortlisted homes: +$39.
    • “Neighborhood Deep Dive” per target area: +$49.
  • Renewal hooks:
    • Monthly summary email showing hours saved (e.g., “Saved you ~8 hours across 8 tours this month”).
    • A/B test different template styles; show before/after.

Why Manus for this use case

Your first live run in 10 minutes (checklist)

  • Receive Form response (or email) with 4–6 properties.
  • Ensure files/links landed in the client folder and Google Sheets row.
  • Fire the Manus workflow; it extracts and enriches in ~1–3 minutes.
  • Review the route order; lock it.
  • Generate PDF; quick visual scan; approve send.
  • Emails and SMS go out with the itinerary and route link.

Troubleshooting quick wins

  • Missing addresses or geocode fails: Ensure PDFs have clear address blocks; allow Manus OCR; add a fallback geocoding step using Google Maps Platform Geocoding API.
  • Conflicting data across sources: Prefer MLS CSV over public pages; in Manus, set a source priority order: CSV > PDF > public link.
  • Too many places results: Constrain radius to 1 mile; require minimum rating 4.0 and 50+ reviews when available.
  • Ugly PDF pagination: In the template, keep per-property sections within 1–2 pages; use page breaks after 2 properties.
  • SMS links break on some phones: Shorten URLs and avoid query strings longer than 1,000 characters.

Numbers that matter to the agent

  • Time saved per tour: 45–80 minutes.
  • Information density: 1 clean PDF replaces 5–10 disjointed docs and tabs.
  • Client experience: ETA table + mobile route means fewer late arrivals and lost buyers.
  • Decision clarity: Schools and comps right where they need them.

Realistic path to $500–$2,000/month

  • Week 1: Build the workflow, design the template, produce 1 killer sample. Book 3 demos.
  • Week 2: Close 2 subscriptions at $199 and complete 6 ad-hoc tours → $398 + $294 = $692.
  • Month 2: Reach 5 subscriptions and 10 ad-hoc tours → ~$1,485.
  • Month 3: 8 subscriptions and 12 ad-hoc tours → ~$2,180.
  • You can manage 40–60 tours/month solo at ~10 minutes per packet.

Exact tool stack recap (use these)

FAQ for objections you’ll hear

  • “I already have a checklist.” Great—feed it to the workflow; you’ll still save the routing and summarizing time.
  • “Clients don’t read PDFs.” Then emphasize the SMS + route link. The PDF doubles as the agent’s binder and meets brokerage compliance.
  • “I need this tomorrow.” It’s a 1–2 hour onboarding for branding; after that, 10-minute runs are easy.
  • “Is the data accurate?” You’re pulling from the agent’s own MLS exports and Google Maps Platform. You’re not inventing data—just standardizing and presenting it professionally.

Next steps for you, right now

  • Create your Manus account with the invitation link above.
  • Draft a clean Google Docs template with placeholders.
  • Wire Forms → Sheets → Manus → Docs → Gmail/SMS in Zapier or Make.
  • Test with two mock tours; fix pagination and table widths.
  • Send three free trials to local agents and close paid plans.

CTA — Start your first tour packet today

Top comments (0)