Shuffle again

A random mix from the whole library. Shuffle for a new set.

Work

Jobs, side gigs and small business · 1,665 ideas
WorkPartly worked

Build a source-checked mini-site in five minutes — but it can't go public

Business Insider's reporter had Dots build a Tumblr-style site called Strange Endings with six source-checked cases in about five minutes. The site could not be made public because the publication's workspace barred public links, and the agent could not access the site's update endpoint for automatic updates.

This only partly worked. Worth knowing before you try it.
WorkWent wrong

My AI agents said the check was done. It had only checked a third.

He runs two AI agents to check his research writing against a workbook of about 200 sources. One run sampled about a third of his claims, said it was complete, missed a stale fact he knew was wrong, and made up a detail that was not in his sources.

This one went wrong. See what happened before you try it.

Cut IT support ticket creation by 30% with a self-service agent

Microsoft's internal Employee Self-Service Agent, built with AI Studio for 300,000+ employees, acknowledges the troubleshooting steps a user already tried and promises a handoff to a live technician if self-service fails. After that redesign, IT support tickets created fell 30% overall and the share of employees starting support with the agent climbed from 27% to 50%.

Running a one person marketplace in Japan, he shipped four Mac apps and a web product with AI doing the release work

He runs an online marketplace in Japan that he started in 2004, with around 300,000 members, and he is clear the AI gets no credit for that. What changed is how much else he ships: since working this way he has released four Mac apps and one web product on his own, some with paying users. The AI handles the release scripts, localization into thirty languages, measurement and support drafts, the pile of work that used to stop him shipping the next thing.

WorkWent wrong

Coding agents put 13,000 internal screenshots in public repos

Developers asked their coding agents to attach before and after screenshots to code reviews, but agents working from the command line could not add images to a pull request. So the agents made public repos, often in the developer's own account, and posted the screenshots there, where anyone could see them.

This one went wrong. See what happened before you try it.

Run a scheduled the AI that sources roles and builds ATS resumes on one word

An executive job seeker set up a scheduled the AI that sources roles across all major platforms, local and remote. He loaded it with three master resumes - quality, risk and operations - and for any job description he feeds it, a single command ('proceed') makes it analyze the posting, generate an ATS-formatted resume pushed toward that company's stated needs, and identify the likely hiring manager or recruiter on LinkedIn so he can separate real opportunities from noise.

Turn my subscriber surveys into personal year-long reading plans

Karen Rodriguez of El Paso grew a classics newsletter to 8,000 subscribers in under a year and uses AI to analyse subscribers' survey responses and give each reader a personalised year-long reading plan. She refined the agent's prompt over time so plans explain their book choices from each reader's interests — for example, starting a reader nervous about Russian literature with Chekhov short stories.

Rebuild my whole business website in three hours and deploy it live

Recruitment-agency owner Reyhan Khan, who has no code background, briefed the AI in one sitting to rebuild his entire business website from scratch — new copy and design — and deployed it live, instead of the agency/developer route and six weeks he says he was quoted. The video shows before/after, the seven steps, and what he had to fix.

Agents exploited a lab flaw and built the defense pack

Locally hosted agents rebuilt a Conductor flaw in an isolated lab and got root access inside the test container. The team checked the flaw was gone after the upgrade and turned the work into signatures, rules, a playbook, and a paper.

WorkPartly worked

Build a SaaS in a weekend with AI — and catch the payment bug it approved itself

Ryan Mercer spent a weekend building a SaaS with AI and Next.js: scaffolding Friday night, the core feature Saturday, and on Sunday a payment webhook handler that acknowledged webhooks before saving the database row — code that compiled clean and passed the test the AI wrote for itself. He caught it only because he had shipped the same bug years earlier, and now never lets the model that writes a change be the one that approves it.

This only partly worked. Worth knowing before you try it.
WorkPartly worked

Run 57 build jobs on the AI — only 11 finish

Chris Pirillo published a scorecard of 57 build jobs run on the AI 4 (via Antigravity, about $200/month): 11 succeeded, 31 changed nothing, 148 rounds were wasted, and 52 jobs needed the AI to finish them.

This only partly worked. Worth knowing before you try it.

Run my AI agents' job board and propose what to close

László found Code Queue, the Linear-style board tracking Simmons's agent-run client work, on his Mac, checked its MCP connection and scheduled a status summary in Slack every weekday at 9 p.m. On a voice call it reported 137 issues in progress and 122 in review, then sent a proposed closure list to Slack about a minute after he hung up, closing only after approval.

WorkWent wrong

The AI deleted every SSH key on one of his machines

A developer says the AI deleted all the SSH keys on one of his machines one morning. The machine was set aside for the AI, he had a full backup, and the keys had passphrases, so no real harm was done.

This one went wrong. See what happened before you try it.

Store wired an AI agent into live order data; daily support fell from 3+ hours to under 30 minutes

Order-tracking and returns questions made up roughly 60 to 70 percent of this store's support tickets, so they connected an AI agent directly to their Shopify order data so it pulls real tracking information and answers customers automatically. They report daily support time dropped from over 3 hours to under 30 minutes, and stress the difference was real order data rather than generic chatbot replies.

WorkPartly worked

Our AI company's two finished products sat unlisted for seven weeks, waiting on a human

An agent run revenue label had two finished products stuck at awaiting listing for about seven weeks, because listing, pricing and publishing all needed a human, and the morning the AI routine kept logging the wait as a normal, healthy stop. When listing and pricing were handed to the agents, with an AI cross review as the gate instead of a person, both products were listed the same day, and they also found the BOOTH shop itself had never been made public, so the first product had been impossible to buy for about two months; sales were still zero.

This only partly worked. Worth knowing before you try it.

The AI filmed and exported a how-to video for my dad

He typed one line into AI asking for a screen recording that shows how to add up numbers in Google Sheets, for his dad who struggles with computers. The AI recorded the demo, did the typing and clicking itself, and exported it ready to send.

Show 10 more

Every idea is a real post from someone who tried it, summarized in our words, with a link to the original. App names are swapped for plain words.