Not Pace, But Workload: The New Math of Buying Fast Bowlers in the Franchise Market

Not Pace, But Workload: The New Math of Buying Fast Bowlers in the Franchise Market

Last November I was sitting in a franchise trial. A young right-arm pacer hurled his very first ball at 148.6 km/h. The scout beside me immediately ticked a box in his notebook. On my laptop screen, however, a different number was glowing—the bowler's total deliveries that week were 317, of which 114 came across three consecutive matches, and the average speed of his final overs had dropped to 139.2 km/h. Nobody in that trial room saw the decline. Eight days later, the bowler was out for six weeks with a hamstring injury. The franchise that had been considering signing him is now chasing the scouting report—wondering why it didn't contain a single line about workload.

In today's franchise market, pace is an auction weapon. But pace never arrives alone; it comes with delivery counts, rest intervals, and the quiet arithmetic of the body.

The transfer window is now a rumour market in cricket much as it is in football. Before every auction, each franchise gets stuck on the same question: whom do we buy? The answer usually comes from a speed-gun reading, sometimes from a viral yorker clip. But the more matches I watch, the more I understand—what determines the value of a fast bowler is not his top speed, but how much his body can carry. When I joined The Daily Star's cricket desk in 2026, strike rate and bowling average were everything. Now, twenty years on, the camera angle of data has shifted. We now measure speed decay per over, rest hours between matches, and which overs produced a bowler's fastest deliveries.

I keep my model simple. Three layers. First layer, load: total weekly deliveries, minimum rest between matches, and spell length. Second layer, decay: average speed in the first spell versus the last spell, and the pace drop after the 16th over. Third layer, risk: injury record over the previous two seasons and return time. Together these three layers produce an index—conditional workload risk. The curious thing is that this index is the least-consulted item at the auction table.

Let me take a few cases, because I dislike claims without numbers. Just before the 2026 T20 World Cup, Shaheen Afridi's knee injury changed not only Pakistan's plans but the whole market's arithmetic. Continuous bowling across a franchise season, followed by a packed national schedule—for the body, that is not a request, it is a command. On the other hand, Jasprit Bumrah's back stress fracture showed us that rest is not a cost, it is an investment. I traced the ball back until the highlight forgot where it began—and almost every time, a cluster of consecutive matches was sitting behind it.

I have one specific example in hand. During a 2026 franchise season, I compared the data of three pacers. Each averaged between 138 and 141 km/h—meaning on the speed gun they were nearly identical. But the first played an average of 1.3 matches a week, the second 2.0, the third 2.4. By the end of the season, it was the third who got injured, and his speed in the last five matches had fallen to 133 km/h. At auction, all three were priced almost the same. But the actual return was three different things. This is my core point: pace sets the market, workload sets the future.

I've noticed a second thing. A fast bowler's decay is not linear. First spell 142, second spell 141, third spell suddenly 134—that jump is the body's signal. Those who look only at average speed miss that jump. I look at the last two balls of every spell separately, because that is where the truth hides. Last season I traced ball-by-ball data from 64 T20 matches and found that bowlers whose final-spell speed fell more than 7 percent below their first spell had roughly double the injury probability over the next six months.

Now to a cricket-specific pressure metric. In football, PPDA measures pressing; in cricket, my equivalent is the proportion of deliveries bowled in the death overs. If a pacer bowls 12 of his 24 balls between the 17th and 20th overs, his per-ball risk is much higher—because in the death overs a bowler must give full effort, and the batter is in attacking mode. Over the last two seasons I've seen that franchises keeping more than two reliable pacers for the death overs had significantly lower injury rates among their primary pacers.

Let me simplify the market math. Suppose a franchise is paying 2 crore for a pacer. The speed gun says he is a 145 km/h bowler. But his workload index says that last season he averaged 22 balls per match, with rest intervals of only four days. Now do the math—if he plays 14 matches in a season, that is 308 deliveries, a large share of them in the death overs. My data says a bowler of this profile misses at least two matches mid-season with roughly 38 percent probability. That means in a 2 crore contract, you are actually getting 12.4 matches' worth for your 2 crore, not 14. Is that a small difference? In a franchise's play-off race, one match is everything.

So I say: a transfer rumour is a data point until it becomes a person. When you see 38 percent risk on a workload index, it is a number. But when you see that bowler sitting outside the field, frustrated in front of his family, it is no longer a number. Building a bridge between the two is my job.

I do not worship the dashboard; I ask who is missing from it. There is a big gap in workload data—the load away from the match. Travel, time-zone shifts, being away from family, being locked inside a bio-bubble. In May 2026, when I was analysing 50 spectator-less Bundesliga matches, I saw that the home win rate had fallen from 43.3 percent to 32 percent, and pressing intensity had dropped 7 percent. Cricket has a similar quiet effect. Sometimes I cross-check data from empty-stadium franchise matches and ask—did the bowler's speed drop because his body was tired, or because there was no crowd energy? My answer is often: both, and our model usually captures neither.

Now to the part where I stand against my own model. Because this is the biggest trap. There is a relationship between workload and injury—but a relationship is not causation. I've learned from years of watching matches that sometimes a pace drop is not a sign of fatigue but the result of planning. A smart pacer deliberately mixes slower balls, cutters, wide yorkers in the death overs—speed drops, but wickets rise. If I label him 'risky' just from a pace drop, I make a fool of myself.

The second trap is subtler. Franchises now have workload data, but they often make the wrong decision—they don't rest players, they buy bowlers who play less. Less play means less data, less data means less accountability. This is a hidden shame: we treat the lazy bowler as safe and the hard-working bowler as risky. The truth is the opposite. A bowler who fights in every match has limits in his body, but his mentality is built; a bowler who plays occasionally has a fresh body, but his match-fitness is a question mark. Nobody asks this question at the auction table.

I want to add another thing that usually gets missed—bowling action. When measuring load, I look at action type alongside pace and delivery count. Those whose action involves more spinal rotation have a different load tolerance. This information usually sits in the physio's file, not in the scout's notebook. Yet in the franchise market, this should be the first question.

What I've said so far does not claim that workload data is a prediction machine. I am saying it is a filter. Before the auction, look at the speed-gun number, then sift it through the workload index. The bowler who is good at both—give him the most money. The bowler who is good only at pace—price him excluding the risk. That is a healthy market.

For me, this whole exercise is like a public verification loop. I see a number, trace it, put it on social media, fans ask questions, I re-code the model. In June 2026, for that France versus Argentina 4-3 match, I built a live model for Kylian Mbappé—0.78 xG, 5 shots, 4 progressive carries, and a 37 km/h sprint. After the match, French and Argentine fans debated what was decisive—Mbappé's speed or Argentina's high line? I ran a poll, 12,000 votes came in, and then I added 'line height' and 'recovery runs' to the model. The model did not change because of the speed; it changed because you voted. The same principle applies to cricket. The pace number is not mine alone; it belongs to that fan too, who stays up watching matches and asks—why is this bowler bowling the last over?

In the Bangladesh context, this question is even more urgent. Our pace foundation is small, our load is large. When the BPL and national-team schedules overlap, a fast bowler's weekly delivery count matches a franchise league's—yet the physio, trainer, and rest planning are not comparable. I am not saying anyone is to blame. I am saying the number should be looked at before the decision is made. As part of the diaspora, I watch both markets—England's county contracts and Asia's franchise contracts. Both make the same mistake: they pay for fresh bodies, not for management.

Let me leave the final question for the future. If, in the next auction, franchises start buying bowlers by the workload index instead of the speed gun, where will the market balance settle? My guess—the bowler who burns a little less but carries more matches will rise in price. The bowler who hits 150 km/h and folds his knee two matches later will fall. That is not bad for the market. But one caution: workload data is also a model, and outside every model someone is left behind. That someone is usually the bowler who fought the most and complained the least. Every number has a first touch, and every first touch has a witness. If we forget that witness, data becomes a mere dashboard—and cricket becomes cold arithmetic. When the first ball of next season is bowled, keep a question beside the speed gun: how much can this body carry? The answer will be on the table, if we are willing to look.