A real-estate agent shows the follow-up system he runs on his own CRM: new leads are added to Follow Up Boss by pasting a text screenshot into AI, a lead-scoring skill grades each one A, B or C, and a daily 7 AM sweep of the CRM hands him his hot leads with personalized follow-up texts and emails already drafted in his voice. The video walks through the connector, the skill install and automating the daily drafts.
A solo developer built a women's clothing brand's production WooCommerce store with AI writing most of the code: a custom block theme matched to the client's React prototype, real-time CommerceML sync with their 1C ERP (including patching a stock parser that silently dropped nested per-warehouse counts and cleaning up roughly 1,000 orphaned variations), and zero dollars in platform licenses. Two client revision rounds of about thirty items each cleared in days, and the whole build took weeks instead of months.
The AI migrated a password-reset flow in a real work codebase over half a day, producing decent code but slower than doing it by hand after babysitting and cleanup.
This only partly worked. Worth knowing before you try it.
He had the AI transcribe more than 70,000 images of old documents in two days, for $380 in total. The handwriting and worn pages hurt the quality and it did worse in Portuguese than in English, but the AI handled the whole run.
He runs a music school and cannot code. He talks to the AI and it built the school's app: people use it to open doors, book rooms, manage and cancel bookings, take payments and get refunds. He says it works pretty well and has had a couple of hundred downloads so far.
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.