I Watched Three Founders Bet Everything. Now I Can't Unsee How Most PMs Play It Safe.

The moment I realized I was thinking about risk all wrong

I was three weeks into Sonic Linker when our founder made a call that terrified me. We had zero revenue, maybe 15 interested prospects, and he wanted to spend most of our remaining runway building the core AI matching engine. Not a prototype. The actual thing.

My instinct was to push back. Build something smaller first. Validate more. Get some revenue, then invest in the hard infrastructure. That's what I learned in B-school. That's what every product framework tells you.

But he didn't hedge. He said if we couldn't solve the core problem really well, nothing else mattered. We either built something 10x better than manual LinkedIn outreach or we'd fail anyway. The risk wasn't spending the money. The risk was wasting time pretending we could succeed without it.

We shipped that core product in three months. It worked. That bet is why we exist.

What founders see that most PMs miss

Here's what changed for me after working directly with founders at Sonic Linker, and before that at Finvestfx and NJ Group.

Founders don't think about risk as something to minimize. They think about it as something to choose. Every decision is a bet, and the question isn't "how do I avoid risk" but "which risk gets me closest to finding out if this can work."

At Finvestfx, we were managing treasury operations for 20+ enterprise clients. I kept pushing to add features that would make the product more flexible, more customizable. Lower risk, right? Keep more clients happy.

Our founder kept saying no. He wanted to nail the core workflow for FX trades first. Make it so fast and reliable that finance teams couldn't live without it. He was willing to risk losing clients who wanted customization because he believed the real risk was being mediocre at everything.

He was right. Retention went up when we stopped trying to be everything. Clients stayed because we were the best at one thing, not because we were okay at ten things.

Most PMs I talk to treat risk like a bad thing that needs to be managed away. Founders treat it like information. Taking a risk and failing fast tells you something valuable. Playing it safe just delays finding out you're wrong.

The risks I started taking (and the ones I stopped)

This shift changed how I make product decisions.

I stopped trying to de-risk everything upfront. At Sonic Linker, I used to want three customer interviews, a competitive analysis, and a prototype before building anything. Now I ask: what's the cheapest way to find out if this matters?

Sometimes that's interviews. Sometimes it's just building a rough version and putting it in front of five users. The risk isn't building the wrong thing. The risk is spending three weeks preparing to build when you could have learned the same thing in three days by just doing it.

I started taking bigger bets on core value. When I was working with insurance advisors and IFAs at NJ Group, I spent weeks trying to figure out how to get all 60 of them to adopt a new product. I kept tweaking the pitch, adding features, trying to make it easier.

Then I stopped and asked: what if I just focused on the 10 who actually wanted this? What if I made it so good for them that they became the story that convinced the others? That's a risk. You're betting that depth matters more than breadth.

It worked. Those 10 became champions. The rest followed because they saw real results, not because I had a better slide deck.

I stopped hedging on product strategy. This is the big one. I used to build roadmaps that tried to satisfy everyone. A little for enterprise, a little for SMBs, a little for the loudest customer. That feels low-risk because no one gets upset.

But it's actually the highest risk move you can make. You end up building a product that no one loves. Founders taught me that you have to pick. You have to say "we're going all in on this segment, this use case, this problem." That feels risky because you might be wrong. But at least you'll find out.

What this actually looks like in practice

I'm not saying be reckless. I'm saying be intentional about which risks you take.

At Sonic Linker, we took a massive risk on the AI engine but we didn't take risks on pricing experiments or messaging. We kept that simple and predictable while we figured out the product.

At Finvestfx, we took a risk on focus (nail one workflow) but not on reliability. Enterprise clients need uptime. We didn't experiment with that.

The pattern is: take risks on the things that could make you win. Don't take risks on the things that could make you lose.

Most PMs get this backwards. They play it safe on product direction (the thing that matters) and take random risks on execution (the thing that kills you).

The real lesson

Working with founders didn't make me fearless. It made me way more honest about what I'm actually afraid of.

I used to be afraid of building the wrong feature. Now I'm more afraid of building something no one cares about deeply. I used to be afraid of upsetting a customer. Now I'm more afraid of being forgettable.

Founders bet everything because they have to. But the lesson isn't about the size of the bet. It's about knowing what you're betting on. Most product decisions fail because we're trying not to lose instead of trying to win. Once you see that, you can't unsee it.