Shuffle again

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

Went wrong

When it didn’t work, and how to avoid the same mistake · 970 ideas
MoneyPartly worked

The AI read his enterprise software contract and caught the two year lock-in the salesperson never mentioned

He was negotiating a contract for an enterprise SaaS product. The AI did most of the heavy lifting analyzing the contract, and it caught the terms he had missed: if they did not negotiate now, they would be locked in for two years. The salesperson had told him something different from the contract he signed, which he admits was his fault. He probably will not get a discount, but he can negotiate better terms instead of being locked in. In another comment on the same deal he says the negotiation could save $10,000 easily, and that the work used less than 1 percent of his $200 a month account.

$10,000
This only partly worked. Worth knowing before you try it.
TravelPartly worked

Booked a Midtown restaurant for two and synced it to the calendar,

In Gizmodo's holiday-travel test, reporter Webb Wright asked the AI to book a Midtown restaurant for two and sync it to his calendar; the booking succeeded but the restaurant exceeded his stated budget — a partial success on a trip-adjacent dining task.

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

My agent watches flight prices for my trip and only pings me on a real drop

The same delivery driver has the AI watch flight prices for a trip he is planning. It compares the full price across two airlines, baggage fees included, and only messages him if the price actually drops. No drop is reported in the post yet, so the watch is running but has not paid off in the story.

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

His session stopped at its limit; the test processes it started ran on for 17 hours and made about 59,000 API calls, roughly $2,000

An AI session started verification tests as background processes. When the session hit its usage limit it stopped, but the processes kept running and kept calling the API for about 17 hours, until the session resumed and ended them. Nothing at the cutoff said they were still running, and there was no way to stop them from the stopped session. The test loop had no cap on turns or calls. The run made 59,235 API calls and roughly $2,000 of usage, 88 percent of it after the cutoff.

$2,000at stake
This one went wrong. See what happened before you try it.
WorkWent wrong

The AI ran my marketing for a month and got zero signups

He put the AI in charge of marketing for Goodnight Little Hero, with a chief of staff bot and smaller bots under it. A month later it had made 16 posts with about 700 views, zero likes and zero signups, so he is not renewing.

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

Fix Meta Ads targeting lookups that the AI’s MCP cannot do

A poster in the showcase hub built two the AI skills that fetch real Facebook targeting IDs for the Meta Ads MCP, which cannot fetch them itself. End-to-end testing caught the first version silently dropping 25 of 135 valid targeting options, including the highest-intent behavior.

This only partly worked. Worth knowing before you try it.
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.