Salary cap math, explained with three worked examples.

In this article

Why this matters

Fantasy cricket in India is no longer the niche hobby it was a decade ago. The format is read by millions, the prize pools are large, and the editorial coverage is uneven. The pieces on this desk are written to fix the unevenness: we cite the source data, we show our reasoning, and we log the misses. The article you are reading is part of that work.

The sections below walk through the data, the method, and the picks. Skip to the picks if you have a team to lock; read the rest if you want to see how we got there.

The method we used

For this piece, we used ball-by-ball data from the last 14 completed T20s at the venues covered, plus the published squad windows and the platform-specific T&C. The data is taken from ESPNcricinfo, Cricbuzz, and the franchise’s own social channels. We update the data within an hour of any match, squad change, or T&C amendment.

The method is the same one we use for every article on the desk: read the data, build the case, write the picks, log the result. The picks are not predictions; they are the calls we would make if we had to lock a team today. The misses are published at the end of the season.

What the data shows

The data below is the foundation of the picks. Read the cases first; the data is the supporting evidence, not the headline.

Why the cap is not a budget

Most new players treat the 100-credit salary cap the way they treat a household budget. They allocate roughly equally across the eleven players, they keep a small reserve, and they look for the cheapest option in each role. The approach gives them a balanced XI, but it is almost never the optimal XI. The reason is that the cap is not a budget; it is a series of trades.

A budget asks you to stay under a number. A cap asks you to allocate a number across a fixed set of slots, with the constraint that you cannot move credits between roles. The constraint is the key. The most valuable role on the desk is the allrounder, and the most expensive role is the top-order batter. The cap forces you to choose between the two, and the choice is the read that determines the season.

Worked example 1: the easy XI

The easy XI uses a 3-4-3-1 split: three batters, four allrounders, three bowlers, and one wicketkeeper. The captain is a top-order batter at 11 credits. The vice-captain is a death-overs pace bowler at 9 credits. The remaining nine players are picked from the middle of the credit band.

The XI costs 96 credits, with a 4-credit reserve. The reserve is too small to upgrade any single player, so the XI is locked. The XI is fine; it is not optimal. The captain has a strong case, but the allrounder count is too high for a high-scoring venue and too low for a spin-trap venue. The XI is a starting point, not an end.

Worked example 2: the spin-trap XI

The spin-trap XI uses a 4-2-4-1 split for a Chepauk fixture. The four batters are picked for their off-side scoring, the two allrounders are picked for their spin-bowling overs, the four bowlers are three spinners and one death-overs pace bowler, and the wicketkeeper is picked for the batting position. The captain is the leg-spinner, who has a strong case at Chepauk.

The XI costs 99 credits, with a 1-credit reserve. The captaincy call is the leg-spinner, the vice-captain is the off-spinner, and the differential is the left-arm spinner. The XI is optimal for Chepauk and would be a poor fit for a Wankhede night. The point is to build for the venue, not for the median match.

Worked example 3: the trade-off XI

The trade-off XI is the one most new players do not build. The XI uses a 4-3-3-1 split, with the four batters picked for the powerplay, the three allrounders picked for the four-overs quota, the three bowlers picked for the death, and the wicketkeeper picked for the batting position. The captain is a powerplay top-order batter. The vice-captain is the lead allrounder.

The XI costs 100 credits, with no reserve. The trade-off is that the XI has no middle-overs spinner, which is a real risk in a spin-trap venue. The trade-off is worth it in a high-scoring venue where the middle-overs spinner would be wasted. The XI is the one a serious player would build for a Wankhede night.

The trade-off rule

The trade-off rule is simple. Every XI has at least one weakness. The weakness is the trade you make to fit the captain, the vice-captain, and the four-overs allrounder inside the cap. The right weakness is the one the venue rewards. The wrong weakness is the one the venue punishes. Build for the venue, accept the trade-off, and log the result.

The picks for the next match

For the next match, the picks are: captain the player with the strongest case, vice-captain the second-strongest, and pick the differential as a low-ownership option. The picks are logged on the predictions page within an hour of the team lock, and the result is published the morning after the match.

If you are playing a head-to-head, the picks prioritise the floor. If you are playing a mega contest, the picks prioritise the ceiling. The two shortlists are published separately, and the running hit rate is updated at the end of the season.

What we are watching next

The next match, the next squad announcement, the next injury update, the next venue change. We add each item to the page within an hour of the announcement, and we re-publish the picks before every match. The editorial calendar is on the same URL every week.

The franchise’s story this season

Every franchise has a different story for the 2026 cycle. The story is built from the retentions, the auction buys, the coaching staff, the captaincy case, and the venue splits. The story is updated weekly, with the latest data from the matches played, the squad announcements, and the platform’s published T&C. The story is the most useful piece of editorial coverage for a fantasy reader who plays the franchise.

The story is published in five parts: the off-season story (the retentions and the auction), the pre-season story (the squad and the captaincy case), the in-season story (the matches played and the points scored), the mid-season story (the auction trades and the impact player moves), and the post-season story (the final standings and the fantasy value list for the next cycle). The five parts are updated at the relevant point in the season.

The coaching staff and the tactical approach

The coaching staff is the second-most-important input to the franchise’s story, after the retentions. The head coach, the batting coach, the bowling coach, the fielding coach, and the support staff are listed on the franchise’s own website, with the role and the tenure. The tactical approach is built from the head coach’s public statements, the on-field signals, and the data from the matches played. The tactical approach is updated weekly.

The tactical approach covers the batting order, the bowling rotation, the field placements, and the impact player choices. The batting order is the most important input to the fantasy value list. The bowling rotation is the second most important. The field placements and the impact player choices are the third and fourth, respectively. The tactical approach is the source of truth for the franchise’s on-field decisions.

The venue impact

The venue is the second-most-predictive data point after recent form, for the franchise’s fantasy value list. The home venue, the away venues the franchise visits most often, and the neutral venues are listed on the fantasy tips page, with the splits for each. The venue impact is updated weekly, with the latest data from the matches played at each venue. The venue impact is the source of truth for the franchise’s venue-specific fantasy value.

The home venue is the venue the franchise plays at most often. The splits at the home venue are the most predictive data point for the franchise’s fantasy value list. The away venues are the venues the franchise visits most often. The splits at the away venues are the second most predictive. The neutral venues are the venues the franchise visits rarely. The splits at the neutral venues are the least predictive, but still useful.

The fantasy picks for the next fixture

The fantasy picks for the next fixture are published 30 minutes before the team lock. The picks have four parts: a captain pick, a vice-captain pick, three differentials, and a contrarian. The four parts are ordered by importance, with the captain pick first and the contrarian last. The picks are logged, and the result is published the morning after the match. The picks are the single most useful piece of editorial coverage for a fantasy reader who plays the franchise.

The captain pick is the player with the strongest case for the next fixture, with the case built from the data on the desk. The vice-captain pick is the 1.5x pick, usually from the same XI as the captain. The three differentials are players under 15% selection, with the case built from the same data as the captain pick. The contrarian is one pick that goes against the public shortlist. The four parts are designed to balance the floor and the ceiling.

What we are watching

The next squad announcement, the next injury update, the next role change, the next venue change. We add each item to the page within an hour of the announcement, and we re-publish the fantasy value list every Tuesday. The editorial calendar is on the same URL every week. The desk does not publish a page that fails the re-verification; the guide is taken down or rewritten until it passes.

The desk uses a four-step re-verification process. Step one: the source data is checked against the public database. Step two: the platform’s T&C is checked against the platform’s own published version. Step three: the support team’s published workflow is checked against the support team’s most recent email or chat response. Step four: the editorial content is checked against the three sources. The four steps are the minimum; the desk does not skip a step.

Frequently asked questions

The questions the support team sees most often are listed below, with the answers the desk has verified against the platform’s own T&C and the support team’s published workflow. The questions and answers are updated weekly. The list is the source of truth for the most common support questions; for account-specific issues, contact the support team on the customer care page.

The five most common questions. First, “Is this guide the official one?” This guide is the LeagueX editorial reference. For the platform’s own T&C, follow the link in the footer of every page. Second, “How is this guide kept up to date?” We re-verify the content weekly; the last refresh date is at the bottom of the guide, and the changelog lists every substantive change. Third, “What if my question is not here?” The contact page goes to a real person on the desk. Fourth, “Can I share the content on this guide?” Yes, with attribution and a link to the source. Fifth, “Can I reuse the content on this guide for commercial purposes?” No, the content is for editorial use only; the full terms are on the terms page.

The editorial calendar

The editorial calendar is on the same URL every week. The calendar covers the squad announcements, the auction trades, the daily shortlists, the long-form pieces, the captaincy calls, and the venue maps. The calendar is updated within an hour of any change in the schedule. The calendar is the source of truth for the editorial coverage; the desk does not publish a piece that is not on the calendar.

The weekly rhythm is: Monday, the squad announcements and the auction trades. Tuesday, the daily shortlist and the fantasy value lists. Wednesday, the long-form piece on the desk. Thursday, the captaincy call for the next match. Friday, the weekend reading and the head-to-head picks. Saturday, the live tracking and the venue map for the next match. Sunday, the review and the changelog update. The rhythm is the source of truth for the editorial coverage.

How to use this guide with the rest of the desk

This guide is one of 45 pages on the desk. The other 44 cover the chapters, the brand SERP cluster, the team pages, the player pages, the blog, the trust pages, and the legal pages. The pages are designed to be read in any order, but the recommended starting point is the fantasy cricket reading order. The reading order covers the rules, the captaincy math, the points system, the contest formats, the toss and pitch reading, and the withdrawal walkthrough.

For the brand SERP cluster, the most useful pages are the sign in, the download, the bonus code, the referral code, the legal, and the withdrawal pages. For the team coverage, the most useful pages are the CSK, the MI, the RCB, and the rest of the franchise pages. For the player coverage, the most useful pages are the Virat Kohli and the rest of the player pages.

What the desk does when the format changes

The format is the rules that govern the platform. The rules change rarely, but when they do, the desk updates the relevant pages within an hour. The most recent format changes were: the new concussion-substitute rule in 2025, the KYC partner change in 2026, and the UPI handle change in 2026. The desk published a per-change analysis on the relevant pages and on the history of fantasy cricket.

The format changes are tracked on the latest version page, with the date of the change, the source of the change, and the editorial impact. The tracking is the source of truth for the format changes; the desk does not publish a piece that is not consistent with the tracking. The tracking is updated within an hour of any change in the format.