I want to tell you something most operators won't say publicly: I operated during $280M in combined revenue growth across two companies, and I'm not certain how much of it I caused.
This matters. Not for false modesty. For honest accounting. The story operators tell about themselves (and that the market rewards them for telling) usually conflates "was present during growth" with "drove growth." Those are not the same thing.
At US Mobile, revenue went from $20M to $150M during my tenure. At Retailo, $80M to $230M. I ran operations, built GTM infrastructure, led fundraising, managed the board. I was not a passive observer. But I can't draw a straight line from anything I did to $130M in incremental revenue at US Mobile. The product got better. The market expanded. The founder's vision executed at scale. The team grew from dozens to hundreds. Any of those could be the explanatory variable. Probably all of them, interacting in ways that resist clean decomposition.
Here is what I think operators actually do that matters: we remove friction from growth that's already happening. We build scaffolding that lets the company run faster. We prevent the organizational failures that would slow things down or cause the company to implode under its own growth. That is genuinely valuable. It is not the same as being the source of the growth.
The CFO who makes the Excel model faster doesn't make the company more profitable. The COO who runs cleaner operations doesn't determine whether the product has market fit. The Chief of Staff who manages the board beautifully doesn't make investors believe in the category. There are founding-level decisions (what to build, who to sell it to, how to position it, when to raise) that determine the arc of a company. Operators implement that arc. They don't define it.
I think about this distinction often because the way operators present themselves obscures it. A LinkedIn profile that says "led company from $80M to $230M" implies causation. What actually happened is correlation with some contribution. The contribution matters. So does honesty about what it was.
This has practical implications. If you need someone to drive growth, you need a founder or a revenue leader, someone making decisions about what to build and how to sell it. If you need someone to build the infrastructure that lets growth scale without breaking, you need an operator. Adjacent but distinct roles. Confusing them leads to mismatched hires.
Operating during growth is genuinely exciting. The company is winning. You're in the rooms where important things happen. That environment creates a strong association between your presence and the company's success, even when the causal relationship is weak. It takes active effort to resist that association.
Where I can make specific claims: the fundraising process at Retailo, where I built the data room and managed investor diligence. The Riyadh operations, stood up from scratch. The board reporting infrastructure that gave seven directors consistent information through a critical period. These are outputs I can point to.
Where the honest answer is "I contributed to a great team executing well": almost everything else.
Operators create value. But the value is usually organizational, not financial. It shows up in what didn't break, what got built before it was needed, what decisions got made faster because a system existed. It's counterfactual, hard to measure, easy to overstate.
The operators I trust most can tell the difference. They say "here's what I built and why it mattered" instead of "I grew the company from X to Y." The resume signal is the same. The underlying honesty is not.