What I actually do
I find one specific problem that people genuinely have, build something small that solves it properly, and sell it at a price nobody has to think very hard about.
The products are not courses about artificial intelligence. There is no theory in them and no attempt to make you interested in the technology. One is a complete setup for running your week through Claude. One is a pack of workflows for paperwork, forms, broken appliances and the phone calls everyone puts off. One is an audit that finds money quietly leaving your account through subscriptions and renewals you stopped noticing years ago.
Each one does a single job for a single kind of person, and each one is designed so you get a result the same evening you buy it.
The part most people do not see
I build the whole thing myself.
That means the products, but it also means the website, the email automation, the payment infrastructure, the customer tagging, the analytics and the advertising creative. When somebody buys, a webhook fires into an automation platform, tags them correctly in my email system, and starts a sequence I designed and wrote. The onboarding, the cross-sells and the win-back flows all run without me touching them.
None of that was outsourced and none of it came out of a template. I taught myself every piece of it, mostly by needing the thing to exist and having nobody to ask.
I mention it because it is the actual business. Anyone can write a PDF. The difference between a PDF and a product is the machinery around it, and building that machinery is most of what I do.
How I decide what to build
I do not guess, and I do not build things I find interesting.
Everything I have made came out of something a customer said to me first. The two newest products exist because a buyer wrote to tell me that the thing helping her most was not work at all. It was household admin, money, and fixing tech problems she had never been able to fix on her own before. That one message changed the direction of everything I make.
So I ask, constantly, and I read every reply. That is the research, and it is the reason the products sell rather than sit.
Why these people
Most explanations of AI are written by technical people, for technical people, in language that assumes you want to understand how it works.
The result is that the group with the most to gain from these tools gets the least usable help. The people I write for are not developers and have no interest in becoming developers. Many of them are decades older than me. They do not want to learn about AI. They want the letter explained, the bill checked, the form filled in, and their week to stop feeling like a pile.
I am not an expert on much, and I am the wrong age to pretend otherwise. But I have spent every day for a long time pointing these tools at ordinary problems and writing down what worked, what failed, and where it quietly got things wrong. That has turned out to be more useful than expertise.
How I work
Every product carries a thirty day money back guarantee with no forms and no questions. You reply to an email and I refund you.
I do not run countdown timers, fake scarcity or prices that pretend to be about to rise. I tell people who a product is not for, in the sales copy, before they buy it, because a refund costs me more than a missed sale and because I would like this to still be here in ten years.
The newsletter is free and stays free. Most of the people who read it have never bought anything, and that is a perfectly good outcome.
What I am building towards
More products, each one narrower than the last, and the infrastructure to run them properly. I am interested in the boring part: the systems that let one person operate something that would normally need a team.
If you want the weekly email, it is free and you can get it below. If you want to tell me what you are stuck on, reply to any of them. It comes straight to me and I read all of it.