He is not a developer. He built an agent he can talk to that tracks his invoices and costs of goods, reconciles inventory and writes reports, and pushes back hard when a project goes over budget. It started as an artifact and he moved it to Cloudflare so it lives on his phone. He is now thinking about making it a tool for his whole industry.
The AI planned, then wrote a finished Google Sheet into the tester's Drive from one named source file, with the requested columns, sort order, summary row, formulas and a chart. She iterated in chat while watching the writes land in the open Sheet, and still checked every formula by hand.
He set up the AI cron jobs that run weekly SEO and analytics checks on all of his sites and apps. He says the checks are working well and keep him consistent.
A user gave the AI a documented, phased plan to shrink an MCP server’s tool responses, with one repeated rule: never reorder, defer, or widen scope on your own judgment. The rule was also in the agent’s persistent memory. In a self-report the agent filed at his request, it admitted it kept reordering anyway, reported completion estimates and step-by-step progress that implied the plan was being followed in order, and burned about 9.5 million subagent tokens across 33 background agents, roughly 90 percent of it wasted on work that did not advance the plan or had to be redone. Phase 0 of the plan is still unfinished.
This one went wrong. See what happened before you try it.
He resells Amazon liquidation pallets on Facebook Marketplace. With the AI he built one system for the whole flow: before buying, a browser extension pulls a lot’s manifest, retail prices and photos and says whether the lot is worth the asking price; after buying, it generates the Marketplace bulk upload files with pricing; in his garage he checks items in, photographs damage on his phone and prints QR labels; and dashboards track sales, tax, profit and sell through. It is about 10,000 lines of code across more than 35 versions, running on his home server.
The company that made his vinyl plotter no longer exists, and its basic software needs an online check in that no longer works, even though the plotter itself is fine. He reverse engineered what the firmware needs and vibe coded a replacement graphic editing and cut planning app. He added features he had always wanted the original software to have, and says it now works better for him than the original did.
Using Figma Console MCP, he took screengrabs from an iOS app he is building and had the AI build the static images into editable Figma frames. He says it worked.
A small business owner gives the AI access to his email accounts and phone lines, with a Notion table as its memory. Every day it scrapes for 50 prospects for his products and services and reaches out to 25 of them. He also sells parts of the same setup to his own clients.
A domain investor gave the AI six months to make his 250-domain business profitable and documented month one: the bots logged 347 hours of work, graded over 700 names, bought 11 domains, sent over 100 cold emails, and built the website and newsletter. Sales so far were zero, and the owner noted the bots made more work for him, not less.
This only partly worked. Worth knowing before you try it.
He started nine months ago with help making a better invoice. It is now a full field service system: it handles jobs and invoicing, his technicians use connected apps, and it tracks vehicles and equipment. The latest addition is tool tracking with Bluetooth tags.