Before Billingz, my job was to make large operations work. Multi-region teams, multi-language playbooks, governance across time zones. The skills that earn you trust at that altitude, process design, escalation, formal alignment, structured communication, are real skills. They keep companies from coming apart at the seams. They are also, almost without exception, exactly the wrong skills for an early-stage product.
Founders coming from large operating roles tend to underestimate this. They assume the rigour they brought to scale will translate down. It doesn't translate down; it actively suffocates the thing it's trying to help. Knowing this in advance saves you months.
What scale rewards
Scale rewards predictability. If you have two thousand people executing a playbook, the playbook needs to be unambiguous, and changes to it need to be deliberate, communicated, and documented. The operating muscle you build is one of orchestration: getting many parts to move together, slowly, in the same direction.
Process is what you reach for when you can't reach the work directly. In a startup, you can.
That muscle is built around an assumption, that you, as the operator, will not personally do the work. You'll design the system that does the work, and your job is to keep that system healthy. It's the right reflex when there are too many surfaces for one person to touch.
What early-stage punishes
In a startup, you can touch every surface. There are five of them, not five thousand. The right move is to do the work, see what happens, change the work, see what happens again. Process is what you reach for when you can't reach the work directly. In an early product, you can, and the operating reflex of designing a system before doing the thing slows the loop that matters most.
The other reflex worth dropping is consensus. At scale, decisions need buy-in because the cost of misalignment is enormous. In a startup, the cost of moving slowly is much higher than the cost of moving in the wrong direction for two weeks. Consensus is a luxury that gets paid for in months you don't have.
What survives the transition
Not everything from scale is dead weight. Strategic patience survives, the willingness to build something that won't pay off for a year. So does the discipline of writing things down, the tolerance for uncomfortable conversations, and the operator's instinct for spotting which problem is actually load-bearing. Those translate. The orchestration reflex doesn't.
Forgetting what you know is harder than learning what you don't. But until you do it, the product never gets to feel like a product. It feels like a small enterprise, and small enterprises don't ship fast enough to find out whether they should exist.