REI School Charter and Source Inventory

2026-08-18 · owner directive (Patrick): build a sister school for Real Estate Investment Automations — “our own REI Automated (similar but different name)” — as its own income pipeline, supplementing the automation platform, with its own separate community. Story: processautomater-education-platform (education lane owns curriculum; platform lane owns the automation library category; naming + counsel items flagged below).

1. THE VISION (owner’s words, structured)

A parallel school beside the general ProcessAutomater school, for real estate investors and real estate professionals: lessons + pre-built real-estate automations they can use in their business, in a separate community. Teach the practice; ship the automations that perform it. Everything their $15,000 program claimed to be — actually automated this time.

Scope named by owner: SEO automation · backlink management · Google Ads management · realtor CRM/consistent-touch systems · the newsletter/email engine (the $265/mo Constant Contact replacement, 40k emails) · wholesaler-list automation (get on lists, intake deals, manage staleness/immediacy timelines) · deal intake→analysis→offer structuring (the un-mangled quote methods) · scripts-to-automation (inbound lead → triage → booking → acquisition-manager escalation, via voice AI or text) · data-mapping-first design (gather most data up front so questions are short and pointed — the anti-pattern their “automated” system shipped, where the same data was input multiple times).

2. GUARDRAILS (binding)

1. IP: the archive below is competitive research and a component map. We learn what they did (and did clunky) and build original automations, lessons, spreadsheets, and scripts. No copying of their copyrighted text, no use of their name in the product, no characters from the program (consistent with the book’s Story-20 ruling). Note: many contract templates in the archive are third-party packs (e.g., “Pace’s Contract Pack,” Flip Talk docs) — those are OTHER people’s IP too; reference-only.
2. Naming: “similar but different” to REI Automated → trademark screening + counsel before any name is adopted. (Not legal advice; get counsel.)
3. Legal/compliance for the school itself: real-estate education touches licensed activity (brokerage, lending, contracts state-by-state). Curriculum ships with not-legal/not-financial-advice framing, and the attorney-reviewed docs we use are OUR attorney-reviewed docs (we have two in the archive: PSA edited by attorney 2023-04; Right of First Refusal updated by attorney 2024 — ours, usable).
4. ⚠ SECURITY (fix now): the master “REI Automated Files” Google Doc contains plain-text logins/passwords on page 1. Move those to the credential vault and edit them out of the doc. (Not reproduced here.)

3. WHAT THE ARCHIVE CONTAINS (full inventory, mapped 2026-08-18)

Root folder: Google Drive → REI Automated (id 125TZuL6NPRuoyIUQSbRHYFItO3Gim4h2), ~300 files.

3a. The master compilations (the whole program in doc form)

• REI Automated Files — 18 MB master doc, full TOC: Basics (equity, velocity of money, terminology, liens, business hierarchy) → Deal Structure (Hybrid, Sub-To→Wrap, Sub-To→Retail, 0% owner financing, deal analyzer outline) → Marketing for Motivation (Big Five, sweat marketing, PPC, channels, weekly report) → Scripts & Walk-away Basics → Triage Call (results/conditions/outline, repair estimating) → ARV Finder (comps) → Deal Analysis (checklist, creative-finance analyzer) → Perfect Presentation (never-make-offers doctrine, pitching, SNSL) → PSA + cheat sheet → Asana ops → Raising Private Capital/KPIs → Misc legal docs → CRM statuses & flows (status taxonomies, flow charts, communication rules). 1OqL2-nb24HUe8Sr4JvsdNhSauAZhlH7kz4iEusPzpgE
• Duplicate/edit copies: REI Automated Files (6.8 MB, 1KRtB8ee...), SOP TOC Test (6.7 MB, 1G1h-iyd...), Untitled document (6.7 MB, 1dELugPm...), WELCOME TO REI AUTOMATED (1EM4jWsD...).

3b. The training curriculum, unbundled (13 module folders under " clean up rei automated sub folder")

The Basics (20 files) · Deal Structure (15) · Marketing for Motivation (13) · Prepping for Execution (Scripts & Walk-away Basics 4.6 MB docx; Triage/Perfect-Presentation/Post-Contract call scripts as PDFs) · The Triage Call (7) · The ARV Finder · Deal Analysis ([TEMPLATE] Deal Analyzer sheet, 759 KB — the mangled quote-method spreadsheet, 1kPY_mC4YxAsuqmtN2Cw9rjzqzTtpW8x9_WJlVYhSCA8 + Creative Finance Deal Analyzer Rules.pdf) · The Perfect Presentation (19) · Purchase & Sale Agreement (incl. Patrick’s attorney-edited draft) · Asana template · KPIs templates · Miscellaneous legal docs (14) · exams throughout.

3c. Operations artifacts (how it actually ran)

• REI Automated SOP Process doc — the end-to-end Podio-based pipeline: lead intake → contact → triage (with “dirty ARV”) → Deal Analyzer (Propstream comps → ARV Finder tab → Repair Estimator → Optimize) → Perfect Presentation → PSA. 1RvawHQgKfgRtiQElgFXk-7653udtYh1RqlvlqOh8uHQ
• Deal Analyzer component buildout doc (1Og0JXR43...) + Deal Analyzer Repair Estimator sheet (19Kodsrz...) — Patrick’s own prior rebuild work; the un-mangling has a head start.
• EOS meeting files (incl. the to-do that says it all: “WHY AREN’T SCRIPTS AND DEAL ANALYZER TIED TOGETHER WITH DOCUSIGN?”), Call Porter integration sheet, Mojo/Batch skiptrace SOPs, Google Ads SOP, FB Marketplace listings SOP, PPC lead-update sheet.
• Video Messages: two screen recordings of their tech failing (40 MB iPhone web-form failure; 350 MB “tech set up and tie together issue”) — receipts for the book’s claims.

3d. Live ammunition (ours, usable)

• 77 lead-list spreadsheets (Batch Leads 33 + Mojo Dialer 44, ~40 MB): VA/NC markets — tired-landlord, tax-default, vacants, liens, expired listings, absentee owners, cash buyers. Real fuel for the school’s worked examples and for Brandon-class automations. (Contains personal data — handle under privacy rules; never ships as course material raw.)
• ~104 contract/legal templates in Cold Call SOPs (mostly third-party packs — reference-only per Guardrail 1) + our two attorney-reviewed docs.

4. THE COMPONENT MAP — their clunk → our automation

5. PROPOSED SHAPE (for owner reaction — parallels the main school’s architecture)

• Name: TBD (Guardrail 2). Working placeholder: “The REI Automation School.”
• Tracks: mirrors the main school’s U/P/A pattern — RE-UNIVERSAL (equity, velocity of money, deal structures, magic math — original lessons at the plain-folks bar), RE-PLATFORM (each module = one working automation the learner installs and runs: the newsletter engine, the wholesaler intake, the comps collector, the offer engine, the follow-up CRM touch system, the transaction-coordination chain), RE-APPLIED (wholesaling pipeline · realtor practice · property management · land/zoning plays · dispo outreach).
• The gallery = the automation library’s real-estate category, kept as its own community per owner directive.
• Revenue: separate membership from the main school (pricing = owner decision alongside SCHOOL-BENCHMARK ranks).
• Book tie-in: the book stays universal; the REI school is where the book’s real-estate stories point readers who want Patrick’s actual domain.

6. IMMEDIATE NEXT STEPS (proposed)

1. Owner: approve charter shape + name screening; move the plain-text credentials out of the master doc (Guardrail 4).
2. Fable task queued: un-mangle the Deal Analyzer (1kPY_mC4... + Patrick’s rebuild docs) into a clean offer-engine spec — inputs, math, outputs in plain words.
3. Curriculum skeleton: draft RE-track module list against the component map (same charter-card machinery as the main school).
4. CTMS: file this as a new chapter under the education story + cross-link to platform lane for the automation-library category.

REI School Sibling Charter

2026-08-18 · owner GO · full sibling platform to the ProcessAutomater School · extends REI-SCHOOL-CHARTER-AND-SOURCE-INVENTORY.md Inherits in full: VOICE-AND-RULES.md (vocabulary + secrecy line), TRUTH-AND-STORY-DOCTRINE.md (three lanes), SCHOOL-MODULE-SPEC.md (9-section module format), the plain-folks bar (§9.2), and the honesty key. Name: TBD pending trademark screen — “REI Process Automater School” is the working label.

1. WHAT THIS SCHOOL IS

A complete, separate school platform for real estate investors and professionals: the whole investment pipeline taught in plain words, with working automations included in membership — installable on day one, deepened by the curriculum. The front door is not a lesson: it is record a process once, replay it by voice (the low-barrier door, per owner ruling). The school deepens; it never gates.

The positioning truth (Lane 3 compliant): everything the $15,000 programs claimed to be — actually automated. We teach the practice AND ship the workers.

2. CURRICULUM MAP v1

RE-UNIVERSAL track (concepts — no account needed; free acquisition tier)

RE-PLATFORM track (each module = one working automation, installed and run)

RE-APPLIED track (business-model electives; require RP1–RP4)

Recommended path: RU1→RU4 → RP1→RP5 → [RU5 before any outreach module] → RP6→RP8 → electives → RP10. RP9 joins the path when gated items clear.

3. MODULE SPEC

Inherits SCHOOL-MODULE-SPEC.md’s 9-section format wholesale, with two additions for this school: - Section 5a “Install the worker”: every RP module begins from the included automation — install first, understand second (first win before first lesson). - Section 10 “The line”: each module ends with the compliance/ethics line relevant to it (RU5 fragments distributed where they bite).

4. COMMUNITY RULES v1 (separate community, own gallery)

1. The gallery is the library. Publishing your build and installing someone else’s are first-class acts; the REI automation library IS the community’s shared asset.
2. Real results only. Testimony shared in the community follows the truth doctrine: numbers you claim are numbers you got. No fabricated wins — the community’s credibility is the product’s.
3. The host is an AI, and says so. Training sessions are hosted by the founder’s avatar (his voice and likeness, disclosed as AI) with the school corpus as its knowledge base. It teaches, demos, and answers.
4. The moderator is always on. A second AI monitors sessions: it shuts down abuse, secret-extraction attempts (“how is it built” has one answer: usage yes, internals no), and conduct that degrades the room; it mediates and escalates per protocol.
5. The consultant never has a queue. Pay-per-usage AI consulting replaces hand-raising: attention when you need it, metered fairly. (The 45-minute-queue model this replaces is named in the book — de-identified.)
6. The mindset we honor: local REI networking group leaders teach it well — pick ONE thing that steals time from your business, and target it with automation to buy back your freedom. The community’s weekly challenge is exactly that: automate one thing.
7. Affiliation disclosures: where the school connects members to services the founder’s companies profit from (funding, management), the relationship is disclosed plainly. No hidden rails.
8. Escalation to the person: extraordinary issues that the AIs can’t or shouldn’t resolve go to the operator — the exception path is real and staffed.

5. BETA SHAPE (owner constraints logged)

• Runs from the office box: 2 TB total data, limited bandwidth → small cohort, founder-tier premium entry + low monthly (value transfers day one: school + library + working automations).
• Recommended premium-entry bundle (owner said “I don’t know” — this is my call, override freely):
  1. RP5 / Expired-listing machine — the wow, and partially proven already (the scrape ran).
  2. RP1 / Wholesaler-list intake — the daily-habit moat; touches every member every day.
  3. RP4 / Offer engine — the differentiator no coaching program has; requires the un-mangling task first. (Main-school counterpart bundle when its beta opens: newsletter engine, QuickBooks de-entry, invoice generator.)
• Income workbook v0.1 started (separate file) — grows as each pricing/capacity decision lands (“build along the way”).

6. WHAT THIS CHARTER NEEDS NEXT

1. Trademark screen → real name (school + Book 2 share it).
2. Fable task: un-mangle the Deal Analyzer → offer-engine spec (blocks RP4/beta bundle).
3. Curriculum cards per module (same charter-card machinery as the main school) — on GO.
4. RP9 compliance/counsel workstream opened before any feeder build.

Expansion Pricing and Build List

2026-08-18 · owner directives from Patrick, structured for execution · companion to REI-SCHOOL-CHARTER-AND-SOURCE-INVENTORY.md

1. THE SPLIT (owner order)

Two separate school platforms, two books:

2. BOOK 2 — “the REI Automated killer” (working label, INTERNAL ONLY)

• Structure: the whole real-estate-investment pipeline, chapter by chapter, each chapter = one stage + the automation that runs it + the school module + (where built) the installable automation itself.
• Pipeline spine: lead acquisition (lists, letters-pipeline, wholesaler intake) → outreach (mail/voice/compliance-safe channels) → triage (data-mapping-first) → deal analysis (un-mangled offer engine; magic math) → offers (cash/seller-finance/hybrid) → contract → funding (see §3) → rehab management (verified-is-payable) → dispo → hold/PM.
• ⚠ NAMING/POSITIONING: “Scribe Killer” and “REI Automated killer” are internal nicknames only. In print: name competitors factually and fairly or not at all (see §5). Book 2’s public name: TBD with the school name (trademark screen).

3. THE CKC FEEDER (the vertical-integration play — owner’s words structured)

Inside the REI membership: working automations that scrape data, send offers, extract deal data, and submit it through the Century Key Capital funding platform → term-sheet applications auto-composed → financing options auto-generated → best option presented per deal (magic-math math, cash-left-in-deal, etc., real software calculations). - The pipeline literally feeds the financing company we profit from: school → automations → deals → funding. - ⚠ COMPLIANCE FLAGS (before launch, with counsel — not legal advice): lending/brokering is licensed activity state-by-state (NMLS etc.); the affiliation between the school and the lender must be disclosed to members; RESPA-adjacent referral rules may apply. Also: the CKC funnel isn’t live yet (V2 engine still being polished) — the feeder ships when the funnel does. Same timing gate as naming CKC in Book 1.

4. THE AI-RUN SCHOOL (membership without intervention — spec capture)

• “A membership that requires no human intervention is a testimony to a good system.” The cost side: the AI that performs the lessons, hosts training sessions, and answers questions on group calls.
• The host: Patrick’s avatar — his face-motion, his voice (the PAIF clone lineage), a knowledge base to help people build and solve automation shortcomings.
• The moderator: a second AI monitoring sessions — shutting down abuse, secret-extraction attempts, and behavior not conducive to the community’s educational gain; steps in and mediates.
• The consultant: pay-per-usage access anytime — the anti-queue (Story 33: no more 45-minute hand-raised waiting). Usage pricing makes attention-on-demand self-funding.
• Honesty rule carried over: the avatar is presented AS an AI host (no pretending it’s live-Patrick); the “built our own” claims follow the Lane-3 rule (describe what it does; never internals).

5. COMPETITOR POSITIONING (researched, book-safe)

• Scribe (scribehow): the SOP-capture company. Verified: raised a $25M Series B (Feb 2024) and by Nov 2025 hit a $1.3B valuation on a later round — Patrick’s “$75M” recollection is off; total raised is closer to ~$55M lifetime, verify before print. Fair-use framing for the book: Scribe records what you do and turns it into an SOP a person can follow. That’s where it ends. We record what you do and the SOP becomes a worker — the document is the byproduct, the execution is the product. Both true, both checkable, no disparagement.
• THE PRODUCT INSIGHT (owner’s, big): SOP documents are a byproduct of our process recording — we can emit the Scribe-style artifact for free on the way to something Scribe can’t do: running it. One recording → (a) an executable automation, (b) a written SOP, (c) a training asset for the school, (d) assistant-KB content. Four outputs, one capture.
• Viktor (verified earlier): $75M Series A, Slack/Teams-resident, no phone, no browser-hands. Same fair framing.
• Mentioning competitor COSTS opens the value proposition (their per-seat/credit pricing vs. ours) — collect published pricing for Scribe/Viktor/Zapier-class into the pricing model below.

6. PRICING & INFRASTRUCTURE MODEL (owner requirement — to build next)

• Beta reality: a few adopters, running from the office box (2 TB total data, limited bandwidth). Beta pricing = founder-tier, capacity-capped, priced as scarce access (premium entry + low monthly, per §7).
• Scale model needed BEFORE AWS migration: per-user unit economics — hosting cost per usage known → user price = multiple of our cost + pass-through of their AI operating costs as part of the deal. Deliverable: an income-model workbook covering each system and membership (main school, REI school, platform usage, PAIF, the AI consultant’s per-usage metering, the CKC feeder’s revenue share). Owner asked for “income models for our different systems and memberships” — queue as its own work item (xlsx deliverable, next session or on GO).
• Pricing shape (owner’s instinct, logged): premium price of entry (buys school access + information + working automations immediately usable) → lower monthly thereafter. Matches the value curve: most value transfers on day one.

7. THE LOW-BARRIER DOOR (owner question answered — see chat 2026-08-18)

The entry experience for the skeptical non-user: record a process once → replay it by voice command. No school required to start; the school deepens, it doesn’t gate. “The conversational equivalent of the Google input bar” — which is literally the landing-page hero already mocked (the one-input cell). The room objection (Story 34) is the target persona for this door.

8. AUTOMATIONS-TO-BUILD LIST (v1 — shareable / demoable / usable in the membership)

Drawn from the story bank; each is real (he’s lived the need), demoable, and priced-in value for the premium entry.

REI school launch set: 1. Expired-listing offer machine (90-day scrape → realtor/owner identification → offer letters at X% → acceptance → calendar-scheduled walkthrough) [Story 16] 2. Wholesaler-list intake (get on lists → parse inbound deals → staleness timers → immediacy contact surface) [Story 23] 3. Jurisdiction-letters pipeline (records requests via print-and-mail API → response ingestion → lifecycle-weighted lead pipeline) [Story 25] 4. Deal analyzer / offer engine (un-mangled: inputs → cash/seller-finance/hybrid outputs + magic-math readout) [Story 10, Fable task] 5. CKC term-sheet feeder (deal data → funding application → options → best-option presentation) [§3 — gated on CKC live + compliance] 6. Comps collector (address in → comps/records out, no export-import ritual) [Story 20 map] 7. Dispo blaster (buyer scrape → contact extraction → compliant outreach sequences) [Story 10] 8. Vendor-discovery monitor (Nextdoor/Reddit/FB-HOA recommendation scraping per trade/region → vendor reservoir) [Story 26] 9. Rehab payout qualifier (photo/doc submission → verified-is-payable gate → tenant/owner confirmation loop) [Story 29] 10. PM turnover chain (notice → contractor dispatch → verification follow-up → lockbox/photos → listing) [Stories 5, 19, 21]

Main school launch set: 11. Newsletter/email engine (spam-paced distribution, neighborhood/HOA segmentation — the Mailchimp/Constant-Contact killer) [Story 22] 12. QuickBooks de-entry (any-form intake → extraction → QB entries, audit gate) [Story 32] 13. Vendor self-onboarding (website signup → insurance-spec request → approve gate → doc forwarding) [Story 31] 14. Invoice generator for contractors (the friend-hero automation — give it away) [Story 30] 15. Social content pipeline (clips → edit platform → multi-platform scheduling) [Story 14] 16. Morning briefing / digest (the capstone starter) [book Ch 17] 17. Review-queue follow-up chain (3-touch, reply-halt, quiet hours) [book Ch 8, real PM practice] 18. SOP-emitter (every recording also outputs a written SOP document — the Scribe-artifact byproduct) [§5]

DECISIONS THIS DOC NEEDS FROM PATRICK

1. GO to draft the REI school platform charter as a full sibling (its own curriculum map, module specs, community rules) — extends the existing charter.
2. GO to spec Book 2’s TOC (after Book 1’s story conversion, or in parallel?).
3. Priority order for the build list (which 3 automations make the beta’s premium-entry bundle?).
4. Income-model workbook: build now or after beta capacity is decided?
5. Rich Lennon citation: reach out for a courtesy OK / possible relationship?