When you buy an education franchise, the franchisor's content pipeline is your product. One of the questions every buyer should ask is how current the curriculum is and who maintains it, and it sits right at the top of our due-diligence checklist for buyers. This is the full answer, stage by stage.
We start with the audience, not the content. Who the course is for, children aged 6 to 7 or 10 to 14, what they are interested in, what they care about, and what matters to their parents. Everything downstream is shaped by that.
We define the result we want by the end of the course, then break it down module by module and lesson by lesson, so every part of the program has a job. The question is not what we will cover, but what the child will be able to do afterwards.
A lead methodologist writes a short plan for each lesson, around 15 to 30 lines, setting out its purpose and target outcome. Sometimes a methodologist drafts it and the lead methodologist reviews it.
A methodologist turns that short plan into a full lesson. It includes a detailed teacher guide with a minute-by-minute plan and the goal for each stage, and a presentation built for practically every minute of the lesson: what to show, which examples to use, how to explain each idea, and which tasks to practice on.
Then the tasks are built on the platform. Some are simple in mechanic, like matching or multiple choice, but they look interactive, and the platform also has real coding environments built in: an isolated Scratch environment protected from outside changes, a built-in Python environment with its own dedicated VS Code for Algorithmics that sends student results straight back to the platform, and an HTML environment for more advanced work. The methodologist writes every automated check, every correct answer, and the code variations that should pass. For project work rather than code, they write the full grading criteria, so the teacher knows exactly what to give feedback on.
The lead methodologist checks constructive alignment: does the lesson actually produce the outcome it claims? Every method, every piece of theory, and every task has to serve that one outcome, with nothing drifting off to something else.
Take a first lesson in a programming language. It can explain how to write the first lines of code, down to print("Hello, World!"). But if the children only watch and never practice, the skill does not form. At best the child leaves familiar with a few commands. Whether that becomes a skill? Usually not. This is exactly what the review is built to catch.
The lesson goes to editing: correct language, no errors, every idea clearly and cleanly expressed.
Then technical testing: links work, mechanics are set up correctly, the lesson reads well, and someone coming to it fresh can actually solve the tasks with the information provided. It is a deliberate double-check of what the lead methodologist already reviewed.
Finally the lesson is rebuilt in the target language, which is more than translation. Locally meaningful elements are swapped so the lesson feels native, from names to imagery, and content is adapted to the cultural and religious norms of each market. The localized version is often reviewed by a local expert, usually one of the partner's own teachers, who checks the terminology, the translation, and the local details.
This is a large body of work you never have to do. As a partner you are not building courses at your kitchen table, you are delivering lessons that a full methodology, review, and localization team has already built and pressure-tested. The same team that builds a lesson is the one that keeps the curriculum current over time.
Every course this team builds, including this year's new Minecraft course with AI, maths and Python, ships to our partners ready to teach. Want to see what you would be delivering?
Message us on WhatsAppEach lesson passes through a nine-stage production pipeline before a child sees it: course design, learning-outcome mapping, lesson planning, full lesson build, platform tasks with automated checks, review by a lead methodologist, editing, technical testing, and localization. The result is a lesson that is already built, reviewed and tested, not a set of raw slides.
Methodologists build each lesson and a lead methodologist reviews it for constructive alignment, checking that it produces the learning outcome it claims. The same methodology, review and localization team maintains the curriculum over time, so a partner never has to write or update lessons themselves.
The platform has real coding environments built in: an isolated Scratch environment protected from outside changes, a built-in Python environment with a dedicated VS Code for Algorithmics that sends student results back to the platform, and an HTML environment for more advanced work. Simpler interactive tasks, such as matching and multiple choice, run on the same platform with automated checks.
Localization goes beyond translation. Locally meaningful elements are swapped so the lesson feels native, from names to imagery, and content is adapted to the cultural and religious norms of each market. The localized version is often reviewed by a local expert, usually one of the partner's own teachers, who checks terminology, translation and local detail.
No. Partners deliver lessons that a full methodology, review and localization team has already built and tested. The content pipeline is part of what you buy as a partner, which is the difference between buying a curriculum and building one yourself.
Every lesson is reviewed for constructive alignment: the theory, the methods and the tasks all have to serve the stated learning outcome. A lesson that only shows children how to write code, without giving them practice, does not form a skill, and that is exactly what the review stage is built to catch.
Updated: July 22nd, 2026