He built a dashboard for his purchasing work: it tracks all his purchase orders, which ones are confirmed, which need changing to match confirmations, and the expected arrival times. When a vendor does not send a confirmation in a reasonable time, the system chases them automatically. He says his metrics are better and the job is less stressful.
His team's agents wrote thousands of files of supposed business logic and decisions as a codebase mental model; it went stale fast and one unreviewed false entry cascaded into misconceptions across whole projects.
This one went wrong. See what happened before you try it.
He is job hunting in tech, aiming at startups and big tech. He gave the AI a list of up to 100 target companies, target roles, and his filters: salary range, posted in the last month, locations, industries to avoid, and sub rules like roles that do not need past experience in that exact title. Twice a week the AI sweeps the list and brings back matches. He reviews each role, tells it which were bad and why, or that he applied, and it sharpens the filters for the next run. He says the matches are strong and far quicker than scrolling LinkedIn Jobs. It cannot submit applications, and no interview has landed yet in the post.
His team is replacing a client's 15 year old system. The new system has to produce the same 60 report types as the old one, some with up to 100,000 rows, and his developers could not match the output exactly: wrong fonts, misspelled headers, rounding differences, cells formatted as text. He gave Fable 5.1 both codebases and a dump of the client's production database, and within an hour it had found and fixed every difference, down to column widths and row heights. Matching the reports by hand would have taken weeks.
A Japanese non-programmer who posts about shochu, his garden and the AI across X, Instagram and Facebook gets a 7 AM message from the AI with today's paste-ready post text, the photo to use and 3-4 posting steps, prepared from a one-page work memo of what is due and what is already posted. Drafts are scored against his rules and only those scoring 80+ are sent; the agent must ask him rather than invent personal experiences it cannot know.
Mailing thousands of people brought hundreds of auto replies that nobody read. The AI scanned them read only, flagged who had left or changed roles, and updated Mailchimp, leaving a cleaner list and better deliverability.
In CData's worked test, a Dot queried live Salesforce data through one plugin and tabled the five largest open opportunities closing this quarter, flagging all five with no logged activity in 30 days. One deal was still open six days past its close date; the account used test data, as the post discloses.
Polish marketing freelancer Damian Nowaczek runs AI agents on his own server: every day at 06:00 one pulls data from his Google Ads accounts, compares performance and sends a report with conclusions to the company chat, so he never opens ad dashboards to spot a campaign burning budget. A second agent scans new public tenders daily and picks the marketing-related ones.