Not every great builder wants to build a company.
That may sound obvious. But when you watch something go viral, when the momentum builds and investors start paying attention, there is an invisible force that pulls you toward the default script: raise money, hire a team, scale fast.
Most people follow it without asking if they actually want to.
Peter Steinberger didn't. And the story of how he built OpenClaw and what he chose to do with it is a good lens for thinking about what it means to build something on your own terms.
What is OpenClaw?
OpenClaw is a local AI framework. You install it directly on your machine, and if you let it, it has system-level access to do anything on your computer.
By itself, it is just a shell. The creator jokes it is like a "space lobster harness", nothing happens until you plug in a brain. But once you connect it to a powerful LLM like Claude Opus 4.6 or GPT-5.3 Codex, it becomes something that can genuinely act. Not just answer questions, but do things. That is the official slogan: "the AI that actually does things."
You can talk to it through WhatsApp, Telegram, or any chat app you already use. It can connect to your browser, translate an audio file you send from your phone, and remind you to buy milk at 2PM. That last feature runs on something called Heartbeat which is basically just a clever cron job but it lets OpenClaw reach out to you, instead of waiting for you to ask.
There is also a soul.md file. That is where you give it a real personality and values. The creator calls it the soul.
But here is the thing about a tool with full system access and a proactive heartbeat: the security concerns are massive. When a bot gets this level of permission, it becomes a real risk.
And the plugins that extend OpenClaw's power? You can never be totally sure what they contain. To address this, Peter partnered with VirusTotal so that every skill is automatically scanned for bad code. It is not a perfect fix, but it is a serious attempt.
The Naming Drama (And What It Reveals)
OpenClaw did not start as OpenClaw.
After some early prototype names, Peter landed on "Clawdbot" (spelled with a W), like a lobster claw. He thought it was clever. He owned the domain. It felt right.
Anthropic, the company behind Claude (spelled with a U), did not think so. An employee sent him a friendly but urgent message: change it before the lawyers get involved. There was no lawsuit. But the message was clear.
Under sleep deprivation and stress, he panic-renamed it to MoltBot because he already owned those domains and needed a fast solution. He hated it immediately. His exact words: "the mold's not growing on me."
After sleeping on it, he came up with OpenClaw. And just to be safe, he actually called Sam Altman at OpenAI to confirm the name was okay to use before committing to it.
That detail matters. It is not just a funny anecdote. It shows someone who moves fast and figures things out under pressure but also someone who does the unglamorous work of getting it right, even when no one would notice if he skipped it.
The Part That Surprised Me
When something goes this viral, the expected move is a funding round.
OpenClaw had everything lined up for it. A strong technical foundation. A lot of buzz. A clear use case. The kind of momentum that usually ends in a hiring spree.
But Peter had already run a software company called PSPDFKit for 13 years. He knew what that path looked like, and not just the technical part but the people part. Managing employees, handling conflicts, navigating high-stress customers. That is what burned him out. And he is already financially comfortable, so making more money is not his main goal.
He also saw a conflict of interest. If OpenClaw became a SaaS startup, every cool community-built feature would become a temptation to lock behind an enterprise paywall. He did not want that pressure shaping his decisions. He believes OpenClaw should stay free.
So instead of starting another company, he joined OpenAI.
His reasoning was direct: "What I want is to change the world, not build a large company, and teaming up with OpenAI is the fastest way to bring this to everyone." OpenAI gave him access to their latest tools and massive computing power. Sam Altman announced that Peter would "drive the next generation of personal agents" at OpenAI.
His one condition: OpenClaw stays open-source forever, similar to how Google treats Chrome. OpenAI agreed. The project will live on in a foundation.
Why This Is Worth Thinking About
I will be honest: when I first read this, it felt strange.
If you build something valuable, aren't you supposed to scale it?
But the more I sat with it, the more I understood.
There is a shift that happens when something you built starts to grow. In the beginning, it is just you and the work, like writing code, shipping fast, and making decisions directly. It feels creative. It feels like building.
Then, if it works, things change. You hire. You manage. You sit in more meetings than you expected. Eventually, you are not building the thing anymore. You are running the thing.
Some people love that transition. Others realize they actually just want to keep building. That is a hard thing to admit in a culture that treats scale as the only real measure of success.
I have moved between freelancing, leading teams, running parts of companies, and building again. When I was in a Director of Engineering role, my days looked very different from when I was freelancing or writing books. Not worse just different. More coordination, more responsibility, less time in the codebase.
When I look at someone who ran a company for 13 years and chose not to spin up another one, I do not see a missed opportunity. I see clarity.
Growth Is Not Always the Goal
There is a quiet assumption in tech that if something works, you should maximize it. Staying small is often framed as lacking ambition.
But sometimes staying intentionally small is a strategic choice.
Growth changes the nature of the work. Once you raise money, you are no longer optimizing for what you find interesting. You are optimizing for revenue, retention, and returns.
That is not evil, that’s just how it works. The question is whether that is the deal you want.
The AI shift makes this question more interesting than it used to be. One developer with the right tools can now do what used to require a small team. If you can build meaningful things without hiring aggressively, you do not automatically need to scale headcount to scale your output.
Personally, I do not want a 50-person team and layers of management. I want something tight. Solid. Work that still feels like building. A small group of smart people who can achieve almost anything.
That does not mean avoiding impact, it just means choosing the shape of the impact.
What OpenClaw Actually Teaches Us
OpenClaw could have become a startup. Maybe a unicorn. Maybe it will still evolve in ways none of us expect, but what stood out to me was not the technology. It was the restraint.
Instead of following the predictable path, Peter asked a different question: what kind of work do I actually want to be doing?
That is the question most builders skip. Momentum is powerful, traction is addictive, and it’s easy to drift into growth because it feels like the responsible next step.
But that changes the job:
- You go from building to managing.
- From designing systems to designing org charts.
- From solving problems to absorbing them.
Some people want that. They thrive on it.
I don’t.
I don’t want a giant company. I don’t want layers of management and constant operational weight. I want something tight. Small. A strong group of smart people building fun things deliberately.
That is not playing small. It is choosing the shape of the work.
OpenClaw is interesting because its creator made that choice consciously. He didn’t drift into scale. He decided what kind of work he wanted to keep doing.
Most builders never stop to ask that question, they just follow the script.