Skip to content
Fast Company Executive Board

The Fast Company Executive Board is a private, fee-based network of influential leaders, experts, executives, and entrepreneurs who share their insights with our audience.

For startups, fewer bets are better

Focus on a single bold bet and minimize risk distractions.

[Photo: Getty Images]

Profile photo of Neel Somani

Founder · Eclipse Labs

When I first started my project on the Terra blockchain, I chose it for its rapid growth. What I didn’t account for was the risk that its value fell to $0.

People asked me if I was surprised. The reality is that if a founder is going to build a project like that, they shouldn’t hedge against failure. The project’s purpose was to support the Terra ecosystem, and that was the big bet the project was making. My advice is that whenever you build something new, ask yourself, “What is the big bet I’m making?”

The best projects limit themselves to one big bet. So, let’s talk about my Terra project, which might have worked if Terra hadn’t stopped trading at its intended value. But the real challenge was that the project had too many big bets to succeed.

What I’ve learned is simple: a startup should make one big bet and hedge the rest.

MAKE AS FEW BETS AS POSSIBLE

Founders like to rethink everything from first principles. Sometimes that’s good, but a lot of the time, it’s a dangerous bias.

If your company exists to prove one thing, make as few bets as possible. That’s the lesson I took from Terra, and I still use that reasoning when I think about what investments are reasonable and what projects I want to build.

A startup should absolutely be willing to make one uncomfortable, non-consensus bet. But once that bet is chosen, be careful about adding more. You don’t need to be unconventionally weird about how the company works, the tools it uses, or how every process gets done. That’s not always intelligence. Sometimes it’s just adding noise.

WHEN YOU HEDGE IT IS NOT ABOUT BEING RIGHT

Airlines hedge jet fuel, producers hedge output, and power plants lock in spark spreads or dark spreads. If you’re not deep in commodities, a spark spread is the gap between what a plant earns from selling power and what it pays for fuel. Power plants lock themselves into a spark spread because they don’t want unrelated price moves to swamp the economics of the business.

Southwest is the cleanest airline example. The company has said its fuel hedging program saved an estimated $3.5 billion from 1998 to the summer of 2008, and its 2008 SEC filing said hedges contributed almost $1.3 billion in cash savings that year.

That’s the point. The airline still had to run the planes. It just didn’t want the whole business getting swung around by jet fuel.

And this isn’t just a historical point. In 2026, Virgin Australia said fuel volatility was raising costs while it remained heavily hedged. Same logic: run the airline, don’t let fuel prices become the whole story.

There’s always a cost associated with reducing risk, but it’s not always worth it. The question is whether the thing you are protecting is your main bet or if it is an unrelated risk layered on top. That’s the difference between reducing risk and limiting upside. If it’s your main bet, keep it. If it’s not your main bet, ask why you are carrying it at all.

CHOOSE CONSENSUS WHEN IT DOESN’T MATTER

The non-commodities version of hedging is usually operational. It means not turning every tool, vendor, or internal process into a second thesis.

Use standard software like Salesforce for your CRM, and use payroll software that everyone else uses, like Rippling. Don’t invent internal systems unless that’s actually your business. If the company’s thesis is about product insight, your payroll system should not also become a thesis.

This is where first-principles thinking becomes dangerous. High-level strategic decisions, especially as a startup, are not a group exercise. They are best reasoned through in isolation. But once the main bet is set, the rest of the company should get simpler. The company thesis should be the bet, not every internal tool or process.

BE BOLD ON THE MAIN BET

The practical advice isn’t complicated. Ask what the company is trying to prove, and that reveals the main bet. Then look at the rest of the business and ask what strengthens that bet and what has nothing to do with it.

If it has nothing to do with it, make it boring.

Use standard tools, use default processes, and don’t fight convention just to feel original. Save your non-consensus energy for the one place where it matters. You want the company to win or lose on the thing it actually exists to test. Be bold on the main bet and hedge the rest.

Neel Somani is the founder of Eclipse Labs.