Speed gets treated like a tax on quality. Move fast and break things, or move carefully and get it right. Pick one. I think that framing is wrong. Speed isn't the opposite of quality. It's a multiplier on everything else, because speed compounds.

The fix you ship today starts working today. The perfect version you ship next quarter gives up a quarter of returns you never get back, and it's usually not even better. Just later. First value early beats more value late, because the early value has time to stack while the perfect version is still in a document.

Read the full essay and follow along with the transcript

Everyone treats complexity like a disease. Simplify, streamline, clean it up. I treat it as the raw material. The messier the business, the more opportunity is sitting in it, unclaimed and usually mispriced.

Here's the logic. In a simple, legible system, the obvious fixes got made years ago. Anyone could see them. In a tangled one, huge wins are hiding in plain sight, not because they're hard, but because no one can hold the whole thing in their head at once to spot them. The complexity is exactly what's keeping the value hidden. And hidden value is cheap to claim.

Read the full essay and follow along with the transcript

The holidays just ended. Rosh Hashana and then Yom Kippur, the Jewish New Year and the Day of Atonement. For anyone who did not grow up with them, they are basically a forced annual audit of your life: a stretch of days where you stop, take stock of who you have been, and decide who you want to be. A week and change of that, plus time with friends, some travel, and a lot of sitting with my own head.

What kept surfacing was not work. It was people, and specifically one question I have wrestled with for years. I am a giver by nature. So how do I keep giving without getting taken advantage of?

Read the full essay and follow along with the transcript

The difference between a consultant and an operator isn't seniority, and it isn't how smart anyone is. It's what you hand over at the end. A consultant hands you a recommendation. I hand you the working thing.

A deck is a description of a solution. It is not the solution. The gap between "here's what you should do" and "here's the thing, running" is where most value quietly dies, and it's the client left to cross that gap, alone, after the expensive person has already gone home.

Read the full essay and follow along with the transcript

Everyone says be data-driven like it ends the argument. I'm not, at least not in that order. I run gut first, data second, system third, and the order is the entire point. Get it out of sequence and you end up slow, or confidently wrong, or both.

Most people fail one of two ways. They never leave their gut and get burned when the pattern doesn't hold. Or they lead with data, no instinct, and drown in dashboards that never quite decide anything. The move isn't choosing one over the other. It's running all three, in the right order.

Read the full essay and follow along with the transcript

People assume industries are different worlds, and from the outside they are. Healthcare has nothing in common with packaging. Packaging has nothing in common with a Web3 startup. Different products, different buyers, different rules. Then you get inside the growth problem and it's the same problem every time. Almost boringly so.

I've now built or fixed growth systems across healthcare, packaging, consumer, and Web3. Wildly different companies. Identical failure mode. Channels that don't talk to each other. No system holding it together. Growth that works only when a specific person is paying attention and quietly stalls when they aren't. Change the product and the story doesn't change at all.

Read the full essay and follow along with the transcript

Every business I walk into has a list of small broken things everyone knows about and nobody fixes. The report that gets rebuilt by hand every Monday. The two systems that don't talk, so someone retypes the same data between them. The follow-up that only happens when the right person remembers. None of it is a crisis. All of it leaks.

The reason it never got fixed isn't laziness. It's math. For years the calculus on a small fix was honest and brutal: this would take an engineer a week, the problem only costs us a few hours a month, so leave it. Multiply that across a company and you get a long tail of problems that were correctly ignored. Each one too small to justify the fix. Together, a slow bleed nobody's accountable for.

Read the full essay and follow along with the transcript

The best thing I can hear about work I've done is that nobody remembers I did it. The fix is just how things run now. No hero, no dependency, no name attached. That's the whole goal, and most people build the exact opposite without noticing.

They build things that work while they're watching. Then they call it a system, when really the system was them. Take the person out and the thing sags back to where it started.

Read the full essay and follow along with the transcript

Early in my career, the work had answers you could find. Google Ads, marketing platforms, the standard growth motions. Someone had always done it before me. There were docs, case studies, a person one Slack message away who'd solved the exact thing. The skill back then was mostly learning the existing playbook and running it well.

That skill has a shelf life, and lately it runs out fast.

Read the full essay and follow along with the transcript

Every owner I talk to can tell you exactly what's holding the business back. Marketing isn't generating enough. Sales isn't closing. The market softened. There's always an answer, it's always confident, and it's almost always wrong.

Not wrong because the owner is careless. Wrong because the explanation everyone settled on is the one you can see. The real constraint is usually somewhere you can't, and that's precisely why it's still there.

Read the full essay and follow along with the transcript

I wrote a couple months ago about memory being infrastructure and building your own tools. Since then I've been deep in the implementation. This post is about the patterns that actually worked.

The short version: the LLM is one component. The architecture around it is where the real leverage lives. And "architecture" isn't a hand-wave. It's a set of specific, solvable engineering problems that most people skip because they're busy optimizing prompts.

Read the full essay and follow along with the transcript

I use AI constantly. Not casually. Structurally. It's embedded in how I work, how I think through problems, how I manage information across multiple projects and contexts. I'm not an AI tourist. I'm a daily operator. And daily operators have a specific kind of frustration that tourists never encounter.

Everything forgets. (I wrote about why this matters architecturally in Memory Is Infrastructure, Not a Feature.)

Read the full essay and follow along with the transcript

Most people get this backwards. They think responsibility is a weight. Something you tolerate on the way to getting what you want. Take on enough of it, prove yourself, and eventually someone hands you authority. Then you can relax.

That's not how it works. Not even close.

Read the full essay and follow along with the transcript

I've walked away from money. Real money. The kind that would have made a meaningful difference in my life at the time. Not because the deal was illegal. Not because anyone would have found out. Because I wouldn't have been able to look at myself the same way after.

That's the whole framework. That's the post.

Read the full essay and follow along with the transcript

There's a version of me that people see in meetings. He walks in with a direction already formed. He talks fast, connects dots quickly, and sounds like he's three steps ahead. People assume that version of me has it figured out. That he sees the whole picture. That the confidence comes from certainty.

It doesn't. It comes from something closer to the opposite.

Read the full essay and follow along with the transcript

Most people building AI agents are optimizing for speed. Faster responses, lower latency, snappier interactions.

That's the wrong race to win.

Read the full essay and follow along with the transcript

I don't remember the first time I wrote a line of code. I remember the feeling, though. It was the same feeling I got the first time I closed a deal, the first time I launched something people actually used, the first time I watched a system I designed start running without me. It's the feeling of making something exist that didn't before. That's the whole thing. That's why I build.

I was fourteen. Most of my friends were doing normal fourteen-year-old things. I was the youngest of eight kids in a religious family, which means I grew up watching everyone else figure out their lives before I got a chance to figure out mine. That does something to you. You either settle into the youngest-kid role, the one who gets carried, the one who benefits from everyone else's lessons, or you decide, somewhere deep and maybe a little irrational, that you're going to prove something.

Read the full essay and follow along with the transcript

Every marketing team I've ever encountered thinks in funnels. Awareness at the top, consideration in the middle, conversion at the bottom. It's clean. It's intuitive. It fits on a slide. And it's almost entirely wrong.

Funnels are linear. Stuff goes in the top, some of it leaks out along the way, and whatever survives reaches the bottom. The fundamental assumption is loss. You accept that most of what enters will never convert, and you optimize by widening the top or plugging leaks in the middle. This is how most people think about marketing. It's also how most people think about hiring, operations, and growth in general. Linear. Sequential. Lossy.

Read the full essay and follow along with the transcript

I was nineteen when I started building in crypto. Not trading, building. I joined NFTzilla as Head of Media and Marketing, helping scale a platform for minting and selling NFTs. By twenty, I co-founded NFTuence, a Web3 marketing agency connecting creators with brands. I made real money. I lost some real money. I met people who became millionaires overnight and people who lost everything just as fast. I watched an entire industry inflate, pop, and leave most of its participants holding nothing but lessons.

I don't regret any of it. Not even the losses. Especially not the losses.

Read the full essay and follow along with the transcript