// CASE STUDY
6 MIN READHow env0 unified operations intelligence
What they had before, what they connected, what changed in the first ninety days, and what they'd tell you to do differently.
env0 — infrastructure automation platform
Approximately 180 employees across four countries
VP Operations, with the finance lead as second user
Under a week from first connection
Before
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 monthly review argued about.
Pipeline, stage history, deal owners
Cash position, burn, inbound payments
Headcount, monthly cost, team composition
Customer correspondence context on open deals
The first board
They rebuilt the monthly operating review as a single dashboard rather than starting with something new — 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
removed from the monthly close cycle
standing boards replacing the reporting spreadsheet
changes to any connected system
"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.
Connecting with the wrong account first
The CRM was connected by someone whose visibility didn't cover every team, so early answers looked incomplete for reasons that had nothing to do with the product. Reconnecting fixed it in a minute, after a week of mild confusion.
Building too many boards too early
The first enthusiastic fortnight produced nine dashboards, of which three were ever opened again. Their advice: rebuild the report you already argue about, and let the rest come from real questions.
// NEXT