Every Monday at 10:00, twenty-two people gathered in a room called Aurora to read the same numbers off the same dashboard. It was, in retrospect, completely insane.
The meeting that ate Monday
The numbers meeting started in 2023, when we were eighteen people and nobody really knew how the business was doing on any given week. It made sense then. By 2025 we were a hundred and forty, and the meeting had grown to forty-five minutes of someone reading a slide aloud while the rest of us pretended not to be on Slack.
We did the math once. Forty-five minutes × twenty-two attendees × fifty-two weeks. That's eight hundred and fifty-eight hours a year. Two and a half people, full-time, listening to numbers they could have read in two minutes.
What we noticed was broken
The signal-to-noise was awful. Most weeks the numbers were fine — boring, even. The meeting still ran. When something was off, we'd discover it on Monday, four days after it happened. By then the cohort had already moved on.
"If you only look at the dashboard once a week, you have a once-a-week business."
We also noticed that the people presenting the numbers were the only ones who'd actually engaged with them. Everyone else was experiencing the data through a narrator. That's a great way to make sure no one in the room can argue with the framing.
Replacing meetings with digests
The replacement was almost embarrassingly simple. Every Monday at 08:00, an automated digest lands in
: ARR delta, net new logos, churn count, NPS, top three anomalies. Five bullets. Three charts. One link.
If a number is off by more than two standard deviations, it's flagged.
Anyone who wants context posts a thread under the digest.
If a thread gets more than five replies, it becomes a 25-minute working session — but only with the people who replied.
That last rule was the unlock. The meeting still exists, technically, but only when there's a real reason for it and only with the people who care.
Six weeks in: the numbers
We tracked four things before and after the change. The deltas, in order of how much they surprised us:
The third row is the one we keep coming back to. The async format didn't just save time — it produced more conversation about the numbers, not less. Turns out people had been thinking things in that room for years and not saying them.
What we'd do differently
Two things. First, we'd have killed the meeting six months earlier — the only thing keeping it alive was nobody wanting to be the one to suggest killing it. Second, we'd have invested in the digest itself sooner. The first version was a janky Zapier flow that broke roughly once a fortnight. The current version is built on Metrify (obviously) and hasn't missed a Monday since.
If your team has a recurring meeting whose primary content is reading numbers aloud, here is your sign.
David Hamilton
Founder & CEO, Metrify
Writes about operating cadences, async culture and the small details that compound. Previously RevOps at Linear. Six of them atleast.
Read More
