AI for Fractional CFOs: What to Automate, What to Sign (2026 Guide)

On 8 October 2026, a16z published You Need a New CFO. The argument fits in one line: the CFO went from accountant to banker, and is now becoming a builder. The scarce skill, they write, is "designing the operating system the company runs on. This means the data, workflows, agents, skills and controls that turn context into intelligence and decisions."

The piece never mentions fractional CFOs. Read it with one in mind anyway, and it reads like a portrait:

• lean teams, down to 2% of headcount → a team of one
• "senior domain experts can get the most leverage out of AI" → senior by definition
• CFOs building their own tools → no IT department to ask
• "an auditable, trusted chain from each of finance's numbers to its source" → your name on the numbers of every client
• scenarios run live in the meeting → a different founder asking "what if?" every week
• "if you do something twice, write a workflow" → the same close, three or four times a month

There is one difference, and it is the subject of this guide. a16z describes a CFO with a team, an engineering department down the hall, and one company to run. You have none of that, and four companies. So what does an AI-native practice look like when it is one person, several ledgers, and a signature on each?

The Shape of the Job, in Numbers

Start with what is measured. All figures below are on our fractional CFO statistics page, with sources and scope.

Read the last two lines together. You are more likely to use AI than your clients are. In most engagements, you are the one who brings it in, which means you are also the one who answers for it.

Three Layers: Drafted, Computed, Signed

Most advice on "AI for finance" asks which tasks to hand to a model. For a fractional CFO, the better question is who is accountable for each number, because the answer is always you.

Split every deliverable into three layers.

1. Drafted by the model. Commentary, summaries, first-pass mappings, the list of anomalies worth a look, the email to the founder explaining a variance. Language work. Fast, cheap, and fine to be wrong in a first draft, because you read it.
2. Computed by a structure. Totals, balances, ratios, the forecast, the cash runway. These should come from formulas in a model with a known structure, not from a model's arithmetic in a chat. A language model asked twice can answer twice differently. A formula cannot.
3. Signed by you. The accepted close, the board pack, the forecast you present, the advice. Nothing here should contain a figure you cannot trace back to its source in two clicks.

a16z puts the same idea in one sentence: "finance sets the rules and owns sign-off. Having controls enables speed." The second half matters as much as the first. Controls are what let you go fast, because you stop re-checking every step by hand.

The fear behind this split is not abstract. Fractional CFOs describe it in almost the same words everywhere: AI that silently changed figures, dropped lines from an invoice base, hardcoded an assumption, or gave a different result when asked the same question twice. When a full-time CFO is wrong, one company is affected. When you are wrong, the client is affected and so is the referral network your practice runs on.

Your Month, Stage by Stage

Here is the recurring work of a fractional practice, with what to hand to AI and what to keep.

1. Switching between clients

Every switch costs a warm-up: where was I, what did we decide, which version is current. Asked about the biggest pain of the job, a fractional CFO on r/CFO answered with the problem of every consulting business: "context switching." Across four clients and several switches a day, the warm-ups add up to hours a week.

Give AI: the recap. What changed since the last session, what is open, what the founder asked.

What makes it work: the context has to live somewhere other than the chat history. One project or workspace per client, with the conventions written down (currency, sign convention, what counts as recurring, the fiscal year), so the assistant reads them instead of guessing. We published FINANCE.md as an open format for exactly that file. Without it, every session starts from zero, and the six things that must survive between sessions are listed in Persistent Memory for a Financial Model.

2. The month-end close

You usually do not close the books. The bookkeeper or the accountant does. You accept the close, and you cannot accept four of them on the same day.

Give AI: normalising exports, flagging what moved, proposing explanations, drafting the acceptance checklist.

Keep: the acceptance itself, and every adjustment. The rule that works across a portfolio is short: reuse the workflow, never the sign-off. The full multi-client playbook (staggered calendar, acceptance checks, adjustments kept as data) is in Month-End Close Across Multiple Clients.

3. Reporting and the board pack

The pack is what the client judges you on. Keep the layout identical across clients, so the fourth pack of the month costs a fraction of the first.

Give AI: the first draft of the commentary, ranked by materiality; a plain-language summary for a founder who reads one page.

Keep: the numbers in the pack come from the model, never typed from a chat answer. And the file stays editable without AI. A board can move a slide five minutes before the meeting, and you will not be re-prompting anything then.

4. Forecasts and scenarios

a16z points to continuous planning and "complex scenarios live in the meeting". For a fractional CFO, the meeting is where the value is visible: a founder asks what happens to cash if hiring slips a quarter, and you answer on the spot.

Give AI: the scenario request in plain language, and the explanation of the result.

Keep: the scenario runs on the model's structure, as a variant you can compare to the base case, not as a fresh calculation in the chat. Otherwise you have a number you cannot reproduce next week.

5. Onboarding a new client

This is where a fractional practice wins or loses its margin. The first month on a new client is mostly reading someone else's spreadsheet and mapping a new chart of accounts.

Give AI: reading the inherited model, listing hardcoded values and broken links, proposing a mapping from the client's chart of accounts to your standard structure.

Keep: the decision about what to rebuild. The first-week checklist is in Taking Over a Client's Financial Model, and the way to reuse one structure across clients is in Fractional CFO Financial Model Template.

6. The founder's questions

"Can we afford this hire?" "Why is gross margin down?" These arrive by message, between closes. They are the most visible part of the job and the least priced.

Give AI: the first answer, drafted against the model, with the figures pulled from it.

Keep: the judgment. a16z quotes a growth-stage CFO saying junior staff "lack the experience and context to know what 'great' looks like". That context is what the client pays you for.

Write the Workflow Once, Run It at Every Client

a16z gives the operating rule of the finance engineer: "if you do something twice, write a workflow; if you write the workflow twice, write an agent." Anthropic's own finance team, they report, maintains "70+ finance-specific AI skills they treat like production code", one of which produces a 90 to 95% complete monthly review in about thirty minutes.

A portfolio gives you more repetitions than any in-house CFO. Translate the rule:

• If you do it at two clients, make it a template. The model structure, the board pack layout, the acceptance checklist.
• If you do it at four clients, make it a skill. A written procedure your assistant runs the same way every month: load actuals, run the checks, draft the variance commentary, list what needs your decision.
• Version it like code. When a skill changes, you know which month's output it produced.

The test is consistency. The owner of an accounting practice with CFO advisory put the requirement plainly on r/CFO, after an automation that worked for 30 days and then switched tools on its own: "I want the same workflow and I want the same output." A skill that behaves differently at each client, or each month, is a prompt, not a workflow.

Build or Buy: The Fractional Version

Fractional CFOs were builders before the word was fashionable, because nobody else was going to build for them. Some of the most AI-fluent are now writing their own tools: a three-statement FP&A app built in Claude Code and used with paying clients, a saved script per client company driving QuickBooks through MCP, a close pipeline of CSV files and checks. Kevin Steele, a fractional CFO, walked through his own app at a CFO Connect live build: six weeks, no prior coding experience. His view: "If you're a fractional CFO, you can go crazy and code your own app." His warning, in the same session: "People are making business decisions with your information. It cannot be wrong."

That is a real option. It has three costs that are easy to miss at the start:

1. Upkeep. The tool works for the clients you built it on. Every new ledger, chart of accounts or edge case is a maintenance task, and the hours saved on the close go into the code.
2. Drift. A workflow that lets the model decide the structure each run will produce a slightly different model each run. That is fine for a draft, not for a forecast you present every month.
3. Key-person risk. A client, or a buyer in due diligence, will eventually ask who else can run this. An undocumented tool that lives on your laptop is a weak answer.

The line we would draw: build the method, own it, and keep it portable. The structure of your models, your mappings, your conventions, your skills. Put the computation and the history on a layer that does not depend on you remembering how it works, and that the client can open without you.

Confidentiality, Client by Client

A question that now reaches search engines almost word for word: how do fractional CFO firms handle confidentiality around financial data when they use AI? There is no single policy, because every client contract is different. There is a set of habits that holds up.

• Work on the client's subscriptions, not yours. Ask for an advisor seat on their ledger. Do not import their books into an account you pay for.
• One workspace per client. Never let one client's numbers sit in a conversation where another client's are.
• Read-only on ledgers you do not own. The official Xero and QuickBooks MCP servers expose write operations as well as reads. For analysis, read-only is the right scope.
• Check the contract, then ask. Some agreements forbid putting financials into an LLM, others require consent or specific retention terms. What those clauses actually cover is in Your Client's Contract Says No AI, and what happens to data on each AI plan is in AI and Confidential Financial Data.
• Leave a clean exit. When the engagement ends, the client keeps a working Excel model, formulas intact, that their next CFO can read.

The Time You Save Is Not Free Time

The most common complaint in fractional practices is not about tools. It is about scope: "some clients were getting 60-70% more of my time than the engagement was priced for," one fractional CFO wrote on r/CFO, once they started tracking hours per client against the retainer. AI does not fix that by itself. It can make it worse, because faster answers invite more questions.

Two habits help. Track hours per client per close, so you can see whether the fourth close of the month is actually cheaper than the first. And price on the deliverable, not the hours, once the deliverable is stable. a16z frames the new CFO as someone who decides "what's best done by the team and by software". For a practice of one, that decision is also a pricing decision.

A Four-Week Start

If you are starting from scattered prompts, do not try to automate the whole month. Pick one client and one loop.

Week 4 is the only one that matters. If the second client costs as much as the first, the setup is not portable yet.

Where Layerz Fits

Layerz is a structured spreadsheet, ready for AI. It covers the "computed" layer of the split above: the model's structure (items, formulas, timelines, the links between the P&L, cash flow and balance sheet) is kept separate from each client's data, so you reuse one structure across clients while the values stay in each client's own model.

You bring your own agent. Claude drives Layerz over MCP: it reads the conventions in each model's FINANCE.md, loads actuals, builds scenarios as variants of the base case, and changes the model without breaking the formulas. Actuals come from Pennylane, Qonto and Stripe through native connectors, or from FEC, DATEV, and any ledger report exported to Excel or CSV. Every model exports to clean Excel with formulas intact, so the client keeps a file they can open without you.

It is free for one person working alone, with unlimited models. That is the shape of most fractional practices.

FAQ

How do fractional CFOs use AI in 2026? Mostly for language work around the numbers: drafting commentary and board narratives, explaining variances, normalising exports, reading inherited models, answering founders' questions. The numbers themselves are better computed in a model with a known structure, and signed by the CFO.

Can AI replace a fractional CFO? It replaces part of the hours, not the accountability. Clients hire a fractional CFO for judgment and for a name on the numbers. We wrote the longer answer in Will AI Replace the CFO?

What should a fractional CFO never hand to AI? Posting journal entries in a ledger you do not own, accepting a close, and any figure in a deliverable that cannot be traced back to its source.

Which AI assistant do finance teams use? In CFO Connect's 2026 tools survey, 41% of finance teams named Claude, ahead of Gemini (12%), ChatGPT (10%) and Copilot (9%). For a fractional CFO, whose account the assistant runs on and whether the client agreed matter more than which brand.

How do I keep AI outputs consistent across clients? Write the conventions down once per client, run the same written procedure (a skill) every month, and let a structured model do the computation. Consistency comes from what persists between sessions, not from a better prompt.

The Takeaway

a16z wrote about CFOs with teams becoming builders. Fractional CFOs got there first, by necessity, and with a harder constraint: one person, several companies, and a signature on each.

Let the model draft. Let a structure compute. Keep the signature. And judge every piece of your setup by one question: does it make the next client cheaper than the last?

Keep Reading

• Month-End Close Across Multiple Clients: An AI Playbook for Fractional CFOs
• The Fractional CFO Tech Stack, Layer by Layer (2026)
• Fractional CFO Statistics: Demand, Pay, and the Engagement Model