How to Actually Make Money With AI in 2026: An Engineer Ranks 13 Side Hustles
An engineer who builds AI systems ranks 13 ways to make money with AI in 2026 by ceiling, moat, time to first dollar, and fulfillment burden.
We can't find the internet
Attempting to reconnect
Something went wrong!
Attempting to reconnect
Writing · Tag
43 posts on founders, page 2 of 4. Or browse the full writing index →
An engineer who builds AI systems ranks 13 ways to make money with AI in 2026 by ceiling, moat, time to first dollar, and fulfillment burden.
PRC labs harvested their own users' sessions, many arriving via third-party model routers. The fix is treating the router as a vendor.
Anthropic published an economic upside scenario and an alignment risk admission the same week. The upside needs the thing nobody has a plan for.
Agents stop before the work is done, not because the model is lazy but because nobody built the management system a human employee gets for free.
The two documents an enterprise reviewer wants for your AI agent, the allow-list and the tool-call log, specified field by field and generated from code.
Security checklists only ever grow, because nobody who writes them pays the cost of a control a small team cannot staff. Which to defer, and which never wait.
McKinsey didn't swap 25,000 people for AI agents. What its CEO actually said is more useful to founders, and changes the question to ask before hiring.
The consultant's playbook for taking over an undocumented AI-built app after the builder walks away: what to audit first, and how to price it.
Paul Graham’s schlep blindness, updated for 2026: agents made the fun half of your product free to copy, so the tedious half is the only part left worth owning.
What a sixteen-week embedded AI engineering rotation ships, month by month, from the first merge to the handoff artifacts that let it end.
Microsoft just made vulnerability detection cheaper and more accurate. For a 12-40 person AI startup, that was never the bottleneck.
What a buyer's technical reviewer checks in a reverse acqui-hire when the code isn't the asset: key-person risk, IP scope, and contribution forensics.