For fractional CFOs

You cannot hire your way to the eleventh client.

You hold the finance seat at several companies at once, and the constraint is you. Every engagement is another close, another reporting pack, another set of logins and the same brain. And every engagement ends — handover is part of what you sell, not an afterthought at the end of it.

Book a Close Teardown Run the free Diagnostic

What it does

The modules that matter when the entities are other people’s companies

Each one runs a real workflow, in the order it runs. The point of all of them is the same: the tenth engagement runs like the first, without a tenth of you.

One cadence across every companyseed from prior-year actuals → build → approve → compare month by month Budget against actuals monthly, blended into a rolling forecast that uses actuals for closed months and budget for open ones, with operator-defined KPIs computed against live balances and snapshotted so period comparisons hold still.

Every client gets the same pack on the same schedule, built the same way.

Thirteen-week cash, per companyopen AR and AP → place by that entity’s DSO and DPO → weekly grid → override a cell Built from each company’s own collection and payment behaviour rather than a shared assumption, with a pattern-based fallback for payroll and rent and saved overrides where you know something the ledger does not.

The cash call you are actually hired for stops taking a morning per client.

Weekly transaction reviewpull the last 7 days → compare to the prior 4-week average → flag the outliers Purchases and deposits measured against the rolling four-week norm, with individual transactions flagged where they deviate materially.

You read exceptions instead of registers, and you catch the duplicate payment in week one.

Handoff packagesassemble from the work graph → hand over → receiver rehydrates from the package alone Completed and remaining work, blockers and risks, missing evidence, stale conclusions, open questions, and the decisions someone still has to make — built from current state rather than written from memory.

Your exit is a document, not three weeks you cannot bill.

Documents and agreementsupload → virus-scan → extract terms → feed the modules that need them Renewal dates, covenant language, payment and escalation terms read out of the contracts and made available to the modules that depend on them. Document content is fenced as untrusted data before it reaches the model.

A contract can inform the system. It cannot instruct it.

Alerts across the portfolioaggregate every module live → rank by severity → open onto the driver Sync health, cash risk, close status, budget variance, AP and AR risk and proposals awaiting review in one view, with each alert opening onto the data that produced it rather than a summary of it.

One place that says which client needs you today.

Cost attributionmeter every model call → attribute to the entity → roll up What the automation costs, per company, visible to you rather than arriving as one line on somebody else’s invoice.

You can price an engagement knowing what running it costs.

Modules you do not need are switched off rather than shipped as clutter. What each one does for your book of clients — their entities, calendars, charts of accounts and approvers — is configured during the build, against their books.

The rule, before the modules

One rule holds across every workflow above

The AI retrieves, analyses, drafts and proposes. Deterministic code calculates and checks. An authorised person approves anything that reaches the ledger. There is no unsupervised posting, and no setting that turns it on.

Four-tier action gate

Every action is classified into exactly one side-effect tier. Ledger and customer-facing writes are proposal-first, human approval only. An unrecognised action fails closed into the most-gated tier.

Preparer and approver

Review policy set per entity, with role floors and per-check materiality overrides, and separate preparer and approver roles wherever the control requires segregation.

Readable proposals

Each proposal carries before and after, its source data, risk level, the role required to approve it, a content fingerprint, an expiry, and its execution record.

One audit chain

The prompt, the run, each tool call, the proposal, the approval or rejection, the sync — recorded as one chain you can walk backwards.

Circuit breaker

When a task’s accuracy degrades, the system revokes that task’s autonomy and alerts. It can only demote. It can never promote itself.

Grounded answers

Answers cite period, basis, source reference and sync timestamp. Prose claims are verified against facts captured at the tool boundary; anything unverified is marked.

How an engagement is bought

Five rungs. You can stop after any of them.

The Run is monthly; nothing else here is. Nothing renews against your will, nothing commits you to the next rung, and each one ends with something written down that you keep — the last of them the source itself.

Free·three minutes·nothing leaves your browser

The Handover Test

Pick the engagement you would least like to lose and answer six questions about what happens to it if you stop on Friday. The work only you can do is not leverage — it is the reason there is no room for an eleventh client.

Take the Handover Test →

You leave withA workpaper naming what a successor could not do, in the order worth fixing.

Free·45 minutes·five a month

The Close Teardown

Not a demo and not a discovery call. You bring your close — the checklist, the calendar, the entity you argue with most — and we go through it together.

Book a teardown →

You leave withOne written page about your own close, sent afterwards, whether or not anything else happens.

$7,500·one close cycle

The Pilot

Pick the process that costs you the most every month — the intercompany reconciliation, the flux commentary, the board pack, the covenant certificate. We run it. Not a report about running it: the thing itself, on your calendar, against your books, delivered in the month you would have delivered it anyway.

What the pilot covers →

You leave withThat month’s output delivered on time, the evidence pack behind it, and a written read on what the next two processes are worth. Yours whether or not anything follows.

$5,000 a month·three months to start

The Run

We keep running it, then the second process, then the third. An evidence pack every close — what ran, what it proposed, who approved it, what changed. The second process costs less than the first, because the control layer it needs is already standing.

You leave withA close that arrives on the date it is due, and a written record of every judgment inside it.

At twelve months

The Handover

The Handover Test named what a successor could not do. This is where that stops being true: after a year of it running, the engagement comes with the source, the training, and support while whoever takes it settles in.

You leave withThe source, on your own infrastructure and your own model keys. Nothing to renew, and no login to lose.

If you would rather own it outright from the start, we build it that way instead — scoped against what your close actually is, so it carries no published price. Most people do not start there. The teardown is where you find out whether you should.

Where to start

Find the layer that is least ready to carry it.

Twelve questions across six control layers. About six minutes, and the result stays on your screen — sharing it is optional.

Book a Close Teardown Run the free Diagnostic

Not quite you? PE-backed portfolio companies → Accounting firms and CAS teams →