I run a company on my own. This is what I'm doubling down on, what I've let go, and why.
Amos Whitewolf · Halo
Nine months ago, more instructions did mean better output. The models got smarter. Now it's the other way round. Smaller skills. Fewer words on every page. The model and the operator can put it together.
A skill is a reusable instruction file the AI reads before a job. Mine used to run to thousands of words with strict rules. The short ones do better. The model needs room to be right. Over-prescribe it and you stop it growing, and it's a pain to maintain.
Steps in order, same every time. The blog pipeline. Long is fine here, because the job is long.
My voice skill. How I sound changes with my mood and who I'm talking to. Same with art, photography, video. Taste is the one thing you never over-prescribe.
It gets there on its own, and keeps going while you sleep.
The loop wanders. This needs a human going back and forth, and that's fine.
New data every week. Rage clicks, funnel drop-off, why people don't pay. The human matters most here. The paywall is still at this stage.
A number going in to plan the work, a number coming out to judge it. Tie a bow on it and let it run. The blog got there.
Reads search data, picks the keywords it can win, writes, publishes, checks the result, plans next week. Every 2 hours, unattended.
Screenshot the built screen. Screenshot the design. Overlay them. The agent sees the gap and fixes it. Loop until they match.
Screenshot every screen of the site, the app and the watch app. Build one map. Every flow in one view. Used to be a full manual day. Sometimes longer.
Fresh domain, no paid traffic, 5 months. One post carries most of it, which is the point. I didn't pick that topic. The loop found the keyword.
Anyone can build the app now. Nobody can copy a loop that feeds on your numbers, because they don't have the numbers. It costs money to start one. Once it's running, it's hard to stop.
Same logic, applied to the companies selling you software. The ones with millions of users feeding them data now ship at startup speed. Their moats get stronger. And each one covers more ground every quarter, so the niche a new startup can own gets smaller.
PostHog is the analytics I use. This year it started reading my session replays and errors, writing the fix, and opening a pull request for me to review. I couldn't build that, and I shouldn't try. Knowing which tools to use matters more than it ever has. The tools you pick are part of your moat.
I'm a developer, so I built it. Weeks I should have spent on product and marketing. Then the maintenance bill. And every bit of data I burned getting it right was data I could have used fixing the product. Time, money and data. Someone already sold the thing. Buy it on day one.
The 2005 winners were 2 amateurs with a better process. The edge was knowing what to check, not chess skill.
Consultants with AI, on a task it wasn't good at, were less often right than consultants without. They took what it said.
Same tools, opposite result. Hand AI to a video editor with 15 years of reps and they don't just make better work than you would. They make 10 times as much of it. Judgement is what switches the multiplier on.
6 months writing my own scripts and ads with AI. Didn't work. So: a script writer, an ads person, an AI video person. Same tools, better output, because they know what good looks like. The one hire I won't make is an AI developer who was never a developer. With video you see the problem straight away. With code you find out later.
I built my paywall off research into apps people already trust. It gave me the wrong answers, because Halo isn't trusted yet and those apps don't have that problem. So I re-scoped it to products at my stage and what worked for them. Clearer answers, better results. When you turn research into a skill, be specific about who it came from.
Building, reviewing, thinking out loud. Every workflow starts here, by hand, until it's boring.
The blog loop, every 2 hours. Browsing on its own. Voice notes from my phone that land in Notion as scripts.
Data on both ends means it compounds while I do something else.
The app works. It needs more people using it. 80 percent of my week now, up from 30.
Every loop starts with data you own. Working out where the good data is, and how to get it, is the job now.
Research got deeper, not wider. It feeds the ads and the positioning directly.
Autonomous social, AI-written ads. It's good with data and not good at taste, and I don't have enough data yet for it to learn. I write, AI helps.
I was going to sell Halo through schools. Then I talked to teachers. Schools won't mandate it, parents will. That's domain knowledge you only get by asking the people in the room. Parent nights, not principals.
Attribution, gamification, anything a company already sells. One exception: where I know the domain deeply, like SEO and the blog, and no product does it as well as I understand it. That's a moat. Everything else, buy.
The word "code" scares off the people who'd get the most out of it. It's not a coding tool. It's the agent that does everything. The chat window will do the thing. Go one level deeper anyway. That's where people are getting ahead.
If you can't answer with your own list, you haven't pushed it hard enough. AI tells everyone they're good at AI. That's why it's hard to prove you are. Go find the edges. Then you've got an opinion, and that's the part nobody can fake.
If anything here sparked something, a question, a "wait, how did you", or just a riff over coffee, tell me.
Amos Whitewolf · September 2026