Welcome to the first issue of The Fractional Operator. The short version of why this exists: fractional and outsourced work roughly doubled in two years, and most of us run our practices in our own silos with nowhere non-threatening to compare notes. This newsletter — and the podcast it ships alongside — is the attempt to fix that.
Each Thursday: a tight set of links worth your time, and the week's episode. No filler. If a link isn't actually good, it won't be here. This week leans into the doing — how the work actually runs across the COO, CMO, and finance seats. Here's what's worth your attention.
Episode #1 - Welcome to the Show
The first episode is the mission statement. I lay out who this is for — the COOs, CTOs, CFOs, CMOs, agency owners, and consultants running fractional practices — and the one promise behind it: if you want to grow and scale, we'll help with that; if you're running a lifestyle practice and have no interest in scaling, we'll help you do more with less and work less. Two audiences, one show.
The format is a knowledge-share, not a monologue — every episode brings on another operator to talk software, processes, problems, and the lessons they're working through. The number that frames the whole thing: the fractional workforce grew from 60,000 in 2022 to 120,000 in 2024.
The Fractional Workforce
What the first 90 days of a COO engagement should actually look like
The most useful operating piece I read this week, and refreshingly blunt for something published by a staffing firm — it even tells founders when not to hire fractional. The 90-day shape worth stealing: days 1–30 listen and map (don't decide anything), days 31–60 write a five-to-seven-page diagnosis including what not to do, days 61–90 drive one thing to done as proof that operational projects can finish.
The line that'll land with any operator who's blown a first engagement: arriving on day three with a transformation roadmap is a flag — it means you haven't listened yet. Also good on the COO-vs-consultant-vs-integrator distinction.
Read it here → https://www.kore1.com/fractional-coo-services-2026/
Build authority, not availability
The sharpest take this week on the lifestyle-vs-scale question every fractional operator faces. The core argument: most people leave corporate, call themselves "fractional," then spend 18 months competing with cheaper freelancers because they're selling availability instead of authority.
The fixes are concrete — specialize, price on outcomes not hours, and hold the line on scope (the "can you just take a quick look?" creep that turns one client into a second boss). The framing of the income-vs-freedom tradeoff is the part worth sitting with: two clients at $10K beats four at $5K for the same revenue and half the context-switching — but only if you choose it deliberately.
Read it here → https://kenyarmosh.com/blog/how-to-become-a-fractional-cmo/
What operators are actually using AI for — and where it stops
The most honest AI piece I read this week, and it applies across every seat. The framing that lands: treat AI as a junior analyst or a first-draft machine, not a strategist — the operators who expect it to think for them get the least out of it.
It's candid about the limits (first drafts are useful but imperfect, usually three-to-five passes to get there) and direct about the part everyone glosses over — public tools may train on your inputs, so client-sensitive work needs enterprise-grade tools or no identifiable data at all. Use it as leverage on the hours you already bill, not a replacement for judgment.
The workload math nobody puts in the pitch deck
A guide worth reading for one honest section most fractional content skips: the actual time arithmetic. Fractional operators average 5–20 hours per month per client (10–15 is the norm), which realistically supports three to four clients, five if you stretch.
The part that earns the link — that math doesn't count running the business itself: admin, marketing, managing your outsourced team, and BD. If you've ever wondered why four clients feels like a full plate, this is why.
That's issue #1.
If something here saved you a click or sharpened a thought, that's the whole idea. Reply and tell me what you'd want more (or less) of — this gets better with your input.
See you Friday,
Mike