ai Case study
English Boss Bot
Language practice fails on consistency, not on content. There is more good material available free than anyone can use, and almost nobody keeps a daily habit unaided, which makes the scheduler the actual product.
The business problem
Practice apps are opened enthusiastically for a week and then not at all. Any design that waits for the learner to initiate is competing with everything else on their phone and losing. The exercises themselves are the easy part; getting someone to do the fourth week is the problem worth solving.
What I delivered
- Scheduled practice sessions that reach the learner rather than waiting to be opened.
- Short exercises sized for the gaps in a day, since a session that requires a free half hour will not happen.
- Progress tracking and gamified feedback, so the streak itself becomes a reason to continue.
- Performance review across sessions, which is what turns practice into something with a visible trajectory.
- IELTS-oriented routines for learners working toward a specific exam rather than general fluency.
Technical approach
- The scheduler is treated as the core feature and everything else as content for it. That is the inversion the category usually gets wrong.
- Sessions are deliberately short. Completion rate matters more than session length, because the habit is what compounds.
- Progress is made visible because the effect of practice is invisible day to day, and invisible progress is indistinguishable from no progress.
- Exam-oriented routines are separated from general practice, since the two have genuinely different structures and success criteria.
Result and evidence
Practice arrives on a schedule with progress the learner can see, which addresses the failure mode the category actually has.
Commercial value
Any product in this space competes with free content. The differentiator is not the material, it is whether the learner is still using it in week four.
Readable implementation brief
implementation_brief {
project: "English Boss Bot"
core_feature: "the scheduler; exercises are content for it"
session_design: "short, sized for gaps in a day"
retention: "visible progress + streaks + performance review"
tracks: "general practice and IELTS-oriented routines,
kept separate"
competes_with: "free content -- so week four is the metric"
}What this project shows
Identifying the scheduler as the product rather than the exercises is the judgement I would point at. It determines the entire architecture.
Keeping sessions short is a decision against apparent value in favour of actual completion, and completion is the only thing that produces a result here.