I Watched a Founder Bet the Company on a Three-Week Sprint. It Rewired How I Think About Risk.

The moment I realized I was thinking about risk backwards

Three months into Sonic Linker, we were building an AI-powered linking platform. We had a roadmap. We had designs. We'd already started building the core workflow.

Then our founder listened to 12 customer calls in two days and said: "We're solving the wrong problem. We need to reposition completely."

Half the code we'd written was now irrelevant. I remember thinking this was incredibly risky. We were a founding team. Runway mattered. Pivoting meant losing weeks of work.

But here's what I missed: the *real* risk wasn't changing direction. The real risk was spending three more months building something nobody wanted.

That's the first thing working with founders taught me. Risk isn't about how much you've already invested. It's about how long you're willing to keep investing in the wrong thing.

What corporate risk management actually optimizes for

Before Sonic Linker, I worked at Finvestfx, managing 20+ enterprise clients in forex and treasury management. Good company. Smart people. But the way we thought about risk was completely different.

At Finvestfx, risk meant: "Will this upset existing clients? Will this take longer than one quarter? Do we have three backup plans?"

Those aren't bad questions. But they optimize for *not losing what you already have*. That works when you have 50 enterprise clients and predictable revenue. It doesn't work when you're trying to find product-market fit with 200 users and a three-month runway.

I remember proposing a change to our onboarding flow at Finvestfx. It would have cut setup time in half. But it required retraining the customer success team and updating documentation. So we scheduled it for "next quarter" and then pushed it again.

At Sonic Linker, that same decision would have taken 48 hours. Not because we were reckless. Because the cost of moving slowly was *higher* than the cost of breaking something.

Working with founders didn't make me more risk-tolerant. It made me better at identifying what the actual risk was.

The one question that changed how I evaluate every decision

Here's the question I ask now, every time I'm weighing a decision:

What happens if I'm wrong, and what happens if I'm slow?

At Finvestfx, being slow was usually fine. Being wrong could hurt retention or create support tickets. So we moved carefully.

At Sonic Linker, being slow meant someone else would ship first, or we'd run out of money, or users would churn before we fixed the problem. Being wrong meant we'd learn something and fix it in the next sprint.

Completely different risk profile. Same job title.

I saw this play out in our analytics setup. I wanted to implement a full event tracking system with proper taxonomy, session replay, the works. It would have taken two weeks and required eng time we didn't have.

Our founder said: "Ship Mixpanel with five core events today. We'll add more next week if we need them."

I thought that was sloppy. Turns out, three of those five events were enough to answer 80% of our questions for the next two months. We added the rest later, when it actually mattered.

That's not "moving fast and breaking things." That's understanding that incomplete data *now* is better than perfect data *never*.

Why this matters if you're not at a startup

I'm not saying every company should operate like a seed-stage startup. That would be stupid.

But I do think most PMs overestimate the risk of being wrong and underestimate the risk of being slow.

At NJ Group, I coached 60 insurance advisors and IFAs on product adoption. These were people who'd been doing things the same way for 10-15 years. Change was genuinely risky for them.

But you know what was riskier? Watching younger, digital-first competitors take their clients because they were too slow to adopt new tools.

The advisors who succeeded weren't the ones who waited until everything was perfect. They were the ones who ran small experiments, learned fast, and adjusted.

Same principle. Different context.

What I do differently now

I don't treat every decision like it's life or death. But I also don't treat every decision like it's reversible.

I ask: What's the cost of moving now versus moving later? What's the cost of being wrong versus being slow?

If being slow is expensive and being wrong is cheap, I move fast. If being wrong is expensive and being slow is cheap, I move carefully.

At Sonic Linker, most decisions fell into the first category. At Finvestfx, most fell into the second. Neither approach is "right." But confusing the two will kill your product.

The best founders I've worked with don't take big risks because they're fearless. They take big risks because they've done the math, and the alternative is worse.