Behind the Build
Field notes from the inside of an AI-native operating company. One founder, four divisions, 123 AI Specialists. Wins, mistakes, and the architecture decisions in between — dated and real.
Sophie is the practice partner. Nigel AI is the expert coach clone for the conversation Sophie cannot have. The architectural decision the platform would not work without.
Read the post →Every piece of paid acquisition on EnglishFluency.Online runs against an ICP defined by one agent. The Audience Architect is the agent who decides who the platform should be marketing to — and, more importantly, who it should not. The decision shapes every ad, every landing page, every dollar of spend downstream.
Read the post →Sophie's voice is what the learner actually hears. Coach Speak is the agent that turns Sophie's text into audio in under a second, while preserving the warmth, the British accent, and the slight imperfection that makes her sound like a person rather than a system. The latency is the build problem. The imperfection is the design problem.
Read the post →A real advisory board costs CHF 8-15k and weeks. The Strategic Council returns the same in twelve minutes, with structure designed against convergence.
Read the post →I deleted our lead qualification form. The Diagnostic Chat Designer replaced it with a bilingual AI conversation that qualifies and demos at the same time.
Read the post →The Strategic Council surfaced a Swiss FADP audio-retention exposure I was not tracking. Within days, a nightly data-protection agent closed the gap.
Read the post →Sophie is the practice partner the learner talks to. But Sophie does not pick the conversation topic — she pulls it from the Conversation Partner agent. The Conversation Partner is the agent who decides, for each learner, what conversation they should have next, and the design decisions behind that choice are why Sophie's sessions feel personal.
Read the post →Every post on EnglishFluency.Online ships with translations into Italian, French, and German, a vocabulary list with CEFR levels, three grammar notes, and five comprehension questions. The agent who produces all of that is the Language Analyst — the one who turns each blog post into a piece of learning material, not just a piece of marketing.
Read the post →Every post on EnglishFluency.Online has a writer who decided what it says, an editor who decided whether it ships, and an SEO Specialist who decided whether anyone will find it. The third decision is the one most content operations get wrong, because they treat SEO as decoration on the writing. The SEO Specialist treats it as a parallel design problem.
Read the post →Nine specialist agents built EFO's eduQua:2021 quality dossier in three weeks. The traditional consulting cost was CHF 25,000-60,000. The architecture is also now the live QMS.
Read the post →Of the 123 AI specialists in the EFO operation, Sophie is the only one a learner actually talks to. A practice partner that fails politely is a learner who closes the tab and never comes back. The build story of Sophie: why she exists, what she does that the other 122 cannot, and the three design decisions that decide whether a practice session is the start of a habit or the end of one.
Read the post →Every learner on the platform records a 60-second speaking sample at regular intervals. The Snapshot Fluency Analyst is the agent that scores it — four sub-scores, in roughly twenty seconds, with the level of precision that a human assessor would take twenty minutes to produce. The design problem was not the scoring. It was the trust.
Read the post →When a new learner arrives on the platform, the Onboarding Placement Agent runs the first session — the one that decides where the learner gets dropped into the programme. Wrong placement means months of wasted practice. The agent has three minutes of audio and the rest of the learner's intake answers to get it right.
Read the post →A financial operating intelligence layer for a specific founder decision: where the next franc has to go. Six agents, triple-auth wall, Swiss SME context.
Read the post →