BATTERY IQ
THE PITCH-CALLING GAME · V0.2
● PLAYABLE · OFFLINE
READ THE HITTER. OWN THE COUNT. EXECUTE THE PLAN.

Call the pitch. Live with the outcome.

Play through baseball situations, choose your pitch and target, then see what happens. Work a single at-bat or call every pitch in a complete game—then study the strategy behind your decisions.

PLAY

01 / The count

Select any of the twelve legal counts

BALLS × STRIKES

02 / The hitter

Lineup spot is a starting assumption, not a scouting report

Edit actual batter tendencies

03 / Game situation

Walks, contact and execution risks shift by context

Available pitches (choose at least one)
Pitch-specific execution confidence

04 / Pitch calling board

Compare available pitches and targets

LIVE MODEL
TOP MODEL CALL
—
—
—UTILITY / 100

The scores and outcome probabilities are from an illustrative coaching model, not measured MLB probabilities, medical advice, or individualized player projections. Higher is a relative utility score within this model—not chance of success.

05 / Your selected call

Experiment with a different zone location

Target from catcher’s view
Pitch & target
—
—
Chase targets
Illustrative next-pitch outcome mix
—Swinging strike, all pitches
—Ball outcome, all pitches
—Hard contact if in play

06 / Pitch sequencing & tunneling

The previous pitch changes the next pitch's intent

RELEASEDECISIONPLATEConcept illustration — not tracked flight data

Good tunneling means comparable early trajectories before later separation. Different eye levels can disrupt timing, but excessive repetition or poor command can undo the plan. The drawing is conceptual, not a ball-flight model.

Scenario Reps / Think like the battery

A decision drill with context, feedback, and multiple defensible answers

0 reps completed
ON THE MOUND

Make the call

The 12-count field guide

Objectives change with ball-strike leverage, command and hitter tendencies

Click any count to analyze it in the lab
FOUNDATION 01

Pitch tunneling

Two pitches may look similar during the early flight that informs the hitter's swing decision, yet reach different final locations or arrive with different timing. Shared release/early paths and late separation can create deception, but pitch-to-pitch execution matters.

Example: a four-seam fastball at the top of the zone and a changeup that begins on a similar line before finishing lower. Whether they truly tunnel depends on real release, movement and trajectory data.
FOUNDATION 02

Change eye level

Use up–down location variation to force recalibration. A high fastball may pair with a lower breaking or offspeed pitch. The highest target is not always a strike, and a chase pitch is not always justified.

Teaching question: Did your last pitch make the hitter anticipate the same visual lane? If so, can your next pitch change the height without losing the strike zone when needed?
FOUNDATION 03

Count leverage

A ball on 3–1 can concede a walk, whereas 0–2 provides more room for a competitive chase pitch. Two-strike fouls extend the at-bat; they are not strikeouts. Early counts still carry contact risk.

Training question: How likely can this pitcher execute this target? A deceptive pitch that cannot be thrown competitively may be a poor 3–2 choice.
FOUNDATION 04

Pitch to the hitter, not the lineup card

Lineup spot offers a scouting prior only. In one lineup the ninth batter may have elite contact; in another the leadoff hitter may have middle-of-the-order power. Editable chase, discipline, contact and power ratings should override generalized roles.

Training question: What is the batter hunting? What has this hitter shown today? What is your best-executed pitch—not merely your hardest one?
FOUNDATION 05

Same-side and opposite-side matchups

Some pitch shapes and movement directions play differently against right- and left-handed hitters. Matchup rules are not universal: pitch shape, command, release, hitter strengths and individualized splits must govern.

Teaching question: Which pitch moves away from this batter's barrel, and can the pitcher locate it without leaving it over the plate?
FOUNDATION 06

Sequence without becoming predictable

Repeated pitches can be useful when executed well, but repeated speed–location combinations may become easier to anticipate. The tool gives a modest illustrative benefit to meaningful vertical contrast and useful pitch-pair changes.

Teaching question: What did the hitter see on the last two pitches? What story does the next pitch tell?
New game mode: At-bat and full-game outcomes, pitch execution misses, hits, runner movement, simulated team offense, and fatigue are original synthetic game mechanics. Displayed probabilities and decision scores are not MLB-calibrated or a substitute for scouting data. The catcher chooses each pitch and target; chance determines the realized result.

What the probabilities mean

This is a working instructional simulation, not a validated prediction system. The five outcomes are mutually exclusive and sum to 100% for a specific candidate:

  1. Called strike
  2. Swinging strike
  3. Foul ball
  4. Ball
  5. Ball put in play

The display also shows a separate conditional risk: estimated hard contact given that the ball is put in play. This is not a sixth outcome and must not be added to the five-category total.

Inputs are assumed: target-specific zone probability, model swing likelihood, pitch whiff tendency, hitter traits, command and sequencing bonuses. The app scores the candidates using an adjustable conceptual utility formula, not measured expected runs. Use scores comparatively, never as a real-world success rate.

Known limitations: no pitcher's real tracking data, no batter scouting records, no velocity/spin/movement calibration, no umpire zone, no true pitch trajectory, no validated probabilistic training set. The simulation is not a substitute for coaching judgment.

How to improve statistical validity

To publish calibrated outcome probabilities, import pitch-by-pitch data, separate training from validation samples, account for count, pitch type, trajectory, movement, handedness, hitter, game situation and execution, then report sample size, uncertainty and model reliability. Do not infer a real hitter's ability solely from batting order.

For true tunneling metrics, use flight-coordinate data to estimate release, decision-point and plate separation. The illustration in this demo does not calculate those distances.

Primary references

Future development track

Planned areas—not capabilities claimed for this prototype

Real Statcast-calibrated probabilitiesCustom roster + hitter scouting notebookPitcher-specific shape / command mapsValidated tunnel geometryCoach-authored scenario collectionsClassroom practice + assessmentsPitcher/catcher shared game plansHistorical plate appearance replay