Larch runs the monthly CFO loop for owner-led companies and the advisory firms behind them. Close data in, Pack out, decisions logged in between.
Close data lands. Observations get written against the KPIs. The forecast locks. The Pack goes through review before the client ever sees it. Quiet month or loud one, the order does not change.
Larch holds the whole loop in one place: the Working Brief, the forecast versions, the decisions and asks, and the Pack itself, all connected. When something slips, the cycle says where.
It is the second week of June and you still do not know. The bookkeeper says the numbers are in. The dashboard has forty tiles and no opinion. Somewhere in there is the one number that should change what you do this month.
Larch sends a monthly read instead: what moved and why, plus the two or three calls that are actually waiting on you. Twenty minutes, once a cycle, written to be acted on.
One client's April pack went out on the 9th. Another slipped to the 22nd because the brief sat unreviewed in an inbox, and nobody noticed until the client did. Every firm has a version of that month.
Larch puts every engagement on one queue with its cycle stage visible: whose close data has landed and which pack is due this week. When a brief stalls in review, the queue says so. Last month's context is already loaded when this month starts.
The monthly read starts above the ledger, not inside it.
A Pack carries the few numbers that matter this month and leaves the rest in the appendix, where they belong.
The cycle runs in the same order whether the month was quiet or loud.
Decisions get logged, then revisited next cycle. The point of the read is the call you make after it.
Under partner review, lender questions, and the next monthly cycle. The specifics, not the adjectives.
Every figure in a Pack traces back to a source row. When a partner asks where a number came from, the answer is a click, not a hunt.
Firm-scoped isolation, hosted in Canada (ca-central-1). Your clients' books never sit next to anyone else's.
The AI drafts observations and never publishes. A person reviews and signs every Pack that goes out. What it can and cannot touch is written down, in plain terms, on the security page.
Decisions get IDs and links to the actions they created. Next cycle, the queue asks what happened.
Demonstration engagement · every pack ships with one
Thirty minutes. Your numbers if you want, and a sample Pack either way.