| Counterparty | Why the lane exists |
|---|---|
| Districts and charter networks | Need one lane for multi-school rollout, family communication, and phased procurement. |
| Ministries and public systems | Need a staged path that starts with named surfaces and multilingual deployment instead of an abstract platform pitch. |
| Foundations and conveners | Need a credible operating partner for place-based or public-interest learning deployments. |
| SKU | Status | What the operator can inspect now |
|---|---|---|
| The Daily Lesson | Live now | One shared lesson every day across 365 calendar-locked days, 4 tracks, and 19 lesson languages. |
| Kelly guided delivery | Live now | A recognizable teacher surface with teaching-style adaptation, voice, and learner-facing continuity. |
| Word Orb API | Live now | Verified vocabulary, structured lessons, quiz endpoints, translations, and developer pricing. |
| District rollout lane | Pilot ready | A multi-school rollout lane focused on family continuity, translation, procurement, and phased deployment. |
| Global education directory | Pilot ready | A searchable directory, taxonomy, claim flow, and lane routing layer for institutions and learners. |
| Access and offline pack | Design stage | Device and offline access remain staged, not falsely sold as a fully live institutional SKU. |
| LOTD brings | The operator brings |
|---|---|
| Live learner surface, Kelly, language API, and one routed partner lane. | Real learners, deployment context, local constraints, and decision-making clarity. |
| Multilingual lesson and assessment infrastructure that can be inspected before rollout. | Language priorities, local standards, accessibility requirements, and distribution reality. |
| A staged path that can start with a pilot instead of an all-at-once system promise. | A first proof target: engagement, language support, family continuity, or partner fit. |
Use this checklist before the first institutional call so the conversation starts with the real operating questions, not generic enthusiasm.
| Step | Checklist item | Why it matters |
|---|---|---|
| 1 | Pick the first 2-5 sites | Choose the smallest multi-site footprint that still proves coordination, family continuity, and language support. |
| 2 | Map family and translation requirements | Name the communication, language, and accessibility obligations before the first learner sees the product. |
| 3 | Define the approval path | List procurement, curriculum, innovation, or foundation stakeholders who must clear the first phase. |
| 4 | Decide the reporting shape | Be explicit about what a successful first phase needs to show across schools, cohorts, or regions. |
| 5 | Lock the 30/60/90-day proof plan | Set the operating rhythm now so the rollout is measured against real checkpoints instead of optimism. |
If this fits, send the lane-specific intake below. LOTD will see the page, the route, the source tags, and the operating context instead of receiving another generic contact note.
Use this intake if you are coordinating more than one site and need the rollout framed in plain terms: who the learners are, what the language needs are, what the family continuity risk is, and what a realistic first phase looks like.
District-scale credibility comes from phased rollout, not from pretending one purchase order solves the entire system.
Use this lane when more than one site is in play.