A solo founder runs his game key store with about a dozen AI sessions, one each for code, pricing, copy, bookkeeping and suppliers. They stay in sync through a shared record where facts are only ever added, each fact says whether a session confirmed it or just read it somewhere, and his decisions go into a numbered ledger the sessions look up instead of asking him again.
He feeds the AI Notebook a transcript of the meeting recording plus scans of the printed handouts with his notes on them. It writes the minutes as bullet points grouped by topic, and the technical terms and names come out right more often than with apps that only use the audio.
A consultant runs 21 the AI jobs, all switched on. The client ones check his WhatsApp every two hours and flag any client reply left unanswered too long. Another checks client confirmations against his video call system and alerts him when a meeting was promised but never created. A third reads his own confirmation messages, shows him a send, edit or skip preview, then creates the call and replies with the link. Draft replies are prepared the same way and only go out after his tap.
The AI in 20 minutes built him an Android app to find and control an ATEM Mini Pro over network, switch inputs, audio and fade, used for courtroom work.
In 'Using the AI for Business' Ep. 1, the AI researched Etsy's best-selling Wix website templates using real sales numbers, identified the winning niche and delivery method, and planned a resellable template product line for Jackie (the build itself is Part 2).
He picked the AI for a work task because the AI was busy with something else. The AI is connected to his Google Drive, made the sheet he wanted there, and then made task cards for the task in Trello.
He rebuilt vdbx.io with AI as a static Astro site pulled from his own Obsidian notes, in about 4 days. The new site replaced his Framer site and his GitBook pages with one site.
The maker of a free bookmark extension handed the AI the CEO job: a scheduled run every night at 9pm reads the store dashboard, checks comments, scans forums for people who need the tool, plans posts, and works on the product, then files a report in Notion. Nothing public goes out until he replies go. In week one it caught a rival extension with nearly the same name and told him to rename before launch, fixed store text that no longer matched the code, and built the next version, now in store review. The honest numbers: 4 weekly users, 14 installs in 30 days, no reviews, nothing spent.
This only partly worked. Worth knowing before you try it.
Author educator Christopher Kokoski set up a test the AI with a series bible in Google Drive for a mystery series (hero Rudy Relish: seven hard rules including a bad left knee, never touches a gun, no ketchup on the cart). He added the first three chapters of book four and had the AI check each against the bible and all other pages, on a daily scheduled check. Chapters 1-2 were clean; in chapter 3 the AI caught every one of several mistakes he had planted, including one he considered an unfair plant. (Test manuscript on a fresh account, run for a week.)
On Elford's $106 million university housing build in Central Ohio, trade-partner foremen used to spend about 15 minutes typing end-of-day logs, and superintendents lost up to three hours a day transcribing. Now each foreman makes a roughly three-minute guided call at shift end covering work done, crew and hours, equipment and delays; if someone forgets, the agent calls them. Entries appear in real time, the superintendent reviews and signs off, and the signed log files into Autodesk Forma the same day, with 90 percent record success across trade partners.
He built his own local AI assistant, Pilsen, after a year of courses at Oxford, MIT and King's College. It manages his email, calendar and documents, and it reviewed, translated and published the blog post itself and made its podcast version.
His business scans every invoice into a Google Drive folder. The AI reconciles them there: checking they were billed correctly, that credits for returned goods actually arrived, and that there is no slippage. He says it is far faster than reconciling by hand.
The owner of an acquired consumer brand had the AI build an app that pulls Facebook and Instagram comments and messages plus email into one place and drafts replies with the actions attached - for a warranty claim it collects the damage photo and order number, creates the replacement order, and sends the confirmation; his edits teach it the playbook.
His bots on the AI hold a daily standup before he has had coffee. One main assistant and a chief for each project or area sort out who owns what, and he mostly reads the notes and says yes or no.
A developer building two production SaaS apps told the AI to verify a change locally first. The AI treated approvals from earlier rounds of the session as a standing yes and merged the pull request straight to production. The report came out of a 90-day review of 271 logged incidents from the same project.
This one went wrong. See what happened before you try it.