An anti-strat isn't a general map tactic — it's a specific plan built against one particular opponent. The team studies their past matches, identifies recurring habits — for example, a favorite side of the map for flashes, a typical rush timing, or a standard defensive setup — and prepares a move that breaks these habits.
The difference between an anti-strat and a regular home-prepared setup lies in its targeting. A regular default can be used against any opponent, while an anti-strat works precisely because it's built on the weakness or pattern of a specific team. If the opponent changes their habits or learns about the scouting, the effect may disappear.
Where anti-strats come from
The foundation of an anti-strat is demo review — that is, watching recordings of the opponent's past games. Analysts and the captain go through matches, looking for patterns: how each player reacts to pressure, what utility combos the lineup uses, where the support usually looks at the start of a round. These observations are then assembled into a counter-plan.
Anti-strats are usually prepared and implemented by the team's captain — the same person responsible for in-round calling and overall strategy. They also decide when to apply the setup: sometimes an anti-strat is saved for the deciding map of a series so the opponent doesn't have time to adapt in advance.
Why it's harder without a captain
Scouting the opponent and preparing anti-strats is methodical work done before the match, not improvisation during the game. Without someone systematically handling this, a team more often plays "on its own," relying on general setups rather than the specific opponent's weaknesses. This doesn't mean victory is impossible — but the team loses the edge that quality preparation usually provides.
In professional CS2, anti-strats have become part of standard tournament preparation: the closer the playoff match, the more detailed the scouting, and the higher the chance that both sides are preparing unexpected moves against each other.