So Why Now?

I've spent the last two decades inside companies at their most critical moments. Pre-revenue chaos. Hypergrowth growing pains. Acquisition due diligence. Post-merger integration. The kind of work where you learn something new every week whether you want to or not.

Most of what I've learned didn't come from books or MBA programs. It came from being in the room when things went sideways and figuring out how to fix them. Building the first hire's onboarding process at 2am because the company didn't have one. Running a due diligence process for a Goldman Sachs acquisition while simultaneously keeping the lights on for a 30-person team.

Two Worlds Colliding

Here's what I've noticed: the line between "business person" and "technical person" is disappearing. Fast.

I'm the Chief Commercial Officer for Strangeworks and fractional executive for others. I've spent my career on the business side. Operations, go-to-market, finance, hiring. I'm not a developer. But right now, I'm building tools with AI that would have required a full engineering team three years ago. I built the system you're reading this on. I built the content pipeline that manages these posts. And I did it in a single afternoon with Claude Code.

That's not a flex. That's the point.

The question every business leader should be asking right now isn't "should I learn to code?" It's "what should I still be doing myself, and what should I be automating?" The answer is changing every month.

What Are My Blogs About

This blog lives at that intersection. I'm writing about two things:

The business side. The real work of scaling companies. The messy, unglamorous, operational stuff that actually determines whether a startup makes it. Not theory. The actual playbooks I've used across six companies, one Goldman Sachs acquisition, and 1200% revenue growth.

The AI side. What happens when a non-technical business operator starts using AI tools to build real systems. Claude Code, Openclaw, and whatever comes next. I'm documenting my full AI journey: what works, what breaks, what surprises me, and what I'd tell another business person about to do the same thing.

These two tracks aren't separate. They're the same conversation. Every business leader is going to face this collision. I'm just writing it down as it happens.

What to Expect

Posts will cover:

• Operations that scale. The systems, processes, and structures that let you grow without things falling apart. Actual playbooks I've used.
• Fractional leadership field notes. What it really looks like to embed with a company as a fractional executive. The good, the bad, and the parts nobody warns you about.
• The AI journey. A non-tech person documenting the full experience of building with AI tools. Claude Code, Openclaw, and everything in between. From "what is this?" to "I just built a CMS in an afternoon."
• The automation question. What business leaders should automate, what they shouldn't, and how to think about the line between the two.

Why Now?

Two reasons.

First, I keep having the same conversations. Founders ask the same questions. Companies hit the same walls. The advice I give in advisory sessions keeps repeating, and it's good advice that shouldn't stay locked behind a retainer.

Second, I'm watching AI change what's possible for people like me. Business operators who couldn't build software six months ago are now building it. That shift is massive, and almost nobody is documenting it from the business side. The tech community is all over it. The business community is still watching from the sidelines.

I'm not watching from the sidelines. I'm in it. And I'm writing about it.

A Note on How This Blog Is Made

I use AI tools to help write this blog. I'm not going to pretend otherwise. But here's what that actually means.

I sit down, talk through what happened, share my real experiences, and AI helps me organize it into something readable. It handles the drafting and research. I handle the thinking, the opinions, and the final review. Every word gets read and approved by me before it goes live.

This is not an AI content farm. There are plenty of those already, and they're all terrible. This blog exists because I have 20 years of experience building companies and a genuine journey with AI that I want to share. The AI makes the writing process faster. It doesn't replace the experience.

If something on this blog resonates with you, it's because it came from a real person who actually did the work.

Who This Is For

If you're a founder or operator at a company between pre-seed and Series B, this is for you. If you're growing fast and feeling the pain: things breaking, processes that don't exist, roles that aren't defined. You'll find something useful here.

If you're a business person wondering whether AI tools are actually useful or just hype, this is especially for you. I'm the test case.

First real post drops next week. If you want to talk about any of this, get in touch.

---

This post was written by Steven Gibson with AI assistance for drafting and research. All experiences, opinions, and advice are my own. Every post is reviewed and approved before publishing.