About

My evenings disappeared a little at a time.

I run an apparel business called WindRider, wholesale and direct-to-consumer, and for most of its life I wore too many hats. I did all the Amazon work, I oversaw the marketing, I did all the finance, I had my hand in Ops. There was me, at nights, on weekends trying to get everything done.

For a few years that was manageable, and then the math started turning against me. Tariffs pushed up the cost of nearly everything we sell. Meta got more expensive at the same time, so the same results cost a little more every quarter. And while the costs climbed, the job itself kept growing, because somewhere along the way "be everywhere" became the standard - more channels and more formats, with the same hours, the same budget, and the same me.

AI was supposed to be the relief. Instead it was just 1 more thing on my plate. Every tool that promised to save time arrived with its own learning curve, its own tab, and its own decisions to make, and the work grew faster than the help did.

The cost of all this never showed up in a spreadsheet. It showed up at home, on my waistline, my hairline. The laptop started reopening after dinner. I'd be at the table but not really at the table, half-there, having to constantly ask my kids to repeat their questions as I was thinking about all the things I had to do or answering one more Slack message. None of it felt like a crisis on any single day, which is exactly why I let it go on for so long. It just kept taking a little more.

If you work inside a small business, you probably recognize the shape of this. Costs climb, the channel list grows, the team doesn't, and the thing that was supposed to help becomes one more thing to manage.

The turn

There were no more hours to give.

For years, my answer to every squeeze was the same one: work harder. It had always sort of worked, which is why it took me so long to admit it had quietly stopped working. There were no more evenings left to spend, and the demands weren't done growing. You cannot out-hustle a problem that compounds.

The normal answer is to hire. I didn't have that option. The same squeeze that built the wall - tariffs, rising ad costs, resources that weren't growing - meant there was no budget for a marketing hire, an analyst, an extra set of hands. Whatever was going to take work off my plate could not come with a salary attached.

Which brought me back to AI, but differently this time. My first round with it had failed because I treated it like another tool: open a chat window, type, copy the result out, do it all again tomorrow. Every piece of work still ran through me. The shift was learning to treat AI less like a tool I operate and more like a worker I train.

That training - building a system - turned out to look less like engineering and more like writing things down. I'd take one piece of repetitive work and document how I actually do it: what information it needs, what a good result looks like, what it should never touch, and when it has to stop and check with me. Then I'd hand that to AI agents and review everything they produced. Early on I corrected constantly. Over time the corrections got rarer and the reviews got faster, and at some point I noticed I wasn't doing the work anymore - I was directing it. I decide what good looks like, I review what ships, and I step in where judgment is needed. That sentence took me about 30 seconds to write and more than a year to live. But it's the whole difference. AI stopped being 1 more thing on my plate and started taking things off it. And the business stopped needing my hours to move, because I was no longer the bottleneck.

Where it started

I started where the time was bleeding.

The first system wasn't ambitious. I just looked at where my time was bleeding the worst, and for me that was creating and posting facebook ads.

Here's what that work actually looked like. We had a designer producing about 40 ads a week, but the designer was never the bottleneck - I was. Every ad started with me: the concepts, the hooks, the angles, what to test next. And every ad ended with me too, because I was the one posting them all - downloading the images, re-uploading them, copying and pasting every line of copy and every URL. The thinking happened at night, and just the posting ate a few hours a week.

Then Meta changed the game underneath us. You can't run the same ad for months anymore; the platform wants fresh creative weekly, and not just more of the same ad - more concepts, more variety. Every new ad needed another idea, and the ideas came from the one resource I was completely out of.

So, working with Claude, I built my first real system. Agents draft the ad concepts, generate the creative, and prepare everything for upload. I review everything before it goes live. The concepting, the hooks, the variations - the work that used to soak up my nights - moved onto the system, and reviewing its output takes a fraction of the time creating it ever did.

Today we could generate hundreds of ads in the time it used to take to get 40. We don't actually run hundreds - we don't need to - but that's the part that changed how I think. Volume stopped being the constraint. Ad creative costs us under 50¢ each now too, but honestly, the money was never the point. The time was.

I want to be honest about how small this first step actually was. It wasn't an overnight AI makeover of the business. It was one repetitive, expensive piece of work, moved onto a system I could review. But it was the first time in years I'd gotten time back instead of losing it, and once I'd felt that, I wanted it everywhere.

The build-out

Then I did it again. And again.

Once the ads system proved the model, I kept going, one system at a time.

Next was analytics. The weekly reporting used to eat a full day, and not because writing the report was the hard part. It was everything underneath it: compiling the data, comparing our Shopify numbers against Google Analytics against Facebook, reconciling the places where they disagreed, and only then getting to the part where you figure out what it means. That whole chain became a system, along with the context that keeps an analytics agent from misreading our numbers.

Then came content generation. Then a CMO agent that runs the daily standup and keeps the other agents pointed at the right work. Then finance agents helping manage the books, and operations agents helping with sourcing. And over all of it, approval gates, so nothing risky ships without our involvement.

Somewhere along the way it became a whole team of agents actually getting work done. One person overseeing.

That's the part I want to be precise about, because it's the part that changed my life. I didn't get faster, and I didn't start working more. The structure is what freed me. The work moved onto systems, the judgment stayed with me, and my hours stopped being the constraint on the business.

The honest part

The turns that mattered came from conversations.

I'd love to tell you I figured all of this out alone, through discipline and cleverness. I didn't. The parts I did alone were the slowest and most expensive parts - getting it wrong, rebuilding, then getting it wrong in a new way.

The turns that actually moved me forward came from conversations with other operators doing the same thing inside their own companies, and almost always from the parts of those conversations about what didn't work. Somebody 2 steps ahead would say "we tried that, here's where it breaks," and save me a month. Somebody 2 steps behind would ask a question I'd stopped asking, and expose an assumption I didn't know I was making.

The failures were worth more than the wins, because failure is where the actual learning happens. A win tells you something worked. A failure tells you why something didn't, what it cost, and what to watch for the next time. But nobody publishes their failures - they publish the wins, the launch announcements, the screenshot of the dashboard on a good day. Which means the most valuable lessons in this whole space live almost entirely in private conversations, because that's the only place people will actually say them out loud.

That's the honest reason AIIMN is a community and not a course. A course is one person's answers, frozen at the moment they were written down. The conversations are where the real learning lives, and they keep moving as the tools change.

Where it landed

You can have it all.

I want to be careful with that sentence, because it sounds like a poster. So let me tell you what it means at my house.

The core business is growing and I'm hitting my numbers, and the work gets done without me sitting in every loop. My evenings belong to me again. I coach my son's baseball team. I'm at dinner - actually at dinner, not halfway through Slack - and the laptop stays shut after. I can take a vacation and actually relax, and nothing breaks while I'm gone.

I always knew what I needed: systems in place to take things off my plate so I could focus on the work that actually mattered. What I didn't have, for years, was a way to build them that didn't start with hiring.

And that's the spot most small businesses are stuck in. There's always more the business needs to be doing, and there's no budget for more people to do it, so "more" just turns into more hours for the owner or a few key employees. We lived in that grind for a long time.

AI, used appropriately and in the right places, is what finally broke that cycle for us. You can do more with the same limited resources. You can grow and get your time back. For years I assumed that was a trade: the business gets your evenings or it doesn't grow, pick one. It's not an either-or. It's a both.

Why this exists

I'm building the room I needed.

Which brings me to why this community exists. The operator conversations that changed everything for me are still changing things for me - I'm in them every week, still learning from people building inside their own businesses. What changed is my capacity. The systems gave me back enough time that I can now facilitate those conversations instead of just hunting for them. That's what AIIMN is: a network of operators sharing real systems, real wins, and real failures, so nobody has to rebuild this alone the slow way I did.

I won't pretend the motivation isn't selfish. The community only grows if members get real results, and I improve faster by being in a room with people trying things I haven't tried or asking questions I haven't asked myself yet.

You start with my experience: the playbooks, the teardowns, what broke at WindRider and what we changed. Then we walk it together. The map isn't finished, and we're building it as we go, all of us.

Straight answers

What I'm not.

A few straight answers before you decide anything.

I'm not a guru. I'm just a guy running a small business that's had some success using AI inside it. AIIMN is me showing what I've done so far, and getting the chance to learn from other people doing the same.

This isn't a course. There are lessons and guides inside to help you start, but the bigger value is the community - people sharing their experiences and knowledge through posts and discussions, what's working and what isn't.

Join

Get your evenings back.

Public membership opens June 8, 2026. If the first part of this page felt familiar - if the laptop reopens after dinner at your house too - join the waitlist and you'll get first access when the doors open.