Fractional COO or an embedded system. Which one your business actually needs.
Both solve founder dependency. They solve it differently, and one of them is the wrong answer for your situation right now. This page is written to help you tell which.
No pitch. The section on when to hire a fractional COO instead is real.
What a fractional COO is good at
A fractional COO is an experienced operator who runs part of your business for a few days a month. Done well, it is a strong hire. You get senior judgment without a senior full-time salary. You get someone who has seen the problem you are having in three other companies. They can walk into a difficult conversation with a team lead on Tuesday and handle it properly, which no document can do.
They are also fast. A capable operator can take a function off a founder's desk in weeks, because they are doing the work instead of designing how it should run.
If your honest situation is that operations need an adult in the room starting now, that is the right call and this page is not trying to talk you out of it.
What it costs you that is not the fee
The trade is dependency. You were the single point of failure. Now there are two of you, and one is on a contract.
That is a real improvement and it should not be dismissed. A business that can run four days a week without the founder is better than one that cannot run at all. But the shape of the risk has not changed, it has moved. When the engagement ends, or the operator takes a bigger client, the question of who makes the recurring decisions comes back open.
The fix is to write knowledge transfer into the engagement at the start, name the person on your team who receives it, and treat the documentation as a deliverable. Ask for it in the scope of work. An engagement that is priced on the operator's time will not include it by default, because it is extra work that makes them less necessary later.
What an embedded system is
The other approach is to build the structure that makes the recurring decisions repeatable, so they stop needing a senior person at all.
In practice that means the same four things the playbook covers for free. Find where the founder's week actually goes. Draw the line on who decides what. Design the roles against the work that needs an owner. Write down the processes that currently live in someone's head. Then put those in a place the team already works, so reaching the standard does not require asking you.
It is slower to feel. There is no week where a capable stranger takes the load off your desk. The relief arrives as fewer things coming back to you, which is less satisfying and more durable.
The comparison
| Fractional COO | Embedded system | |
|---|---|---|
| Cost | Monthly retainer | Fixed, from USD 499 |
| Duration | Open-ended | 30 to 90 days |
| Output | A person deciding | Structure that decides |
| Speed | Weeks | A quarter |
| Risk | Dependency moves | Team never adopts |
| Transfer | Only if negotiated | The deliverable |
| Best fit | Judgment you lack | Decisions only you make |
The one row that needs unpacking is cost. A fractional COO is priced on availability, so the cost continues for as long as you need the capacity. An embedded build is priced on scope and stops. Founder OS Setup starts from USD 499. Business Rewire is scoped on the call, because the number depends on which function you pick and how much of it already exists.
How to tell which one you need
Ask one question about the work that keeps reaching you. Do you know how to make these decisions, or do you not?
If you know how, and the problem is that only you can make them, the answer is structure. Hiring someone senior to make decisions you already understand is buying capacity to solve a design problem, and it works until they leave.
If you genuinely do not know how, because the function is outside your experience or the business has hit a scale you have not run before, then you need judgment you do not have yet. Hire the operator. Get the judgment. Ask for the transfer in writing.
Plenty of businesses need both, in that order. An operator to stabilise, then a structure so the stability outlasts the contract.
Where we sit
We build the second thing, for founder-led service businesses of roughly ten to thirty people. We do not place fractional COOs and we do not take over your operations. If the diagnosis says what you need is capacity instead of structure, we will say that on the call. We will not sell you a build that will not hold.
The diagnosis is free and does not need an account. So is the playbook, which contains the whole method whether or not you ever speak to us.
Two different jobs.
A fractional COO adds senior capacity to run operations. An embedded system removes the need for a senior person to be in the room for recurring decisions. Neither is better in the abstract.
Hire a fractional COO when
You need someone running it, starting now
There is a live operational problem that needs an experienced adult in the room this month. Your team needs a leader rather than a process. Someone has to own delivery or a P&L and be accountable for it. You are managing a crisis, a turnaround, or an integration where judgment matters more than structure.
Build the system when
The work is known, and it still routes through you
The recurring decisions are ones you already know how to make. The problem is that only you can make them. You want the capability to stay in the business after the engagement ends instead of leaving with the person you hired.
What an embedded system does not do.
If any of these is what you need, a fractional COO is the better spend and we will say so on the call.
It does not manage your team day to day
Nobody from ARCAS sits in your standups after the build.
It does not absorb a crisis
A system is built on how the work runs normally, and a business in the middle of an emergency does not have a normal to build on yet.
It does not carry accountability for your numbers
A fractional COO can own a target. We build the structure the person owning the target uses.
It needs your team's time while it is being built
If nobody on your side has hours to give this quarter, it will not stick, and a part-time operator who does the work themselves is the more honest fit.
What is different six months after it ends.
This is the part that separates the two, and it is worth deciding on deliberately.
After a fractional COO leaves
What stays depends on what was agreed at the start. If knowledge transfer was written into the engagement and someone on your team was named to receive it, a lot stays. If it was not, the judgment that made it work leaves with them, and the founder often picks the load back up within a quarter. This is worth negotiating for explicitly.
After an embedded build ends
The decisions, standards, and processes sit in something your team already uses, and they were written by the people who will run them. The failure mode is different. If the team never adopted it during the build, you own a well-documented thing nobody opens.
Find out which one your business needs.
The diagnosis is the cheaper way to answer this than a paid discovery process. It is free, it takes about five minutes, and it does not need an account.
Free, 5 minutes
Run the Operational Stress Test
Seven audits mapped onto five leaks. It names whether your problem is a capacity problem or a structure problem, which is exactly the question this page is about.
Free, 30 minutes
Talk it through with a human
We work on your business live on the call and you keep what we build, whether or not we work together afterwards.