The AI Tools Master List
Stop paying for tools you stopped using. See every one I run, what it costs, and whether I would buy it again.
Mark ThompsonFounder, Codas Labs
Writing
AI can automate far more of your business than you think. I run six software products on it. Every Thursday I show you exactly how, one thing at a time.
What I run, how it is built, and who this is for, so you can decide in three minutes whether the rest of this is worth your time.
Watch the introBuffalo, then Raleigh, then fifteen years of building software the traditional way. Outsourced development, hiring cycles, payroll, and the coordination tax that comes with all three. It worked. It also cost a great deal more than it needed to.
Not PDFs I wrote once and forgot. These are living documents I update as my own business changes, and you get every revision.
Stop paying for tools you stopped using. See every one I run, what it costs, and whether I would buy it again.
Every part of a marketing site, in three complete looks. Preview it, then take the code or the prompt for whatever you build with.
One email opens everything here, and every update, for as long as you want them. Or take The Claude Code Command Reference with no email at all — every command, flag and shortcut, read from the program itself.
TokenUsage shows you exactly what every model is costing you, live, across every project you run. It is the tool I built because I could not answer that question about my own companies.
No roundups of other people's news. If it did not happen in my own business, it does not go in.
How a non-developer ships real software. The workflow, the tools, and the parts that still need a human.
“I shipped a billing migration on a Sunday and reviewed every line of it.”From a recent issue
What agents can genuinely own, how to hold them to a standard, and where handing over costs more than it saves.
“The review step is not optional. Here is what it caught this month.”From a recent issue
What actually changed this week and what was just loud, with the receipts, and what I stopped using.
“Three tools left the stack this quarter. Two of them I had recommended.”From a recent issue
One command took 663% of the CPU and killed five running sessions. What that taught me about giving the build its own hardware.
Read Issue 022Both were confident. One was wrong. The cheap habit that now catches it before I act.
Read Issue 021What one engineering hire actually costs fully loaded, and the four things I bought instead last year.
ReadSame material, different format. Everything I write up on Thursday ends up here too.
Velocity is the full setup I run in my own companies — the agents, the review steps and the gates, taught properly. Everything above is free and stays free.
Some businesses want the outcome without becoming the person who builds it. I take a small number of these each quarter: agent workflows, internal automation, the infrastructure underneath.
Work with MarkFour reasons people get in touch. Any of them is a good reason, and they all land in the same inbox, which is mine.
You want the agent workflows and the automation running inside your own business, not a course about it.
You sell something operators and founders actually need, and you want it in front of them.
You have the market and the customers. I have the system that ships. Joint ventures, equity, revenue share.
Podcast, stage, a question, an introduction. If it does not fit a box above, use this one.
Goes straight to me, not an assistant. I read everything and reply to what I can.
Everything I write about here is running in a real studio: products in market, maintained the way I describe.
See the portfolioOne letter, every Thursday. One thing I built, learned or improved, laid out so you can copy it. No theory, no shiny objects, no pitch.
No spam, no affiliate dumps. Unsubscribe in one click.
See you Thursday. Mark