Ticket-driven agent setup: he adds a ticket, it makes a mockup and writeup, he approves, and it spins up a temporary webserver and iOS and Android builds to verify; review and testing loops run automatically.
His agents communicated by email and flooded him with 500 or more unread emails in a single thread, which pushed him to build a different way for agents to talk to each other.
This one went wrong. See what happened before you try it.
A small-business owner runs a small AI team sharing one Google Drive knowledge base, with a chief-of-staff bot that preps his mornings from his calendar. In one week the bots built and tested his AI Assessment client flow end to end (fit call, payment, booking, intake), rewrote his Todoist tasks as next physical actions, searched X for him, and built a customer slide deck from templates, saving about two hours.
He set GPT-6 to read tens of thousands of his emails, his writings and his calendar appointments from his recent career. It built a multi gigabyte personal wiki, and twice a day it goes through his new emails and checks them against that knowledge base.
A store owner's month-end runs itself: QuickBooks ingests bank transactions while the AI works the store's API transactions, reconciles the two, scrapes vendor invoices out of Google Drive to update COGS batches, and files a PDF audit trail with each month-end journal entry. Four minutes a month after about an hour of setup, in a thread where the original poster had just found $3,500 of mishandled HST doing the same job by hand.
Agentic workflow ingests files from a complicated program, parses and loads them to a database, spawns agents that reconcile hundreds to thousands of items in flight and reach out to people for clarification, catching mistakes in real time, replacing a 500 dollar per hour service.
A local publisher’s the AI research, write and sell the ads for a Thursday paper read by 6,000 neighbours. The bots cover the whole production loop of a real local news product, not just the writing.