Most people who ask me this question are asking a different question underneath it. They are asking: am I about to pay someone six figures a year to sit in meetings and tell me things I already know?
Fair. So here is the direct answer, with real engagements attached to it.
A fractional C.O.O. is a senior operations leader you hire part-time. Not a coach, not a consultant who hands you a deck, not a virtual assistant. Someone who takes the operations seat in your organization, runs it alongside you, and builds the systems your team keeps after the engagement ends.
The work usually falls into five buckets: daily systems and workflow, staffing structure and accountability, financial rhythm, board and funder reporting, and compliance. That list is accurate and it is also useless, because every ops page on the internet says roughly the same thing. What actually matters is how the work gets found and in what order it gets fixed. That part is worth explaining.
The first 30 days: I do not walk in with a plan
I do not arrive with a 90-day roadmap. I cannot, because I do not know your organization yet, and anyone who hands you one in week one built it from a template.
What I do instead is spend the first month learning the organization from the inside. I meet with the team. I sit in on the meetings you already have, including the ones you think are boring. I ask a lot of questions, and I ask a specific one that most consultants skip: what do you think my role here should be? Then I give feedback on the answer, because the gap between what a leader thinks they are hiring for and what the organization actually needs is often the first real finding of the engagement.
Thirty days of listening surfaces the pain points people will not put in an email. Once those are on the table, you fix them in the order of what is costing the most, not in the order that is most comfortable.
What that looked like at a therapeutic services nonprofit
When I came into a therapeutic services nonprofit here in Southern California, I ran that same first 30 days. Meetings, questions, listening for where the friction was.
Two things came out of it.
The first was funding. Inside those conversations it became clear the organization was eligible for state funding through CalAIM that it was not fully pursuing. That is not a discovery you make from an org chart. You make it by sitting with the people delivering the service and hearing what they are already doing that somebody else will pay for.
The second was program delivery. We changed how our team ran the program under an existing contract. Same contract, same funder, different operating approach. Our team ended up with 50% more success than the rest of the organization working that same contract.
A month of listening, then two changes: one that opened a funding stream, one that changed how the work got done.
That is the shape of the job. Not a reorganization. Not a new software stack.
The work nobody puts on a services page
Here is a less flattering example, and it is the one I would want a prospective client to read.
We took on an organization where a former employee had never reported work to the federal government. Not a small oversight. Hundreds of thousands of dollars in funded work that was performed and never properly reported. By the time anyone noticed, the employee was gone and the window had effectively closed.
What we did was not glamorous. We pulled every document. We reconstructed what was actually done, by whom, and when. We built the record that should have existed, and we filed a formal appeal with the federal government. That appeal is pending as of this writing, and I am not going to tell you we won it, because we do not know yet.
I include this because it is the honest version of the job. A meaningful part of operations work is going back through somebody else's mess with a flashlight. If your last operations person left and you are not completely sure what they were sitting on, that is not an unusual situation. It is one of the most common reasons a leader calls me.
Operations is only half of it
This is where my practice differs from most fractional C.O.O.s, and it is worth being blunt about.
Fixing operations without fixing funding just means you have a well-run organization that still runs out of money. So I look at both. When I am inside your operations, I am also looking at what you are already doing that is fundable, what contracts you qualify for and are not pursuing, and what your programs would need to look like to be sustainable rather than grant-to-grant. That is why grant writing sits alongside the operations work rather than in a separate silo.
The CalAIM opening at that nonprofit came out of an operations review, not a grant search. That is usually how it works. The funding is often hiding inside the operational detail, and the person reading your workflow is better positioned to spot it than the person reading your case statement.
What it costs, honestly
A full-time chief operating officer is a six-figure salary. Add benefits, payroll taxes, and the recruiting cycle to find one, and the real number is higher than the number in the offer letter.
A fractional engagement runs about half that, with the same level of experience in the seat. You are buying the judgment without buying the forty hours.
I price based on the fiscal budget of the organization, because a $500,000 nonprofit and a $5 million nonprofit are not buying the same thing and should not pay the same. Engagements come in three shapes: an annual fractional program, a quarterly intensive on your highest-impact gaps, and a one-time deep consultation that ends with five concrete action items you execute yourself.
When you should not hire a fractional C.O.O.
I turn down work, and these are the reasons.
- Your funding is not there yet. If bringing me on means you cannot make payroll, that is not an operations problem I can fix with better systems. Fix the money first, or hire me for a one-time consultation instead of a retainer.
- You are less than a year old. New organizations usually do not have enough history for me to work with. No track record, no data, no established relationships in the community. There is nothing to diagnose yet.
- You have no staff. This is the one I learned the hard way. I was brought on by a brand new nonprofit with no employees, and the expectation was that I would personally do all the work and fix all the problems. That is not a fractional C.O.O. engagement, that is asking one person to be the entire organization. It failed, and it was going to fail from the start, because there was no team to build systems around and no operating history to learn from.
A fractional C.O.O. multiplies a team. If there is no team, there is nothing to multiply. If you are earlier than that, capacity coaching is usually the better fit.
The mistake leaders make when they hire one
Following from that: the most common misunderstanding is expecting a fractional C.O.O. to be a doer rather than an operator.
If what you want is someone to take a list of tasks off your desk, you want a director, a coordinator, or a contractor, and you will be happier and spend less. What a fractional C.O.O. is for is the layer above that: deciding which work matters, building the structure that gets it done consistently, and making sure it keeps happening when the fractional engagement ends.
A fractional C.O.O. who makes themselves permanent has failed.
The measure of the engagement is whether your team still runs the systems a year after I stop showing up.
Are you at that point?
The pattern is usually the same. Growth outran structure. New grants, new staff, new board expectations, and the executive director is doing operations at night. Too big to wing it, too small to afford a full-time C.O.O.
If that describes you, a free 30-minute call is enough for me to tell you honestly whether you need a fractional C.O.O., a coach, or just a better calendar. If the fit is not there, I will say so on the call.