How env0 took 4 days out of its monthly close

The manual work

The monthly operating review took the first week of every month. Pipeline came out of the CRM, spend and runway out of banking and accounting, headcount and payroll cost out of the payroll system. Three exports, one spreadsheet, and a standing meeting to reconcile the places where the three disagreed.

The team had looked at BI tooling twice and stopped both times at the same place: it needed someone to own the data model, and nobody had the capacity to be that person.

What they connected

Four systems in the first sitting, chosen because between them they held everything the team compiled by hand each month.

Retiring the manual pack

The first job was to stop assembling the monthly operating review by hand, so they rebuilt it as a single live board — a deliberate choice, because it gave them an exact comparison against the spreadsheet they already trusted.

The first run surfaced a discrepancy in how two systems counted the same category of spend. That was not a fault of the tooling — it had been wrong in the spreadsheet for months, and nobody had been in a position to notice.

The first agent

A weekly agent that reviewed pipeline movement, identified deals that had stalled past their normal stage duration, and drafted a note to each owner. It ran Monday mornings, and the drafts waited for the VP Operations to approve.

Their reported approval rate settled around four in five drafts sent as written. The value was less the drafting and more that the review happened every week without anyone remembering to do it.

Ninety days on

"Our ops team used to lose the first week of every month to assembling the same reports by hand. Now we ask ORiON and the answer is already there — and the agents handle the follow-up work in the tools we were doing it in anyway.

What didn't work

Two things they'd do differently, in their own framing.