What happens when a founder suddenly has a boss

There is no single day when you notice it. It's more a collection of small moments: You have an opinion on a personnel decision, draft it carefully — and realize as you hit send that you've just written a recommendation, not an instruction.

For ten years, I was the final authority. Who gets hired, how teams are structured, what money is spent on — in the end, I made the call. Today, I get to say a lot and propose a lot on all these questions. I no longer decide them alone. That is the most honest sentence I can write about recent times, and it has two sides, both of which are true.

The Matrix: Local People, Global Motions

The structure I work in today is a classic matrix. Locally, I lead my team members — with everything that comes with it: development, accountability, proximity. And globally, I lead the motions, meaning how we approach customers in specific markets and segments.

On paper, that sounds clear. In practice, it means that virtually every major decision takes two paths: the functional one and the organizational one. You're right — and you still have to convince three people who each have their own equally legitimate perspective.

In your own company, you decide. In a group, you convince. Both get you to the goal, but the second takes longer and initially feels like a loss of control.

The Tedious Part: Speed

I'm not going to sugarcoat it. The part that costs me the most energy is speed. What used to be an afternoon decision is now a proposal, an alignment round, a presentation, a follow-up. You explain more, you justify more, and part of the work is simply internal lobbying — winning over people in other time zones so that something obvious in the Swiss market makes it into global planning.

That is rarely bad intent, it's physics: The larger an organization, the more context needs to be conveyed before a decision can be made. Still, there are days when I experience this as friction, not process. Anyone coming from ten years of bootstrapping has a visceral sense of how fast things could move — and that feeling doesn't disappear just because the organization has grown larger.

The Good Part: No Longer Carrying Everything Alone

I underestimated the other side, and it's the bigger surprise. There is a huge difference between carrying 100 percent of all responsibility every single day — and being part of a system with strong people in multiple seats who are better at their domain than you are.

In a bootstrapped company, the founder is the bottleneck for almost everything. For a long time, that feels like control, but in reality, it's a burden you only notice once it shrinks. Today, there are topics where I know: Someone capable is handling that, and I don't need to second-guess it. That experience was new to me.

On top of that is something I would describe as the real gift of this phase: I work with people who have scaled organizations to several thousand employees or taken software companies public. These are experiences you can't learn from books. In almost every conversation with them, I learn something about a scale I've never experienced myself — and about mistakes I would have otherwise had to make first.

The Mindset Shift That Takes the Longest

The hardest part isn't the structure. It's the relationship with money.

Ten years of bootstrapping means: Every franc was earned first before it was spent. Saving wasn't a tactic, it was a mindset — the default answer to almost every question was "can we do this cheaper?" That is the reflex that gets a company through a decade without outside capital, and it got us to where we are today.

And that exact reflex is wrong in many situations today. In a group with larger budgets, the right question is no longer "how do we save," but "where do we invest so that something bigger stands twelve months from now" — in infrastructure, in headcount, in marketing. Less conservative, more growth trajectory.

That sounds simple. It isn't. To this day, I notice that with larger expenses, I have to overcome an internal resistance that was a virtue for ten years. You don't switch off a pattern like that; you retrain it — and I'm right in the middle of that process. What helps is deliberately reframing the question: not "what does this cost," but "what does it cost if we don't do it?"

A Beginner Again After Ten Years

What I wouldn't hide from anyone facing a similar path: I am still in learning mode. Not as a cliché — but in the sense that in many situations, I still don't know the right way to do things and have to ask.

That's unfamiliar when you were the one with the answers for a decade. At the same time, it's the reason why I wouldn't trade this phase. The skills that take a company from zero to one aren't the same ones that integrate two organizations into one — and it's much better to admit that early than to have the results tell you later.

Whether I will look back on this role change as a gain or a loss, I don't know yet. Right now, it's both at the same time, sometimes shifting hour by hour. That's probably the most honest interim assessment you can give while you're still right in the middle of it.