New Idea Protocol · Visual Spec

Realtor Listing and Local Content Engine

Brand The Green Anchor Date 2026-07-16 Maturity Solution-first Type Content automation + AI workflow Lens Founder + Engineer
MVP Promise

Turn an address, permitted listing, neighborhood, ZIP code, or local trend into a rights-cleared Realtor content package and schedule it through Buffer.

Who and Why
Primary user

Jose, operating TGA

Needs a working proof of fast, local, multi-platform Realtor content before pitching the service to clients.

Success moment

One request becomes a campaign

A human-approved Reel, carousel, single image, captions, and five network variants arrive in Buffer with sources, rights, and attribution recorded.

Scope
In scope - V1
  • Address, ZIP/neighborhood, pasted URL, authorized API/MLS, or manual listing intake
  • Instagram Reel, carousel, single image, caption/hashtags, Facebook, LinkedIn, Threads, and X
  • Rights classifier, human approval, Buffer drafts/scheduling, and a complete run ledger
Non-goals
  • No public SaaS, client dashboard, payments, CRM, or autonomous publishing
  • No Zillow, Redfin, or Realtor.com photo scraping as the production data source
  • No guaranteed virality, nationwide MLS coverage, or autonomous compliance decisions
Core rule: Publicly visible does not mean licensed for reuse. Listing facts, listing-display rights, and photo copyrights must be evaluated separately.
Happy Path
1

Enter address, location, listing source, manual package, or trend.

2

Resolve permitted property facts and candidate media.

3

Classify every source and asset: authorized, reference-only, review, or blocked.

4

Generate platform copy plus Reel, carousel, and single-image assets.

5

Human checks facts, Fair Housing, attribution, rights, and tone.

6

Create Buffer drafts, queue entries, or scheduled posts and save IDs.

Source and Image Strategy
Live listing + photos

Authorized MLS route

Bridge, MLS Grid, Trestle, SimplyRETS, Repliers, or local RESO access. The exact MLS contract must cover the intended social display and attribution.

Facts without photos

RentCast or ATTOM

Use licensed facts for address-driven posts, market cards, pricing context, and neighborhood content. RentCast intentionally omits listing photos.

Safe visual substitutes

Original and licensed media

Agent uploads, original footage, typography, maps, charts, local data, stock lifestyle assets, or Mapillary CC BY-SA streetscapes with attribution.

System Design Sketch
Components

n8n intake, source adapters, rights gate, fact validator, content planner, media renderer, approval gate, Buffer publisher, run ledger.

Data flow

Trigger → normalize → permitted data → rights check → facts → copy/media → human review → Buffer → audit record.

API surface

Internal sub-workflows for property resolution, rights classification, package generation, asset rendering, and Buffer publication.

Storage

n8n Data Tables or PostgreSQL for state and rights. Controlled object storage for media URLs that remain live through publication.

Caching and queueing

No dedicated queue for the manual demo. Use idempotency keys and provider-compliant observed-at caching.

10x bottleneck

Rendering and upload latency first, provider limits second. V1 does not need distributed infrastructure.

Buffer Integration
Current API

GraphQL at api.buffer.com

Use organization and channel queries plus createPost for drafts, queues, and scheduled publishing.

Supported outputs

Media and network metadata

Images, videos, Instagram Reels and carousels, first comments, and Threads or X threaded posts.

Critical constraint

Persistent asset URLs

Buffer must be able to fetch each asset, and the media must stay available until publication. Retries need idempotency protection.

Pressure Test
Riskiest user assumption

Realtors will pay for the time saved and local quality, rather than dismissing the output as generic AI content. Validate with ten packages and five pilot pitches.

Riskiest technical assumption

A normalized data adapter can keep facts current while media rights remain clear. Test three properties across manual, fact-only API, and authorized MLS paths.

Riskiest business assumption

Trend-reactive content can stay timely, relevant, and tasteful. Keep trend choice manual and require shelf-life plus sensitivity review.

Fake first

Manually select listings, confirm permission, upload media, choose trends, approve copy, and save Buffer drafts.

What breaks later

License changes, stale listing status, missing attribution, expired asset URLs, duplicate retries, false agency implications, Fair Housing language, or content that looks templated instead of locally expert.

Gates
GateStatusNotes
Problem is clear enoughPassTGA needs concrete proof that one request can become useful local Realtor content.
MVP scope is small enoughPass with assumptionOne operator, one market, manual review, one data route, and limited templates.
Handoff is implementation-readyPass with assumptionArchitecture is ready. The first data provider and local MLS permissions remain to be selected.
Wizard-of-Oz path consideredPassThe actual n8n flow can validate demand while selection, permission, trend choice, and approval remain manual.
Definition of Done