Systems strategy & fractional ops for founder-led companies
Better businesses are built by design.
We install the operating systems, decision rights, and work rhythms that let a founder-led business run without living in your head — and then we run it with you until it does.
For founders past $500K in revenue who are tired of being the bottleneck.
// what changes when the business stops running through you
FIG. 01 — What changes when decisions, data, and delivery run through one system instead of through you.
N.01 The diagnosis
You are the org chart.
Draw your company's real org chart — not the one in the deck, the one that's actually true. Every arrow ends at you. Sales questions, hiring calls, the one vendor nobody else knows how to talk to, the pricing exception only you remember you made. None of it is written down, because you don't need it written down. You remember.
That's not a systems problem. It's a memory problem wearing a systems costume. And it scales exactly as well as your memory does — which is to say, it stops scaling somewhere around your tenth employee, your third city, or the first week of vacation you actually take.
Founder-led companies under $2M rarely stall from a bad idea. They stall because the business can't act on anything the founder hasn't personally shown it how to do. Every new hire is a rerun of you teaching yourself the job. Every new tool is duct tape over the last one. You didn't build a company — you built a very complicated relationship with your own inbox. We build the thing you meant to build instead.
Runtime cost
The founder tax
Every decision that has to pass through you is a small tax on the business — paid in hours, in hiring mistakes, in growth you can see but can't reach because you're the only one who can approve it.
- Hires who can't move past "ask the founder"
- Growth that stalls at your personal capacity
- Decisions re-litigated because no one owns them
- A vacation that isn't actually a vacation
N.02 The method
Four moves, in order. No shortcuts.
Systems work fails when it skips a step — usually the boring one. We've built this in the same sequence for every engagement, because the order is the point: you can't install what you haven't designed, and you can't design what you haven't honestly diagnosed.
Diagnose Systems Audit
We spend a full day together inside your business — not your org chart, your actual business. Your calendar. Your Slack. Your inbox. The decisions people make and the ones they bring back to you. We're mapping the company that exists in realty, not the one on paper. You get a clear picture of where work gets stuck, where the business depends on you, and what it's costing you in hours, hires, and headroom.
Design Operating Blueprint
We design the version of your business that doesn't need you in every room: the workflows, the decision rights, the meeting rhythms, the dashboards that tell the truth before you have to ask for it. Every system we design has a named owner who isn't you — if we can't name that person, we haven't finished designing it.
Install Fractional Operations
Blueprints don't run companies; people do. This is where we step in as embedded operators — often as a fractional Head of Ops or COO — and run the new systems alongside your team until they're load-bearing. We're in your standups and your inbox, not just in a strategy document you'll open twice.
Hand off Documentation & Training
The engagement ends when your team can run the system without us — and without you. We document what matters, train the people who own it, and make sure the knowledge stays with the business. Then we leave.
N.03 Ways to work together
Start with a day. Go further if it's worth it.
You don't need to commit to months of work before understanding the problem. Most engagements start with one day inside the business. Sometimes, that's enough to see what needs to change.
Diagnostic Day
A day to properly understand your business.
You know the business is ready for a change but can't quite see what it should be — you could restructure, hire, automate, delegate, change your pricing. Some of those are exactly right. Others are distractions. Before the day, you complete a contextual questionnaire; on the day, we work through the business together — how things actually happen, the relationships between the parts, the patterns underneath. You have direct access to me throughout, by Zoom and async message. Afterward, you get a written report: the most important findings, what deserves attention, and a clear set of priorities for what happens next.
- Context questionnaire and pre-work review
- A full day working through the business together
- A detailed written diagnostic within 48 hours
- A clear, prioritized view of what to do next
Fractional Ops
Embedded operational support for the work ahead.
Sometimes the Diagnostic Day reveals a set of changes that would benefit from someone working alongside you to actually implement them. Fractional Ops is that: experienced operational support without hiring an entire senior operations function internally. We begin with the Diagnostic Day, agree where support creates the most value, and work together for an initial three months. The scope is bespoke — it might mean designing or improving operating systems, restructuring workflows, implementing automation, clarifying responsibilities, improving information flows, establishing team rhythms, or building better decision-making.
- Operating systems and workflow redesign
- Clearer ownership and decision-making
- Better information flow and team rhythms
- Automation where it genuinely reduces friction
A good diagnosis should make you more capable of making your own decisions. Plenty of founders take the report, work through it themselves, and never book Fractional Ops — that's a successful outcome too.
N.04 Who this is for
Built for a specific kind of founder.
We turn down more engagements than we take — not out of exclusivity, but because this work only holds up when the fit is real on both sides.
This is for you if
- You're past $500K in revenue and the business still can't run a normal week without you in it.
- You've hired people, but you're still the one who trains them, unblocks them, and remembers the exceptions.
- You know roughly what's broken. You just haven't had the uninterrupted hours to fix it properly.
- You'd rather pay once for a system than pay forever with your own attention.
- You want an operator inside the business, not a consultant who disappears after the slide deck.
This isn't for you if
- You're pre-revenue or still finding product-market fit — you need a cofounder, not an ops team.
- You're looking for software, not judgment. We're not here to sell you a project management tool.
- You want someone to run the business so you can check out entirely. We build systems that need you less — not businesses that need you never.
- You need this finished in a week. Real systems take exactly as long as real systems take.
N.05 What we believe
A short, opinionated list.
We'd rather you know how we think before you hire us than find out halfway through the engagement.
Systems over software
A tool can't fix a decision nobody owns. We fix the decision first — the tool is usually the easy part, and often, you already own it.
Clarity is kindness
The kindest thing you can do for your team is tell them exactly what's expected, who decides what, and what happens when something breaks. Ambiguity isn't flexibility — it's just work you haven't finished.
The org chart is a hypothesis
Most org charts describe an ambition, not a reality. We design around how decisions actually get made, then we make the chart tell the truth about it.
If it needs you to remember it, it isn't a system
A real system survives you being on a plane, in a hospital, or simply thinking about something else for a week at a time.
Good systems have an exit built in
We measure our work by how quickly we become unnecessary to it — not by how long the retainer manages to last.
Boring is a feature
The best operating system is one nobody notices, because nothing is on fire. We're not chasing exciting. We're chasing quiet.
N.06 The work, in public
Notes, models, and practical tools for understanding the systems beneath a business.
The way a business operates deserves to be thought about as carefully as its product, brand, or growth strategy. This is some of that thinking, out in the open — observations, models, diagrams, and questions for founder-led businesses.
Featured note
The business behind the business
A business has an offer, customers, revenue, and a team. But underneath that visible business is another layer: how work moves, how decisions are made, how information is shared, and how responsibility is distributed.
As a business grows, this layer becomes the one that actually decides what happens next.
Explore the idea →A model
Where does the business live?
A visual way of thinking about the difference between a business that exists primarily in the founder's head and one that has developed organizational capability.
View the model →A question
What actually happens when you're not there?
A short exercise for examining how dependent different parts of a business are on founder involvement — and what that tells you.
Explore the question →A tool
The Business Map
A simple tool for stepping back and looking at the moving parts of your business as one connected system, rather than a list of departments.
Use the tool →A note
Busy vs. building capacity
A short observation about why adding more activity does not necessarily make a business more capable.
Read the note →N.07 Why this exists
Founders don't need another consultant. They need someone who's done the job.
The Systems Brain started from a familiar complaint: founders kept hiring strategy consultants who left them with a beautiful deck and no idea how to actually run the thing. Or they hired operators who could execute but couldn't step back far enough to see what was actually broken in the first place.
We built this to do both, in the right order. Every engagement starts with real operating experience — inside sales, delivery, and finance, not circling around them from a slide — and ends with our fingerprints removed from the business, not baked into it forever. We're not trying to become your permanent Tuesday meeting.
We work with a small number of founder-led companies at a time, on purpose. Systems work isn't a volume business. It's close, specific, and a little bit personal — you're not handing us a project, you're handing us the parts of your business you've been quietly holding together by hand for longer than you'd like to admit. We take that seriously, and we treat the handoff back to you as the actual finish line, not the exploratory call.
About Michèle du Toit
I'm Michèle, the founder of The Systems Brain. I work across strategy, systems, and operations, with a particular interest in the relationships between things — how demand affects delivery, how delivery affects capacity, how capacity affects people, how people affect structure, and how structure ends up right back at the founder's desk.
I'm less interested in whether a business has a particular process than in understanding why that process exists, what it connects to, and whether it's actually helping the business do what it needs to do. I like complexity when it can be made intelligible. My role is to look at your business with enough distance to see the whole, and enough proximity to understand the detail — then work out what should happen next.
The Systems Brain is part of a wider body of work exploring systems, cognition, and the relationship between better models and better action.
N.08 Questions
Before you book a call.
How is this different from hiring a COO?
A full-time COO costs more than most $500K–$2M businesses can justify, and most don't need one forever — just for the specific season of building the operating system. Fractional ops gives you the same seniority and hands-on leadership, scoped to exactly the work that's needed, with a plan to hand off rather than a permanent seat at the table.
What if I don't know exactly what's broken?
Almost nobody does going in — that's normal, and it's exactly what the Systems Audit is for. You already know the symptoms: the hours, the bottlenecks, the small fires that keep reappearing. We're trained to find the actual causes sitting underneath them.
Do you replace my existing tools?
Rarely. Most businesses this size already own more tools than they use well. We usually design around what you have and fix how it's actually used before we ever suggest buying something new — new software on top of a broken process just makes an expensive version of the same mess.
How much of my own time will this take?
More at the start, less over time — the opposite of most consulting engagements you've probably sat through. Expect real involvement during the audit and design phases, then a deliberate handoff as we install the systems and gradually remove ourselves from the day-to-day.
What size businesses do you work with?
Founder-led companies roughly between $500K and $2M in revenue, usually with 3 to 25 people. Below that, you likely need a cofounder more than an ops team. Above that, the math on a full-time hire usually starts to shift in its favor.
What happens after the engagement ends?
You keep everything: the documentation, the systems, the training. Most clients take a short async support window after we leave, and a few bring us back for one specific new system months later. Nobody stays on a retainer they don't actually need — that's the whole point of how we built this.
N.09 Let's talk
Bring us the mess. We're not precious about it.
An exploratory call is thirty minutes, no deck, no pitch. We'll ask about your business, tell you honestly whether this is a fit, and if it isn't, point you somewhere better.
Book an exploratory call →Usually booking two to three weeks out · hello@thesystemsbrain.com