How Systems Replace You

By OSJJ

Open Source Jiu-Jitsu

How Systems Replace You

What a standard operating procedure actually is, the mechanism by which it lets an academy outgrow its owner, why most owners resist building them, and a complete worked example from blank page to finished document.

For any owner who knows their academy runs on them, and wants to understand how systems actually replace that.

Every academy already runs on procedures. The only question is whether those procedures live in one person's head or on paper. Procedures in the head cap the academy at the size of the one person who knows them. Procedures on paper let the academy grow past that limit, because the work no longer depends on the owner personally doing it. The transition between those two kinds of business is the entire point of building SOPs, and the construction is simpler and less mysterious than most owners think.

What is inside:

There are two kinds of academy, and only one can grow

If you walked into a hundred Jiu-Jitsu academies in a single day and watched how each one actually operated, you would notice something that would explain almost everything about why some of them grow and most of them do not.

In about ninety of them, the academy runs on the owner. The owner is the one who answers the phone, or trains whoever answers the phone, or knows the unwritten rules for what to say when. The owner is the one who handles the difficult member, decides how the intro class goes that day, makes the call about the cancellation, runs the open and the close. The procedures of the academy exist, but they live in one place: the owner's head. The academy operates because the owner remembers how it operates. If the owner is sick, the academy stutters. If the owner is on vacation, the academy stalls. If the owner is just tired, the academy quietly drops a few balls that day. The whole thing is held together by one person continuously holding it together.

In about ten of them, the academy runs on systems. The way things get done is written down. The lead response process is a document. The intro class is a defined sequence. The cancellation save conversation has a script. The procedures of the academy live on paper, accessible to anyone working there, and the owner is not the only person who can do them. The owner can leave for a week and the academy keeps running, because the systems are doing the work the owner used to do in their head.

These are two completely different businesses, and they have completely different futures. The owner-based academy is capped at the size of one human being and the number of hours that human being can stand to work. The system-based academy is not capped that way. It can grow past the owner's personal capacity, because the work no longer depends on the owner personally doing it. The difference between the two is not strategy. It is not marketing. It is not branding. It is whether the procedures of the business live in one person's head or on paper. That is the entire difference.

Standard operating procedures, or SOPs, are how an academy makes the transition from the first kind to the second. This article is about what they actually are, the mechanism by which they let a business outgrow its owner, why most owners resist building them, and how to build one yourself.

What an SOP really is

Forget the corporate associations for a minute. An SOP is not a binder. It is not a legal document. It is not something only large companies need.

A standard operating procedure is, at its simplest, the written answer to a single question: how does this thing get done in our academy, every single time, regardless of who is doing it. That is the whole concept. If a new front desk person started tomorrow and asked you, how do I respond to a new lead, you should be able to hand them a piece of paper that answers that question completely. If you cannot, you do not have an SOP for lead response. You have a habit, locked inside your own head, that produces results when you are the one doing it and unreliable results when anyone else tries.

Every academy already runs on procedures. There is no academy without them. The only question is whether those procedures are written down or whether they live in the memory of one person. Procedures that live in memory cannot be taught quickly, cannot be improved deliberately, cannot survive the bad days, and cannot be done by anyone but the person who memorized them. Procedures that live on paper can do all four. That is the whole power of an SOP. It takes something that existed only in one person and turns it into something that can exist in many people, on demand, the same way every time.

An SOP is not a binder. It is one person's working knowledge, turned into something the whole team can use.

The mechanism: how systems replace you

Here is the part most owners never have explained to them clearly, so they never quite understand why building SOPs feels like the most important thing and the most tedious thing at the same time. The mechanism by which an SOP produces growth is worth slowing down on, because once you see it you cannot unsee it.

Think about everything you currently do in your academy that nobody else there can do as well as you. The lead conversation. The intro class. The save call to the member about to cancel. The handling of a parent who is frustrated. The way you greet a member who has not been around in a while. Each of those is a task that produces value, and each of those is currently locked to you, because the way you do it lives in your head. The size of your academy is, mechanically, the number of those tasks you can personally do in a week, multiplied by the number of weeks in a year. That is the literal ceiling of an academy run on one person. It is the size of one person's bandwidth.

Now think about what happens the moment any one of those tasks gets written down well enough that another capable person can do it. The lead conversation, for example. If you take the way you handle a lead and you turn it into a real document, with the words you actually say and the timing you actually use and the follow-up cadence you actually run, and then you hand that document to a trained front desk person, two things change at once.

The first thing that changes is that the task is no longer locked to you. It can now happen ten times in a day without you being involved, because the document is doing the teaching that used to require you to be present. The capacity of the academy for that task just multiplied. The second thing that changes is more subtle, and it is the part most owners miss. The act of writing the SOP forced you to define what good looks like for that task. Before the SOP, the task was a feeling, a thing you did well by instinct but could not articulate. After the SOP, the task is a definition. And anything that has a definition can be measured, improved, taught faster, and held to a standard. Anything that has only a feeling cannot.

Multiply that effect across every task in the academy and you have the mechanism. An academy built on SOPs is one in which the owner has been gradually translated, task by task, out of the work and into the document, where many people can carry the work the owner used to carry alone. The owner is not replaced as a person. The owner is replaced as a bottleneck. Their knowledge, their standard, their way of doing things, becomes the academy's way of doing things, and the academy can grow as large as the team can carry it. That is the entire mechanism of scaling a service business, and SOPs are the unit of work that does it.

Why owners resist building them

If SOPs are this important, the obvious question is why so few academies have them. The answer is honest and worth naming, because the resistance is real and it is the first thing standing between an owner and actually doing this work.

Owners resist writing SOPs for three reasons. The first is that SOPs feel like overhead. They are not a class, not a sale, not a lead, not a sparring round, not anything that obviously moves the business forward. Sitting down to write a procedure feels like the least productive thing you could possibly do with an hour, especially compared to the thousand other urgent things competing for the same hour. So owners do the urgent things and the SOPs never get written, and the urgent things keep being urgent because no SOP exists to make them less so.

The second reason is that owners often quietly enjoy being indispensable. The fact that the academy needs them to function is, on some level, validating. It says you matter, you are central, you are not replaceable. Writing the SOPs that would make you replaceable as a worker in your own academy can feel like writing yourself out of importance. This is rarely conscious. But it is real, and it is part of why the binder stays empty. The honest reframe is that being indispensable as a worker is the thing that keeps you trapped as an owner. The goal is to be indispensable as a leader, not as the person who has to do every task.

The third reason is that owners do not know how to start. They imagine an SOP as something polished and complete, the kind of document that takes months to produce, and the size of that imagined project makes it impossible to begin. So they wait for a slow week that never comes, and a year goes by, and nothing gets written. The fix for this one is the easiest to fix, because the imagined version of an SOP is wrong. A real, working SOP is not polished. It is a usable one-page document written in plain language, built in an hour, and refined over the following weeks as it gets used. We will build one together at the end of this article, and you will see how much simpler it really is than the imagined version.

Building one from blank page to finished document

The best way to understand what an SOP actually is, is to watch one get built. So that is what we are going to do. The example will be a Lead Response SOP, which is the single highest-leverage procedure in any academy, the one most directly responsible for whether the leads you have paid to generate ever become members. By the time we are done, you will have seen the entire shape of a working SOP, and you will be able to build others on the same model.

We are going to do this in four passes. The first pass is observation. The second is a rough draft. The third is the cleaned-up working document. The fourth is the test-and-refine pass that turns the working document into a real, durable SOP. Each pass takes less time than you would think, and most of the work happens in the first two.

Pass one: observe yourself doing the work

Before you write anything, you have to know what you actually do. You will be surprised how little you can describe it without watching yourself. So the first pass of building an SOP is not writing. It is observation. The next time a lead comes in, you do not just handle it. You handle it deliberately, paying attention to what you do, in what order, with what timing, and you write each step down as it happens. Talk out loud and record yourself if it helps. Capture the actual reality, not the idealized version.

Here is what an honest first pass might look like for handling a single lead that just came in:

Lead came in at 2:14 PM, Facebook form. Saw the notification at 2:18, finished writing an email, called the number at 2:21. Lead picked up. Asked how they heard about us, asked what they were looking for, asked if they had trained before. They said no, looking for fitness and self-defense, partner does Jiu-Jitsu. Offered a free trial class. Asked when works for them. They said maybe this week. I said let's get something on the calendar, how about Thursday at 6:30. They said sure. I texted them a confirmation with the address and what to wear. Made a note in the CRM. Total time: about seven minutes.

That is your raw material. It is not an SOP yet. It is one observation of one lead, and it is messy and specific. But it is the truth of how the task actually gets done, and now you have something to work with. Do this for the next three or four leads, ideally across different situations: a phone lead, a form lead, a walk-in, a referral. You will start to see patterns in what you do. Those patterns are what the SOP is going to capture.

Pass two: turn observation into a rough draft

Now you take what you observed and pull the consistent pattern out of it. The goal is not to be exhaustive. The goal is to capture, in plain language, the spine of the procedure. What gets done, in what order, with what target timing, with what fallback if something does not go to plan. Bullet points are fine. Plain language is required. A rough draft of a Lead Response SOP, built from the observations above, might look like this:

LEAD RESPONSE SOP — ROUGH DRAFT

Step 1. When a lead comes in (form, call, DM, or walk-in), respond within 5 minutes during business hours. For leads that arrive after hours, the first response goes out within the first 30 minutes of the next business day.

Step 2. First response is a phone call. Not a text. Not an email. A call.

Step 3. If the lead does not pick up, leave a brief voicemail, then immediately send a text confirming you tried to call and offering to schedule a quick chat.

Step 4. When you reach the lead, ask three things: how they heard about us, what they are looking for, and whether they have trained before.

Step 5. Offer a free trial class. Get a specific day and time on the calendar in the same conversation. Do not let them say they will call back.

Step 6. Send a confirmation text within 5 minutes of the call, with the address, the date and time of the trial, and what to wear.

Step 7. Add the lead to the CRM with source, notes, and scheduled trial date.

Step 8. If the lead does not respond to the initial outreach, follow up: same day text, next day call, day three text, day five call, day seven final text. Stop after seven days unless they engage.

That is a rough draft. It took maybe fifteen minutes to write. It is not pretty. It is not complete. It is, however, immediately more useful than nothing, because somebody else could pick it up right now and run a recognizable version of your lead response process. That is the test of an SOP: not whether it is polished, but whether somebody other than you could use it to do the work.

Pass three: turn the draft into a working document

The rough draft becomes a working document when you clean it up, organize it into sections, and add the specifics that make it usable. This is the version you actually hand to a team member. It might look like this:

LEAD RESPONSE SOP — WORKING VERSION

PURPOSE

To ensure every new lead receives a fast, consistent, professional response that books a trial class. Speed and consistency are the goals.

STANDARD

First response within 5 minutes during business hours (9 AM to 8 PM). For leads that arrive after hours, the first response goes out within the first 30 minutes of the next business day.

FIRST CONTACT — PROCEDURE

1. Identify the lead source (Facebook form, website form, phone call, DM, walk-in, referral). Note it for tracking.

2. Call the lead. Always call first. Voice contact converts dramatically better than text-only contact.

3. If they answer, run the discovery conversation (see below).

4. If they do not answer, leave a 20-second voicemail: introduce yourself by name and the academy, say you saw their inquiry, offer a quick call back at their convenience.

5. Within 2 minutes of the voicemail, send a follow-up text: “Hi [name], this is [your name] from [academy]. I just tried you about your interest in training. Happy to answer any questions or get you scheduled for a free trial. What works best, a quick call or text?”

DISCOVERY CONVERSATION (when you reach them)

Ask three questions, in this order:

1. How did you hear about us?

2. What are you hoping to get out of training? Fitness, self-defense, sport, family activity, something else?

3. Have you trained any martial arts before, and if so, what?

Listen. Take notes. Their answers tell you what to emphasize when you describe the trial.

THE OFFER

Offer a free trial class. Say it clearly: “I'd like to invite you to come try a class for free, so you can see what we do and how it feels. We have intro classes Thursday at 6:30 and Saturday at 10. Which one works better for you?”

Always present two specific options. Never ask an open question like “when works for you” or “when this week is good” — open questions get answers like “let me check and get back to you,” and the booking dies there. Two specific options changes the question from whether they will come in to which day they will come in. The prospect picks. The trial is booked.

If both of those times genuinely do not work, offer two more. Always two specific options, never an open calendar.

CONFIRMATION

Within 5 minutes of the call ending, send a confirmation text: date, time, address, what to wear (comfortable workout clothes, no shoes on the mat), where to park, and your direct number in case anything comes up.

Add the lead to the CRM: name, contact, source, notes from the conversation, scheduled trial date.

FOLLOW-UP CADENCE (if no response to first contact)

Day 1: Initial call and text (above).

Day 2: Second call. Voicemail if no answer. No text.

Day 3: Text only. Friendly check-in.

Day 5: Third call. Voicemail if no answer.

Day 7: Final text. “Hey [name], I haven't been able to catch you. I'll stop reaching out, but if training ever fits your schedule, the door is open. Here's our number any time.”

After day 7, no further contact unless the lead initiates.

DAY-BEFORE REMINDER

The day before any scheduled trial, send a text confirming the time and expressing genuine excitement to meet them. This single touchpoint significantly reduces no-shows.

That is a usable, working SOP. It fits on roughly one page when formatted properly, it is written in language anyone can understand, and you could hand it to a trained front desk person and have them run it tomorrow. It is also still a draft, in the sense that it has not yet survived contact with real use. That is the fourth pass.

Pass four: test and refine in the real world

An SOP that has never been used by anyone but you is theoretical. The pass that turns it into a real, durable document is the one where you hand it to a team member and let them actually run it for a week or two. Whatever questions they ask you in that period are not interruptions. They are the gaps in the SOP, surfacing themselves. Every question gets answered once in conversation and then added to the document, so the next person who picks it up does not need to ask the same thing.

A team member running the lead response SOP for a week might surface questions like: what do I do if they want to come in for a class today and we have a class starting in an hour, do I let them. What do I do if they ask about prices on the first call, how much detail do I give. What do I do if the lead is a kid's parent and they want their seven-year-old to try, do I run the same script or is it different. Every one of those is a gap. Every gap gets answered in the document. The SOP grows, gets sharper, and becomes more durable with every cycle of use.

After a few weeks of this, the document has been tested by reality. It handles the common cases, it answers the common questions, and the team member running it is no longer dependent on you to fill in the blanks. That is when an SOP becomes what it is supposed to be: a piece of the academy's knowledge that exists outside of any single person's head, and that the team can run together. That is the artifact you have just built.

What you just did, abstracted

The four passes you just watched are the entire process of building any SOP in your academy. They scale to any procedure. The intro class, the cancellation save, the opening and closing routine, the way a parent's complaint is handled, the way an injured student is taken care of. Every one of these can be built the same way.

That is it. There is no secret. The whole process for one SOP is maybe four to six hours of work spread across a few weeks, most of it in short sessions, and at the end you have a piece of your academy permanently installed in writing instead of in your head.

Which SOPs to build first, and where to go next

Once you understand the model, the question becomes which SOPs to write first. The honest answer is that not every SOP is equally valuable. Some procedures, if systemized, would change the trajectory of your academy. Others would just be paperwork. The right order to build them is the order that closes the leaks costing you the most money or capping your growth the most directly.

We have written about that specific question in a separate piece, called The First 5 SOPs, which walks through the five highest-impact procedures every academy owner should build before any others, and exactly why each one sits where it does on the list. If you have read this article and you are ready to start building, that piece is the natural next step. This article taught you how to build one. That one tells you which ones to build first.

The bottom line

An academy without SOPs is an academy that runs on its owner, and the size of an academy that runs on its owner is, mechanically, the size of one human being's available time and attention. An academy with SOPs is an academy that runs on its systems, and the size of that academy is bounded by the size of the team that can carry it. These are not the same business, and they do not have the same future.

The work of building SOPs is unglamorous. It is not what you got into Jiu-Jitsu to do. It produces no class, no roll, no win, no immediate gratification of the kind teaching produces. It is the slow, deliberate translation of your working knowledge into a form that other people can use. It is, however, the work that decides whether your academy grows past you, and whether you ever get to step back from the inside of your business and look at it from outside.

Pick one procedure. Observe yourself doing it. Write the rough draft. Clean it into a working document. Hand it to someone and let them run it. Refine. Repeat with the next one. That is how an academy stops being a job and starts being a business. And it starts with one page, written in plain language, this week.

Open Source Jiu-Jitsu

Open Minds. Open Mats. Open Source.

Back to the Free Library