GPP Strategy and Summary for 2018 – Part I
The allure of the Guaranteed Prize Pool (GPP) contests is the hope that with a small investment, a fantasy owner will have the opportunity to win a huge prize worth many multiples of the original entry fee. However, all too often, the opposite tends to take place as players pour more and more of their precious bankrolls into these large contests and never see a big payday. Obviously, the main culprit for these losing players is simple bankroll management where too much is put at risk in ways that nearly guarantee losses over time. The other, much less obvious issue is in how a player crafts his lineups to begin with.
Each season, we collect data on the winning lineups from most of the large prize pool $3 GPP events all the way up to the winning lineups for the $555 GPP each week. Over the years, there has been much debate among various people within the industry about the construction of cash lineups versus those used for GPP events. While much of the debate has largely been settled since the early days when just a small handful of sites vied for attention within the industry, the perpetual question of lineup construction for GPP events still looms large.
If you’ve never considered the concept of ownership outside of the idea of chalk vs contrarian plays, this should be a column that helps you to recalibrate your process in terms of your overall roster builds from week to week, whether you are mass entering 150 lineups, or simply taking one or two shots at a higher dollar entry event. We are not here to say that there is a one size fits all approach to lineup construction, but in looking at it each year, we can fine tune the total range of ownership which gets us close to an optimal aggregate ownership as well as the individual ownership levels for each player that you can target. This won’t guarantee you success, but it will certainly help you in avoiding failure before the first golfer has teed off to start the week.
Sign up for an FGI account today to see the rest of this post.