Before we begin, I want to be upfront about something.
The voice in this episode is mine, but it’s AI-generated.
I cloned my voice using ElevenLabs, and the entire episode was produced that way. I think it’s important to be transparent about that. The words are mine. The ideas are mine. The delivery is artificial.
That feels like a fitting place to start, because a big part of what I want to talk about is exactly that tension: how technology should be used as a tool, not as a replacement for what is real.
This post is the written version of something deeper than a company update. It is not the pitch version. Not the investor version. This is the real version — what I actually believe, why I believe it, and what I’m asking of the people building with me.
But first, something important.
I did not start this company alone. I started it with my co-founders. This has always been about the team. I take my role as CEO extremely seriously, and I do everything I can to earn that position every day. But I would never pretend this is a one-man show. It isn’t. The reason we have something worth talking about is because a group of people decided to build it together.
Some of you reading this are part of that team. Some of you are following from the outside. Either way, I want to be straight with you, because I think that is the only way any of this works.
And to understand where we are going, you need to understand where this started.
A kid in Småland
I grew up in Åseda, a small town in Småland.
If you know anything about Småland, you know it tends to produce stubborn people. People who do not quit easily. That matters more than it might seem.
Even as a kid, I had a certain way of disappearing into things. My first-grade teacher told my parents that I was often somewhere else in my mind. Back then they called it daydreaming. It did not feel like daydreaming to me. It felt like locking in. When I got interested in something, everything else disappeared.
That trait has followed me my whole life. On some days it is a superpower. On other days it is a curse.
Very early on, I wanted to understand how things worked. I tinkered with hardware, took computers apart, put them back together, built machines from parts. I was not of the C64 generation. I started with a 286 PC running MS-DOS. From that point on, I was hooked.
I read everything I could get my hands on — Tolkien, Asimov, anything that expanded the world. I was deep into RPGs, tabletop games, worldbuilding, systems. I wrote text-based games in QBasic and spent absurd amounts of time optimizing memory just to make them run. Back then, 640 kilobytes was supposed to be enough for everyone. It rarely felt like enough.
What all of that taught me, early, was simple: systems have rules. If you understand the rules, you can make systems do what you want.
That is still basically what I do for a living.
By the age of eleven, I had set up a bulletin board system in my room called The Heart of Gold, named after the ship in The Hitchhiker’s Guide to the Galaxy. This was 1991. I was connecting with people over phone lines, learning how networks worked before I fully understood what a network even was. FidoNet. The proto-internet before the internet. I still remember the sound of a 2400 baud modem connecting.
I was also part of the wares scene. The pirating movement. Cracking and distributing software. It was not legal, and I am not trying to romanticize it. But it taught me things school never did: how communities self-organize, how information flows, how systems that try too hard to close themselves eventually get routed around.
By my mid-teens I was running Linux Slackware and compiling my own kernels. Not casually. Obsessively. Learning what each module did, what belonged, what did not, how the full system fit together. That bottom-up systems thinking never left me.
And that is where Sourceful really comes from. Not from a business plan. Not from a market map. It comes from a kid in Småland who built PCs, ran a BBS, compiled kernels, and never stopped wanting to understand how systems work.
Systems under pressure
The Navy was where systems thinking stopped being theoretical.
I started on fast attack craft with gas turbine propulsion. Raw speed. Raw power. In that environment, you are responsible for the whole system, not just one part of it. If something fails, you cannot call support. You cannot Google it. You fix it, or you have a serious problem.
Later I moved to submarines with electric battery propulsion. A completely different environment — quieter, more confined, slower in some ways, but under even greater pressure. Weeks underwater. No help coming. The same principle applied: if you do not understand the full system, you are a liability.
That shaped me profoundly.
As a marine engineer, you learn that nothing exists in isolation. The electrical system affects propulsion. Propulsion affects cooling. Cooling affects air systems. Everything touches everything else. If you only understand a component but not the system, you are dangerous.
And then there is the human side. Rough conditions. Broken sleep. Tight spaces. Stress. You learn to lead tired people in environments where mistakes have immediate physical consequences. In the Navy, the commanding officer stands in what we call the windshield — the position where the impact hits first.
That idea stayed with me.
That is how I think about leadership. When you are in the windshield, you do not get to have an off day. You do not get to be unprepared. The people around you depend on you being sharp, present, and honest about what you see and what you do not see.
First principles or nothing
After the Navy and a short period as a project leader, I did something that surprised a lot of people: I went into teaching.
I became an adjunkt, teaching marine engineers subjects like pumping technology and hydromechanics. And that is where I really fell in love with first principles.
I would stand at the whiteboard and derive SI units from scratch. No shortcuts. No hand-waving. I wanted students to understand where formulas came from, not just memorize them. I would spend so much time writing that I would lose my voice and wear out my arm.
That period shaped how I think about everything.
If you cannot derive it, you do not understand it. If you do not understand it, you cannot build on it.
For a lot of people, “first principles” is a buzzword. For me, it is literal. It is years of standing at a whiteboard, reducing ideas to fundamentals until there is nowhere left to hide.
That mindset later led me into a PhD, where I spent years studying how to optimize ship energy systems using machine learning. A PhD requires a specific kind of lock-in. But more than that, it taught me something about teamwork. Academic work is collaborative, but the thesis is still yours to defend. You build with others, but you also carry something alone.
During that work, I encountered an idea that changed my worldview: Jevons paradox.
William Stanley Jevons observed in 1865 that when coal became more efficient to use, people did not use less coal. They used more. Efficiency lowered cost. Lower cost increased accessibility. Increased accessibility increased demand.
That realization broke my brain in the best possible way.
Before that, I held a more traditional environmentalist mindset: conserve, reduce, use less. Jevons forced me to see that this framing was not morally wrong, but mechanically wrong. The path forward is not austerity. It is abundance. The way to outcompete fossil fuels is to make clean energy so cheap, so scalable, and so abundant that it wins on economics.
That was a major shift for me. I stopped being a conservationist in the traditional sense and became something closer to an accelerationist — not the reckless kind, but the kind that believes we solve the climate problem by building overwhelming clean energy capacity.
That insight became the seed of Sourceful.
The real problem: coordination
But abundance alone is not enough.
You can pu…