Not chatbots. Not a platform you have to learn. Small systems that draft the repetitive writing you already do โ in your voice, from your own past work โ so you review and send instead of starting from a blank page.
Every one of these started as a real person telling me which part of their week they dread. That's still the only way I start.
You hand me the emails you already send. The system learns your phrasing, your sign-off, your rhythm โ then drafts the next one. You read it and hit send. Nothing goes out on its own.
Current data in, a short script out โ ready to read on camera or send to a list. Built around numbers you actually have access to, so it's yours and not something generic anyone could post.
The file you rename, the list you copy over, the update you retype. If you do it the same way every time, it can usually run without you โ and tell you when something looks wrong.
No discovery deck, no six-week engagement. I'd rather build one small thing that works than describe a big one that doesn't.
I've driven a forklift in a big warehouse for nineteen years. I started building software with AI because I wanted a way out, and I found out I'm good at it.
I build in public, including the failures. I've published the time my trading bot's stop losses turned out not to exist, the time a missing number told it to buy, and the test that proved a system I'd spent a month on had no real edge at all. That last one I ran on purpose, and I posted the result even though it wasn't the answer I wanted.
I mention that because it's the thing you're actually hiring. Plenty of people will sell you an AI system. Fewer will tell you when it isn't working โ and with this stuff, knowing the difference is most of the job.
If there's a piece of your week you dread, that's the conversation. If I can't help, I'll say so โ that's a faster answer than most people will give you.
briankfox@me.com