What the founder-to-employee transition is actually like
I built a startup called eCommHub. We automated dropshipping for ecommerce merchants, built a team, raised money, signed real customers. We went through leadership changes, a merger, and eventually an acquisition. The full startup lifecycle, compressed into a few intense years.
After the acquisition closed and the products were handed off, I joined Shopify in 2016. When you’re a founder, the company becomes your identity for years, and stepping into a big company after that is a strange experience. It uses completely different muscles, and I don’t think founders talk about what the transition is actually like enough. Back then it was still pretty unusual. Today it’s common, and companies actively seek out ex-founders for good reason. But at the time, it was just a strange adjustment. You go from running your own thing to being one of thousands, and nobody really prepares you for what that feels like.
Seeing what good looks like
The thing that hit me first at Shopify was seeing what products look like past the MVP stage, at real scale, with real discipline behind them. As a startup founder, you’re building fast and shipping on instinct. You develop a feel for what users want and you move quickly, and that instinct is real. But you don’t have a benchmark for what “good” looks like when you have millions of users and thousands of employees. You’re pattern-matching from other startups and whatever you picked up along the way, which is fine until you realize nobody around you has seen it done at scale either.
Working inside a world-class company gave me that benchmark. The metric-driven decision making, the code quality standards, the deliberateness in how products get built and shipped. It’s like a talented home cook who goes to work in a Michelin kitchen. You can already cook. You have good instincts about flavor and timing. But watching a team that operates at that level of precision, seeing how they think about consistency and quality and the thousand small decisions that separate good from great, that sharpens you in ways that cooking at home never would. I had raw product intuition when I got to Shopify. What I built there was the discipline and craft to back it up.
I shipped at scale for the first time. Bulk shipping, mobile features, carrier integrations. I worked with engineers and designers who were world-class at what they do. And I got to see how decisions get made when the stakes are real, not through a case study, but by being in the room.
Influence vs authority
What caught me off guard was the people dynamics. When you’re a CEO, people listen to you by default. You don’t even realize how much of your effectiveness comes from positional authority until it’s gone. It’s like being Hercules without the glow. You walk in with all the same skills and experience, but nobody defers to you, nobody clears the path, and the things that used to happen because you said so now require convincing six people across three teams.
At a big company, you lead through influence. You have to earn buy-in from people who don’t report to you, who have their own priorities and their own roadmaps, who need to be convinced that your thing matters more than the other five things competing for their attention. That’s a completely different skill from anything I’d done as a founder, and I didn’t have it when I got there.
One of the things I didn’t expect was how much Shopify invested in developing that skill. Management training, leadership coaching, public speaking development. They had personal leadership coaches, the same ones the exec team used, available to people across the company. As a startup founder, you learn leadership by surviving. Nobody teaches you how to run a meeting or give feedback or communicate a strategy clearly, you just figure it out under pressure and hope it works. At Shopify, I got to watch great leaders operate up close, and I had access to coaching and training that would have cost a fortune on my own. The craft isn’t just product craft, it’s leadership craft too, and having a world-class company invest in yours is something most founders never get. And the skill you come out with, influence without positional authority, follows you everywhere regardless of your title.
The scope problem
Nobody warns you about the scope change. As a founder, your field of agency is the entire company. If sales is slow, that’s your problem. If the onboarding flow is confusing or the deploy pipeline is flaky, those are your problems too. You develop this instinct to see the whole system and fix whatever’s broken, regardless of whose “area” it is.
At a big company, that instinct doesn’t go away. You see things that are broken across team boundaries, connections between products that nobody’s making, inefficiencies that feel obvious to you. But you can’t just fix them. They’re on another team’s roadmap, or they’re not on anyone’s roadmap, or fixing them requires navigating three layers of stakeholders. And the pace is different. Something that would have taken a day at your startup takes a quarter at a big company, because it touches five teams and needs alignment and review and scheduling. You’re operating at founder speed inside a system that moves deliberately, and that friction is frustrating until you learn to work with it instead of against it. Some of that deliberateness is bureaucracy, but a lot of it is earned wisdom about what happens when you ship fast to millions of people without thinking it through.
But that same instinct, the ability to think across the whole business, to see systems instead of silos, is exactly what makes ex-founders valuable inside large organizations. You pattern-match across the whole thing because that’s how you survived.
What you unlearn
A few months into Shopify, my manager had to tell me I didn’t have to work evenings and weekends. I didn’t even realize I was doing it. I was so used to working around the clock that it had just become my default, a habit from a different life that nobody was asking me to keep. That one was easy to fix once someone pointed it out.
The bigger adjustment was learning how directness lands in a different environment. As a founder, you talk about the work directly. Something looks off in a design review, you say so. That’s not political, it’s just how you move fast. At Shopify, I was the same way, calling things out in design meetings, giving candid feedback on the work itself, nothing personal. And my feedback was often spot on. But I had to learn that directness that felt normal to me could feel abrupt to people who didn’t have that same context. I wasn’t wrong about the work, but I had to learn how to read the room and tailor how I delivered it. That was actually one of the things I used Shopify’s leadership coaching for, and it was one of the most useful transformations I made there.
That was the pattern with most of my founder instincts. Some were just bad habits, like the overwork. But most were calibrated for a specific environment, and when I changed environments they didn’t automatically recalibrate with me. The intensity, the directness, the bias toward just doing the thing myself instead of building consensus first. All of that served me well at a startup. At Shopify, I had to figure out which instincts were still strengths and which ones I was just running on muscle memory.
The resources shock
I wasn’t prepared for what happens when you actually have resources. At a startup, you’re building with duct tape and willpower. You’re the PM, the designer, the QA team, the customer support backup, and occasionally the person fixing the deploy pipeline at midnight. You get used to that. It becomes your identity, the scrappy founder who can do anything.
Then you walk into a company that has a dedicated data team, a design team, a research team, QA engineers, infrastructure that just works. Shopify even had dedicated UX copywriters, people whose entire job was making sure the words in the product were clear and consistent. That level of specialization blew my mind. These people were incredible at what they did in ways I never could have been while wearing six hats. And your first instinct is to keep doing everything yourself, because that’s what you know. Learning to actually use those resources, to let the data team run the analysis instead of eyeballing it, to let design explore options instead of sketching something on a napkin and shipping it, that’s its own skill and it took me longer than I expected to develop it. But once you do, it completely changes what you think is possible. The scope of what you can build when you have real support behind you is an order of magnitude bigger than what you can do alone, and that realization stays with you. It permanently changes how you think about building teams.
What companies get wrong
Tobi Lütke talked about this on the Founders Podcast earlier this year. He called it “founder day care,” where companies acquire founders and push them to the outskirts instead of putting them where their instincts can be useful. His point was blunt: founders are the people willing to tell you what’s actually broken, and most companies would rather not hear it. He noticed it happening at Shopify during the pandemic and changed it, creating a dedicated channel with acquired founders and regularly asking them for help. That resonated with me. Founders inside big companies have a perspective that’s hard to get any other way. They’ve been the person responsible for everything. They’ve felt what it’s like when the company’s survival depends on the next decision. That doesn’t go away when you take a job. It shows up as impatience with process for the sake of process, as a bias toward action, as an allergy to meetings that could have been decisions. Most organizations don’t know what to do with that energy.
If you’re a founder considering the jump
You’re not settling. But be deliberate about it. Pick a company where you’ll be in the room when decisions get made, not on the outskirts building something nobody asked for. The things you’ll learn, leading through influence, operating at scale, seeing what disciplined excellence actually looks like, those stay with you. They make you better at everything you do after. And over time, you start to appreciate that many of the hardest problems in technology aren’t startup problems at all. They’re coordination problems, infrastructure problems, and systems problems that only emerge at scale.
Know that it will feel strange at first. Your instincts are calibrated for a different environment and it takes time to recalibrate. The authority is gone, the scope is narrower, and the pace feels slow. That’s the adjustment, not a sign that you made the wrong choice. The skill you’re there to develop, influence without authority, is the one that scales with you for the rest of your career.
If you’re hiring founders
The companies that get the most out of ex-founders tend to do the same thing: give them real problems and space to move. Their instinct is to operate across the whole business, to see systems instead of silos. That instinct is exactly what makes them valuable, but it only works if they have room to use it. The companies that don’t figure that out end up with frustrated people who either flatten out or leave, and then someone says “founders don’t do well in big companies” when the real problem was the environment.
Tobi’s hiring filter is simple: “Have you started a company before?” Not because founders are inherently better employees, but because the experience of building something from nothing leaves you with pattern recognition that’s hard to get any other way. Specialists are often extraordinary at their craft in ways founders never will be. The question is whether the company can use both kinds of strengths.
This post started as a draft in 2018. I revisited and expanded it in 2026 after hearing Tobi discuss founder cocooning on the Founders Podcast, which put words to something I’d felt but couldn’t articulate at the time.