Welcome everyone to our Lineup Optimizer strategy article for 5/15/22. This is a new article I will be doing daily that discusses the stacks and players the optimizer is popping for today’s slate. We are very blessed to have out optimizer powered by SaberSim — and you can get access by clicking HERE. Let’s get into it…
Overview
We have been on fire with this article, and I’m once again going to be building for smaller-field single entry tournaments on Sunday.
Top Stacks
We have no Coors Field on this DraftKings slate, so we don’t need to worry about that game. We also have pretty good weather across the board. I went ahead and locked in Justin Verlander + Tarik Skubal at pitcher — let’s see the results…
No surprise, Houston is dominating the attention against Patrick Corbin. Corbin has been abysmal in 2022, it seems he’s completely lost his fastball and continues to walk more batters. Overall, the Astros have the highest team total today and I do think they will be the clear highest-owned stack. Surprisingly, second and third we have two pretty bad teams in the Tigers and Pirates. I actually think there is some value to this Pirates stack against Hunter Greene, who has underwhelmed after a hot start for the Reds. He’s giving up big numbers to both sides of the plate — mainly due to his fastball. He’s lost some velo on it from the start of the season, and he’s still throwing it over 50% of the time despite allowing a .600 wOBA with it. Pittsburgh is not a great fastball hitting team because they aren’t a great hitting team in general — but this is making me re-think my strategy. I think that Skubal is a clear value on DK, but full-stacking the Pirates could allow a double-spend up at pitcher. Either way, I think Houston and Pittsburgh are my clear top two.
Conclusion
In conclusion, I want either a full stack of Pittsburgh or Houston with a mini-stack of the other team built around. I’m leaning towards Verly + Skubal at pitcher, but may end up double-spending on someone like Brandon Woodruff or Alek Manoah as my SP2.
Written by Ben Hossler (Follow @BenHossler on Twitter)
