I should be honest about what this article is and isn't. It's not a growth playbook. Two companies is not a statistically significant sample. What it is: the specific things I built inside two fast-growing companies, what I think mattered, and where I'm genuinely uncertain.
I joined US Mobile at about $20M in revenue. When I left, it was $150M. I joined Retailo at $80M. When I left, $230M with operations across three GCC markets and a $60M fundraise. I am not claiming I caused those numbers. The products got better, the markets expanded, the founders' visions executed at scale. What I can tell you is what I built and why I believe it mattered.
The common thread across both companies was the same: fast-growing organizations drowning in their own momentum. Smart people moving fast in loosely coordinated directions. The founder stretched across everything. The product being built while the GTM is being invented while operations run on spreadsheets and group chats.
My job was to build scaffolding that let everything else go faster. It always started in the same place: information architecture. In a fast-growing company, the most valuable thing you can create is shared situational awareness. Not more data. These companies had plenty of data scattered across sixteen platforms with nobody owning it. I found where the important information lived and built systems to surface it to the people who needed it. It sounds administrative, but information architecture is strategy in disguise.
Next came decision infrastructure. Growing companies make hundreds of decisions a week and document none of them. Three months later, nobody remembers why something was built a certain way. The team relitigates settled questions constantly. A simple decision log (what, by whom, when, why) sounds bureaucratic. It saves an enormous amount of time and prevents organizational confusion from compounding.
Then the operating cadence. Weekly team meetings, monthly business reviews, quarterly planning. Not because process is good in the abstract, but because without a predictable rhythm, companies default to crisis management. When everything is urgent, nothing is strategic.
At Retailo, I also ran a $60M raise while the business operated across Saudi Arabia, Pakistan, and the UAE. Fundraising from the operator side is mostly a data room problem and a narrative problem. The company that can show clean metrics, tight unit economics, and a coherent growth thesis in a well-organized data room closes faster and at better terms.
But here is the part I find most interesting, and it's rarely discussed in operator content: none of this works if the founder doesn't trust you enough to let you build it. Before touching any of these systems, I start by understanding what the founder worries about and where they feel unsupported. That conversation tells me where to begin and how fast I can move. The scaffolding is a systems problem. The permission to build it is a relationship problem. The relationship problem is harder.
What makes these patterns transferable across industries is that they're not industry-specific. Every fast-growing company has the same organizational growing pains in different surface forms. In a US telecom, the information problem is a dozen Slack channels and a CRM nobody updates. In a GCC B2B commerce company, it's WhatsApp chains between ops leads and a finance function running on weekly Excel exports. The solution is the same. The implementation looks different.
The $0-to-$100M journey is mostly a people problem with a systems solution. The systems are the easy part.