FluenTea: a video classroom with an AI speaking coach
I co-founded FluenTea so that language schools can prove their students speak. Teachers run live classes in it, and an AI coach called ChaCha sits in, runs practice calls between classes, and turns what students say into feedback for the student, the teacher and the department. I was the only technical person on the team.
- What I bought and what I built. I paid for real-time video, a hosted speech model and a managed database, and spent my own time on the coach's behaviour, the feedback pipeline and the school workflow. Concept to launch took three months.
- Safety and testing. Every action the coach can take is listed in a manifest, and a test fails if the model can see a tool that is not on the list. Anything that reaches another person needs a confirmed second turn. Text that did not come from the learner is treated as data. A red-team suite feeds her text written to make her misbehave, a second model grades her real answers against a baseline per error type that each release has to match or beat, and I read a sample of real transcripts every week.
- Running it alone. Deploys go through a test gate and a check of the live database schema against the code. After each incident in eighteen months I added a check that would have caught it. To test a forty-student class on one laptop I wrote a harness that holds forty participants in a single browser, and after one traffic stall I moved the analytics writes behind a Redis queue so that a class never waits on them.
- Listening to users. The early interviews I ran myself, and the dashboard rebuilt from them lifted monthly active users 247 percent in four months. Since October ChaCha runs them. She calls students and teachers at the partner university, asks eight scripted questions in Spanish or English, by voice or typed, and the server counts the answers and closes the interview, so the model never decides that it is done. When three of the first eight people answered the eighty-word opener with "¿Qué?", I cut it to a greeting and one question. The first round produced eleven fixes, built within the week, and the same mechanism now checks in with new users on their second day.
- Finding problems before anyone reports them. A nightly script plays a confused first-time user. It signs up through the real form, wanders the app on desktop and phone, and files what breaks. Microsoft Clarity shows me where people rage-click or give up. ChaCha's own transcripts are a complaint channel, so the weekly read looks for bugs and confusion as well as for her mistakes. And the team holds its meetings inside FluenTea, so we hit problems before a school does.
- The rest of a founder's week, with help. I wrote the outreach to language schools in Spanish, French and English as AI-drafted sequences by email and LinkedIn, with a do-not-contact list and a stop on the first reply. I also wrote the workflow that turns an advisor's or teacher's suggestion into code: a plan with the tests specified, coding agents that build it in parallel, the full test suite, and my review before anything merges. That is how eleven interview items became code in a week.
We launched three months after the concept, have more than 16,000 registered users from 136 countries, and work with three universities.
Python · FastAPI · PostgreSQL · React · LiveKit · Kubernetes on GKE · Cloud SQL · Cloudflare · Capacitor · Stripe
Close
Close
Close
Close
Close