Every school we talk to asks the same question within the first ten minutes, and they ask it warily, because they have heard a lot of promises from a lot of education software. The question is: if every student is writing every day, who reads all of it? The honest answer is the one that makes the rest of the conversation possible. Nobody reads all of it. Not the teacher, not an army of assistants, not the founder. The system reads it. The teacher is freed to do the one thing software cannot do — sit with the child who is stuck and talk to them. That inversion is the whole product, and everything below is a description of how it plays out in a real building with real timetables.
The unit is the student, not the class
A traditional language classroom moves as a convoy. Everyone is on chapter four. Everyone does the same worksheet. The fast students are bored, the slow students are lost, and the teacher aims at the middle because there is no other option when thirty people must be served by one set of instructions.
Storica does not move as a convoy. On day one, each student picks a book from a shelf appropriate to their level — a true beginner might take an A1 reader, a confident fourteen-year-old might take Kafka at A2+, another might be deep in Austen at B2. Thirty students, potentially thirty different books, all running the same daily rhythm: read a passage, write a short response, get specific feedback, continue. The rhythm is shared. The content is individual. This is the part that does not scale with teachers and worksheets and does scale with software, which is exactly why software should do it.
What makes this pedagogically honest rather than just logistically clever is that the book each student reads next is not chosen by difficulty alone. It is chosen by what their writing revealed. A student whose responses never name an internal state — who writes "I was happy, then I was sad" and nothing underneath — will start to encounter books that quietly foreground characters with richer emotional vocabulary. Not a drill. Not a flashcard deck. Exposure, in context, to the language they are missing. They absorb it the way children absorb a first language: by meeting it in something they actually want to read.
What the teacher actually sees
The teacher does not get a pile of essays. The teacher gets a screen. One class, every student on it: where each child is in their book, how many days they have been active, where their writing is developing, where it has stalled, and — crucially — a short list of who needs a human this week and why.
"Arda's last three responses came back under twenty words; he may need a different book — try one with more action." "Zeynep's emotional expression jumped this week; worth a note home." The diagnostic work — the slow, unscalable reading of thirty pieces of student writing every single day — is done by the system. What surfaces to the teacher is judgment-shaped: not here is the data, but here is the child to talk to, and here is what to talk about. You can see the live version of this — the same screen a teacher would actually use — at storica.club/dashboard.
Schools sometimes assume this means the teacher matters less. It is the opposite. The teacher's time is the scarcest, most expensive, most valuable resource in the building, and Storica spends every minute of it on the part of teaching that is irreducibly human — sitting next to a struggling student and coaching them — instead of on the part that is mechanical and miserable, which is marking. A teacher who is not buried in grading is a teacher who can teach.
What the parent receives
For a private school in particular, this slide of the story is more important than it first appears. Parents are paying — often a great deal — and the standard artifacts of school progress (a grade, a percentile, a generic comment) tell them almost nothing about whether their child can actually use the language. Storica's parent report does something a grade cannot. It puts the child's own writing side by side, eight weeks apart.
Week one: "I went to the park. I was happy. Then it started to rain and I was sad. I went home." Twenty-one words, two feeling-words, five unique verbs. Week eight, same prompt: "I went to the park alone. I felt invisible in the crowd. The rain came suddenly and I felt small, like the people in my book." Thirty-eight words, four feeling-words, nine unique verbs — and a sentence that simply did not exist eight weeks earlier. The parent does not need a rubric explained to them. They can read it. They have a story to tell about their child's English, and it is true. You can see the parent-facing version at storica.club/dashboard/veli.
How a school actually starts
No school should — and no good school will — roll a new method out to every class on a vendor's say-so. So we do not ask them to. The shape that works is a term-long pilot with one or two cohorts. The school needs three things, and only three: devices the students already have (a tablet, a Chromebook, a phone — we do not sell hardware), fifteen minutes of class time three times a week, and one coordinator from the language department who is our point of contact. That is the entire ask.
The timeline is deliberately unglamorous. Week one: a half-day of teacher onboarding, student accounts created, a baseline writing sample captured, and every student choosing a first book — agency from the first day, which matters more than it sounds. Month one: by the fourth week the dashboard has accumulated enough writing to be genuinely useful, and the first coaching conversations happen on real student work rather than on guesses. End of term: a measurement on the seven developmental dimensions we track, side-by-side writing samples for every student, and a document the school can take to parents or to a board. The pilot ends with evidence, not with a renewal pitch.
What changes over a term — and what we will not claim
In pilot cohorts we have seen vocabulary range in student writing rise meaningfully, syntactic complexity increase (more subordination, fewer fragments), and — the one teachers care about most — several hours of teacher time recovered per week because the grading bottleneck is gone. Parent satisfaction is high, for the reason described above: they can finally see the thing they are paying for.
Here is what we will not do. We will not pretend these are universal numbers, or that they will be identical at your school, or that a tool changes outcomes without good teachers using it well. The honest version of the pitch is this: if a school runs a real pilot, the numbers from that pilot become their numbers, measured on their students, baseline at week zero and again at week twelve. We would rather commit to a school's real data than wave someone else's around. A method that works should be willing to be measured on the people who doubt it.
Why this belongs in a school and not only in an app
Storica works as a consumer product — people read on their own, every day, and get better. But a school adds something a phone in a teenager's pocket cannot: accountability, rhythm, and a teacher who notices. A disengaged student does not acquire language, and engagement is not a marketing input — it is a pedagogical one. Real books, level-tuned but never dumbed down, are read more than worksheets are, and a student who reads more produces more, and a student who produces more is the only kind of student who actually becomes fluent. The classroom is where that loop has the best chance of closing, because the classroom is where someone is paying attention.
That is the entire argument. Reading you can't fake, writing that is actually the student's own, a teacher freed to coach, and a parent who can finally read the progress for themselves. Schools that want the longer version, in Turkish, can find it at storica.club/tr/okullar.
I'm one of the makers of Storica, a daily reading club for the language you're learning. For schools, we run term-long pilots with one or two cohorts — fifteen minutes a day, real books, no grading pile. The teacher and parent dashboards are live to explore at storica.club/dashboard.