About

Larch came out of a practice, not a pitch deck.

FourX Partners runs CFO engagements for owner-led companies. For years the monthly cycle lived where it lives at most firms: a spreadsheet with a careful naming convention, an email thread with the client, and one person who remembered why the March forecast moved.

That held until it did not. Engagements grew faster than the team's memory, and the partners faced the choice every advisory firm eventually faces: hire ahead of the work, or build the discipline into software. They looked for the software first. Everything on the market was either a dashboard that skipped the judgment or a workflow tool that skipped the numbers.

So Larch got built the slow way: inside the practice, against live engagements, with controllers and partners as the first and least forgiving users. The product on this site is the version that survived them.

Built byFourX Partners
Based inCalgary, Canada
First internal cycle2024
Opened to outside firms2026
Data regionca-central-1

The short version, for the diligence file

The charter

The work is to see clearly from a higher vantage point.

An owner inside a business sees this week's invoices and the loudest problem. The job of a CFO practice is altitude: far enough up to see the pattern, close enough to name the specific job, the specific crew, the specific lease.

Larch exists to hold that vantage point steady every single month, on the months the team is stretched as much as the months they are not. The judgment stays human. The discipline is the product.

The one photograph on this site, kept where the metaphor earns it

Four pillars

The words we check our work against.

Every product decision gets argued against these four. When a feature fails all four, it dies, however good the demo would have looked.

Elevation

The read starts above the transactions. Pattern first, line items as support, never the reverse. A page that opens with a table has already failed this one.

Focus

Six KPIs, not forty tiles. Two decisions, not a backlog. If everything is highlighted, the firm has handed the client a search problem and called it insight.

Rhythm

The same steps, the same order, every month. Rhythm is what lets a small team carry many engagements, and what makes a missed step visible instead of silent.

Impact

The cycle ends in decisions made, not reports delivered. Next month's read says how each call played out. That loop closing is the whole point of the product.

Who builds it

A small team, with the practice down the hall.

Larch is built by a small product team inside FourX Partners. The arrangement is unfashionable and useful: when a controller hits a wall in the Thursday close, the person who built that screen hears about it before lunch.

It also sets the incentive that matters most. FourX runs its own client engagements on the same build outside firms get. A shortcut in the product costs the practice before it costs a customer, which is the right order.

How we decide what to build
  • The cycle comes first. Anything that does not serve close-to-Pack waits, whatever the prospect asked for.
  • Dogfood before ship. A feature runs on FourX engagements for at least one full cycle before any outside firm sees it.
  • Statuses tell the truth. The scope ledger on the Platform page changes only when the software does.
  • The AI boundary holds. No release moves a client-visible surface past human sign-off. This one is not up for argument.

Working rules, not values copy

Talk to the people who run it, not a funnel.

Walkthroughs are given by someone who carries engagements on Larch. For anything else, hello@uselarch.com reaches the team directly.

Book a walkthrough