What actually happens when you try this
When you try to build an actual bowling attack instead of just listing bowlers, two things hit you quickly.
First, people get emotional. The guy who used to open every match suddenly hears, “You’re first change today because we need your cutters on this pitch.” He thinks it’s a demotion. You can literally see shoulders drop. That’s when you realise captaincy is half strategy, half HR.
I remember one game on a slow red‑soil strip where our only quick insisted on bowling three overs head‑down at the new ball. It looked great for Instagram, less great for the scoreboard. The ball stopped doing anything, the batters adjusted, and by over 10 he was cooked. No lift, no reverse, nothing. We basically played the rest of the innings without our strike bowler. The wicket belonged to our left‑arm spinner, who came on late and suddenly made it look like a different match. Classic Indian story: we treated pace like a status symbol, not a tool.
Second, you notice how often you used to waste overs. Once you think in roles, you catch yourself not burning your best spinner in the 7th over just “because he’s ready”. Instead, you ask: who bowls best when the ball is 15 overs old and grips more? A lot of modern T20 analysis of India’s campaigns talks about how they handled pace and spin in shorter, targeted spells, saving their best for key phases. Try that in club cricket and you realise how many overs you were throwing away earlier just out of habit.
There’s a pattern the generic “captaincy tips” articles miss: in Indian conditions, your attack isn’t just pace vs spin. It’s also “new ball guys vs scuff‑ball guys.” One bowler becomes 2x better once the ball is rough and reversing even slightly, or once the seam grips the surface. Another is only useful up top. If you don’t know which is which in your team, you’re guessing every time you toss the ball.
What surprised me most was how much easier field setting becomes once the attack is built right. Instead of nine tiny field changes for every mood swing, you start setting fields in packages: this is our “new ball attacking” field, this is our “spin choke” field, this is our “death defence with one attacking catcher” field. A lot of field‑setting guides actually recommend exactly that: match fields to roles, not random vibes. At our level, we just took longer to learn it.
You’ll still mess it up. You will over‑bowl your pet bowler, under‑use the ugly but effective guy, bring spin too late once, pace too late another time. The difference is that once you frame your attack as a combination of roles instead of friends, your mistakes at least come from thinking, not autopilot.
The advice everyone gives vs what actually works
“Always take three fast bowlers and two spinners.” This is the default WhatsApp strategy. It sounds balanced. It’s also lazy. That ratio evolved from watching Test and ODI teams with specific resources. Your college pitch and bowlers are not that. On some Indian strips, two seamers who can swing early and bowl cutters later plus three spinners is ideal. On a green, damp morning, three seamers and one frontline spinner might be better. My opinion: start from roles, then back into numbers.
“Pick your best bowlers, roles will sort themselves.” That’s how you end up with four guys who all want to bowl the same length at the same phase. Modern teams explicitly build attacks with diversity in mind—different angles, speeds, and spin types—to ask multiple questions. If your “best bowlers” all live in one skill set, your attack has a ceiling no pep talk can break.
“Always open with your fastest bowler.” That’s the IPL hangover talking. Sometimes your quickest guy is actually your best first‑change option: he hits the deck harder when the ball is slightly older, or he’s wild with the brand‑new ball. Analysts describe how India’s pace cavalry evolved by using different quicks in different roles, not just shoving them all at the start. If your medium‑fast seamer can hit a better new‑ball length, let him start. Ego doesn’t get you wickets. Match‑ups do.
“Spinners only after 10 overs.” That’s how you waste conditions. Recent tactics even at pro level show spinners bowling inside the powerplay to break rhythm and exploit sticky surfaces. On many Indian club pitches, the ball grips from over two. If your off‑spinner or left‑arm orthodox can keep control, you’re throwing away advantages by waiting “because TV teams do that.” Use your eyes, not habits.
My honest stance: the moment you start treating bowlers as roles and not status badges, half the generic advice around you will start sounding like background static.
The practical part what to actually do
Audit your current attack on paper. Not by names, by roles. List your bowlers and ask: new ball? Middle overs control? Wicket‑taker? Death? Who bowls best with a slightly older ball? Who controls? Be brutal. If two players fill exactly the same box, ask if both should play or if one becomes backup.
Build one default template for your home pitch. Think of it as “our standard XI for our ground”. Maybe it’s two seamers and three spinners. Maybe it’s three seamers and two spinners. Base it on what usually happens when you play there, not on one freak match. Data at higher levels literally shows how India changed from spin‑heavy at home to more pace‑heavy abroad by matching attacks to conditions. You’re doing the same, just on a smaller, more chaotic stage.
Plan overs in blocks, not as a never‑ending line. Before the game, sketch something like: 1–4: seamers; 5–10: one seamer + one spinner; 11–20: both main spinners; 21–30: mix depending on situation; 30–40: best seamer plus best spinner; final overs: your most trusted death pair. That’s exactly how tactical breakdowns describe modern attacks using pace and spin in short, aggressive spells. You’ll still adjust, but at least you’re reacting from a base plan.
Talk to your bowlers about roles before toss, not after you’ve gone for 60. Tell someone, “You’re first change, your job is squeeze and bowl cutters,” or “You’re our middle‑overs wicket‑taker, you will get attacking fields for four overs.” Fast bowlers often talk about captains like Virat being “bowlers’ captains” because they backed roles and let them attack in clear phases. You don’t need Virat’s brand to steal his method.
Use part‑timers on purpose, not as apology. That one batter‑bowler who can sneak 4–5 overs of decent medium pace or off‑spin is your plug when a main bowler has a bad day. Tactical threads online keep pointing out how modern captains use all‑rounders to ease load and keep main bowlers fresh for key phases. Plan those overs. Don’t dump them randomly because someone complained about not bowling.
Finally, learn from one match a week, not from 20. After each game, ask: which phase did we lose? New ball, middle, or death? Did we have the wrong bowler for that phase? Adjust the template. Even elite sides tweak their attack profiles after tours when data shows pace or spin under‑ or over‑performing. You can do a low‑budget version with a notebook and honesty.
Questions people actually ask
How many fast bowlers and spinners should I pick on Indian pitches?
There’s no magic ratio, but a balanced template of two to three seamers and two to three spinners works for most Indian conditions. On dry, turning tracks, you might tilt to one fewer seamer and one extra spinner, while on greener or overcast days you can add a seamer. Think roles: new ball, middle overs control, wicket‑takers, death specialists.
Should I always open with pace in India?
Not always. While most teams still start with pace, many modern sides use spin in powerplays when conditions favour it, especially in T20s. If the pitch grips or the ball is not swinging, an accurate spinner with a new ball can be harder to attack than an aimless medium pacer. Your decision should come from warm‑ups and first over, not tradition.
How do I pair pace and spin in the middle overs?
Use them as a team. One common pattern is one attacking spinner with slip and close fielders at one end, and a controlling seamer or another spinner tying down the other side. Data analysis of recent series shows successful sides squeezing run‑rates in the middle by pairing spin with disciplined seamers rather than rotating randomly. Your goal is to create pressure from both ends so wickets come.
1,437 words
← Previous part
How to Build a Complete Bowling Attack as a Captain (Indian Pitches)
Next part →
How to Build a Complete Bowling Attack as a Captain (Indian Pitches) — Part 3
Written by
CricketCore Editorial
Cricket Coach & Content Writer
Arjun is a former age-group cricketer turned coach who writes CricketCore's technical guides. Every article is reviewed for technical accuracy before publishing.
You Might Also Like
More Coaching Guides
Best Cricket Shoes for Indian Club Cricket (2026 Buyer's Guide)
The wrong cricket shoes cause stress fractures, slipped landings, and twisted ankles. Here's how to buy right for Indian conditions.
How to Build a Club Cricket Batting Order That Wins Matches (2026)
Most club teams pick batting orders by ego. Here's how to pick one by role — and add 30 runs to your average total.
Cricket Fielding Drills That Actually Win Matches (Club Cricket 2026)
Most club teams lose 25-30 runs a match in the field. These seven drills fix it inside a month.