Someone has to take the first step to solve the chicken and egg problem. If there are jobs requiring Haskell, it might get more users.
It is quite difficult to get a first Haskell job though, because they mostly require production Haskell experience, so there's your chicken and egg problem.
I'm not sure what your current level is, but I can give some general advice for people that happen upon this:
---
Haskellers are generally expected to understand most of the typeclassopedia (https://wiki.haskell.org/Typeclassopedia), don't worry about learning it all in one go. I had to read this page many times before I grokked most of it.
---
Avoid tutorials that overuse analogies. A Monad only adds one operation to Applicative:
class Monad m where
(>>=) :: m a -> (a -> m b) -> m b
---
It's important to be really good at using Monads that support multiple effects, to create little DSLs. If I want a component of my program to support throwing errors, creating a log, and reading an environment, (all purely), I'd use something like this:
type MyDSL
= ReaderT Environment
(WriterT [String]
(Except ErrorType))
Where I work we use free monads instead of monad transformers, but that's just an implementation detail, it's used the same as a transformer stack.
---
Create a cool project, Haskell people like languages. When I was interviewing I showed off a tiny lisp-like language implemented in Haskell (https://github.com/414owen/phage). This was my first non-trivial Haskell project so don't judge it too harshly.
---
Read Haskell Weekly (https://haskellweekly.news/newsletter.html). It's a great source of ideas and knowledge.
---
A lot of Haskell shops use, or are migrating towards using, nix (https://nixos.org/).
---
Apply! The Haskell market seems to favor the interviewee. In the end, I had more than one offer, even for my first Haskell job.
Good luck!
It's the role of applause (and in your case, downvotes). The crowd throws cheap adulation at individuals who act against their own interests.
Planning for that far down the road is the least of your worries. And any plans you make along those lines are not likely to be very accurate anyway. You're much better off optimizing for the near to mid term. Based on the hosting costs described by the OP they are already reaping a tangible value here.
So given the upside to paying people to using Haskell (they get to learn it for life, many join + grow the community, they enjoy working for your company more), I think it's worth that kind of harm to a corporation.
I'll keep trying to sap corporate resources into Haskell I take with me for life at least :)