CapFriendly

» see capfriendly.com as it lived, on the wayback machine

~ the goodbye ~

by the time i would have looked at capfriendly, it was already an internal washington capitals tool. i was never going to look at it. hockey is not a turkish sport, and the nhl salary cap database category is a specific canadian internet sub-genre. still, the death shape here is worth noting because it is different from every other grave i have written.

the davis brothers, joined by designer dominik zrim, launched capfriendly in may 2015 as a direct successor to [[capgeek]]. they picked up the capgeek template almost directly and added their own contract-modeling layer. they merged with hockeyscap in 2016 and by 2020 capfriendly was the default nhl contract-database source that capgeek had been.

on 9 june 2024 the washington capitals announced they were buying capfriendly. this was unusual on multiple levels. an nhl team had never bought a fan-facing contract database before. the announcement said the site would stay live through the 2024 nhl entry draft and the beginning of free agency, then be sunset. that happened on 10 july 2024. every other team in the league lost access to the tool it had been informally treating as league infrastructure.

~ the chronicle ~

~ how it landed ~

capfriendly launched into an obvious gap. capgeek had shut down in january 2015 for founder-health reasons and the nhl was in the middle of a rising salary-cap era where every trade required a cap-math calculator. puckpedia and hockeyscap were both trying to fill the same gap, but capfriendly moved fastest on adding tools that fans and teams both wanted. the armchair-gm trade simulator was the killer feature: fans could construct hypothetical trades that were cap-compliant, and journalists then used the same tool for reporting scenarios.

~ the decline ~

the tension in capfriendly's business model was that its own audience was two very different groups. one was hockey fans who wanted a public contract database. the other was nhl teams themselves, who used the site as internal infrastructure while wishing the public had less visibility into contract structures. this second group had leverage. the eventual acquisition by a single team was the resolution of that tension, and not in the fans' favor.

~ what it became ~

capfriendly is now a private washington capitals tool with no public interface and no api access for the rest of the league. puckpedia became the default replacement for public consumption, and other teams have reportedly built their own internal cap tools rather than depend on a competitor's asset. the acquisition-and-kill pattern here was closer to a talent grab than a product death, but the effect on the public database category was identical.

@}-->--

              )
             (_)
            .-'-.
            |   |
            |   |
            |   |
            |   |
          __|   |__   .-.
       .-'  |   |  `-:   :
      :     `---'     :-'
       `-._       _.-'
           '""""""

« previous  ·  random  ·  next »