How to run a revenue review when you only have 40 customers

Most advice about revenue reviews assumes you have enough customers that averages mean something. At 40 customers, an average is noise. One account moving changes your growth rate by 2.5 percentage points. The advice that works for a 500-account team will actively mislead you.

Name every account

At this size, there is no reason to talk about “our mid-market segment.” There are eleven mid-market accounts and you should know all eleven names. Build the review around a list of accounts, not a chart of a segment. If a chart is standing in for a list you could just read out loud in ninety seconds, replace it with the list.

Replace statistics with anecdotes you can verify

“Churn is up 15% this quarter” at 40 customers usually means one customer left. Say that instead: “Meridian left, and here’s why.” A verifiable anecdote about one named account is more useful than a percentage that one departure can move by double digits. It’s also honest about how much signal you actually have.

A thirty-minute agenda for a small team

This is close to what we run, and it fits in half an hour without anyone rushing:

• Five minutes: which accounts moved this week, named individually.

• Ten minutes: the two or three accounts at real risk, one at a time, with an owner and a next step.

• Ten minutes: any deal that crossed a stage, discussed by name, not by count.

• Five minutes: one thing the team almost missed, and why the process almost missed it.

Two mistakes small teams make

The first is importing a big-company agenda wholesale: segments, cohort charts, quarter-over-quarter trend lines. All of it technically works on 40 rows of data and all of it hides more than it reveals at that size.

The second is assuming that because the team is small, no review is needed at all — that everyone already knows what’s happening because they talk constantly. In practice, constant informal conversation is exactly how a small team misses a quiet account: everyone assumes someone else is watching it.

At 40 customers, you don’t need better statistics. You need a list, read out loud, every week, by name.

There’s a version of this advice that sounds condescending — “you don’t need real tools yet” — and that’s not what we mean. Forty customers is exactly the size where the tooling matters most, because there’s no room for a stale spreadsheet to hide a mistake. The tooling should do less analysis and more assembling: pull the list, flag the movement, and get out of the way.

We’ve seen teams at this size try to run a lightweight version of a big-company operating cadence: a Monday review, a mid-week pipeline check, a Friday retro. Three meetings a week for a five-person team is its own kind of overhead. One thirty-minute review, run consistently, beats three shorter ones that each lose momentum by their second month.

The account-naming habit pays off past forty customers too, but it gets harder to sustain past roughly a hundred, which is usually when teams start reaching for segments again. That’s a reasonable transition — the mistake is making it at twenty accounts because it feels more sophisticated, not because the list actually got too long to read.

If there’s one number worth tracking at this size, it’s not a rate at all. It’s the number of accounts nobody has spoken with in three weeks. That number should be close to zero, and if it isn’t, the review just found its first agenda item. Track it weekly, name the accounts on it, and resist the urge to average it into a percentage.

We’ve started recommending one more habit to teams at this size: read the list of forty names out loud once a quarter, not just the ones that moved. It takes four minutes and it reliably surfaces an account nobody has thought about in months, simply because saying a name forces a moment of attention that a spreadsheet row never does. That account is rarely a crisis. It is, more often, a quiet reminder that “no news” and “fine” are not the same thing at this size.

This gets easier once you stop trying to make your data look like a bigger company’s. Forty customers is a manageable list, not a small sample. Treat it that way and the meeting gets shorter and more useful at the same time.