Team, Hiring, and SOPs
SOP creation: film it once, hand it to your hires and your AI
Record a workflow once on Loom, feed the transcript to Claude, and get a numbered SOP with decision trees that your hires and your AI both follow.
Prep for Week 4: AI, live Tuesday, October 27Coming soonThis lesson is not recorded yet. Ty films it next. It will appear here, with its video and the written walkthrough, the day it goes live.
What this lesson will cover
- The SOP-first rule: never hire before the role's processes are documented; a VA without SOPs invents their own workflow, and when they leave the knowledge leaves with them
- The 5-step SOP pipeline: (1) do the task yourself at least twice, (2) record it with Loom narrating decisions not just clicks, (3) grab the auto-transcript, (4) feed the FULL unedited transcript to th
- What the skill outputs: process maps (max 7 nodes), decision trees from every IF/THEN in your narration, numbered steps with Goal/Actions/Decision Gates, screenshot placeholders, a worked example, a q
- The transformation benchmark: a 40-minute ramble (6,200 words, zero structure) became an 11-page, 6-step SOP with 2 decision trees and 7 pro tips
- Recording tools by situation: Loom for solo screen work, Fireflies for live training calls (Ty's default note-taker for ~4 years), the Teach Claude Chrome extension for browser-heavy processes
- Quality levers: narrate WHY ("I check Zillow here because the county site does not show renovation status"), include edge cases (they become decision-tree nodes), feed multiple recordings of the same
- Embed the original recording at the TOP of the finished SOP so the hire watches the real walkthrough first, then follows the doc
- Library structure: naming convention [ROLE] - [PROCESS] - [VERSION]; store the working copy in ClickUp AND the versioned library in Google Drive; quarterly review cadence
- Connect Claude to wherever the SOPs live: the same playbook that trains a human steers the AI workflows, so Claude uses your own SOPs to navigate SiftStack and pull data correctly
- SOP priorities by role: data manager first (county-specific pulls, skip tracing, upload and tagging), then caller (scripts, objection flowchart, dispositions, voicemail), lead manager (STABM daily rou
- Where SOPs come from at scale: SiftStack ships a playbook/SOP generator that produces custom playbooks by strategy, market, and team size
- 40-minute recording to 11-page SOP; screenshots cut training questions ~in half
- Recording 20-60 min, skill pass 3-5 min, polish 15-30 min
- The assembly line: Loom video in, transcript, skill, 11-page SOP out, with a 2-cent price sticker on the belt
‹ What to pay, by country and role, and why no clawbacksThe KPI system: from a revenue goal to Tuesday's dial count ›
We build this with you live in Week 4: AI, Tuesday, October 27, 1 to 4 PM ET. Add it to your calendar.
