The Operator's Edge: How Business Experience Shapes What I Ship

15/12

Strategy, P&L ownership, and stakeholder management aren't just corporate skills — they're product superpowers.

Operators who learn to build don't just ship features—they ship businesses, because every product decision is already a strategy call.

Before I ever touched a line of code, I spent years deep in corporate strategy, operations, and running business units. I've owned P&Ls, gone through M&A processes, managed cross-functional teams, reported to C-suites and boards. None of that was technical. All of it made me a better builder. And I think that's the part most people miss.

So let me put it this way. Here's what operators understand that most first-time builders don't: every product is a business model in disguise. When I scope a new project, I'm not just thinking about features — I'm thinking about unit economics, customer acquisition costs, retention mechanics, margin structure. That lens? It eliminates a huge number of bad ideas before they consume any build time. I deduct, deduct, deduct — and what's left is what's actually worth shipping.

Number one — stakeholder management. I honed that through years of multi-functional alignment, and it turns out to be remarkably similar to user research. In both cases, you're trying to understand what people actually need versus what they say they want. You're reading between the lines, identifying unstated constraints, finding solutions that satisfy competing priorities. Same muscle, different context.

Number two — P&L ownership taught me ruthless prioritisation. When every dollar and every hour has an opportunity cost, you learn to cut scope aggressively and ship the version that delivers 80% of the value with 20% of the complexity. That discipline is exactly what product development demands — especially when the tools make it tempting to build everything at once. I'm very disciplined on this because, for my projects, I'm doing it on my own.

Number three — and I don't want to beat around the bush here — the tech world sometimes draws a hard line between "business people" and "builders." From my POV, that line is artificial, and increasingly irrelevant. The best products come from people who understand both the problem space and the solution space. Operators who learn to build — or who find tools that let them build — have an edge that's hard to replicate.

So yeah, that's a little bit about why I think the operator background matters. It's not a detour. It's the foundation.