Skip to main content
Rocket Routine OSRocket Routine
Blog article image

Why I'm building an operating system for companies

45 years in software. 33 years in quality management. 4 companies at once. Why I'm building Rocket Routine OS — the AI-native operating system for founder-led B2B companies.

Most companies struggle with three problems.

  1. A real strategy often doesn't exist at all.
  1. When a strategy does exist, it's rarely communicated in a way that people actually understand.
  1. even when strategy and goals are clearly defined, execution fails in everyday operations.

I've observed these patterns for decades. In my own companies. In companies I've consulted. In conversations with founders who experience the same thing.

Rocket Routine OS didn't originate from a product idea. It's the result of a long chain of experiences and mistakes.

The starting question

In 2016, I acquired antoher company. The task: To integrate an existing company into a running organization. The central question was simple.

How can a company be structured so that people work successfully together — even during integration, growth, or change?

During that time I understood that traditional hierarchies create many unnecessary problems. Companies function better when people take responsibility, when decision-making capability exists, and when everyone works toward shared goals. This sounds obvious. In practice, very few actually do it.

I described these experiences in my book "Auf geht's" (Let's go!), co-authored with Christian Wißmann. An agile transformation. What worked. What didn't.

The strategy problem

At the same time, a deeper problem became clear. Where do we want to go as a company? What's our purpose, what's our vision? What mid-term goals follow from it? Everyone asks these questions.

The real question is different: how do we ensure that these ideas don't remain slides in a presentation, but actually guide everyday work?

Strategy is not a one-time exercise. It constantly evolves through interaction with markets, customers, and internal developments. Companies must observe, learn, and adjust continuously. Strategy requires infrastructure, not just intention.

The first attempt

Out of these considerations, I founded Rocket Routine as a startup in 2022. The idea: support strategy, goals, and execution with software.

The problem became visible fast. Many users didn't recognize the strategic capabilities. The system was treated as an OKR tool. In that market, established providers compete. That was the wrong fight.

But the core idea behind Rocket Routine was always bigger than an OKR system. Over many years, a larger picture had formed. A leadership model that connects strategy, responsibility, decision-making, and execution. Not as a methodology slide. As a running system.

What has changed

Three forces are converging right now.

  1. Fragmentation. A typical growth-stage B2B company runs on 15 or more tools. Each owns a slice of reality. None of them know what matters this week. The CEO has no single view of work in flight.
  1. AI generates, but nobody verifies. Generative AI has made content production fast and cheap. But production without governance is not execution. AI can draft a campaign, write code, produce a financial report. It cannot verify whether the output meets the standard, follows the right method, or moves the right outcome.
  1. Frameworks describe, but they don't operate. EOS, Scaling Up, OKRs — they all provide valuable methods and a shared language. But they were designed for a world where humans execute everything. They define what to discuss in meetings. They don't provide a governed execution layer.

Tools fragment visibility. AI generates without verification. Frameworks structure thinking, but not execution.

That's the gap.

What I'm building

Rocket Routine OS is an AI-native operating system for founder-led B2B companies. It sits on top of your existing tools and frameworks. It doesn't replace them on day one. It adds what they lack: a governed execution layer with quality confirmation and systematic learning.

A Control Tower where the CEO sees everything in flight. Role-based AI operators that aren't chatbots, but governed digital teammates with explicit decision rights and quality duties. Verification first — nothing ships without evidence that it meets the standard.

The foundation is proven lean management methods: PDCA, Poka Yoke, pull principle, structured decision-making. Translated from manufacturing to knowledge work. Not as metaphor. As structural infrastructure.

One foundational principle runs through everything:

Processes are the problem, not people.

When quality confirmation fails, the first diagnostic is the routine, not the operator.

Why I'm qualified to build this

I've been building software for more than 45 years. 33 years in quality management and process optimization. Working with AI since 2016. I run four companies simultaneously without a single dedicated middle manager. I've written a book on corporate management, strategy, and goal systems. I consult companies on leadership methods, OKRs, and AI imlementation

All of that feeds into Rocket Routine OS. Not as theory. As daily practice.

Company 0

Rocket Routine GmbH is the first company running on Rocket Routine OS. I call it Company 0. Every day, I produce real work using the routines, artifacts, and quality processes that Rocket Routine OS defines. Every run generates improvement items. The system updates itself.

If Company 0 can't run on it, customers won't either. That's the strongest form of credibility I can offer: I use the system to build the system.

Rocket Routine OS is not a theoretical framework. It's the operating system I use to run my own companies. If it doesn't work for me first, it won't ship to you.

What comes next

Rocket Routine OS is being built right now. The waitlist is open. The first 30 signups get early access and founding member pricing. The first 5 get weekly strategy calls with me.

Over the coming weeks, I'll explain the system piece by piece on this blog. One concept per week. Transparent, concrete, no buzzwords. And in the weekly video diary, I'll show what's actually happening in Company 0 — what works and what doesn't.

If you're running a founder-led B2B company with 15 to 50 employees and you want measurable execution control without a consulting-heavy rollout: rocket-routine.com