How to scout your next CS2 opponent

Step 1

Find your opponent's recent demos

Scouting starts with footage, and recency matters more than volume. Three demos from the last two weeks beat ten demos from last season — rosters shift, roles change, and teams patch the exact habits you would otherwise prep against. Aim for three to five recent maps, ideally including the maps you expect in the veto.

Where to find them: FACEIT match rooms keep demos downloadable from the match page for recent games, so walk your opponent's match history and pull the relevant ones. League and tournament platforms (ESEA, ESL Play, collegiate leagues) usually attach demos to completed match pages. If you have scrimmed the team before, your own scrim demos are gold — that is footage of them playing against your style specifically. Prioritize official matches over pugs: a team's FACEIT pug habits often look nothing like their practiced executes.

If a team has almost no recent footage, scout the players instead — their individual match histories tell you who entries, who lurks, and who anchors, even from mixed lineups.

Step 2

Get the demos into one place, per opponent

This sounds trivial and is where most amateur scouting quietly dies. Demos end up scattered — one on a teammate's PC, two in a Discord channel, three behind a match page you cannot find again on Friday night. If you cannot see all of a team's footage in one place, you cannot see patterns across it, and patterns are the whole point.

Keep one folder (or one workspace) per opponent team, with demos labeled by map and date. When a new demo appears, it goes in the same pile. Over a season this compounds: the second time you play a team, half your scouting is already done.

In Prefire, this is the core object model — you create a team, drop demos into it, and every analysis that follows is computed across the whole pile per map, not per file.

Step 3

Read map picks and side tendencies first

Before you watch a single round, work out the shape of the veto. Which maps do they pick? Which do they permaban? On their pick, do they win off T-side rounds or CT-side rounds? A team that picks Mirage and banks on a 9-3 CT half plays the map completely differently from one that grinds T-side executes — and your veto strategy should respond to that before your strats do.

From match history alone you can build a simple table: map, times played, win rate, average T rounds, average CT rounds. Ten minutes of work, and it tells you where they are comfortable, where they are fragile, and what they are likely to leave you in the veto. It also tells you where to spend your limited demo-watching time — deep on the one or two maps you will actually play.

Prefire computes per-map results and side splits automatically from the demos you add, so the veto read is waiting before you open a single round.

Step 4

Identify per-player habits

Teams are creatures of habit, and the habits live in individuals. Watch the same player across multiple rounds and demos, and ask three questions: where do they start the round, where do they go first, and what do they do with their utility?

• Entry paths. Most entry players have one or two favorite first contacts per map. If their entry dry-peeks mid at 0:45 in three separate demos, that is not a coincidence — that is a prefire waiting to happen.
• Utility timings. Note when the first smokes land. A team that commits utility early telegraphs the site call; a team that holds it past the minute mark is defaulting for picks. Either way, their nade usage is a clock you can read.
• Default setups. On CT side, map where each player stands in the standard setup, and who rotates first when contact comes. The player who leaves a site early is the seam your split goes through.

This is the most time-expensive step done by hand. Prefire parses every demo and surfaces per-player positioning, opening-duel patterns, and utility tendencies with round numbers attached, so you verify reads instead of hunting for them.

Step 5

Find the vulnerabilities

Tendencies tell you what a team does; vulnerabilities tell you what beats them. Look hardest at the uncomfortable rounds — that is where practiced structure falls away and real habits show:

• Eco pressure. What do they do on low buys — stack a site, force with pistols toward one choke, save? Many teams run the exact same eco round every time. If you know it, an eco becomes a free round for you.
• After losing pistol. Does the follow-up round tilt them into a desperate force, or do they full-save into a disciplined round 3? This decides how you should spend your own anti-eco money.
• Late-round behavior. Under 30 seconds with no site taken — do they hit their pocket default site, or does the IGL freeze? Post-plant, do CTs re-take together or trickle in one by one?

Prefire flags these situational patterns — economy behavior, pistol aftermath, late-round tendencies — as vulnerabilities in the scouting brief, each with the sample size and rounds behind the claim so you can judge how much to trust it.

Step 6

Turn the read into an anti-strat and brief your team

A scouting doc nobody reads is a scouting doc that never existed. The output of all the work above should be one page, not ten: the veto plan, two or three reads per side, and one named counter for each read. “Their entry always goes B apps on Mirage → have our anchor jiggle-prefire apps at 0:40 and keep a flash for the retake” is a brief. Forty timestamped observations is a diary.

Walk the team through it once before the match, in fifteen minutes or less. Assign each read to the player it affects — the anchor needs the entry-path read, the AWPer needs the mid-control read, and nobody needs all of it. Then pick one or two counters to actually practice; the rest is awareness, not choreography.

This is the artifact Prefire is built around: the scouting brief — tendencies, vulnerabilities, and suggested counters per map, shareable with your whole roster. You can watch this exact workflow play out match by match in the Road to Pro series.

A realistic weekly cadence

If you only have two evenings: spend the first collecting demos and building the veto read (Steps 1–3), and the second on player habits and vulnerabilities for the one or two likely maps (Steps 4–5). Write the brief the night before the match while it is fresh, and keep it to a page. Scouting is a compounding habit — the notes you take this week are the head start you have next time the bracket throws the same team at you.

And if the manual version of this workflow is what is stopping you from doing it at all, that is exactly the gap Prefire exists to close: the demos go in, the brief comes out, and your prep time goes into practicing counters instead of scrubbing timelines.