The biggest single upgrade a fantasy contestant can make is to switch from brand-name picking to form-weighted picking. The desk's heuristic is short: weight the last five innings at 70%, last season at 20%, career-aggregate at 10%. Apply those weights to every player you consider, then choose the higher-weighted pick even if the lower-weighted name is more famous.
The same logic applies to bowlers — last-five economy rate, last-five wickets-per-over, last-five dot-ball percentage. Form decays in T20 cricket faster than in longer formats, so what a bowler did two seasons ago is much less predictive than what he did in the last month.
Form has a horizon. A batter who's misfired in five straight innings is in bad form for a reason — either a technical issue or a match-up the schedule keeps repeating. Don't pick him until the signal flips. A bowler who's had one great match is not yet in form; one good match plus four ordinary ones is four-out-of-five ordinary.

The captain pick has three valid styles, depending on contest format:
Don't blend the three models. A captain pick that tries to be "anchor + differential" usually underperforms both. Pick one model, apply it cleanly, and stick with the call.
Vice-captain is the same model at 1.5x. Pair the captain and vice-captain so they aren't from the same role (one bat, one bowl, one all-rounder). That way if the conditions shift and one role underperforms, the other has a chance to compensate.
A differential pick is owned by less than 20% of contestants in your contest. The leverage is real: if the differential scores big, you jump the field. If the differential fails, you lose ground to a player owned by everyone else.
Use differentials in three situations only:
Skip differentials in small leagues, head-to-heads, and any contest where the entry is meaningful relative to your weekly budget. The variance is the wrong direction for those formats.
The standard "differential" mistake is picking a name because he's not famous. Low ownership is not the same as differential value — the desk only counts the second.

The template. Batters can include the wicket-keeper if he bats top-six. Bowlers can include all-rounders if they bowl four overs. The template breaks only with reason.
Three all-rounders in the line-up is the leverage that small-budget XIs need to compete with big-budget name XIs. Three all-rounders with role-fit > two batters without it.
Three-bowler templates work. Pace-death (death overs), spinner (middle overs, Chepauk-style venues), powerplay wicket-taker (any format). The "five-bowler XI" usually loses on batting depth.
Match-up reads turn a small data signal into a captain pick. The desk reads match-ups by:

Wankhede is a flat, fast, high-scoring surface that rewards top-order batters with ceiling. Chepauk turns square from the tenth over and rewards spinners. Eden Gardens shifts character across the tournament. Narendra Modi Stadium (Ahmedabad) is batting-friendly and brutal on bowlers.
Beyond the surface, dew factors into the second innings. After 8 PM at most venues, the side batting second has a ~55% win rate — that's a meaningful number when you put it next to a contest entry's prize structure.
Wind, rain, and humidity are the variables that flip predictions mid-match. Watch the outfield under the first ten minutes of play. Watch the ball behaviour in the second innings. Watch the curator's face during drinks.
The fantasy tips everyone writes about — captain choices, role-balance templates, match-up reads — are useful only if you can afford to play through 14 match-weeks. The bankroll discipline protects your ability to participate over the season.
The desk's rule: never commit more than 5% of your weekly budget to a single match-day's contests. If your weekly budget is ₹1,000, the maximum across all contests on a single match-day is ₹50. If you hit ₹50 and want to enter more, walk away. Tomorrow's contest is still there.
Multi-entry is fine — three to five line-ups is a sensible upper bound for a single match-day. Anything beyond that is fun, not discipline. The arithmetic reward comes from playing tomorrow's contest, not from chasing last week's losses.
Set a deposit cap in the app's responsible-play settings. Verify your state permits real-money play (see the legality brief). Pause immediately if you feel the urge to chase losses. Real-money fantasy is for adults only.

Read the official announcement at the toss. Most teams confirm 11 of 11 before the official coin flip. The names that surprise (an Impact Player, a returning player, an overseas change) are usually the late info that decides captain picks.
Curator comment + ground reports + your own observation from the warm-up. The pre-match report is a guide, not a verdict.
Check the local weather feed for the venue. After 8 PM at most venues, dew arrives. Rain-shortened matches reset the captain logic.
Three batters, three all-rounders, three bowlers, one wicket-keeper — at minimum. Adjust only with a reason. Don't "balance" a line-up with a wrong captain pick.
The captain pick is the last decision. Don't override it for late information. Lock, submit, walk away from the screen.
Brand recognition is not a signal. Form, match-up, venue and role-fit are signals. Pick by signals, not brand.
A losing streak is a sign of variance, not a sign to play harder. Pause, reset, walk away until the urge to chase is gone.
The captain slot depends on who plays. Re-pick captain after the toss — once, cleanly, with no fiddling afterward.
Bonus code, referral code and contest XI are three different decisions. Don't conflate them. The bonus is a decision; the XI is a decision; keep them separate.
The points system changes. Re-read it. Many contests turn on a milestone rule most readers skip on first scan.
A single match-week is a small sample. Spread the budget across multiple weeks, set a deposit cap, and protect the season-long ability to play.
Open the squad lane, the points reference, and the contest-type explainer together. The three readings build on each other, and applying all three will produce a better XI than any single article on its own.