How many month-end closes can one fractional CFO realistically carry?

With a standard template and one accountant doing preparation, four to six companies of similar size is a normal load; the CFO is reviewing and handling exceptions, not preparing. Without a template it drops to two or three, because every client becomes a separate memory problem. The binding constraint is review capacity in days three through eight, not total hours in the month.

Should every client use the same close template?

Start every client from the same template and let each one diverge only where the business actually differs: inventory, deferred revenue, multi-entity consolidation, foreign currency. Divergence you chose is fine. Divergence that happened because a client once asked for a differently named step is what makes the fifth close expensive.

How do you stagger due days without annoying clients?

Tie the due day to something the client already cares about, usually their board or investor reporting date, and work backward. Clients rarely need the package on business day five; they need it before the meeting. Once you ask, most will move a few days, and you get a schedule where two closes peak on different days instead of five peaking together.

What is the biggest risk in running closes across several clients?

Carrying an assumption from one client into another. The second biggest is that the close history lives with you rather than with the client, so when the engagement ends the company cannot show how anything was done. Both are solved the same way, by keeping the record in the client’s own workspace rather than in your working papers.

How do you hand a client back cleanly?

The client should end with their own workspace containing every closed period, the evidence attached to each step, and the sign-offs, so an incoming controller can read the last three closes and continue. If your handover is a folder of workbooks and a call, you have given them data and kept the knowledge.

Do clients need separate subscriptions?

Usually yes, because the workspace belongs to the company rather than to you, which is what makes the handover clean and keeps each company’s data separate. Where a single owner holds several entities, one subscription covering multiple entities is the cheaper shape.

Guide

Closing five companies at once: how a fractional CFO runs parallel month-end closes

A fractional CFO closing five companies is not doing one close five times. The constraint is not the accounting, it is that all five want the same ten business days and each one keeps its checklist somewhere different. What makes it work is a single close template applied to every client, due days staggered so the crunch does not land on the same three days, one person named as preparer and one as reviewer on every step at every client, and a status view that answers "where is everything" without opening five workbooks. The clients keep their own books, their own entities, and their own quirks; what gets standardized is the sequence, the naming, and the evidence.

By Vanward. Published 2026-09-15. Updated 2026-09-15.

The first two clients are easy. The third is fine. Somewhere around the fourth, the month stops having enough middle in it, and the failure is always the same: everything is due at once, and the only place the full picture exists is in your head.

Stagger the calendar before you optimize anything else

This is the change with the largest effect and the lowest cost, and most people skip it because they assume the dates are fixed. They are usually inherited rather than chosen.

Client	What actually drives the date	Close due	Package due
Board meets the third Tuesday	The board pack, not the close	Business day 8	Business day 10
Monthly investor update on the 15th	The update email	Business day 6	Business day 8
Lender covenant certificate, 30 days after quarter end	The certificate, quarterly only	Business day 5 in quarter-end months	Business day 12
No external reporting yet	Nothing; the date is habit	Business day 10	On request
Parent consolidates	The parent’s deadline	Business day 4, non-negotiable	Business day 5

Two of those five genuinely need an early close. The other three moved because someone asked. That is the difference between a peak of five and a peak of two.

Standardize the sequence, not the business

The same step names, in the same order, at every client. Cash, receivables, payables, revenue, payroll, accruals and prepaids, intercompany if it applies, then reporting. When the names match, you can look at five boards and read them the same way, and an accountant can move between clients without relearning anything.

What is allowed to differ

Inventory and cost of goods. Deferred revenue mechanics. Multi-entity elimination. Foreign currency. Anything driven by the client's actual operations gets its own step, and that is fine, because you added it deliberately.

What should never differ

Who prepares and who reviews. What counts as done. Where the evidence lives. The threshold that triggers a variance explanation. These are your standards, not the client's preference, and they are what makes your review time predictable.

Review is the bottleneck, so protect it

Preparation scales with hiring. Review does not, because it is you. Two habits keep it from becoming the constraint. First, review by exception: look at every flagged variance, every reconciliation with an aged item, and every step that came back late, and spot-check the rest. Second, refuse to review a step that is not actually finished, because reviewing a half-done step means reviewing it twice.

The handover problem

Fractional engagements end, usually because the client grew into a full-time controller, which is a good outcome. What decides whether you get referred is what the client is left holding. If the closes lived in your workbooks and your email, they get an export and a call. If the closes lived in their workspace, with the evidence attached and the sign-offs recorded, the incoming controller reads the last three months and picks it up, and you look like the reason the company is in good shape.

This is also the honest answer to a question clients ask more often than they used to: what happens to our records if we stop working together. The right answer is that nothing happens to them, because they were never yours.

What this looks like in Vanward

Each client is its own company workspace with its own template, and you switch between them from one account. A close-team seat lets a client's accounting staff work the close without seeing anything on the fundraising or diligence side. Every step carries a preparer, a reviewer, a due day, and its evidence; balances are filled from the client's trial balance rather than typed. The close package and the audit trail export belong to the client and stay with them, which makes the handover a link rather than a project.

Questions founders ask

How many month-end closes can one fractional CFO realistically carry?: With a standard template and one accountant doing preparation, four to six companies of similar size is a normal load; the CFO is reviewing and handling exceptions, not preparing. Without a template it drops to two or three, because every client becomes a separate memory problem. The binding constraint is review capacity in days three through eight, not total hours in the month.
Should every client use the same close template?: Start every client from the same template and let each one diverge only where the business actually differs: inventory, deferred revenue, multi-entity consolidation, foreign currency. Divergence you chose is fine. Divergence that happened because a client once asked for a differently named step is what makes the fifth close expensive.
How do you stagger due days without annoying clients?: Tie the due day to something the client already cares about, usually their board or investor reporting date, and work backward. Clients rarely need the package on business day five; they need it before the meeting. Once you ask, most will move a few days, and you get a schedule where two closes peak on different days instead of five peaking together.
What is the biggest risk in running closes across several clients?: Carrying an assumption from one client into another. The second biggest is that the close history lives with you rather than with the client, so when the engagement ends the company cannot show how anything was done. Both are solved the same way, by keeping the record in the client’s own workspace rather than in your working papers.
How do you hand a client back cleanly?: The client should end with their own workspace containing every closed period, the evidence attached to each step, and the sign-offs, so an incoming controller can read the last three closes and continue. If your handover is a folder of workbooks and a call, you have given them data and kept the knowledge.
Do clients need separate subscriptions?: Usually yes, because the workspace belongs to the company rather than to you, which is what makes the handover clean and keeps each company’s data separate. Where a single owner holds several entities, one subscription covering multiple entities is the cheaper shape.

How ready is your close?

Eight yes-or-no questions, two minutes, no account. You get a score out of 100 and the three gaps most likely to come up in an audit or a diligence request.

Take the free close check