I Only Bet Early When I Can Build the Proof
I've spent the better part of 14 years building companies in markets that most serious people hadn't taken seriously yet. Bitcoin mining infrastructure in 2017. Sovereign AI compute infrastructure today. That's not a coincidence, and it's not a contrarian impulse for its own sake. It reflects a belief I've held since my days in enterprise technology consulting at Infosys and Fusion Risk Management: conviction without evidence is just noise. The principle that has defined nearly every major decision I've made is this — I only bet early when I can build the proof myself.
When I discovered Bitcoin in 2012, I didn't see a speculative trade. I saw a monetary network with real infrastructure needs and almost no one treating it that way. But I didn't act immediately. I spent years developing an operator's understanding of the space before founding Blockware Solutions in 2017. By the time I went to market, I wasn't pitching a thesis. I was pitching a solution to a problem miners were already experiencing: fragmented hardware sourcing, unreliable hosting, and a total absence of institutional-grade service. The idea came first. The proof came second. And the company came third.
That sequencing matters more than most people realize. It's easy to read our story and see the milestones: $500 million in revenue, 400,000-plus ASIC machines deployed, a first-ever CME clearing relationship for a Bitcoin mining firm. But none of those happened because we had a compelling pitch deck. They happened because we built enough operational credibility early that the market had no choice but to pay attention. Our research reports reached over a million readers and were cited in Bloomberg, Forbes, and CoinDesk. That wasn't a PR strategy. It was the natural result of doing the work before claiming the expertise.
The clearest example of this principle in action was the Sale and Leaseback model I pioneered at Blockware. When we needed capital, I didn't want to dilute equity to get it. So I looked at the assets we already controlled, specifically mining rigs, and asked whether they could be treated as financial collateral the way traditional equipment is. That question came directly from my finance background. We structured a model that let us access capital without giving up ownership, and it worked. The idea was early. But we could execute it because we'd already built the infrastructure to make it credible.
Compute USA followed the same logic. I'd watched the AI compute market for years before moving. The pattern I kept seeing was familiar: enormous demand, fragmented supply, and an industry treating a financial infrastructure problem like a hardware sales problem. Enterprises needed more than GPUs. They needed structured financing, contractual reliability, and a partner with real balance sheet discipline. That's not a new insight in the abstract. But it's a very specific insight if you've spent a decade building exactly that kind of operation in a different but adjacent space. So when I founded Compute USA, we had $250 million in server revenue bookings and a signed 25 MW letter of intent before we went to strategic partners. The proof came before the ask. That's not luck. That's the principle running on repeat.
I think a lot about what separates durable companies from ones that thrive only in bull markets. The answer, almost every time, is whether the founders built real proof of value or borrowed credibility from a hot cycle. I've seen both play out in Bitcoin mining. The operators who built for durability, who made hard decisions about capital structure and hiring during the peaks, were the ones still standing and growing when the market thinned out. The ones who relied on the momentum of the moment weren't. I carry that lesson into every decision I make at Compute USA.
The principle doesn't make early bets less risky. It makes them more honest. If you genuinely understand a market well enough to build the proof before the market validates you, you're not guessing. You're operating. And operating is the only thing that actually builds something worth keeping. If you're curious how that thinking has shaped the way I approach infrastructure more broadly, my about page gets into the longer arc. But the core of it starts here: believe early, build first, then let the results do the talking.