top of page
HOW-TO ARTICLE

It's OK to Say It's Raining

The Weekly Flash Report Email That Keeps a CRO in the Seat

November 2, 2026

I've sat through a lot of board meetings where the company is missing its number, and the CRO is simply asked, "What are you going to do about it?"

​

Too many times, I've heard answers like "we're going to redouble our efforts," "we're going to find another, higher gear," or "we're going to get creative and really dig deep on deals."

 

Along with everyone else in the room, what I really hear is "this leader has no idea what's going on in their business."​​

“

We're going to find another, higher gear."

What a board hears when a CRO is asked about a number they have no plan for.
 Effort isn't a plan, and everyone at the table knows the difference.

​​It usually isn't the missed number

 

The average CRO lasts about two years - and that time keeps getting shorter. Most people assume they're fired for missing quota.

 

I don't buy it.

​

Run the math on a CRO who starts in November. They get a couple of months to find their footing. Q1 is mostly a wash while they learn the product, the people and the market. Replacing a CRO takes about three months of recruiting, so if the board is interviewing replacements to be in place by the following January SKO, they started doubting that leader well before then.

 

Practically, these decisions are getting made on less than a year's worth  of real performance, often against a number the CRO had no hand in setting.

​

And missing is normal. When QuotaPath surveyed more than 450 sales, finance and RevOps leaders for its 2024 compensation report, 91% said their companies were falling short of their quota targets.

​

The private equity people I work with are smart, financial people. They know this cycle is expensive, and they keep repeating it anyway. I think it's less about missing the number than about poor communication about the number.

“

It's OK to say it's raining. We just need to know how long to keep our umbrellas out."

What a board actually wants to hear. Boards can deal with bad news, they just hate to be surprised.

Boards and investors can weather a storm. What they can't work with is a leader who can't tell them it's raining, or when it might stop.

​

One email, every week, to everyone

 

With that in mind, I developed a simple habit that has saved me more times than I can count. Every week, right after the forecast call, I send one short report to every sales leader, member of the executive team and board member as one large group. I started it during seven years at a PE-backed software company that called it the "flash report," and I've used it everywhere since.

​

There's no separate board version. Everyone sees the same plan and the same progress, good news or bad. When that happens, everything in the company runs better.

​

A RevOps person can build it for you - or even an AI agent - and once the template exists, it takes minutes a week to produce.

​​

03-one-report-to-everyone.png

It starts with defining the plan

 

​​Of course, a flash report only works if everyone agrees on what "on plan" means. So before the first report goes out, break the annual number into your different sources of revenue, and the assumptions your plan requires:

​

  • Renewals. You won't keep every customer. What retention rate are you counting on, and what does customer satisfaction data say about it?

  • Price increases. What do your contracts allow, and how much is reasonable to expect?

  • Upsell and cross-sell. What else has to go right, like on-time product launches and successful deployments?

  • New logos. What's your conversion rate from lead to win, how long does it take, and what does marketing need to feed the funnel?

  • New products. When do they ship, and when will sellers be ready to sell them?

 

Then work out how much pipeline each source needs, and when. Share it with the rest of the leadership team too. If your plan depends on hiring ten sellers, HR has to be ready to deliver them.


​

04-start-with-the-plan.png
Every week, one chart tracks progress against the plan
​

The heart of the flash report is one chart (shown below). Admittedly, it contains a lot of information, but it becomes easy to digest when you understand the six questions it's answering.
 

  1. What week of the quarter is it? That's the x-axis. My example quarter has 14 weeks, and we're in week 8.

  2. What's the booking target? In the example, a $3.7M quarterly plan.

  3. How much quota is on the street? You want to assign more than the plan, because you won't have a full team all year, and not everyone is going to hit 100%.  In the example, a seller left mid-quarter and quota dipped, but it still covers the plan.

  4. What has the team been forecasting each week? Here's the good news: every week the forecast has been above plan, and it keeps going up.

  5. How much has been booked so far? A running total, week by week.

  6. How does that compare to last quarter, and to this quarter last year? That gives everyone a sense of the normal shape of a quarter.

​

05-six-questions-chart.png

If you stop there, you've already enabled your board and your colleagues to read the business in about ten seconds. The booked line is climbing, the forecast sits above the plan, and the two look likely to meet.

​

Alongside it, I also produce the same chart for pipeline generation - with lines showing monthly pipeline goals and whether we're creating enough pipeline to hit next quarter's number.

​

I also like to add a data table with the team-by-team breakout of plan, forecast, bookings and pipeline coverage. Your CFO will want to dive into it, and it shows everyone exactly where the gap is.

 

Finally, a few short lines of commentary: what we've committed, what we're forecasting, and the handful of deals that decide the quarter. Name each deal and say what it needs. For example:
 

  • $2.8M booked, 75% of the quarterly plan, with six weeks to go.

  • $3.6M committed (94% of goal); forecasting $4.1M (107%).

  • LuminaCore needs us to agree on a reduced scope for quick implementation.

  • Veridien can sign if we approve 120-day payment terms.

  • Ethos has a new CFO who wants his own review before signing.

06-team-detail-and-key-deals.png

The board conversation moves from "arguing about the number" to discussing our confidence in those final bits of commentary - and what we can do to change them.  If you're optimistic those deals close, here's where we end up. If you're not, here's where we end up instead. Nobody has to guess, and everyone understands exactly what needs to go right.

​

The whole thing fits on one page

 

All of this content can come together on a single page with two charts, a table, and a few sentences of easy-to-understand bullet points. 

​​

When the news is bad

 

The report matters most when the lines turn ugly. Because I've been sending it every week, I'm never the CRO who shows up at the end of the quarter to announce a miss.

​

Instead of simply saying "we missed," we can have a smart conversation, like "our new product launch slipped eight weeks from what the plan assumed, so we won't get the first five adopters our plan called for. Here's what we need to do to get back on track with the product launch, or here are the costs we can cut to offset the delay." Showing your math moves the conversation from blame to shared responsibility for the path forward.

​

Sharing a flash report about missed numbers doesn't let you off the hook. Loans still come due and payroll still has to be funded, and the company needs you to chase the original number with everything you have. But a board that trusts your read of the business and agrees with your plan on what needs to change will bet a few more quarters on you, even when the revenue isn't there yet.

​

It's not just for the CRO

 

If you lead a front-line team rather than a whole revenue organization, the same habit works at your scale. Break your number into its pieces, send your manager the same short report every week, and name the deals that matter. It's one of the clearest ways to show you're ready for the next job.

​

In closing

​

I've outlived the average CRO tenure more than once. But it wasn't because I never missed my number - it was because the people around me could trust me to tell them what was happening, why, and what we'd do about it.

​

A board can work with bad news. It can't work with a surprise.
 

I'll be walking through this on stage at the CRO Summit in Chicago on November 17.

If you want to start sooner, the Weekly Flash Report Builder tools and AI prompts can be found in the free toolkit for "The Day Nobody Puts on their Calendar."Download the free Excel template and plug in your own numbers, or let the AI prompts guide you, and you can start sending it to your board tomorrow.

Finally, my book, The CRO's Guide to Winning in Private Equity, includes templates and explanations of the full method, including for building the annual plan behind it.

08-whole-report-one-page.png
bottom of page