Deal Revival Operations Manual

Scope

This covers the back office only: publishing, scheduling, member records, and intake routing. It does not cover running the live Deal Room, reviewing deals, or anything requiring a real estate license or judgment about a member's transaction. Those stay with Drew.

Systems & access

An admin needs working access to all of these before their first week. Access is granted by Drew individually; there is no shared password vault yet.

The weekly cycle

The Deal Room runs every Wednesday at 2:00 PM ET. Everything below is anchored to that. The order matters, so it is numbered.

1. Tuesdayany time
   Text blast: Room tomorrow Manual

   Short text to the member cell list. Purpose is to get the Room onto their calendar, not to sell it. Something like: "Room tomorrow, 2 PM ET. Bring something stuck."

   Cell numbers live in the roster. Not every member has one on file.

2. Wednesday12:30 PM ET
   Readiness alert Auto

   A calendar alert fires 15 minutes before the automated post. The only job here is to confirm the computer is awake with the Claude desktop app running, because the automation drives the browser on that machine.

3. Wednesday12:45 PM ET
   Reminder post with email blast Auto

   The scheduled task checks the Skool calendar to confirm a Room is actually on for that day, then publishes the reminder to Start Here & Announcements with Send email to all members switched on. If no Room is scheduled, it skips and sends a notice instead of blasting a dead reminder.

   Confirmation arrives by push notification with the post URL. If it does not arrive, see When automation fails.

4. Wednesday~1:50 PM ET
   Text the live link Manual

   Skool generates the live URL only once Drew starts the session, which is why it cannot go in the 12:45 email. Grab it when he goes live and text it out.

5. Wednesday2:00 PM ET
   The Room runs Manual

   Drew runs it. Admin job during the session is to note which members' deals were reviewed, since that drives follow-up.

6. Aftersame day if possible
   Publish the replay Manual

   Full procedure in Publishing a replay. Do not let this slip more than a couple of days. The replay is part of what members are paying for.

Publishing a replay

Six steps, roughly 20 minutes of attention plus upload time. The order is not optional: Skool cannot validate a YouTube link while the video is still private, so YouTube has to be finished first.

1. Write the lesson first

In Skool, create the lesson under Classroom → Call Replays & Case Studies → Weekly Deal Room Replays, saved as a Draft. Title format: Deal Room Replay - Month D, YYYY.

Write the body before touching YouTube, because the same copy becomes the YouTube description. Standard structure:

• One line: date recorded, runtime, and that it is unedited
• WHAT TO WATCH FOR ... two or three bullets naming the markets and what gets run through the deal engine
• WHERE THIS FITS ... which worksheets to open while watching
• REMINDER ... real deals, different numbers, not a template and not a results claim

2. Upload to YouTube

1. Drop the recording into YouTube Studio.
2. Set the title to match the lesson title exactly.
3. Paste the lesson body as the description.
4. Set No, it's not made for kids.
5. Choose Unlisted. Never Public. Unlisted keeps it behind the community while still letting Skool embed it.

3. Wait for the checks

YouTube runs copyright and community guidelines checks during processing. Wait for both to clear before saving. Publishing early risks a strike on the channel. On a 75-minute video expect five to ten minutes after upload completes.

4. Save and copy the link

Save as Unlisted, then copy the short link, format youtu.be/VIDEOID.

5. Embed and publish the lesson

1. Open the draft lesson, click the pencil to edit.
2. Put the cursor above the first line of copy, click the video button in the toolbar, paste the YouTube link.
3. If it says Invalid video link, the video is still private or still processing. Fix YouTube, do not fight Skool.
4. Switch the toggle at the bottom from Draft to Published.
5. Save.

6. Announce it

Post to Start Here & Announcements pointing members at the lesson. Link the classroom path text directly to the lesson URL so it is one tap on mobile.

Never post the YouTube link in the community or anywhere else. An unlisted URL forwards forever. The classroom link is member-gated; non-members who click it land on the join page.

Leave the email toggle off for a replay announcement. That blast is worth more on something with a deadline.

Roster upkeep

The Google Sheet is the source of truth for anything Skool does not track: cell numbers, billing status, intent notes, follow-up. Skool is the source of truth for who is actually a member.

Refreshing it

Pull a fresh export from Skool → Members → Export and reconcile against the sheet. Add new joiners, do not overwrite existing rows, because the added columns are not in Skool's export.

The two status columns

They are deliberately separate. Mixing them makes revenue impossible to read later.

Billing is a dropdown, so the strings stay consistent and the values can be counted. Use the dropdown; do not free-type into that column.

Comped members

Everyone who joined during the founding window is tagged Founding - comped. They stay free after the community goes paid. This is an internal record only, and exists so that revenue figures can be read correctly later. It is not published anywhere.

Deal intake

Members submit stalled opportunities through the private Google Form. Only Drew sees submissions. There are three support channels and they each have one job.

• Opportunities go through the intake form. Any time, no need to wait for the Room.
• Questions go in the community feed, not DMs, so the answer helps everyone.
• Diagnostic engine access is approved manually. Members can be stuck in a holding state for a few minutes after signing up.

Every submission fires a push notification to Drew's phone through the Apps Script notifier. An admin's job is to confirm the notification fired and log the submission against the member's row in the roster.

When automation fails

The Wednesday post is the only thing currently automated, and it depends on a chain that can break. Here is what to do.

If the blast has already been used in the previous 72 hours, Skool will not send another. In that case post without the email and lean on a text instead.

Terms

MRR

Monthly recurring revenue. The predictable subscription income the community produces each month. Ten members at $149 is $1,490 MRR. It is tracked separately from deal income because it is the number that makes the business sellable and fundable.

Comped

A member given free access. Internal record only.

Founding window

The fixed launch period, Aug 18 to Sept 16, 2026. Everyone who joins inside it has access through the same end date regardless of join day.

The deal engine

Drew's diagnostic framework. Running a deal through it means producing the scorecard and ranked-exit review.

Unlisted

A YouTube visibility setting. Not in search, not on the channel, viewable by anyone holding the link. Used for every replay so Skool can embed it while it stays out of public view.

Novation

One of the six exits the diagnostic engine scores, alongside cash/flip, wholesale, subject-to, seller finance, and listing.

Still undocumented

Written down so it is visible rather than forgotten. Each of these is a gap an admin would hit in their first month.

• Gap  New member onboarding: what happens between someone joining and their onboarding call
• Gap  The text blast itself: which tool sends it, and where the opt-in consent record lives
• Gap  Diagnostic engine account approval: where that queue lives and how fast it should be cleared
• Gap  The founding-to-paid transition in September: sequence, messaging, and who does what
• Gap  Refunds, cancellations, and removing a member
• Gap  Credential handoff: there is no shared vault, so every system is granted one at a time