A developer runs his own repos and production server under a written constitution file in every repo. Automated runs check production logs daily and file bug reports. When he types one short check in message, the system scans and ranks his open issues, sends sub-agents to fix the top ones, and code deploys to production twice a day without him pushing it. A read only agent on the production box acts as his dashboard, checked through a chat app.
During a migration, a written plan in the session said nothing in the legacy repo gets touched. The plan was re-shown in full mid-session. When the user later asked for a follow-up change, the AI searched the folder it had been working in most recently, which was that repo, found a file that looked right, and edited it there. The user caught it, and the edit was reverted and redone in the correct repo.
This one went wrong. See what happened before you try it.
He had the AI on Windows develop two PowerShell scripts for multi step data processing, each with a small window on top that launches the whole process with a single click. Both start from an encrypted Excel file received by email and decrypt it. The first takes the data from the file, searches the CRM for records, places the results into a different Excel file using a defined template, and drafts an email summarizing the findings with the new file attached. The second combines the file’s data with other CRM data to validate it, runs the data update against the CRM, and produces the validation results in a templated Excel file with a draft summary email.
Replaced Bugbot at 1,000 dollars a month for a small team with a custom OpenCode harness at maybe 100 dollars, rebuilt its features including cross PR memory, added a security reviewer action.
He has been building a fantasy sports app with AI since June. It gives lineup advice and waiver alerts, and its autopilot mode actually makes moves in your league for you. It is live with real paying subscribers, and he also sells the same sports data as an API to developers, which has picked up its own small customer base.
A Spanish AI consultant's case study (client anonymized): in autumn 2026 he trained the 8-12 person team of an industrial family office with several companies. Working in department pairs, each pair left with a working the AI Skill or agent prototype on a real case of theirs: a Skill for the monthly storage-unit bank reconciliation, another for comparing offers, a Cowork contract registry over the maintenance folder, and scheduled tasks such as a daily inbox review and a weekly maintenance summary, all on Microsoft 365 connectors, with a governance playbook and 30 days of support.
Peace Call's two-week log of running a HighLevel affiliate site with an AI (Oct 4-18) records a wall of platform rejections: Pinterest suspended the domain and denied the appeal on Oct 18, Ko-fi unpublished the page as SEO spam, Podbean froze the account, both Lemmy servers declined registration (Oct 16-17), Japanese Nostr relays refused the agent's US-based posts, and Reddit returns 403 to the agent's machine. The site's income after two weeks of multi-platform agent publishing: $0.
This one went wrong. See what happened before you try it.
The Rank with Haris channel's daily tutorial series shows the AI drafting a complete landing page from a one-message description of an offer — headline, benefit bullets, CTA — refined through chat and exported as a finished page, with an honest-tips section on what the AI can and can't do.
Content creator Colin Rocker (someone) named his AI 'Marlowe' and set it to keep his personal website updated without manual input. Marlowe runs scheduled background tasks including a monthly scan of the internet for new press and viral posts, pulling findings into his site — but never publishes without his approval.
He left Instinct, an AI agent, with one job: look for 30th anniversary Pokemon cards in stock anywhere. It sits in the background and alerts him to places that have stock.