You grew 42% last month. The growth rate an investor trusts is closer to 8%.

A founder opens the update with the number that looks best. "Revenue was up 42% in June." It is true. It is also the single loudest month in two years, and it happened because one enterprise contract that had been in the pipeline for three quarters finally closed. The investor reading the update hears the 42% and quietly does the arithmetic that turns it back into a trend.

Why one month is not a rate

Monthly revenue is noisy. A single large deal, a delayed renewal, an annual plan billed in full, a seasonal push, each moves a month by more than the underlying business is actually moving. Growth rate is a property of the trend, not of the loudest point on it. Reading it off one month is like judging a runner's pace from the stride where they crossed the line.

The fix investors reach for is a compound monthly growth rate, usually over the trailing six months. CMGR-6 takes where you started, where you ended, and the number of months between, and solves for the steady monthly rate that would have connected them. Ending revenue over beginning revenue, raised to one-sixth, minus one. It is the rate that, repeated every month, produces the six months you actually had.

What the smoothing removes

Take a company that went from $180K to $290K in monthly revenue over six months. Somewhere in the middle, one month jumped 42% because a $70K deal landed. Another month was flat, because a customer churned the same week two new ones signed.

The headline off the best month is 42%. The CMGR-6 is about 8%. Both describe the same six months. Only one of them describes what next month is likely to look like. A 42% monthly rate compounds to more than fifty times a year, a number no one believes and no one is underwriting to. 8% a month is roughly 2.5x a year, which is a real, fundable growth-stage rate. The smoothing did not make the company worse. It made the number usable.

Smoothing cuts both ways

The same math protects a founder as often as it exposes one. A single ugly month, a large logo lost, a deal that slipped from March into April, drags a spot rate down in a way that says nothing about the trajectory. A founder who leads with "we were down 3% last month" is handing over the noise instead of the signal.

CMGR-6 is the honest version of the number in both directions. It is why the smoothed figure, not the spike and not the dip, is what belongs at the top of a board update. The investor is going to compute it anyway. Presenting it first says you already know what your growth actually is.

What the gap tells an investor

The distance between the loud month and the compounded rate is itself information. A large gap, sustained, usually means growth is lumpy. At a certain scale that is fine, and at an early one it is a concentration risk wearing a good month as a disguise. It can also mean the trend is decelerating and one strong month is holding the headline up. A six-month compound rate that is falling while the reported month looks healthy is one of the cleaner tells that momentum has turned before the top line admits it.

None of this requires suspicion. It requires arithmetic that takes ten seconds and that the founder should run before the room does. The question an investor is answering is not "how fast did you grow." It is "what is the rate I can put in a model and expect to hold." The best single month is rarely that rate.

What this means for the founder

Lead with the number you would defend under a decomposition, not the one that photographs best. If the compounded rate and the headline month sit close together, say so, because it means your growth is steady, and steady is worth more than a spike. If they are far apart, you want to be the one explaining why, not the one being asked.

Levian computes CMGR at three-, six-, and twelve-month windows from your income statement revenue and plots it alongside each month's actual revenue, so you can see where a single month is running ahead of or behind the trend. It is the same smoothing an investor does in the margin of your update, run first, on your side of the table.