Tuesday, January 08, 2008

Hitting vs. Pitching Splits In Action

In the course of writing this blog, I talk a lot about "standard" or "typical" hitting/pitching splits. In a Rotisserie League with a $260 budget, these splits usually work out to each team spending $175 for hitters and $85 for pitchers.

However, while I was going through my rundown for last year's hitters and pitchers, I noticed something interesting:

Bid Limits by Tout, N.L. 2007
Tout
Hitter $
(per team)
Pitcher $
(per team)
Total $
Hitter %
Pitcher %
AP
$2168
($167)

$1170
($90)
$332865%
35%
Rotoman
$2173
($167)
$1103
($85)
$327666%
34%
LABR
$2326
($179)
$1046
($80)
$337269%
31%
Tout Wars
$2356
($181)
$1020
($78)
$337670%
30%
Sports
Weekly
$2103
($162)
$1043
($80)
$3146
67%
33%

The pricing wars might be over on a player-by-player basis. But there is a chasm between what the touts (AP, Rotoman, Sports Weekly) are recommending to spend versus what the tout leagues (LABR, Tout Wars) are actually spending.

Sports Weekly recommends that you spend $242 on your roster out of the $260 you have available, so they're disqualified from further consideration. As for the other four sources, there is still a huge difference.

The dollar amounts per team are listed to emphasize the difference. The $14 difference per team between Patton and Rotoman versus Tout Wars is staggering. Another way of looking at this is that Tout Wars' philosophy would have left you with $79 per team to spend on pitching, while Patton's philosophy told you to spend $93 on your pitching staff.

That's a huge philosophical difference in dollar allocation.

But it's also problematic if you're planning your own auction. Ideally, you want to distribute your pre-auction bids the way your league does. If your league spends $180 per team on offense and your bids only recommend spending $170 per team, you're going to fall $130 for your league ($10 per team x 13 teams). That doesn't sound like much, but it will influence who you wind up buying and how you ultimately do allocate your dollars.

I'll look at that in my next post.

No comments: