Ranji's Middle Order and India A: Why the Conversion Rate of Domestic Run-Makers Into Capped Players Stalls

I built a small table over the past few weeks. The purpose was singular — to see how many batsmen who are consistently scoring runs in the Ranji Trophy actually make it to the senior team through the India A route. The table needed to capture age, domestic average, number of India A matches, and the year the cap was awarded. As soon as the columns began filling up, the numbers started arguing with my assumption.

This is not a new question. After every season, the debate resurfaces about why a batsman scoring 900-1000 runs in Ranji doesn't get a chance. But where the discussion stops is where my work begins. The question is not 'why doesn't he get a chance' — the question is how much has the ratio of domestic performance to cap changed over the past decade, and does that change indicate a lack of talent or a selection-structure bottleneck.

The methodology had to be settled first. Ranji's numbers come from elite matches, but their quality is uneven — the bowling edge differs between the Plate Group and the Elite Group, pitches vary state by state, and every season has some matches where both teams cross 600 in the first innings. So simply adding up runs would have been meaningless. I applied three filters: first, only Elite Group matches; second, batsmen who played at least eight innings in a season; third, their selection status in India A or India A-level tours. This third filter was the most important, because the direct door to a cap no longer comes through Ranji — it comes through India A.

The table showed something different at first glance. The number of batsmen maintaining a 50+ average for three consecutive seasons in Ranji has increased, but the proportion of those reaching a cap has not. Production went up, conversion did not. This is where my initial assumption — that domestic cricket lacks talent — took a hit. Talent is not scarce; the pathway is narrow.

To understand this, I looked at the India A calendar. In recent years, India A tours and the domestic season have increasingly overlapped. On one side, the Ranji knockout; on the other, the India A winter tour — both fall in the same time window. The result is that a batsman scoring runs in Ranji is simply not available for India A, and a batsman in India A is out of the Ranji knockout. The selectors never have both sets of numbers on the same table. This is not a question of talent, it is a question of calendar structure.

I have a small example. In 2026, when I was sitting in the Kochi mini-auction, my board had priced an uncapped leg-spinner at ₹5.1 crore, and the room paid ₹9.2 crore. At the time, I thought the market buys narrative, not value. But after looking at this domestic batting data, I think the same logic applies to the selection system. Selectors are also a kind of market — they bet on the story that is heard the loudest, not the one with the strongest numbers. And the Ranji run-machine often sits silently.

Now the part where I had to be cautious about my own table. Correlation and causation are different things. It is true that batsmen who pass through India A have a higher cap-conversion rate. But it is also true that players selected for India A have already passed through a filter — their age, their fitness record, their IPL performance. That is, India A selection is not an independent variable, but part of the same selection process whose outcome we are measuring. If I were to say 'playing India A guarantees a cap', I would be making the same mistake I criticise in others.

There is another overlooked angle — IPL workload. A batsman who scores 900+ runs in Ranji is often also picked in the IPL, and his season gets split into two halves — runs in one format, bench in another. When selectors evaluate, they have both the long-format Ranji data and the short-format IPL data, but no common scale to compare them. This is the same problem I felt during Euro 2026, when building PPDA maps by hand from broadcast footage made me realise that two different metrics from the same match can tell two different stories. Italy's tournament PPDA was around 8.9, and the Wembley final finished 1-1 and was decided on penalties — but the real difference was in midfield control, not the scoreline. In the same way, Ranji average and IPL strike rate are two different languages, and the selector has to translate them into one sentence.

One more thing needs to be added here. In 2026, at sixteen, I coded all 120 death-over deliveries of the IPL final played in Hyderabad — Mumbai Indians defended 129/8 to beat Rising Pune Supergiant by one run — into a table of yorker length and boundary probability. That table taught me that one load-bearing number can change the whole story. What is the load-bearing number in this Ranji data? In my view, it is the India A and Ranji knockout overlap. If that window did not clash, perhaps the conversion rate would be different. This is a hypothesis that can be verified — selectors just need to look at both calendars together.

I should also acknowledge that I have access to some people in franchises and the board. This access has a cost — I cannot make certain claims that would harm that access. So everything I have written here is based on public data and public calendars, not on any insider information. This is the only way this analysis can remain honest.

The forward-looking question is how the India A calendar is built over the next two seasons. If the board separates the window between the Ranji knockout and India A tours, we should see a change in the conversion rate over the next few years — provided there is no major shock to the talent supply. If no change appears, it means the problem is not in the calendar but in the thinking behind selection. And if the problem is in the thinking, then the question arises of what we call a batsman who scores runs in Ranji — a 'domestic star'? That label is perhaps his biggest deception, because it places him outside the national team's door, and we are made to believe the door is closed.

I sat down to build a table; the table sat me down instead. If the very scale of a fully deserving player's merit is incomplete, why should the blame for selection fall on the player. Next time a Ranji batsman scores 1000 runs and still doesn't find a place in Team India, don't ask what is lacking in him. Ask whether we even have a scale to measure him.