top of page

Too Small for Scalable OS? The Business Operating System for a One-Person Business

Writer: Brian Lathe
Brian Lathe
6 days ago
6 min read

Updated: 5 days ago

Too Small for Scalable OS? You're Not Too Small for an Operating System

Here's a strange thing to say on a blog that competes for your attention: Ryan Deiss is probably right, and his system probably works — for the people it's built for.


Scalable.co says who that is, in plain text. Their Scalable Operating System is built for founders generating $2M–$20M in annual revenue with a growing team of 5–10+ people (their current homepage widens it to a team of 5–50). If that's you, honestly, go look at their install. This article is not for you.


This article is for the much larger group of people his ads are reaching right now: the business of one. The freelancer, the coach, the creator, the one-person agency, the network marketer, the side-business operator working a day job — who watched the same video I did, thought "that's exactly my problem, everything depends on me," clicked through, and hit the wall. Too small. No team. Nowhere near $2M.


I'm one of those people. I run a one-person business, and I work a job besides. And I'm going to tell you the thing I had to learn the slow way:


**You are not too small for an operating system. You're too small for his operating system — because his assumes a team, and you are the team.**


What an operating system actually is, stripped of the team

Deiss defines his system by borrowing the computer definition: an operating system is a set of algorithms and a common language that lets different components work together toward the outputs you want. Forget the branding for a second. Underneath it, his six tools are answers to six questions every business has to answer — including a business of one:

  1. How does value actually flow through this business? (His "Value Engines" — a map from first touch to sale, and from sale to a happy customer who refers.)

  2. Which few steps are so high-stakes and error-prone that they need a written procedure? (His "Playbooks" — and notice: he only documents 10–20 steps. He once shut his company down for a month to document everything, and nobody ever read the binders.)

  3. Who is accountable for each step? (His accountability canvas — with the stated goal of getting the founder's name off as many steps as possible.)

  4. What numbers do we watch every week? (His Scorecard — weekly, simple, one page. A metric is only "red" if it's behind and there's no plan.)

  5. When do we review, and when are we allowed to change direction? (His rhythm — weekly pulse, monthly review as the only pivot point, quarterly planning. No annual plan.)

  6. How does the team decide without asking the founder every five minutes? (His one-page "Clarity Compass" — goals, purpose, values, and competitive advantages, written down so other people can decide like the founder would.)

Now look at those six questions with a team of one. Questions 1, 2, 4, and 5 don't need employees at all. They're thinking tools, and they work at any size — arguably they matter more at size one, because there's nobody to catch what you drop.


Questions 3 and 6 are the ones that break. "Who is accountable?" — you. It's always you. "How does the team decide without the founder?" — there is no team. That's the wall you hit. It's not a motivation problem and it's not a knowledge problem. The team-shaped hole is the whole problem.


Filling the team-shaped hole without hiring

This is the part the team-based systems can't sell you, because their answer to the hole is a payroll. There are three other answers, and I've tried them in order:


Answer one: do it all yourself, harder. That's not an operating system, that's a treadmill. Deiss calls the default state "YouOS" — you are the operating system, everything lives in your head, and the business stops when you stop. He's right about the diagnosis at every size. A solo operator with a job lives this in its purest form: the business only moves during the hours you're not at work, not asleep, and not burned out.


Answer two: templates and apps. A Notion template, a project board, a CRM subscription. These help, up to a point — they're better than sticky notes. But nothing in them runs. A template doesn't remember what you decided last month, doesn't notice you forgot to follow up, doesn't do the follow-up. You are still the engine of every single step; the template is just a nicer notebook. Most "solopreneur systems" for sale are this answer in a nicer box.


Answer three: make the system itself do the team jobs. This is the bet I built my business on, and it's what this blog documents. Instead of employees, you build desks — named functions with defined jobs: a contacts desk that keeps every relationship and follow-up, a campaigns desk, a content desk, a deals desk, a knowledge desk that acts as the business's memory. In my system those desks are worked by AI agents under written rules, and — this is the part that matters — the remembering lives in the system, not in my head. Every ruling, every contact, every "where did we leave that" is written down where the desks can read it. I work a job. The system keeps working while I'm there, and when I sit down at night, it shows me the small pile of things that genuinely need me — not the thousand things that used to.


Does that make me unnecessary? No — and this is where I part company with Scalable's endgame, which they literally brand as fading the founder out. In a one-person business, you are the judgment, the relationships, and the trust your customers buy. The goal isn't to remove you. The goal is to stop spending you on work a system can carry, so the hours you do have go to the work only you can do.


The test that tells you if it's working

Deiss has a good test: the 30-Day Vacation Test. If your business falls apart when you disappear for a month, you don't have a business, you have a job you own.


A solo operator who works a job can't wait for a vacation to find out. So I run a harder, more frequent version: the silence test. The business gets no input from me — I'm at work, or asleep, or just silent for a weekend — and afterward I look at three things. What kept moving? What stalled? And how many times did the system truly need me, versus how many times it just needed a rule I hadn't given it yet? Every stall becomes the next thing to fix. That count — how often the system has to tap my shoulder — is the single most honest number in a one-person business, and watching it go down month over month is what "installing an operating system" actually feels like at this size.


Where to start, if you hit his wall and landed here

You don't need all six answers at once. Start where Deiss starts, because he's right about the order: map the flow first. On one page, draw how a stranger becomes a customer in your business, step by step, asking "then what?" until you reach the sale — then keep going until you reach a delivered result and a referral. Most solo operators have never seen their whole business on one page, and the first time you draw it, you'll spot the step that's been silently leaking for a year. That map costs you an evening and nothing else, and every other tool — the scorecard, the procedures, the desks — hangs off it.


Then ask which of the six questions is your actual bottleneck — and whether you're a fit for a team system like Scalable's, a template, or a solo operating system like mine.


Because here's the bottom line his ads are accidentally teaching thousands of solo operators this year: the problem was never that you're too small to systemize. The problem is that the famous systems were built for a company you don't have. Build the one for the company you do have — a company of one, run by a system that remembers, so it can finally run without eating your life.


The scorecard runs inside SuccessBrian OS — and it is free

SuccessBrian OS is the system I run my own one-person business on. The weekly scorecard from this article works inside it.


In plain words: once a week, you type in five numbers — new leads, sales talks, work delivered, things shipped, cash in. The system keeps them, shows you which ones hit your target and which ones fell behind, and remembers the plan and the promise you made. You do not have to keep a spreadsheet alive. You do not have to remember anything. The system remembers for you.


It costs nothing. There is no form to fill out and nothing to buy. Download it and use it:



Rather start on paper? The scorecard template is printed in full on this blog, in "The Weekly Scorecard for a One-Person Business." Start there if you like. Just start this week.


SuccessBrian OS is not affiliated with Scalable.co or Ryan Deiss. Scalable's fit criteria and system descriptions above are from their public manifesto page and case study, read in November 2026. If you run a $2M+ business with a team, their system may genuinely be the right fit for you — this article is for the rest of us.


Read more from Brian Lathe on Substack


This blog is one room in a bigger house. My main writing lives on Substack - longer pieces, new posts first, always free to read: Brian Lathe on Substack.

 
 
 

Recent Posts

See All
Do You Need an Integrator If You're a Team of One?

Do You Need an Integrator If You're a Team of One?If you've read anything about EOS — Gino Wickman's Entrepreneurial Operating System, from Traction — you've met the famous pair. The Visionary is the

 
 
 

Comments


Talk to Brian

on WhatsApp

Appointment booking opens soon.

Questions about this article — or about SuccessBrian OS? Text me here.

Texting is best — please don't call. Calls are by confirmed appointment only.

Talk to Brian

Questions, or want a system like this working for your business? Message me directly.

What is SuccessBrian OS?

One system that runs a solo business while its owner lives his life: a checked second brain, a crew of AI agents, and one calendar that never forgets. The whole system is free and open.

Get new posts by email

I build this in public and post the progress. Follow along on Substack.

bottom of page