152 Students Were Hiding in My Own Database
I have 152 students in one of my courses. Until last week I had no idea who was actually watching the lessons.
My AI assistant found a complete progress-tracking database on my course server. Lesson-level data, watch position, completion percentages, timestamps. It had been quietly collecting for months.
Nobody was reading it.
So I said: build me a report.
One conversation later I had enrollment counts by school, active students over 7 and 30 days, a leaderboard, per-course engagement, revenue. The AI pulled the data via SSH, formatted the whole thing, and scheduled a weekly cron job. Every Sunday at 7 AM, the numbers land on my phone.
Along the way it found a bug. The school detection code was defaulting every student to “writing” regardless of which school they’d enrolled through. One-line fix. Without it, the entire report was scrambled.
Then: certificates. A completion certificate template existed but was broken, redirecting students to a 404. My AI fixed the template, redesigned it with custom border art, made it school-aware (different name and URL per domain), optimized for print, and linked it to the account page. Students at 90%+ completion now see a View Certificate button.
I spent maybe 20 minutes on review decisions. The rest was the AI working through the stack: discover the data, build the report, fix the bugs, ship the feature.
OpenClaw is a self-hosted AI assistant running on your own server. It connects to your tools, reads your files, and handles real work while you do other things.
I teach two classes on setting up and getting the most from OpenClaw at AI Partner School.
