Prepping the half-time review

The half-time review most teams hold in early July is a two-hour meeting where everyone sees the numbers for the first time, reacts to them live, and leaves with a shared commitment to dig in further. Nothing changes, because nothing was decided, because nothing was framed to be decidable. The version that actually changes H2 is built differently, and its difference gets decided now, in the last days of May: the agenda is written before the half ends, so June's data arrives into a frame instead of a scramble.
Choose the five numbers now
Pick the numbers in advance, or the meeting will be held hostage by whichever chart looks most dramatic on the day. Five cover most outbound programs. Pipeline created against the H1 plan, in dollars and count. Held meetings by month, as a trend line, with the acceptance rate beside it. The held-to-opportunity conversion, read against the benchmark that roughly one in two held meetings advances. Observed sales-cycle length against the length the plan assumed, because a two-week miss there quietly rewrites every downstream forecast. And activity against the standards the year started with, the ones set back in January, so effort and outcome can be discussed as separate questions.
Announcing the five in May has a second effect: June gets measured cleanly. Definitions get settled, gaps in the data get fixed while there is still time, and nobody spends the review arguing about what counts as a meeting.
Name the three decisions
A review without named decisions is a documentary. Before the meeting is scheduled, write down the two or three questions it must answer, phrased so that leaving without an answer is visibly a failure. For most teams the list looks like this. First, the list decision: which segments get killed and which get doubled, argued from evidence rather than affection, with cohort views by entry month doing the honest work of showing which bets actually converted. Second, the message decision: whether the core thesis survives six months of contact, a judgment H1 is finally big enough to support, since a half is two full quarters and clears the bar we set in the two-quarter rule. Third, the capacity decision: how many seats H2 needs, decided at the review and not drifted into later, because any seat approved in July spends weeks reaching speed and the second half is shorter than it looks.
The pre-read does the archaeology
The last piece is mechanical and does most of the work. The five numbers, with a one-page narrative, circulate two full days before the meeting. Anyone who disputes a figure raises it before the room convenes, so data arguments happen asynchronously and decision arguments happen together. The meeting itself then needs forty-five minutes, not two hours: five minutes reviewing what the pre-read said, the rest on the three decisions, and a written owner and date on each before the call ends.
For CommandVA clients the pre-read is nearly free, because the weekly report has been accumulating exactly these numbers all half: the funnel, the acceptance rate, and the what-changed narrative, week over week since January. Compiling a half-time review from that record is an hour of assembly, not a forensic project. If your own July review is shaping up to be archaeology, book a strategy call before the half closes. We will help you frame the five numbers and the three decisions while May can still do something about June.
One dedicated, full-time SDR inside a complete outbound system. Written meeting SLA, weekly reporting, month-to-month. A 30-minute call tells you if it fits.
Book a strategy call