Fantasy Cricket: How to Build Teams That Survive a Powerplay

Fantasy Cricket: How to Build Teams That Survive a Powerplay

A working mental model for fantasy cricket: role balance, captaincy logic, credit-cap math, and the small rules that decide who finishes a contest near the top.

The mental model most beginners skip

Fantasy cricket looks like a list of names. It is actually a sequence of constraint problems: a credit cap, a role requirement, a captaincy multiplier, and a powerplay scoring window. Most losing teams fail not because of bad players, but because they forgot one of these constraints existed at the moment they were finalising their XI.

On the COME desk we read fantasy through four lenses — balance, ceiling, captaincy, and conditions. The rest of this guide walks through each lens with examples rather than guarantees, because no honest fantasy guide can promise outcomes in a sport where a 30-second rain delay can swing a contest.

If you remember nothing else, remember this: a balanced XI beats a star XI in most contests, because points compound across roles. A star XI concentrates risk on three or four players; if one fails, the whole team fails. The COME desk treats balance as the single non-negotiable variable, and the rest of the guide explains how to maintain it under different contest conditions.

The second non-negotiable is honesty about conditions. No amount of analytics can save an XI that picked five seamers for a flat batting deck. We start every preview with a pitch read, because the pitch decides the contest before the captaincy even matters.

Role balance: the four-role shape that survives most contests

Every fantasy platform runs on four roles: batter, wicketkeeper, all-rounder, bowler. The exact distribution varies by contest type — some allow 1-3-4-3, others 2-3-3-3 — but the principle holds across formats.

The principle: spread your credit spend so that a single role failing does not collapse the team. A bowler-only collapse is recoverable if your batters and all-rounders are reasonably paid. A captain-only collapse is harder, which is why we treat the captain pick as a separate decision from the rest of the XI.

A reasonable starting shape for a small contest: 1 wicketkeeper, 3-4 batters, 2-3 all-rounders, 3-4 bowlers. Adjust for pitch: green seamers favour bowlers, flat decks favour batters, dry turning tracks favour spinners and all-rounders who bowl spin.

Avoid the temptation to fill your XI with five specialist batters on a green seamer. The role-balance math exists for a reason — it tells you how the platform expects the points to be distributed. If your shape disagrees with the platform’s expectations, you are swimming against the tide.

A practical rule: if your XI has fewer than two all-rounders who bowl, you are probably under-invested in the role that swings the most fantasy points in the middle overs.

Captaincy: the single biggest decision in any XI

Captain scores 2×. Vice-captain scores 1.5×. If your captain scores 80 and the rest of your XI averages 25, your team total is roughly 80×2 + 25×10 = 410. If your captain scores 30 and the rest averages 35, your team total is 30×2 + 35×10 = 410.

The COME desk uses a three-question captaincy test before every deadline: (1) Does this player have a high ceiling today — a path to 60+ points? (2) Does this player have a high floor — a path to 30+ even on a bad day? (3) How does this player compare on differential — how many other teams in my contest will captain them?

If you can answer yes to two of the three, captain. If you can only answer yes to differential, that is a vice-captain choice, not a captain choice. If you can only answer yes to ceiling, you need to weigh the upside against the contest size.

Differential captaincy works in large contests where the top 10% separate from the median. In small contests, ceiling captaincy usually wins. Match the captaincy logic to the contest size, not the other way around.

A common mistake: captaincy by reputation. A premium player with a 9.5 credit price feels safe to captain. But reputation lags form by 1-2 contests. The captaincy decision should be made on today’s pitch and today’s matchup, not on last season’s averages.

Ceiling vs floor: who scores on a bad day

A player with a high ceiling (think aggressive top-order batter on a flat deck) has a wide range of outcomes — 20 to 120 in the same conditions. A player with a high floor (think accurate spinner on a turning track) has a narrow range — 25 to 50.

In a small contest, you need ceiling players. In a large contest, you need a balance of ceiling and floor players so that a bad day does not eliminate you from the top 10%.

The mistake most beginners make is picking ceiling players everywhere. They end up with a team that wins big on good days and crashes on bad days. The COME desk recommends at least two floor players in any XI — typically one specialist bowler on a helpful pitch and one wicketkeeper who bats in the top 7.

Floor players are also your hedge against conditions changing mid-match. A spinner picked for a turning track who turns out to bowl on a flat deck will still score 30-40 from fielding and a few batting points. A ceiling batter picked for a flat deck who is suddenly batting on a green seamer may score under 10.

Credit cap math: when to spend, when to save

The credit cap forces a decision. If you spend 9 of 100 credits on three premium players, the remaining 8 players must average 10 credits each. That is achievable. If you spend 11 of 100, the remaining 8 must average 11.1 credits each — and you may not have 8 players worth 11.1.

A reasonable spend distribution: 9-10 credits on captain, 9 on vice-captain, 8-9 on the third premium, and 7-8 on the rest. Adjust for contest type — small contests tolerate more spread, large contests tolerate more concentration.

One anti-pattern: spending 11 credits on a player because they had one big innings last week. Credit prices lag form by 1-2 contests. The market is sticky; the smart captain uses that lag rather than paying premium for last week’s form.

Another anti-pattern: ignoring the value picks. A 7-credit all-rounder who averages 35 points is mathematically more valuable than a 9-credit specialist who averages 38 points, because the credit savings let you upgrade elsewhere. The COME desk tracks value picks in every preview.

Conditions: pitch, weather, toss, dew

Conditions are the multiplier on every other decision. A 9-credit batter on a flat deck is worth more than a 10-credit batter on a green seamer. A 7-credit spinner on a turning track can outscore an 8-credit seamer.

Pitch: read the surface colour, the grass cover, and the cracks. Spinners win on dry, cracked pitches. Seamers win on green pitches. Batters win on flat, true pitches. The match-day pitch report should drive at least 30% of your XI selection.

Weather: dew at night makes the second innings easier to bat on. Cloud cover assists swing bowling. Rain interruptions compress the contest and favour bowlers, because the DLS par scores tend to undervalue chasing teams.

Toss: a captain choosing to bowl on a green seamer has a strong case. A captain choosing to bat on a flat deck has a strong case. Anything in between is a coin flip and should not drive your fantasy picks. Adjust your XI based on whether the chasing or defending side will bat first, not based on who wins the toss.

A useful pre-match checklist: (1) Is the pitch green, dry, or flat? (2) Will there be dew? (3) Is the toss likely to influence the decision? (4) What does the confirmed XI look like? Run these four before you open the player list.

How to review a contest you lost

The most underrated fantasy skill is reviewing a contest you lost. Most players quit after a bad day and never learn from it. The COME desk treats every contest — win or lose — as a learning artefact.

Three questions to ask after every contest: (1) Where did my captain score vs my expectation? (2) Did my role balance hold up — was one role disproportionately responsible for the loss? (3) Did my conditions read hold — would I make the same XI on the same pitch tomorrow?

If you can answer all three honestly, you have learned something. If you blame the platform, the toss, or your captain’s form without looking at your own decisions, you will keep losing.

The COME desk publishes weekly review notes for major contests. Read them — they are designed to be examples of how to ask these questions about your own teams. A useful pattern: keep a notebook (or notes file) with three columns — captain pick, role balance, conditions read — and fill it in before and after every contest.