🎯 Who this is for: Freelancers, virtual assistants, and operations consultants who want to sell SOP documentation as a clear, high-ticket productized service to small businesses, agencies, ecommerce brands, coaches, and consultants.

💡 What this guide helps you do: Collect a client’s raw process walkthrough video, turn it into a crystal-clear SOP using structured AI prompts, build a branded Notion operations handbook, and deliver it with a bulletproof revision and retainer system.

Small business founders are constantly trapped in the exact same bottleneck: “I have to explain everything to my new hires 10 times because nothing in my business is documented.”

They don’t have 40 hours to sit down and write technical documentation manuals. But they do have 20 minutes to record a screen-and-voice walkthrough on Loom while doing the task.

This guide gives you the complete blueprint to collect that messy video, run it through a battle-tested 5-prompt AI stack, construct a branded Notion operations handbook, and deliver it as a recurring $500–$1,200+ service.

⚠️ Critical Rule: AI can organize and draft information, but it should never invent business steps, fake access credentials, legal requirements, or security procedures. Always have the client verify the final SOP before it becomes an official internal company document.

1. The Service You Are Selling

The Simple Offer: Process Documentation Sprint

You are selling a Process Documentation Sprint. Your client records themselves explaining one internal workflow. You turn that recording into a structured, branded, easy-to-follow Notion SOP.

Use this exact positioning in all your conversations:

“I turn your team’s undocumented processes into clear, trainable SOPs your next hire can follow without repeatedly asking questions.”

Do not sell “AI-generated SOPs.” Clients do not care about the tool. They care about faster onboarding, fewer mistakes, less founder dependency, and smoother team delegation.

What Clients Receive in the Box:

  • One completed SOP for one workflow.
  • A branded Notion SOP page.
  • A step-by-step process written in plain, unambiguous language.
  • Required tools, links, and access permission list.
  • Input and output definitions for each major step.
  • Screenshot placeholders for visual guidance.
  • Quality-control (QA) checklist.
  • Common mistakes and edge cases breakdown.
  • One client revision round.
  • A final Notion share or duplicate link.

Ideal Client Types:

  • Marketing Agencies: Onboarding new media buyers, copywriters, and account managers.
  • Ecommerce Brands: Managing inventory fulfillment, tracking, or customer support tickets.
  • Coaches & Consultants: Handling lead intake, sales discovery calls, and client onboarding.
  • Virtual Assistant Agencies: Assigning recurring tasks to remote team members.
  • Local Service Businesses: Handling customer bookings, quotes, and follow-ups.
  • Small Online Businesses: Any business bottlenecked by a single founder-dependent workflow.

Top 10 Workflows to Document First:

Workflow Client Type Why It Matters
1. New Client Onboarding Agencies & Coaches Prevents client churn & onboarding delays
2. Customer Support Ticket Handling Ecommerce & SaaS Ensures consistent customer answers
3. Social Media Post Approval Marketing Teams Eliminates missed deadlines and brand errors
4. Blog & Article Publishing Creators & SEO Brands Standardizes formatting, tags, & links
5. Ecommerce Order Fulfillment Shopify Brands Reduces shipping mistakes and returns
6. Invoice Creation & Payment Follow-Up Service Providers Accelerates cash flow and billing cycles
7. Sales Lead Follow-Up B2B & Consultants Prevents warm leads from falling through cracks
8. Weekly KPI Reporting Founders Saves 4 hours of founder reporting time
9. New Employee Onboarding Growing Teams Standardizes first-week team training
10. Podcast or YouTube Publishing Media Brands Streamlines editing, titles, tags, and distribution
⛔ Workflows to Avoid at the Beginning: Avoid highly sensitive workflows when starting out, such as financial transaction approvals, legal compliance procedures, medical protocols, or master password-management systems.

2. Your Service Packages & Pricing

Productize your documentation service into 3 clear, predictable tiers:

Starter Tier

Single SOP Setup

$150 – $300

Best for: A client testing your service on a single bottleneck.

  • One workflow recording (up to 30 min)
  • One complete Notion SOP
  • One revision round
  • Delivery within 3 business days
Most Popular

SOP Sprint

$500 – $1,000

Best for: A client who needs a small operational system.

  • Up to 3 workflow recordings
  • 3 complete SOPs + Branded Notion Hub
  • SOP database with owners & dates
  • Two revision rounds (5–7 business days)
Agency Tier

Operations Handbook

$1,200 – $2,500+

Best for: Agencies or growing teams with multiple departments.

  • 5 to 10 workflow recordings
  • Department-based Notion workspace
  • New-hire onboarding dashboard & QA checklists
  • Live team handoff call + 2 revision rounds

Pricing Rule: Your price should increase with complexity, number of workflows, recording quality, number of team members involved, revision needs, and urgency. Never promise that clients will save an exact dollar amount or guarantee business growth.

3. The Client Intake System

When onboarding a client, send them this clear intake message so they record high-quality walkthroughs on Loom:

The Client Intake Message
Hi [Client Name], excited to document your workflow. To create an accurate SOP, please record one uninterrupted screen-and-voice walkthrough of the process. Explain it as if you are training a new employee who has never done the task before. Please include: 1. What triggers the process 2. Which tools or accounts are needed 3. Every action in the order you perform it 4. What a successful final result looks like 5. Common mistakes, exceptions, or unusual situations Please avoid showing passwords, payment-card information, private customer information, or any sensitive data. Once the recording is ready, send the Loom link and complete the short intake form below.

Client Intake Form Fields Checklist:

Use Tally.so, Google Forms, or Typeform to collect these 12 essential data points:

Recording Instructions for Clients:

  1. State the name and goal of the process.
  2. Explain when the process begins.
  3. Open the first tool or page.
  4. Narrate every click and decision out loud.
  5. Explain what information is needed at each step.
  6. Explain what the final result should look like.
  7. Mention what usually goes wrong.
  8. Explain what to do when something unusual happens.

4. Your Internal Production Workflow

Follow these 14 chronological steps to manufacture flawless SOPs every single time:

  1. Receive the intake form and Loom recording.
  2. Download or export the transcript (via Loom AI, Descript, or Whisper).
  3. Read the transcript once before using AI.
  4. Remove obvious timestamps and repeated filler.
  5. Run the raw transcript through Prompt 1 (Transcript Cleaner).
  6. Run the cleaned transcript through Prompt 2 (SOP Extractor).
  7. Identify missing or unclear instructions with Prompt 3 (Gap Auditor).
  8. Send concise clarification questions to the client if needed.
  9. Build the QA checklist with Prompt 4 (QA Generator).
  10. Format the Notion layout with Prompt 5 (Notion Structurer).
  11. Create the SOP in your standard Notion template and add screenshot placeholders.
  12. Run your internal 4-point QA checklist.
  13. Send the draft link for the client review round.
  14. Apply approved revisions, deliver final workspace, ask for testimonial, and pitch retainer.
💡 The Clarification Rule: Never skip the clarification stage. If the founder says in the video, “Then you just send the usual email,” you must ask for the exact email template, recipient trigger, timing, and expected response.

5. The 5-Step AI Prompt Stack

Copy and paste these exact prompts into ChatGPT, Claude 3.5 Sonnet, or Gemini 1.5 Pro:

Prompt 1: Clean the Transcript
Act as an operations documentation assistant. Clean the transcript below for readability without changing its meaning. Rules: - Remove filler words, repeated phrases, timestamps, and off-topic conversation. - Preserve every operational instruction, tool name, decision point, and warning. - Do not invent missing steps. - Do not rewrite vague instructions as definite facts. - Mark unclear sections using: [CLARIFICATION NEEDED]. Return only the cleaned transcript. Transcript: [PASTE TRANSCRIPT]
Prompt 2: Extract the SOP
Act as a Senior Operations Consultant. Using the cleaned transcript below, create a clear Standard Operating Procedure. Include these sections: 1. SOP Title 2. Core Objective 3. When This SOP Should Be Used 4. Responsible Role 5. Required Tools and Access 6. Required Inputs Before Starting 7. Step-by-Step Instructions 8. Expected Output 9. Quality-Control Checklist 10. Common Failure Points 11. Edge Cases and Escalation Rules 12. Screenshot or Video Placeholders For each step, include: - Action - Required input - Expected result Rules: - Use plain, direct language. - Keep steps in chronological order. - Do not add information that was not stated in the transcript. - If a detail is missing, write [CLARIFICATION NEEDED]. - Do not include conversational filler. Transcript: [PASTE CLEANED TRANSCRIPT]
Prompt 3: Find Missing Information & Assumptions
Review the SOP below as if you are a new employee trying to complete the process for the first time. Identify every unclear, missing, risky, or assumption-based instruction. For each issue, provide: 1. SOP section or step number 2. Why it may confuse a new employee 3. The exact question the client should answer Do not rewrite the SOP. Only create a clarification-question list. SOP: [PASTE SOP]
Prompt 4: Create a QA Verification Checklist
Turn the SOP below into a final quality-control checklist. The checklist must be used by a team member after completing the workflow. Rules: - Each item must be easy to verify. - Start each line with a checkbox. - Include only checks supported by the SOP. - Separate “Before Starting,” “During the Process,” and “Before Marking Complete.” SOP: [PASTE SOP]
Prompt 5: Create the Notion Layout
Transform the SOP below into a clean Notion document layout. Use this structure: - Page title with relevant emoji - Short purpose callout - “Before You Start” section - Required tools and access - Step-by-step instructions - Toggle blocks for edge cases - Checkbox list for quality assurance - “Need Help?” escalation section - [INSERT SCREENSHOT HERE] placeholders after steps that require visual guidance - Last updated and SOP owner fields at the bottom Do not change process details or add new information. SOP: [PASTE APPROVED SOP]

6. The Master SOP Template

Copy this structure directly into every new Notion SOP page:

Markdown Notion SOP Template
# [SOP TITLE] > Purpose: [Explain the business outcome this process creates.] **Department:** [Department Name] **SOP Owner:** [Role or Team Member] **Last Updated:** [Date] **Version:** [Version Number] --- ## When to Use This SOP [Explain the trigger or situation.] ## Who Is Responsible [Role responsible for completing the workflow.] ## Required Tools and Access - [Tool or platform] - [Required account or permission] - [Template, link, or folder] ## Before You Start - [Required information or input] - [Required file, asset, or approval] - [Required deadline or customer detail] ## Step-by-Step Process ### Step 1: [Action Name] **Action:** [Exact action to perform.] **Input needed:** [What is required before this step.] **Expected result:** [What should happen after this step.] [INSERT SCREENSHOT HERE] ### Step 2: [Action Name] **Action:** [Exact action to perform.] **Input needed:** [What is required before this step.] **Expected result:** [What should happen after this step.] [INSERT SCREENSHOT HERE] ## Quality-Control Checklist - [ ] [Verification item] - [ ] [Verification item] - [ ] [Verification item] ## Common Problems & Edge Cases
[Problem or error title] **What to do:** [Clear fix or escalation instruction.]
## Escalation Rules Contact [Role or Person] when: - [Situation 1] - [Situation 2] - [Situation 3] ## Related Resources - [Template link] - [Folder link] - [Related SOP link]

7. Build the Notion Client Handbook

For Standard and Premium packages, assemble a complete company dashboard called [Client Name] Operations Handbook.

Handbook Homepage Sections:

  • Welcome Message: Overview of the operations handbook.
  • Quick-Start Links: Direct links to most frequently used SOPs.
  • Department Navigation: Clean visual buttons to jump to departments.
  • SOP Master Database: Filterable table of all company SOPs.
  • “Start Here for New Hires” Page: First-week onboarding path.
  • Update Request Form: Embedded form for team members to flag outdated steps.
  • Contact & Escalation Directory: Who to contact when blockers arise.

SOP Database Properties Schema:

Property Type Purpose
SOP Name Title Descriptive name of the process
Department Select Operations, Sales, Marketing, Support, etc.
SOP Owner Person / Text Role responsible for process accuracy
Status Status Draft / In Review / Approved / Archived
Last Updated Date Date of last verification
Priority Select High / Medium / Low
Related Tools Multi-Select Loom, Notion, Stripe, Shopify, Slack, etc.
Recording Link URL Link to original founder video walkthrough
Approval Status Checkbox Verified by founder / manager

Standard Department Categories:

Operations • Sales • Marketing • Customer Support • Content • Finance • Fulfillment • Team Onboarding

Professional Notion Design Rules:

  • Use the client's official brand logo at the top of every page.
  • Use one primary brand color accent only (avoid distracting multi-color setups).
  • Keep headings and typography consistent across all pages.
  • Use short sections and generous white space for scannability.
  • Use callout blocks only for important warnings or prerequisites.
  • Use screenshot placeholders where visual actions matter.
  • Do not overload pages with decorative GIFs or widgets.
  • Build for a brand-new junior employee, not for the founder who already knows the process.

8. Quality-Control Verification Checklist

Run your SOP through this 4-tier verification matrix before sending it for client review:

1. Accuracy Checks

2. Usability Checks

3. Completeness Checks

4. Privacy & Security Checks

9. Draft Review and Revision System

Send the draft for review with structured guardrails so revisions don't drag on forever:

Draft Review Message Script
Hi [Client Name], The first SOP draft is ready for review. I structured it so a new team member can understand the workflow, required tools, step order, quality checks, and common issues. Please review these three areas: 1. Is every step accurate? 2. Is anything missing that a new hire would need? 3. Are there any screenshots, templates, or links you want added? Please send all revisions in one message or comment round by [date]. Once approved, I’ll finalize the Notion handbook and share the final delivery link.

Strict Revision Boundaries:

  • One revision round is included in the Starter package.
  • Two revision rounds are included in Standard and Premium packages.
  • Definition of Revision: Corrections to the original documented workflow.
  • A brand-new workflow, department expansion, or complete tool change is a separate paid scope.
  • All client team feedback must be consolidated through one primary decision-maker.

10. Final Delivery & Testimonial System

Final Delivery Message Template:

Final Delivery Message
Hi [Client Name], Your SOP handbook is complete. You can access it here: [NOTION LINK] Included in this delivery: - [Number] completed SOPs - Branded Notion workspace - Quality-control checklists - Common issue and escalation sections - Screenshot placeholders for future team updates Recommended next step: Ask one team member who did not create the process to follow the SOP once. Their questions will reveal any missing details before you use it for onboarding. Thank you for trusting me with this project. If you would like, I can document your next highest-priority workflow and keep the handbook updated as your business grows.

Ask for a Testimonial Script:

Testimonial Request Script
Hi [Client Name], Thank you again for the opportunity to organize your workflow. Would you be open to sharing a short testimonial about: - What was difficult before the SOP existed - What you found useful about the final handbook - Whether the documentation will help your team onboard or delegate more easily Even 2–3 sentences would help a lot!

11. How to Turn One Project Into a $500–$1,500/Mo Retainer

Ask the founder this single qualifying question during the final delivery:

“Which process causes the most repeated questions, delays, or mistakes in your team right now?”

What Monthly Operations Documentation Support Covers:

  • Documenting 2 to 4 new SOPs every month.
  • Updating existing SOPs whenever tools, dashboards, or team roles change.
  • Adding new screenshots and annotations.
  • Tracking workflow modifications across team members.
  • Collecting team feedback and friction logs.
  • Performing a monthly Notion workspace cleanup and audit.
  • Maintaining a rolling priority list of undocumented processes.

The Monthly Retainer Pitch Script:

Retainer Pitch Script
Now that the first SOP is complete, the easiest way to keep your operations system useful is to document processes as they change instead of waiting until everything becomes disorganized again. I can support this through a monthly documentation retainer ($500–$1,000/mo) that covers new SOPs, updates, screenshots, and handbook maintenance. The goal is simple: every repeatable process should be easy for the right team member to follow without depending on you for repeated explanations. Would you like to put this in place starting next month?

12. How to Find Clients & Viral Content Hooks

Use these 5 battle-tested content hooks on LinkedIn, Twitter/X, and Instagram:

  • “If your new hires keep asking the same questions, you do not have a people problem. You have a documentation problem.”
  • “A founder explaining the same task every week is usually an undocumented SOP waiting to be created.”
  • “Your team should not need to message you to learn how to send an invoice, publish a post, or onboard a client.”
  • “One 30-minute screen recording can become a training asset your team uses for months.”
  • “The best SOP is not a long document. It is a clear process a new hire can follow without guessing.”

The 2-Step Soft Call to Action:

Hand-Raiser CTA: “Comment ‘SOP’ and I’ll send you my workflow for turning a screen recording into a clean Notion handbook.”

Simple Direct Outreach Message:

Cold DM / Email Outreach Template
Hi [Name], I noticed your business is growing and likely has repeatable tasks across [relevant area: client onboarding, fulfillment, content, support]. I help small teams turn founder walkthroughs into clear Notion SOPs that new hires can follow without repeated training. If documenting one recurring workflow would be useful, I can send a short example of what the final SOP handbook looks like. No pressure either way!

Outreach Rule: Personalize every message. Do not mass-send identical outreach or make unrealistic claims about saving money, eliminating mistakes, or guaranteeing results.

🚀 Your Immediate First Action

Build Your Portfolio Sample Today:

Choose one simple workflow for a sample portfolio piece, such as “How I turn a Loom recording into a Notion SOP.” Record yourself for 5 minutes, run it through the 5 prompts in this guide, and build the Notion page.

Having this single working example link in your pocket will make signing your first $500 client 10x easier!