Nonprofit operations consultant for mid-stage executive directors

A nonprofit operations consultant is not a fractional COO, not a software tool, and not a one-off audit. The consultant is a part-time operator who sits inside the ED’s week and clears the steady stream of operational work the ED has been doing themselves — vendor reviews, finance-cycle scrubbing, vendor contract review, grant reporting calendar maintenance, board-finance committee prep, staff SOP library authorship, intake and process redesign, and the weekly check-in that ties it all together.

The first concrete block is the vendor and finance cycle. The consultant drives the month-end close — pulling receipts from the team, scrubbing the books against the chart of accounts, reconciling the credit card, prepping the finance report the board reads. They also own the steady drum of vendor decisions below the pre-set threshold: the new CRM renewal, the audit firm search, the cyber insurance shopping, the office lease exit. Anything above the threshold comes to the ED with the consultant’s analysis and a recommendation; the ED signs.

The second block is the operational documentation layer. The consultant writes the SOPs the team has been talking about for two years — the donor acknowledgment SOP, the intake process SOP, the hiring loop SOP, the incident response SOP, the grant reporting calendar SOP. They also maintain the staff handbook addenda, the IT credential inventory, the document-retention schedule, and the board-facing onboarding packet. The consultant does the writing; the ED signs off; the staff uses them.

The third block is the weekly check-in that ties it together. Forty-five minutes with the ED every week, recurring, on the same day. The consultant brings the open operational items, the approaching deadlines, the decisions queued for the ED’s signature, and the staff or board friction the consultant has been hearing. The ED brings the strategic questions the consultant can answer with a number or a process — the rest go to the chair, the coach, or the next board meeting. This is the meeting that prevents the consultant from drifting into a fractional COO and from drifting into a vendor.

The line is the same as it is for any operator role: delegate the work where the artifact matters more than the signature. Hold onto the work where the ED’s name carries the trust.

Delegate to the consultant: process mapping end-to-end, vendor selections under the pre-set threshold, SOP authoring, finance cycle scrubbing, board-finance packet assembly, the operational dashboard the ED opens every Monday, intake and process redesign, grant reporting calendar maintenance, the steady drum of "we should have this documented." Anything that has been on the ED’s task list for a quarter and is not getting done because the ED is the wrong shape for it.

Keep with the ED: defining org posture on a funder pivot — should we apply for this thing, what is our position on this coalition, what does the next three years of program look like. Signing the largest grant. Terminating a vendor above the pre-set threshold. The board chair relationship. The donor-relationship stewardship in person. The external narrative: Op-Ed, keynote, public statement. Anything where the ED’s signature carries the trust, the relationship, or the strategic weight the consultant cannot speak to.

Keep with the board: approval of the annual budget, the audit, the executive director’s compensation, the strategic plan adoption, the reserve policy. The consultant assembles the packets for each of these; the board owns the decision. The consultant is the operator who makes sure the board has the materials to decide well; the consultant is not a substitute for the board doing the deciding.

A fractional operations consultant works when three conditions hold. One: the operational pain is process-shaped, not strategy-shaped — the team is doing real work, the work is producing outcomes, what is missing is the wiring that lets the work survive the next quarter. Two: the team is writing things down enough to map — finance into the books, program into the CRM, hiring notes into the system, donor conversations into the database. The consultant cannot map a process the team has not described. Three: the ED is willing to let one person sit across functions for a quarter. A consultant who is hired to "fix operations" without authority to read the finance, sit in the program meeting, and ask the development lead what their week looks like will produce a binder no one opens.

It does not work when the org is still pre-product-market fit on its mission — the program is still being shaped, the ED is still the primary program voice, and what looks like an operations problem is actually a strategy problem. A consultant in this shape produces SOPs for a program that has not found its shape, and the SOPs get rewritten three months later. It also does not work when the ED is the bottleneck on decisions not on wiring — when the ED is the one holding every decision and asking the consultant to push them through, the consultant becomes a chief of staff and the consultant was the wrong hire. And it does not work when what the board actually wants is a strategy partner — a board that hires a "operations consultant" hoping to get a fractional ED-side thinker is going to be disappointed at the first quarterly review.

The simplest test: after one quarter the ED should be answering fewer operational questions, the finance close should close faster against fewer ED interventions, the staff should have an SOP library they actually use, and the board-finance packet should arrive a week before the meeting instead of the night before. If those four move, the consultant is working. If they do not, the diagnosis was wrong — usually the ED was the strategy bottleneck, not the operations one.

ChiefDesk pairs an AI operator — drafting, integration, follow-through — with an operator-side scope. The consultant is the human judgment layer ChiefDesk sits beside or underneath. In a solo consultant engagement the consultant does the whole job by hand — vendor research, finance review, board packet assembly, SOP authorship — across however many hours per week the engagement covers. In a ChiefDesk engagement the consultant and the AI split the work by what benefits from sitting in the calendar and what benefits from being drafted and integrated at speed.

The consultant does what benefits from human judgment in the calendar: vendor reference calls, finance review with the bookkeeper, board-finance committee prep alongside the ED, staff SOP walk-through, grant kickoff meetings where the consultant reads the room. The AI — ChiefDesk — does the work that benefits from speed and consistency: drafting the next SOP from the consultant’s outline, integrating the receipt dump into the books format the consultant prefers, scrubbing the donor CRM against the consultant’s revenue forecast, producing the first draft of the next board-finance packet from the prior packet plus the current finance report. The consultant reviews the AI’s draft the same way the ED reviews the AI’s draft — eyes on, edits, signs.

The shape that fits: at a $1M–$5M budget where a full-time COO is over-budget and a single-vendor fractional engagement is under-feasible, this is the shape. The consultant typically works a half-day to a full day per week, the AI runs underneath the consultant on the drafting and integration layer, the ED reviews what the consultant sends up once a week in the standing check-in, and the board sees a finance packet that arrives a week before the meeting instead of the night before. The cost is roughly a third of a full-time COO and a quarter of a solo-vendor fractional engagement; the output is the same artifacts, with the consultant doing the human-judgment work and the AI doing the artifact work under the consultant’s direction.

The most common failure mode for this shape is sizing the consultant for the org chart the org would like to have — not the one it has today. A $1.5M org trying to run a four-day-a-week consultant engagement will end up with the consultant inventing work. The right sizing is the smallest engagement that clears the four tests above in the first quarter; expand it once those tests are stable.