He has a 40 room hotel and two restaurants with nearly 100 staff and zero coding experience, and has spent the last three months down the rabbit hole. On a self hosted NAS, with ERPNext purely as the back end, he built with AI an entire custom front end: a staff portal with apps like a phone home screen, a maintenance ticket board, a housekeeping app integrated with the property system, QR codes in rooms so guests can report issues straight into maintenance, request a room clean, or order food from the kitchen. There is a restaurant point of sale with a delivery interface that links to the kitchen and updates the customer as cooking progresses, check in terminals, and a company chat with a translator. Rostering, the entire accounting and reconciliation, guest passport scanning, stock ordering, receipt scanning into stock, salary and service charge calculations, and sick reporting with AI scanning of doctors’ letters all run through it. Staff visa and permit paperwork that used to take days of complicated preparation is now prepared by AI into a PDF in seconds. About 140,000 lines of unique code, not counting ERPNext.
DeepSeek led his Linux porting project into changing baseline, config and hardware settings together until Linux would not boot, wasting 120 dollars and a weekend; GPT on Monday got it booting again.
$120at stake
This one went wrong. See what happened before you try it.
He is a delivery driver who employs a worker. Every Tuesday his AI pulls the settlement report, runs the commission and billback math, and updates his payroll tracker. The job used to eat a chunk of his evening each week. He set the rules once and it runs in the background; one site keeps killing his login, so he still pastes a password on Tuesdays.
His frontend launch scripts were failing with nothing in the logs. The AI helped him dig through layers of logs and configuration, then wrote a special runner with the right environment variables so he could run the job by hand. The cause was a hidden interactive telemetry prompt from Nuxt that stopped the scripts and never wrote a line.
In the same post he describes tools he built for his own work: invoicing and proposals. Writing a proposal used to take a few hours of his day, enough that he sometimes did not bid on a job at all and left money on the table. Now a proposal takes about five minutes, more of them go out the door, and more work is coming in as a result.
He had his OpenAI Dot read documents, apply to jobs on his behalf and send an email. Reading the documents was fine, but the job applications and the email were done badly, and every task needed him to watch over it.
This one went wrong. See what happened before you try it.
His win back system watches for customers who have gone quiet and sends a sequence to bring them back. Before it blames a customer for leaving, it checks for seven days whether the silence was a false alarm, like a tracking gap, so people are not chased over a data mistake.
She scans new papers as a science journalist. Keyword hits from her search are sent to the AI, which checks each one against markdown files where she keeps green flags and red flags for each topic, so only papers that fit what she cares about reach her.