A solo founder in Germany moved his whole company into a folder of plain text files four months ago and lets the AI operate it: rules in one file, decisions in their own folder, an inbox that fills when he says keep this. Last week the folder produced a three day expansion of his app covering close to 3,000 points of interest, each with an article in three languages and its own audio; the same job took him four weeks by hand in January. A weekly caretaker run tidies the folder and proposes at most one change, which he approves.
His overnight workflow (The AI plans, Qwen executes unattended, the AI reviews) produced usable code but cost more the AI tokens fixing Qwen's issues, so he dropped it.
This only partly worked. Worth knowing before you try it.
He fed the AI two copies of his resume, some parameters, and connections to more job sites than he has the energy to check. Every morning the AI checks them all and reports new postings, how well they fit his resume, and any gaps.
Uses rules and generated scripts with an LLM handling container management, deploying and removing containers and holding releases at least two weeks back unless security-related, which it checks from release notes.
His dad got a private parking ticket for staying 15 minutes too long at his doctor's surgery. The AI drafted the POPLA appeal, it cited the Equalities Act, and his dad saved £100.
A developer new to making videos drops raw files into a folder and the AI, connected to DaVinci Resolve through an MCP server, builds complete edited YouTube videos: transcribing, picking cuts, graphics and music, using a setup it built up over his last three videos. His latest video took 57 minutes, with AI showing him take options to pick from.
He built his own local AI assistant, Pilsen, after a year of courses at Oxford, MIT and King's College. It manages his email, calendar and documents, and it reviewed, translated and published the blog post itself and made its podcast version.