Direct answer
An EOS implementer team quotes about $20,000–$45,000 a year, usually for two years (Strety's 2026 guide), and a UK fractional COO costs about £6,000–£14,000 a month (Fractionus). Both change how decisions and people are organised. Automation fixes something else: the loops that still wait for you. They solve different problems, and some owners need both. Our Audit is £3,500 and Run £2,000 a month, excl. VAT.
The question to ask first is not which one is cheapest. It is what keeps pulling you back into the day-to-day. If the answer is that nobody else is allowed to decide, or the team doesn't know what it is accountable for, that's a people and process problem. If the answer is that enquiries, invoices, chasing, reports or records physically wait for you to do them, that's a loop problem. Most owner-managed firms have some of each.
The options compared
All third-party prices below come from sellers' own pages, checked on 24 October 2026. They are what those sellers publish, not market surveys, and EOS pricing is in US dollars because no UK price list exists.
Swipe or scroll to compare the columns.
| Option | What it costs | How long before it changes your week | What it fixes | What it can't fix |
|---|---|---|---|---|
| EOS with a professional implementer | About $20,000–$45,000 a year for two years, quoted by one implementer team; implementers are independent and set their own fees. Full implementation runs 18–24 months, per EOS Worldwide. The first 90-minute meeting is free. (Strety, which sells EOS software, 15 July 2026) | Months. Sessions are full days, typically five to seven a year. | Who is accountable for what, a meeting rhythm, quarterly priorities, a leadership team that decides together | Work that physically waits for you: the invoice you type, the enquiry you answer, the report only you can pull |
| A fractional COO | £6,000–£14,000 a month, or £72,000–£168,000 a year (Fractionus, a fractional-executive platform, 2026). Senior fractional executives charge about £900–£2,000 a day on the same page. | Weeks, once you've found the right person; you skip the recruitment and notice period of a full-time hire. | Operational leadership without a full-time hire: someone who runs the team, sets priorities and takes decisions off you | Repetitive work stays repetitive. A COO can reassign it, but someone still does it by hand. |
| A full-time COO or operations hire | A full-time COO's total employer cost is £163,000–£277,000 a year on Fractionus's figures. An operations manager costs less, but the shape is the same: salary, employer costs and a hiring process. | Months: recruitment, notice period, then learning the business | A permanent person who owns operations and can deputise for you | Same as a fractional COO, plus the risk of a hire who leaves and takes the knowledge with them |
| Automation, one loop at a time (AutomateFlow) | Audit £3,500, Pilot £15,000 for one workflow in production, Build £35,000 for an operational app, Run £2,000 a month, all excl. VAT | Weeks. A Pilot typically takes four to six weeks to put one workflow into production. | The loops that wait for you: enquiries to bookings, quotes to cash, the numbers only you can pull, the records only you can find | Who decides, who is accountable, and whether customers trust the company rather than you |
Read the costs side by side with care. EOS and a fractional COO are recurring people costs. Automation is mostly a build cost, then a smaller running cost. A year with one loop taken out, on our prices, is the Audit, the Pilot and Run for the rest of the year. That is a different shape of spend, not a like-for-like saving, and it buys a different thing.
When people and process come first
Some owners can't step back because nobody else is allowed to decide. The team brings every question to you, not because the information is missing, but because no one has been told the decision is theirs. Software doesn't fix that. A written structure of who owns what, a regular meeting where priorities get set, and a deputy with real authority do.
Signs that people and process come first:
- The same decision lands on your desk every week, and the person asking already has what they need to decide it.
- Your managers disagree about priorities, and you're the tiebreaker.
- You've hired people to take work off you, and it came back.
- Nobody can say what the business is trying to achieve this quarter.
This is the ground EOS and similar frameworks cover, and where a fractional COO earns their fee. Strety's guide suggests a full EOS engagement fits companies of 20 to 250 people with recurring accountability problems, and that smaller firms often run it themselves with software. A fractional COO suits a firm that needs operational leadership now and can't justify a full-time salary.
If this describes you, automating first can make things worse. A system that routes enquiries to "whoever is free" doesn't help when nobody is sure they're allowed to reply.
When the loops come first
Other owners have a team that could decide, but the work itself runs through them. They type the accepted quote into the accounts software. They chase the overdue invoices because no one else knows who owes what. They're the only one who can pull last week's numbers from three systems. They know where the records are.
Signs that the loops come first:
- You could hand the decision over, but the task itself needs your login, your spreadsheet or your memory.
- The same information is typed into two or three systems.
- Questions wait because the answer is spread across tools only you check.
- When you're away, things don't go wrong; they just stop.
A COO can't fix this without doing the typing themselves. It's a systems problem: integrations between the tools you already pay for, rules for what must be exact, and, where judgement is needed, an AI agent with limits and a person signing off. In the PaxBespoke build, for example, bookings, proposals, e-signatures and deposit invoices are joined across seven tools so details no longer have to be copied between them, while measurements, prices and exceptions stay with the team.
Our four-week owner-absence test separates the two. Eight of its ten questions are about loops; two are about people. A low score on the loops with a decent People score usually means systems first.
Doing both, in which order
Plenty of firms need both, and the order matters.
If no one is allowed to decide, start there. Put a deputy in place, agree who owns what, and give it a few months. Then automate the loops, because you now know who should receive the exceptions a system can't handle. An enquiry agent needs someone to hand the hard cases to. A chasing rule needs someone who can agree a payment plan.
If the team is ready to decide but the work still runs through you, start with the busiest loop. Taking out the invoicing or chasing loop frees hours quickly, and those hours can go into the people work: hiring, training a deputy, or running the meeting rhythm properly. The before-and-after is easy to count, too: invoices you typed this month, reminders you sent yourself.
If you're working with an EOS implementer or a fractional COO already, automation fits inside what they set up. They decide who owns a process; we build the systems that run the routine part of it, inside the tools you already use, with the decisions left with the people they've named. The business owns what we build: code, configurations, documentation and accounts, as agreed in writing.
Whichever order you pick, keep the guardrail in view. Rules handle what must be exact, AI handles what needs judgement, and a person signs off where mistakes are expensive. Stepping back works when someone else can see what's happening and is allowed to act on it.
