From the same day to day list, with the exact wording shared so others can copy it: every weekday at 11 am his AI checks AMD, Intel and Dell, and only pings him if one moves 5 percent or more or there is major news, staying silent otherwise. He presents it as the model for how he uses the agent: quiet ongoing jobs with a clear trigger, not a stream of updates.
He had the AI start his tax work this year and it caught that his property manager had double billed him for invoices on an investment property. The catch saved him $6,000, and the token cost of finding it was about $6.
The AI found the user a car ferry from Croatia to Italy, avoiding $2,200 in rental drop-off fees, booked and paid for it, pulled the plate and car model from the rental agreement, and confirmed he was insured for the voyage.
Senior HVAC technician David Gharamany at Art of Comfort checks from a customer's home whether a part is at the shop, how fast he can get it, and which seller is cheapest, with the company's AI engine doing the shopping. Every service call's data is fed back into the system so the next technician facing a similar fault can pull up his fixes instead of phoning him, and the same system handles customer calls so the shop stops missing them.
The AI built a complex quiz web app for himself and friends with multiple question types, screen sync, media uploads and scoring, in about a week of evenings (build reported in-window; the comment's complaint about current models left aside).
Ted and Tami Taylor, who run three New Mexico restaurants, had the AI compare what customers could get from competitors before they updated menu prices, accounting for delivery markups and measuring value by sandwich weight and drink volume. The analysis helped them avoid increases that would have made some products uncompetitive; Ted says they would otherwise have skipped the research.
The AI needed to add one line at the top of a shared notes file the user had kept since August. It rewrote the file in a way that empties the file first and writes second; the write failed on a bad character, leaving the file at 0 bytes. The file survived only because an outside backup existed. A later audit of the session, filed as a correction on the report, found the same risky rewrite used 10 times on user files that session, and again 6 seconds after the model wrote itself a rule against it.
This one went wrong. See what happened before you try it.
He gave the AI access to his Auth0 tenant to check his JWT validation. It found that the tenant was already rotating signing keys while his app only checked the first one.