"Build" it yourself. You may start out with a junior or seasoned sysadmin. But given the right working set people start to shine.
From a commercial point of view a guru that started out as a seasoned admin in your company will nearly always be cheaper (in terms of salary), on the other hand you need to have a close look at him/her not to cause expense.
From a motivational point of view my own experience is that I was really motivated when I had my first job as a sysadmin, it started out with 1 server and I didn't even have a workstation. After about 10 months we had services running on 3 physical servers with about 20 virtualised instances (OpenVZ very lightweight) that were being used as service separation.
I wouldn't consider myself a guru (and everyone who considers him/herself a guru is to be taken with a grain of salt), but I'm pretty confident that I learned a lot more when I was on my own in that company in any given timeframe than when I am working in a team. Not because I don't like to work together but you somehow start to specialise on things because someone else is better at $topic.
Now I'm leading a team of 5 administrators (including me) and 1 developer. I consider getting a developer assigned to our team the largest success, providing the services isn't that much of an effort but having someone who enjoys developing more than administration is a major win as you can really start building larger toolchains.
So building a guru yourself may pay off. Not within a few months but in the mid to long-term. Everyone I know and consider a guru has started in harsh environments (either because working on their own, or by being assigned to tasks initially out of scope regarding their knowledge but was stilling fighting all the way thru).