--- title: How to Set and Adjust Your Win/Loss Program Cadence canonical: "https://winlossresearch.com/playbook/set-a-win-loss-program-cadence/" description: "Run a win/loss program on a semi-annual cadence by default, adjusted only for a specific market, pipeline, or competitive shift." --- # How to Set and Adjust Your Win/Loss Program Cadence Run a win/loss program on a semi-annual cadence by default. Six months gives the team time to execute on the prior cycle's action items and captures a real window of change in the market, without running so often that findings turn into noise. Adjust off that default only for a specific, dynamic shift, a pipeline problem or competitive change, not on a fixed shorter schedule. 1. [Set the default cadence at semi-annual](#step-1-set-the-default-cadence-at-semi-annual) 2. [Confirm deal volume can support it](#step-2-confirm-deal-volume-can-support-it) 3. [Build a findings review into every cycle](#step-3-build-a-findings-review-into-every-cycle) 4. [Know which findings decay fast and which don't](#step-4-know-which-findings-decay-fast-and-which-dont) 5. [Use an off-cycle refresh for anything more urgent](#step-5-use-an-off-cycle-refresh-for-anything-more-urgent) ## Step 1: Set the Default Cadence at Semi-Annual Six months is the right rhythm for most programs. It gives functions enough time to actually execute on the prior cycle's committed actions before the next round of interviews starts, and it's long enough to capture meaningful movement in buyer sentiment, competitive dynamics, and market conditions, the kind of change worth adjusting GTM strategy over. That's the bar for this cadence: findings that move strategy, not a running tally of every minor shift. Quarterly is too frequent for most programs to get real value from. There isn't enough runway between cycles for committed actions to land before the next readout piles more on top, and the findings start reading as noise rather than signal. A program on a quarterly rhythm ends up presenting the same handful of themes cycle after cycle, mostly unchanged, because six months' worth of real movement hasn't had time to accumulate in three. Treat semi-annual as the fixed baseline once set, not something reopened at the start of every cycle. ## Step 2: Confirm Deal Volume Can Support It Before locking in the cadence, confirm the segment actually produces enough closed deals to support it. Use the same list-size math from [how to build a win/loss interview target list](/playbook/build-a-win-loss-interview-target-list/): roughly 400 loss-eligible and 100 win-eligible contacts within the 30-to-180-day research window.
Example 
Segment produces ~400 losses + ~100 wins within the window
  -> Semi-annual cadence is well-supported

Segment produces meaningfully less
  -> Widen the segment or extend toward the full 180-day edge
     of the window before locking in a fixed cadence
A segment that comes up short here is the same situation the target-list play's own worked example resolves: extend the window or widen the segment, rather than lowering the interview count or forcing a cadence the deal volume can't actually support. ## Step 3: Build a Findings Review into Every Cycle Open every readout with a short review of the prior cycle's findings before presenting anything new, checking which ones still hold up against the current interview set.
Example 
For each finding presented in the prior cycle's readout:
[ ] Still holding up against this cycle's interview set?
[ ] Has anything in the market changed enough to retest it?
[ ] Retire it, keep it as confirmed, or flag it as needing
    current-cycle confirmation before anyone acts on it again
A program that only adds new findings each cycle without retiring stale ones ends up with a battlecard or messaging framework built on a mix of current signal and outdated assumption, with no way to tell which is which without checking. ## Step 4: Know Which Findings Decay Fast and Which Don't Not every finding needs the same review scrutiny. Some hold their shape for years; others are stale within a couple of cycles. | Finding Type | Decay Speed | Example | |---|---|---| | Buying committee structure | Slow, years | Who typically holds veto power in the decision | | Process friction and risk signals | Slow to medium | Recurring budget-approval friction patterns | | Competitor perception | Fast, months | How a named competitor reads after a product update | | Messaging resonance | Fast, months | Whether a specific positioning line still lands | | Pricing perception | Fast, months | How pricing reads against a shifting market | Weight the Step 3 review toward the fast-decaying rows every cycle, and treat the slow-decaying ones as needing a lighter check, confirmed rather than fully retested, unless something specific suggests otherwise. ## Step 5: Use an Off-Cycle Refresh for Anything More Urgent A dynamic market shift, a pipeline problem, or a competitive change that needs an answer faster than the next scheduled cycle allows is a reason to run a scoped off-cycle refresh, not a reason to move the whole program to quarterly.
Example 
Trigger a scoped off-cycle refresh when a specific, already-felt
signal moves faster than the next scheduled cycle would catch it:
a win rate drop in a specific segment, a competitor newly appearing
in evaluations where it never used to, a major product launch, or
a pricing change under active consideration.
The trigger has to be specific, not a general sense that "it's been a while." A refresh scoped around "our Enterprise win rate dropped eight points this quarter" is answerable; a refresh scoped around vague unease isn't, and it usually signals the program needs a clearer objective more than it needs a faster clock. A practical example: a program on a semi-annual cadence is three months into its current cycle when a new competitor starts appearing in evaluations for the first time. Waiting the remaining three months means running interviews against a competitive landscape that's already stale by the time findings come back. An off-cycle refresh, scoped narrowly to the competitive-perception question rather than a full program restart, gets a usable answer to leadership while the signal is still current, then folds back into the regular semi-annual cadence at the next scheduled cycle. This is the exception the default is built around, not a reason to abandon it. ## Related ### Other Plays in This Phase - [How to Measure Whether a Win/Loss Program Is Working](/playbook/measure-whether-a-win-loss-program-is-working/) ### Relevant Pillars - [How to Build a Win/Loss Research Program](/topics/how-to-build-win-loss-program/) - [Win/Loss Research for GTM Strategy](/topics/win-loss-gtm-strategy/) Get the downloadable Playbook →