11:17Ross Harkness · Tutorial
Business is hard until you build systems like this
An 11-minute breakdown of the four-component system model that explains why more marketing will not fix a broken business.
August 3rd 2025The argument in one line.
Building systems without assigning named ownership to every process guarantees the business still relies on you — the missing step is not more automation but a single person responsible for each process getting done.
Read if. Skip if.
READ IF YOU ARE…
- You have built SOPs and automations but still feel like the only person who can actually run the business day-to-day.
- You run a service business — agency, coaching, consulting — with 1-5 team members who keep looping back to you with questions.
- You want a repeatable, sequenced method for delegating tasks so you can gradually remove yourself from execution.
- You have experienced the ghost-writer problem: you hired someone but their output still requires your review and rewrite every time.
SKIP IF…
- You are a solo operator with no team and no near-term plans to hire — the ownership framework requires people to assign responsibility to.
- You are looking for specific automation or AI tooling — the video explicitly argues systems are not about that.
The full version, fast.
Most business owners confuse tools (SOPs, automations, AI) with systems. A system is an input-process-output-feedback loop, and every task in your business belongs to one. The real problem is not missing systems — it is missing named ownership. Without one person explicitly responsible for each process, tasks either go undone or fall back to you. The fix is to map your business into four core functions (marketing, sales, operations, finance), assign exactly one owner per process, then use the Snowball Method — delegating tasks smallest-to-biggest — to progressively remove yourself until everything has an owner that is not you.
Free for members
Chat with this breakdown — free.
Sign in and you get 23 free chat messages on us — ask for the hook, quote a framework, find the exact transcript moment, generate a markdown action plan. Bring your own key when you want unlimited.
Create a free account →Where the time goes.
00:00 – 01:00
01 · Cold open and promise
Pattern interrupt for business owners who built systems but stayed stuck. States the video delivers the exact process to run and scale in four hours a day.
01:00 – 02:04
02 · What a system actually is
Defines the four components — input, process, output, feedback loop — using a sales system as the working example.
02:04 – 03:35
03 · The one reason systems fail
Personal ghost writing agency story. Root cause: still ran every process himself. The bottleneck is not missing systems — it is the owner never letting go.
03:35 – 05:33
04 · Mapping your business systems
Canva whiteboard walkthrough. Identify the four core functions, list every task, assign each to the matching function, sequence in logical order.
05:33 – 06:59
05 · The one thing: ownership
Ship captain metaphor. Freedom comes from assigning ownership, not building more systems. The everybody/somebody/anybody/nobody fable.
06:59 – 08:51
06 · How ownership works in practice
Managers own systems; team members own processes. One person per process. Person A / Person B marketing example.
08:51 – 11:26
07 · How to use this for your business
Two-step execution: (1) Make SOPs per task. (2) Snowball Method — list tasks you own smallest-to-biggest, delegate in order, walk each person through the systems map.
Lines worth screenshotting.
- SOPs, automations, and AI are components of a system, not systems themselves — building more tools without assigning ownership changes nothing.
- A system has exactly four parts: input, process, output, feedback loop — if you cannot name all four for a task, you cannot delegate or improve it.
- Every task in a business maps to one of four functions (marketing, sales, operations, finance) by matching its goal to the function's goal.
- Two people responsible for the same process produces the same result as nobody being responsible — assign exactly one owner per process.
- Ownership means responsible for the outcome, not the only person allowed to do the work — the owner ensures it gets done even when someone else executes it.
- The Snowball Method works because small tasks are quick to document and hand off, and each handoff frees time to tackle the next, heavier task.
- When handing off a task, walk the person through the full systems map so they see where their role fits — meaning and importance make them outperform a job description alone.
- Your business runs itself when every day-to-day task has a named owner that is not you — the goal is not fewer tasks, it is getting your name off every one of them.
- Content is not designed to get followers — as a business, content is designed to get leads. Misidentifying the goal of a task means it ends up in the wrong function.
- Managers own entire systems; team members own specific processes within systems — the hierarchy maps directly to levels of responsibility.
The one gap that keeps every system dependent on you.
WHAT TO LEARN
You are not missing a system — you are missing a named owner for every process in it, and that single gap is why everything still comes back to you.
- A system has exactly four parts — input, process, output, feedback loop — and if you cannot name all four for a task, you cannot delegate or improve it.
- SOPs, automations, and AI are components of a system, not systems themselves; building more tools without assigning ownership changes nothing.
- Every task in a business maps to one of four functions (marketing, sales, operations, finance) by matching its goal to the function's goal, not by where it feels like it belongs.
- Assign exactly one owner per process — not zero, not two — because two people responsible for the same thing produces the same result as nobody being responsible.
- Ownership means responsible for the outcome, not the only person allowed to do the work; the owner ensures the task gets done and improves over time, even when someone else executes it.
- The Snowball Method works because small tasks are quick to document and hand off, and each successful handoff frees time to tackle the next, slightly heavier one.
- When delegating, walk the person through the full systems map so they see where their role connects to everything else — the resulting sense of importance makes them perform better than a job description alone ever would.
Terms worth knowing.
- Systems map
- A visual diagram that organizes all business tasks under the four core functions with named owners beside each process.
- Snowball Method
- A delegation sequence where the owner lists every task they own from smallest to largest, then hands them off in that order so each quick win frees capacity for the next.
- Feedback loop
- The fourth component of any system — the data collected after the output (e.g., call show-up rate, conversion rate) that feeds back into improving the processes.
- Ghost writing agency
- A content production business where writers produce material under the client's name; used as the presenter's personal origin story for why he built systems.
Things they pointed at.
Lines you could clip.
05:37
“Most entrepreneurs think that freedom comes from just building systems. It does not. The actual freedom itself comes from assigning the ownership of those systems.”
02:42
“Business owners will build the systems, but then they still own the systems. They never let go. They keep being the bottleneck.”
08:47
“Ownership does not mean that they are the only person who can do it, it means that they are responsible for it getting done.”
Word for word.
Read-along
Don't just watch it. Burn it in.
See every word as it's spoken — crank it to 2× and still catch all of it. The same dual-channel trick behind Amazon's Kindle + Audible.
metaphoranalogystory
00:00So if you're like most business owners, you've probably looked into systems, made a few SOPs, and built some automations only to find yourself still stuck working ten plus hours a day wondering why your business isn't growing the way you want it to. Well, after helping countless $6.07, and 8 figure entrepreneurs systemize both their personal operations and their business, I've seen the same problem over and over again.
00:20And it is the difference in systems that let you scale in around four hours a day and systems that just feel like documents that nobody ever looks at. So in this video, I'm gonna show you the exact process for building systems in your business and how you can use them so that your business can not only run without you, but can scale faster while you work less.
00:39And you don't need any fancy automations or AI for this because that's not what a system actually is. Let me explain. Okay?
00:46So the likes of AI and automations and even SOPs are not systems, but they can be a part of your systems because a system is really just a group of things which work together to achieve an outcome and it has four components. So we have the input, the processes, the output, and the feedback loop.
01:03So for example, if you imagine a sales system, the input is a lead has booked a call. The processes are going to be the likes of your reminder sequences, taking the call, following the script, etcetera, and the goal output is the seal.
01:15You can then get feedback through data. So how many calls were booked? How many showed up?
01:20How many bought? And that data can then be used to improve the system. And knowing all of this makes running and growing a business so much easier because everything in your business is a system like that and it shows you exactly what matters in your business, what you need to focus on.
01:35But if you don't know what the input is, what the processes are, what the output is, and what feedback to look for, well, how can you ever expect to run or scale your business effectively? Well, you can't. You're essentially driving blindfolded like the first time you ever got in a car when you were 16 or 17, you could not drive that car well.
01:52Well, business is the exact same when you don't have systems. However, there's actually only one reason for this, for why systems never work out right for most business owners. And if you don't fix it, then your business will always rely on you, grow slowly, and feel stressful to run.
02:07And a few years back, I get into systems because I was running a ghost riding agency where I had no time to work on the business, I was overwhelmed, I was working every hour under the sun, and a writer for that would work for me would create a bit of content, I'd look at them and be like, crap, this is terrible, and I'd have to rewrite it.
02:23They'd miss deadlines, all the typical operational problems, and so I tried to find a solution. Turned out systems were the solution to every single problem I had. So I built them all, but yet nothing changed.
02:32I had way more clarity and I had a bit more structure and some time due to that clarity, but I was still doing everything. I was still checking in all the time, micromanaging and rewriting things and answering quick questions which were never quick.
02:44So I had to make a change and it turned out the reason my business still relied on me despite having systems was because I still ran all the systems, so everything still came back to me. And this is something which is incredibly easy to fall into and I see it all the time with my clients. Business owners will build the systems, but then they still own the systems.
03:00You know, they never let go. They keep being the bottleneck. It's like .
03:08And it happens because they miss one crucial component when building systems. But luckily, there is actually a really easy fix and quick win here, which you can get, and I'm gonna show you it in literally one minute. But for it to work, first you need to map out your system.
03:20So let me show you quickly how to do that so that we can get to the fix. I recommend doing this on the likes of Canva whiteboard, but you can do it wherever you want and first you have to identify the major functions in your business. So every single business has the four core functions of marketing, sales, operations, and finance.
03:37Now some bigger businesses will have the likes of HR and maybe even IT, but all businesses have the core four. You then need to identify the goal of each function which for marketing is to generate leads, Sales is to turn leads into customers.
03:49Operations is to deliver your product and service. And finance is to manage cash flow and profitability. You then want to list out every single task that is done in your business.
03:58Yes. Every single one. This will either take you five minutes or five hours.
04:00It depends on your business. Then write out the goal of each task, what it's designed to do. So for example, content is not designed to get followers even though often that's what business owners think they're creating content for.
04:12Really, as a business, content is meant to get leads. Now, what you'll notice is that every task has a goal that aligns with the goal of one of the functions. So put every task under the function with the same goal, then reorganize those tasks into a logical order.
04:25So for example, you can't take a sales call before you send out the reminder emails for the call, so reminder have to come before sales call. Once you've done that, you've literally mapped out your business systems. And obviously, that is only a brief overview.
04:37There can be a lot more nuance and depth than that. But if you want me to personally guide you on how to systemize your business so that you can scale in four hours a day, click the link in the description below. But now let me show you the one thing that allows these systems to then be used so that your business can run without you.
04:52So most business owners build, you know, a few automations and SOPs and then wonder why nothing changes because they skip this step. So imagine you're the , everything is systemized, everyone knows when to check the fuel and how to adjust the seals and all the rest, and it should be perfect, but you end up doing everything yourself.
05:10Why? Well, think about it like this. What happens if nobody is responsible for steering the ship?
05:15Nobody is responsible for checking the fuel? Nobody is responsible for maintaining the engine? Nobody is responsible for monitoring the route?
05:21Well, you have two options. You can either let the ship go the wrong way and the problems pile up, or you can run around and do everything yourself. And that is exactly what happens in most businesses.
05:31See, most entrepreneurs think that freedom comes from just building systems. It doesn't.
05:36The actual freedom itself comes assigning the ownership of those systems because without ownership, it's not clear who does what. And, you know, this might seem simple, but if there's any confusion, nobody will do it. In fact, there's a fantastic story about four people, everybody, somebody, anybody, and nobody, which explains this perfectly.
05:53Okay? It goes like this. There was an important job to be done, and everybody was sure that somebody would do it.
05:59Anybody could have done it, but nobody did it. Somebody got angry about that because it was everybody's job. Everybody thought that anybody could do it, but nobody realized that everybody wouldn't do it.
06:09It ended up that everybody blamed somebody when nobody did what anybody could have done. See, owner ownership isn't clear. Either nobody does it or you do it or you have to micromanage to make sure that someone else does it.
06:21And that's not freedom. Okay? This is what I figured out back when I was running my ghost riding agency.
06:26And as soon as I fixed this, my business stopped relying on me. So how do you fix it? Well, you want to go through your systems map and list out every single team member you have, including yourself.
06:37You then make someone on your team responsible for every process and every system. Okay? Just put their name beside it.
06:42And you'll likely find that you're responsible for a lot. That shows you how much your business relies on you. But that's fine because it also shows you what you can hire and delegate for.
06:51Now, managers are typically responsible for entire systems, whereas normal team members, if that's what you call them. Normal team members, what's the what's the actual name? Are responsible for processes within systems.
07:02Think about it, like managers are higher level roles, so they will have higher levels of responsibility. Now, remember the story I just told you. Well, because of that, you only want one person responsible for something.
07:13Don't have two people responsible for writing your marketing emails because then what will happen is they'll both think the other person will do it and it doesn't get done. It's a bloody headache. So only ever have one person responsible for one thing.
07:23However, one person can be responsible for multiple things. Now, get that this can be a bit confusing, so let me give you an example of this to make it super clear. Let's say you have person a.
07:33They're your marketing manager. They're responsible for your marketing system. If they're your only person in marketing, then they're also responsible for all the processes or tasks in the marketing system.
07:43But if you have a person b, who is your email copywriter, then person b will be responsible for the writing emails process in the marketing system. Now, obviously, what each person is responsible for should be super clear based on your team because you did hire them for a purpose, but a crucial bit of nuance here is that only one person can be responsible for a process.
08:02But that doesn't mean that they're the only person who can do it. Because let's say person b is off sick or on vacation or whatever, well, person a can then write your emails. But it is up to person b to communicate that with person a to ensure that their work is done, and it is up to person b to track all the data and improve that process over time.
08:19So ownership doesn't mean that they're the only person who can do it, it means that they're responsible for it getting done. Like, you own your business. That doesn't mean you have to do everything in your business, but it is your responsibility to ensure it's getting done.
08:32So how can you use this for your business to run itself? Well, there's two things that you need to do. Okay?
08:38First, you need to make sure that your team can actually do things correctly in the right way without constantly running to you. See, what used to happen to me is one of my writers would write a piece of content, and I'd be like, this is wrong, this is crap, what the fuck? And just be like, how many times do I need to tell you?
08:53And, you know, it'd be really annoying. And of course, I I just think it was because they're crap at their job, but really, it wasn't. It was all my fault.
08:58And the fix was actually super simple and completely changed how well my team did their work. So what you have to do is you make SOPs and document the step by step process for each task. This is how you maintain standards without you overlooking everything because your team can just follow the process and do things exactly how you want them done without coming to you.
09:18Now, instead of boring you with ton of SOP theory and all, I've got a custom SOP AI tool which I normally keep for clients. So what I'll do is I'll leave a link to that in the description below. Get it.
09:28It'll make bespoke SOPs for any task in your business in minutes. Now, once you make them, you then direct your team to not only follow the SOP, but if they have questions or problems, they go to the SOP first to see if it has the answer because it likely does. But if it doesn't, they then go to their manager or you, this really depends on your org structure with the problem, and then the SOP can then be updated with the answer to solve that question or problem forever.
09:50That's why standards are maintained and people do things right without you constantly being on their back or doing things for them. But for your business to roam without you, here's exactly what you need to do.
10:00Okay? You look at your systems map. You see what you're responsible for.
10:04You list the tasks out smallest to biggest. This is what I call the snowball method because what you want to do is you work through that list and delegate the tasks in that order because small tasks are easy to systemize and delegate. Right?
10:16But doing that frees up some time for you to then systemize and delegate the next slightly bigger task which takes a bit more time to systemize and delegate and this creates a snowball. So we start small, we work bigger. Okay?
10:29And see when you're delegating, do two things. You want to update the responsibilities on your systems map and secondly, want to walk the person through the systems map, their responsibilities based on the map and the SOP. This will show them the importance of their role that without it, the business cannot operate as the next thing the systems map cannot be done properly, which gives them meaning.
10:48Okay? This meaning and responsibility will make them rise to the challenge and do their Seriously, don't underestimate the impact this can have that showing someone that they're important, it can be a game changer. Right?
10:59And your business will run itself when everything involved in the day to day of your business has an owner that isn't you. Right? It's that simple.
11:05If your business has 20 tasks that are required every day for it to function, then get those 20 tasks off your plate and it will run without you. But obviously, one of the issues here is that you need your people to stick to the systems, actually use SOPs and improve their job over time. So if you want to see how you can do that, click the video on screen now and I will show you the system for it.
The Hook
The bait, then the rug-pull.
You built the SOPs. You set up the automations. You told yourself this time would be different — and then found yourself still answering the same questions, still rewriting the same content, still the last line of defense for everything. This is the tutorial that explains why that happened, and what the one missing step actually is.
Named ideas worth stealing.
01:00model
The 4 Components of a System
- Input
- Processes
- Output
- Feedback Loop
Every task in a business maps to these four stages. If you cannot name all four, you cannot run, delegate, or improve the task.
Steal forOnboarding doc for any new hire to show them how every role fits into a larger flow
03:35list
The 4 Core Business Functions
- Marketing — generate leads
- Sales — turn leads into customers
- Operations — deliver product/service
- Finance — manage cash flow and profitability
Every task belongs under the function whose goal it matches.
Steal forOrg chart or systems map scaffold for any small business
09:54model
The Snowball Method
List every task you personally own, order smallest-to-biggest. Delegate smallest first — quick to systemize, frees time to tackle the next.
Steal forAny founder trying to exit operations without burning out on the transition
06:00concept
The Everybody/Somebody/Anybody/Nobody Fable
Classic accountability story: when responsibility is shared, nobody acts. Used to prove that vague shared ownership always resolves to either the founder doing it or it not getting done.
Steal forOpening a team meeting about unclear responsibility or recurring dropped-ball conversations
How they asked for the click.
VERBAL ASK
11:00next-video
“click the video on screen now and I will show you the system for it”
Low-friction end-screen CTA to a follow-up video on getting your team to stick to systems. Also drops two description links mid-video (coaching program and SOP AI tool).
MENTIONED ON CAMERA
FROM THE DESCRIPTION
PRIMARY CTAWhere the creator wants you to go next.
OTHER LINKSAlso linked in the description.
Visual structure at a glance.
