The SOP That Saved My Sanity: How One Document Changed Everything

The SOP That Saved My Sanity

I was answering the same questions 47 times a month.

Not different questions. The same ones.

"How do we handle refunds?" "What's the login for the scheduling tool?" "Where do I find the client's previous notes?"

That's when I realized I wasn't running a business. I was running a help desk for my own team.

The Breaking Point

The breaking point came on a Tuesday.

I was on a call with a potential client worth $50K annually. Real money. The kind of client who could change our quarter.

My phone buzzed. Then buzzed again. Then my Slack lit up.

"Quick question..." "Hey, sorry to interrupt..." "This will only take a second..."

I muted my mic, answered the urgent question (it wasn't urgent), and returned to find my prospect had moved on.

$50K. Gone. Because my team couldn't find a file.

The Real Problem

The problem wasn't my team. It wasn't their intelligence or dedication. It was architecture.

Every time they asked me a question, they weren't being lazy. They were doing the only thing that worked.

Ask Jeremy → Get answer → Move forward.

That was the system. I just didn't realize I had built it.

The First SOP

I started small.

One document. One process. The refund policy they asked about 12 times a month.

I didn't write a novel. I wrote what my team actually needed:

When to process a refund:

• Client requests within 30 days
• No services delivered yet
• Account balance confirms payment

How to process it:

• 1. Log into Stripe
• 2. Find the charge (screenshot attached)
• 3. Click "Refund" (not "Dispute")
• 4. Use reason: "Customer request"
• 5. Send template email #7

Done. Five minutes to write. Saved 12 conversations per month.

The Compound Effect

That first SOP did something unexpected.

It taught my team that answers existed outside my head.

The next time someone had a question, they checked the doc first. Then they asked each other. Then, only then, they asked me.

Within 30 days, my question volume dropped 60%.

Not because questions stopped. Because answers became accessible.

The Framework That Works

After that first SOP, I built a system.

The 3-Question Test:

• 1. Have I answered this question more than twice?
• 2. Will this process exist in 90 days?
• 3. Can someone besides me execute this?

If yes to all three → Write the SOP.

The SOP Structure:

• When: Trigger conditions
• Who: Responsible role (not name)
• What: Step-by-step actions
• Where: Tools and locations
• Evidence: How to prove it's done

Keep it to one page. If it's longer, you're writing two SOPs.

The Hidden Benefit

SOPs don't just save time. They reveal problems.

When I documented our client onboarding, I found seven unnecessary steps. Steps we'd been doing for years. Steps that existed because "we've always done it that way."

Documentation forces clarity. Clarity exposes waste.

What This Actually Looks Like

Today, our team has 47 documented processes.

Not because I wrote 47 SOPs. I wrote 10.

My team wrote the rest.

Once they saw the format, they started documenting their own discoveries. "Hey, I figured out a faster way to do X. Added it to the doc."

That's the real win.

You're not building a manual. You're building a culture of captured knowledge.

The Question You're Really Asking

"But Jeremy, my business is different. Our work is too custom for SOPs."

I hear this weekly.

Here's the truth: Your client work might be custom. Your operations aren't.

How you onboard clients → SOP How you send invoices → SOP How you handle complaints → SOP How you schedule calls → SOP

The custom work sits on top of operational infrastructure. Without that infrastructure, your custom work drowns in chaos.

Start Today

Pick the question you answered most this week.

Don't think about your whole business. Don't build a documentation strategy. Don't buy software.

Just answer that one question. In writing. Where your team can find it.

That's your first SOP.

The second one will be easier. The third one will feel natural. By the tenth, you'll wonder how you ever operated without them.

Ready to stop being the bottleneck? The Founder's Filter helps you identify which tasks to delegate first, and documentation is almost always on the list.