DataSift
Business Operations

SOP Creation Guide

Turn any workflow into a training-ready playbook in minutes.

Record yourself doing it once. Get a polished SOP back. Every hire starts with the system, not your availability.

~12 min read
The Problem

The Hire-Without-Training Trap

Most operators hire people without SOPs in place. The result is predictable and painful.

You hire a VA. You spend two weeks training them live, on calls, over Zoom, answering the same questions repeatedly. They get decent at the job. Then they leave after 60 days.

Start over. From scratch. Because the knowledge lived in your head, not a system.

That is not a hiring problem. That is a documentation problem. And the Playbook Creator skill solves it in a single session.

See all available skills → Claude Skills for REI

Do This

Build SOPs before posting job listings. Your first hire should read the system on Day 1, not wait for you to be available.

Not This

Train every new hire from scratch via live calls. You become the bottleneck. When they leave, the knowledge leaves with them.

I actually use the Playbook Creator internally at DataSift too. Every new process gets recorded, transcribed, and fed through the skill before anyone else touches it.
The Transformation

From 40-Minute Ramble to 11-Page Playbook

One training call. One transcript. One skill. The difference is night and day.

What You Recorded

...so basically what you want to do is go to the county website, and like, I usually use Chrome for this but you can use whatever, and then you're going to look for the Register of Deeds or sometimes it's called the Clerk of Courts, it depends on the state... anyway, click on that and then, wait let me find it, okay so there's usually a search page somewhere...

40 minutes. 6,200 words. Zero structure.

What the Skill Produced

4-Phase Process Map with decision gates at each stage
6 Numbered Steps with Goal, Actions, and Decision Gates
2 Decision Trees for property type routing and verification
Screenshot Placeholders at every critical UI interaction
Worked Example walking through a real Knox County property
Quality Checklist with 6 verification items

11 pages. 6 steps. 2 decision trees. 7 pro tips.

The Process

The 5-Step SOP Pipeline

Record once, document forever. Five steps from messy knowledge to clean system.

1 LEARN Learn the Skill 2 RECORD Record It 3 TRANSCRIBE Get Transcript 4 SKILL Feed to Skill 5 DEPLOY Polish & Deploy

Step 1: Learn the Skill

Do the task yourself first. You cannot document what you have not done. If you are building a foreclosure pull SOP, pull foreclosures yourself at least twice.

Time: Varies (1-4 hours for first attempt)

Common mistake: Trying to document a process you watched someone else do. You miss the decision points.

Step 2: Record It

Open Loom (or Fireflies for meetings). Hit record. Walk through every click, every decision, every "if this then that" moment. Narrate your thinking, not just your clicks.

Time: 20-60 minutes per recording

Common mistake: Rushing through. The more thorough and detailed you are, the better outputs you get back.

Step 3: Get the Transcript

Loom auto-transcribes every recording. Click the transcript tab, copy the full text. For Fireflies, the transcript is available in your dashboard within minutes.

Time: 2 minutes

Common mistake: Editing the transcript before feeding it to the skill. The skill handles messy input. Give it everything.

Step 4: Feed to Playbook Creator

Open Claude with the Playbook Creator skill active. Paste the transcript. The skill extracts process maps, decision trees, numbered steps, and screenshot placeholders automatically.

Time: 3-5 minutes

Common mistake: Feeding short or vague descriptions. The skill works best with full, unedited transcripts.

Step 5: Polish and Deploy

Review the output. Replace screenshot placeholders with actual screenshots from your screen recording. Store in your Google Drive SOP library by role. Share with your next hire on Day 1.

Time: 15-30 minutes

Common mistake: Skipping the screenshot step. Screenshots cut training questions by half.

Recording Tools

Capture the Knowledge

Three tools for three situations. Pick the one that fits how you work.

Loom (Primary)

Screen + camera recording with auto-transcription. Best for solo screen-based tasks.

Fireflies.ai (Meetings)

AI recorder for Google Meet and Zoom. Best for training calls and Q&A sessions.

Live Training + Teach Claude

Record any session. The Teach Claude Chrome extension records browser actions directly.

Loom

Free tier available. Screen recording with camera overlay so your hire sees your face while learning. Auto-transcription means you never have to type a word. Click the transcript tab after recording, copy, paste into Claude.

Best for: Data pulls, CRM setup, filter configuration, any solo workflow on screen.

URL: loom.com

Fireflies.ai

Joins your Google Meet or Zoom call as a bot participant. Records, transcribes, and summarizes the entire meeting. Perfect for capturing training sessions where you are teaching a VA live.

Best for: Training calls, Q&A sessions, live walkthroughs with team members.

URL: fireflies.ai

Live Training + Teach Claude

For in-person training or sessions where Loom is not practical. Record via Zoom or phone. The Teach Claude Chrome extension captures browser actions as structured steps, which can supplement or replace transcript-based input.

Best for: In-person training, phone-based workflows, browser-heavy processes.

The more thorough and detailed you are, the better you will get the outputs back. If you recorded the same process three times, feed all three transcripts for a richer, more complete SOP.
The Skill

Playbook Creator Deep Dive

Download the skill. Activate it. Feed your transcript. Get a polished SOP back.

Download the Playbook Creator Skill: Google Drive (.skill file)

1

Download the .skill file

Click the link above. Download the file to your computer. It is a single file containing the skill instructions, templates, and examples.

2

Upload to Claude

Open claude.ai. Start a new conversation. Click the attachment icon and upload the .skill file. Claude will confirm the skill is active.

Uploading the Playbook Creator skill to Claude

Upload the .skill file to any Claude conversation.

3

Feed your transcript

Paste the full transcript from Loom or Fireflies. You can also paste written descriptions, existing docs, or screen share narration. The skill accepts any raw input format.

What Goes In, What Comes Out

Inputs

Raw transcript from Loom or Fireflies. Written process description. Existing documentation. Screen share narration. Multiple recordings of the same process.

Outputs

SOP or Playbook document. Mermaid process maps (max 7 nodes). Decision trees for every fork. Screenshot placeholders. 5th-grade reading level. Pro tips extracted from your narration.

Cost: Claude Pro at $20+/mo. No Max plan required. The Playbook Creator skill works on the standard Pro subscription.

Real Example

Anatomy of a Generated SOP

A real 40-minute training call on pulling Knox County foreclosures became this 11-page SOP. Here is what each section contains.

Source and Extraction Summary

Source: 40-minute training call on pulling foreclosure data from Knox County, TN.

The Playbook Creator extracted:

  • 6 numbered steps with goals, actions, and decision gates
  • 2 decision trees (property type routing, verification)
  • 3 tools identified (County website, Google Sheets, DataSift CRM)
  • 7 pro tips from the narrator's experience
  • 1 worked example with real property data

4-Phase Overview Flowchart

The skill automatically generates a Mermaid process map showing the high-level phases. Each phase contains 1-2 steps with clear decision gates between them.

Phases: Research (identify source) → Access (navigate county site) → Extract (pull and clean data) → Upload (format for CRM).

Process map from the generated SOP showing 4 phases

Auto-generated process map with decision gates between phases.

Decision Trees

The skill identifies every IF/THEN fork in your narration and builds visual decision trees. In this SOP, two key forks emerged:

1. Is This a Real Foreclosure? Check for Lis Pendens filing, verify against Register of Deeds, confirm active status.

2. Property Type Routing: Residential → standard comp workflow. Commercial → skip (outside scope). Land → different valuation method.

Decision tree for property type routing

Decision tree extracted from narrator's IF/THEN statements.

Step-by-Step Structure

Each step follows the same format: Goal (what you are trying to accomplish), Actions (exactly what to click/type/check), Decision Gates (what to verify before moving on), Screenshot Placeholders (where to add visual proof), and Pro Tips (wisdom from the narrator).

Example step: "Step 3: Search for Foreclosure Notices. Goal: Pull all active Lis Pendens filings. Actions: Navigate to Document Search, set Instrument Type to 'Lis Pendens', set date range to last 90 days, click Search."

Step-by-step section showing goal, actions, and decision gates

Every step has Goal, Actions, Decision Gates, and Pro Tips.

Worked Example: All Tassel Pike, Knox County

The skill pulled a real property from the narration and walked through the entire process end-to-end. This gives your hire a concrete reference point. They are not reading abstract instructions. They see exactly what the output looks like for a real address.

Worked example showing real Knox County property walkthrough

Real property walkthrough extracted from the training narration.

Quality Checklist

Every generated SOP ends with a quality checklist. Six items your hire checks before marking a pull complete. Plus a Common Problems table for troubleshooting and a Quick Reference card they can print.

Checklist items: Data formatting correct, all fields populated, duplicates removed, property status verified, upload to CRM confirmed, screenshot of final list saved.

Quality checklist from the generated SOP

Built-in quality check ensures nothing gets missed.

Every SOP you create references DataSift workflows. Your team's playbook and their daily tool are the same system. Create Your Account →
Role SOPs

SOPs by Role

Every role needs different SOPs. Start with the role you are hiring for next.

Data Manager

The biggest need. Everyone has a different process for pulling data.

Cold Caller

Scripts, objection handling, disposition tracking, follow-up cadence.

Lead Manager

Daily STABM routine, appointment setting, temperature follow-up.

KPI Tracker

Daily sheet entry, weekly review prep, expense tracking.

Data Manager SOPs (Priority #1)

This is where most operators start. Your Data Manager handles county data pulls, skip tracing, list uploads, data cleaning, and CRM formatting. Every market has different county websites, different data formats, different quirks.

SOPs to build first: County-specific data pull (one per county), skip tracing workflow, list upload and tagging, data cleaning and deduplication, CRM field mapping.

Cross-references: First-to-Market Data Sourcing, Deep Prospecting

Cold Caller SOPs

Callers need scripts they can follow, objection flowcharts for when sellers push back, disposition codes for every call outcome, and a clear voicemail framework. Record yourself making 10 calls and the Playbook Creator will extract the patterns.

SOPs to build: Opening script by list type, objection handling flowchart (price, timeline, third party, trust), disposition and status assignment, voicemail framework, follow-up cadence by temperature.

Cross-references: Niche Sequential Marketing, Lead Management

Lead Manager SOPs

The Lead Manager lives in the CRM. Their daily routine starts with STABM (Status, Task, Board, Message) before any outbound calls. They need SOPs for appointment setting, temperature-based follow-up schedules, and the push-back loop when sellers go cold.

SOPs to build: STABM daily routine, appointment setting scripts, hot/warm/cold follow-up cadence, task management workflow, CRM status change procedures.

Cross-references: Lead Management & CRM, CRM Tasks

KPI Tracker SOPs

KPI tracking is where accountability meets data. Your tracker needs SOPs for daily sheet entry (which columns are admin-updated vs self-reported), weekly review preparation, caller accountability scoring, and expense tracking.

SOPs to build: Daily KPI sheet entry, weekly review dashboard preparation, caller performance scoring, expense categorization, monthly trend reporting.

Cross-references: KPI Tracking, Company Audit

SOP Library

Building Your SOP Library

A Google Drive folder by role with version control. Simple. Scalable. Findable.

Naming Convention

[ROLE] - [PROCESS] - [VERSION]
Example: Data Manager - Knox County Foreclosure Pull - v2.1

Storage Structure

Create a top-level "SOPs" folder in Google Drive. Inside, create one subfolder per role. Store the current version and keep older versions in an "Archive" subfolder. When you update a process, increment the version number.

8-Step SOP Verification Ladder

0 / 8 complete

Record Loom of your #1 daily workflow
Pick the task you do most often. That is your first SOP.
Feed transcript to Playbook Creator
Paste the full, unedited transcript. Let the skill do the structuring.
Review and add screenshots to placeholder locations
Go back through the Loom recording. Screenshot every UI step the skill flagged.
Create a Data Manager SOP folder in Google Drive
Start your library with the role you are hiring for first.
Record a Cold Caller script walkthrough
Even if you are not hiring a caller yet, this is the second most common SOP need.
Create SOPs for every CRM status change
When does a lead move from New to Hot? From Warm to Dead? Document the triggers.
Build an onboarding folder with role-specific SOPs
Combine SOPs into one folder your hire reads on Day 1. No live training needed.
Schedule quarterly SOP review
Processes change. Set a recurring calendar event to audit and update your library.
Blueprint Strategies

Blueprint SOP Priorities

Where you start depends on your blueprint. Each has different first-hire SOP needs.

Blueprint A: Launchpad

You are the team. You are doing everything yourself. Build SOPs anyway. When you hire your first Data Manager ($500-$700/mo), they need to hit the ground running without your availability.

Priority SOPs: County data pull (one per market), marketing cadence setup, lead follow-up workflow.

First hire SOP focus: Data Manager. Document your entire data process before posting the job listing.

Blueprint B: Optimizer

You are time-poor with a W-2. Your Lead Manager ($2,000-$3,000/mo) needs SOPs on Day 1 because you cannot train them live during business hours. Build the lead management daily routine SOP before hiring.

Priority SOPs: Lead management daily routine (STABM), appointment setting scripts, CRM workflow, status change triggers.

First hire SOP focus: Data Manager + Lead Manager (both Week 1). Build SOPs for both before hiring.

Blueprint C: Specialist

Your deep prospecting process IS your competitive advantage. The genealogy research, county record navigation, and heir identification that makes your niche work cannot live in your head alone.

Priority SOPs: Genealogy research workflow, county record navigation, verification ladder, heir identification process.

First hire SOP focus: Data Manager ($500-$700/mo). Your deep research process is complex enough to justify detailed documentation.

Blueprint D: Scale-Up

SOPs are infrastructure. Every role, every process. You are building a machine where people are replaceable components (not because people do not matter, but because the system matters more than any individual).

Priority SOPs: Every role SOP, KPI tracking procedures, hiring onboarding packets, team accountability workflows.

First hire SOP focus: Data Manager ($500-$700/mo), then document every subsequent role before posting.

Best Practices

Getting Better Output

The quality of your SOP depends on the quality of your recording. Here is how to maximize both.

Do This

Narrate your decisions, not just your clicks. "I check Zillow here because the county site does not show renovation status" gives the skill context it cannot infer from clicks alone.

Not This

Rush through the recording to save time. A 20-minute thorough recording produces a better SOP than a 40-minute unfocused one.

Do This

Include edge cases. "If this is a mobile home, skip it because we cannot finance those" turns into a decision tree node automatically.

Not This

Skip the screenshot step after the skill generates the SOP. Screenshots cut training questions by half. Your hire should see exactly what the screen looks like at every step.

Do This

Feed multiple recordings for richer output. If you recorded the same process three different times, the skill will find patterns across all of them and produce a more complete SOP.

Not This

Treat the first output as final. Review it. Walk through the steps yourself. Catch anything the skill missed. Then add your screenshots and deploy.

Your SOP library is your company's most valuable asset after your deal pipeline. When a VA leaves, you lose a person. When you lose your SOPs, you lose the system.
Key Terms

Key Terms

Click any card to reveal the definition.

SOP

Click to flip

SOP

Standard Operating Procedure. A step-by-step document that tells someone exactly how to complete a task. Goal, actions, decision gates, screenshots at every step.

Playbook

Click to flip

Playbook

A strategic framework document. Broader than an SOP. Contains multiple processes, decision trees, and the reasoning behind why things are done a certain way.

Playbook Creator

Click to flip

Playbook Creator

A Claude skill that transforms raw transcripts and process descriptions into structured SOPs and Playbooks. Generates process maps, decision trees, numbered steps, and screenshot placeholders.

Loom

Click to flip

Loom

Screen recording tool with built-in auto-transcription. Free tier available. Records your screen and camera simultaneously. The primary recording tool for SOP creation.

Fireflies.ai

Click to flip

Fireflies.ai

AI meeting recorder and transcriber. Joins Google Meet or Zoom calls as a bot participant. Ideal for capturing live training sessions and Q&A calls for SOP creation.

Mermaid Diagram

Click to flip

Mermaid Diagram

A text-based diagram format that the Playbook Creator uses to generate process maps. Maximum 7 nodes per diagram. Renders as visual flowcharts in compatible viewers.

Decision Tree

Click to flip

Decision Tree

A visual IF/THEN map extracted from your narration. "If the property is commercial, skip. If residential, proceed to step 4." Removes ambiguity for your hire.

Screenshot Placeholder

Click to flip

Screenshot Placeholder

A marker in the generated SOP that says "insert screenshot here." The skill identifies every UI interaction that needs visual proof. You replace placeholders with actual screenshots from your recording.

5th-Grade Reading Level

Click to flip

5th-Grade Reading Level

The target readability for generated SOPs. Short sentences, simple vocabulary, no jargon without definition. Any hire can follow regardless of their experience level or English proficiency.

SOP Library

Click to flip

SOP Library

Your Google Drive folder system organized by role. Contains all current SOPs with version numbers. When a VA leaves, the next hire reads the library. No retraining needed.

Knowledge Check

Knowledge Check

Test your understanding of the SOP Pipeline framework.

1. What is the first step in the SOP Pipeline before recording?

2. Which recording tool is best for solo screen-based workflows?

3. What does the Playbook Creator auto-generate from a transcript?

4. Why does the skill target a 5th-grade reading level?

5. What is the difference between an SOP and a Playbook?

6. When should you build your first SOP?

7. How do you improve Playbook Creator output quality?

Book Your Free Strategy Call 30 min. No obligation.