Chiranjeevi Maddala
May 21, 2026
You have made the decision. The board has approved it. The subscription is signed. And now you are sitting with the question that nobody in the sales process adequately prepared you for: what do we actually do on Monday morning?
Every school leader who has implemented AI seriously has experienced the same gap. The gap between the vendor demo — polished, sequential, effortless — and the reality of an implementation that involves 40 teachers with different comfort levels, 800 students with different needs, an IT team managing a dozen other priorities, and a parent community that has heard the word AI and has opinions ranging from enthusiastic to alarmed.
This blog is for the Monday morning after the decision. It is a 90-day roadmap built from what we have learned across 30+ school implementations in India and internationally. What works, what consistently fails, and what the sequence of decisions looks like when implementation produces outcomes rather than frustration.
The 90-day framework is divided into three phases. Each phase has specific objectives, specific actions, specific people responsible, and specific indicators that tell you whether you are on track. None of it is complicated. All of it requires intention — because the implementations that fail are almost never defeated by technical problems. They are defeated by the absence of intentional structure in the critical first three months.
The first 90 days do not determine whether AI will work in your school. They determine whether your school will work with AI.
Before any teacher opens a platform and before any student interacts with an AI companion, three foundation decisions must be made. These are not technology decisions. They are governance decisions. Schools that skip them spend the next 90 days making them reactively under pressure, which produces worse decisions and more friction than making them proactively now.
Foundation Decision 1: Name Your AI Coordinator
The single most important human decision in your implementation is not which platform to buy. You have already made that decision. It is who inside your school will own the implementation on a day-to-day basis.
The AI coordinator does not need to be your most senior teacher or your most technically sophisticated one. They need to be credible with their colleagues, curious rather than anxious about new tools, comfortable asking questions that reveal uncertainty, and genuinely committed to the belief that AI can help teachers teach better. They will be the person other teachers call when something does not work as expected, the person who surfaces problems to leadership before they become crises, and the person whose enthusiasm or lack of it will determine whether the implementation spreads through peer adoption or stalls in the early cohort.
AI Ready School's implementation team works directly with your AI coordinator throughout the 90-day period. They are not alone in this role. But they must be named before the implementation begins, because every subsequent decision routes through them.
Foundation Decision 2: Define Your Baseline
You cannot demonstrate improvement without a baseline. Before your first teacher uses Morpheus and before your first student interacts with Cypher, measure what you are currently producing.
The baseline does not need to be elaborate. It needs to cover four areas. First, teacher time: how many hours per week are teachers currently spending on lesson planning, assessment creation, and progress reporting? Gather this through a simple survey of your pilot teacher cohort. Second, student outcomes: what are the current assessment results in the subjects and grade levels where you are piloting? These are your before numbers. Third, parent satisfaction: what do parents currently say when asked whether they have a clear picture of how their child is learning? Fourth, student engagement: what does current attendance data, submission rates, and teacher observation of classroom engagement tell you?
These four baseline measurements, gathered before Day 1, are what make your 90-day outcome review meaningful rather than anecdotal. They are also what give you the evidence your board needs at the end of the quarter to evaluate whether the investment is working.
Foundation Decision 3: Establish Your Communication Plan
AI implementation that is not communicated in advance becomes rumour. Teachers hear that something is changing and fill the information vacuum with their own interpretation. Parents hear that their children are using AI and fill the information vacuum with their own concerns. Neither interpretation is usually accurate and both are usually more alarming than the reality.
Your communication plan needs to cover three audiences before Day 1. Teachers: what is changing, why the school decided to change it, what it will mean for their professional life, and what support they will receive. Parents: what AI tools your students will be using, what safety architecture governs those tools, what the educational philosophy behind the implementation is, and how they will be able to see what is happening. Students: what these new tools are, what they are designed to help them do, and what the expectations for their use are.
The communication does not need to be elaborate. A 20-minute staff meeting, a one-page parent letter, and a 10-minute student orientation assembly are sufficient. What it must be is honest, specific, and proactive. Schools that communicate before the implementation begins encounter significantly less resistance than schools that communicate in response to questions after it has started.
The Objective
Month 1 has one primary objective: build genuine confidence in a focused teacher cohort. Not awareness. Not familiarity. Confidence — the ability to use the platform independently, to explain its purpose to a curious colleague or a concerned parent, and to interpret what the data is showing without needing to call a support line.
Every school that successfully expanded AI adoption beyond the initial cohort built that expansion on the foundation of a small group of teachers who were genuinely confident before the expansion began. Every school that experienced stalled adoption tried to move too many teachers too fast, produced superficial familiarity rather than genuine confidence, and then watched early enthusiasm drain away when the initial training event was over and daily questions had no credible internal answer.
Week 1: Infrastructure and Access
The first week is practical and unglamorous. Confirm that every device your pilot cohort will use can access the platform at the required performance level. Confirm that your network connectivity is sufficient for simultaneous use by your pilot group. Confirm that every teacher in your pilot cohort has working login credentials and has successfully accessed their dashboard.
For schools using Matrix on-premises infrastructure, the AI Ready School technical team handles the server installation and configuration. Your IT coordinator's role in Week 1 is to confirm that the installed infrastructure is accessible from every device your pilot will use and that the network configuration is correct. This typically takes two to three days and requires your IT coordinator to be available for technical questions.
For cloud-deployed schools, Week 1 is about confirming access, testing performance across your standard device types, and resolving any login or network issues before training begins. There is no worse way to start a teacher training session than spending the first 20 minutes helping teachers log in.
Week 2: Pilot Teacher Cohort Training
Your pilot teacher cohort is 8 to 15 teachers — roughly 15 to 20 percent of your teaching staff. They are not your department heads by default. They are your most credible, most curious, most open-to-change teachers. Your AI coordinator should have a specific rationale for each person in the cohort.
The training for your pilot cohort is not a product demo. It is a professional development experience. The AI Ready School implementation team delivers this training over two half-days or one full day, with a specific structure: philosophy first, platform second, practice third.
Philosophy first means that before any teacher touches Morpheus, they understand why the tool was built the way it was — what it is designed to produce, what it deliberately does not do, and what the teacher's role is relative to the AI's role. The teacher who understands the philosophy knows what to do when the platform produces something unexpected. The teacher who only knows the buttons does not.
Platform second means a guided walkthrough of the specific workflows the pilot cohort will use in the first four weeks: lesson content generation in Morpheus, the Morpheus student monitoring dashboard, and the Cypher student interface. Practical, hands-on, with the AI coordinator walking through the steps alongside participants rather than watching from the front.
Practice third means that before the training ends, every teacher in the cohort has generated at least one piece of their own content, has seen what a student profile looks like in the monitoring dashboard, and has experienced at least one interaction through the Cypher interface from a student's perspective. Theory without practice produces training that is forgotten by the following Monday.
Weeks 3 and 4: First Real Use and First Observations
Weeks 3 and 4 are when real implementation begins. Pilot teachers use Morpheus for at least 50% of their lesson planning during this period. Students in the pilot teachers' classes begin using Cypher. The Zion Learning Hub opens for student access.
Your AI coordinator holds a 30-minute check-in with the pilot cohort at the end of Week 3 and again at the end of Week 4. The agenda for each check-in is the same three questions. What worked as expected? What did not work as expected? What question came up that you could not answer?
The answers to the third question are particularly valuable. They reveal the gaps between what the training covered and what real implementation requires — which is always different from what training designers predicted. These gaps should be logged, shared with the AI Ready School implementation team, and addressed in supplementary resources before Month 2 begins.
Month 1 Success Indicators
By the end of Month 1, you should be able to confirm: every pilot teacher has used Morpheus for lesson planning at least five times and can do so independently. Every pilot teacher's students have had at least 10 Cypher interactions and the monitoring dashboard is showing live learner data. Your AI coordinator can answer the most common teacher and parent questions without consulting external support. And your baseline measurements are documented and stored for comparison at Day 90.
The Objective
Month 2 has two parallel objectives: deepen the practice of your pilot cohort and begin the organic expansion to interested colleagues outside the cohort. The expansion must be organic — driven by peer curiosity rather than management mandate — to produce the durable adoption that mandate-driven expansion cannot.
Week 5: First Monitoring Dashboard Review
By Week 5, your pilot teachers have enough Cypher student interaction data to see meaningful patterns in their Morpheus monitoring dashboards. Schedule a one-hour dashboard review session with your pilot cohort and your academic coordinator. This session is the most important event in Month 2.
The dashboard review should focus on three questions. What is the data showing you that you did not already know? What does it suggest you should do differently? And what question does it raise that you cannot yet answer?
At B.P. Pujari Government School in Raipur, the first dashboard review was the moment the academic coordinator understood that a student who had been scoring consistently 68 to 74% across two academic years had a specific algebraic misconception from Grade 6 that was silently propagating through seven Grade 8 topics. The monitoring dashboard did not tell the coordinator what to do. It told her what to look at. The professional judgment about what to do was entirely hers. That is exactly how the relationship between AI data and teacher authority should work.
Weeks 6 and 7: Peer-to-Peer Expansion
Create two structures that make following easy. First, schedule open classroom sessions where pilot teachers invite one or two colleagues to observe a lesson where Cypher and Morpheus are in active use. Not a demonstration. A real class. The observer sees what the tool looks like in an actual teaching situation, which is different from what any demo can show. Second, schedule informal conversations — not formal meetings — where pilot teachers talk to their colleagues about their experience honestly, without management present.
By the end of Week 7, the teachers who want to join the implementation because their colleagues have made it look genuinely useful will begin expressing interest. These are your next cohort. Do not make them wait.
Week 8: Second Cohort Onboarding and Zion Expansion
The second teacher cohort begins their training. This training is shorter than the pilot cohort training because your AI coordinator is now experienced enough to lead significant portions of it independently. The AI Ready School implementation team provides the framework. Your AI coordinator provides the credibility.
Simultaneously, Week 8 is when Zion's Creative and Research Hubs open for student access, expanding the platform's student-facing footprint beyond the Learning Hub available in Month 1. Your IT coordinator confirms the access controls are correct for each grade level before the expansion goes live.
Month 2 Success Indicators
By the end of Month 2: your second teacher cohort has begun active platform use. Zion Creative and Research Hubs are in student use. The Morpheus monitoring dashboard has surfaced at least three specific student learning insights that were not visible through traditional assessment. At least two teachers from outside your original pilot cohort have requested access based on what they observed from colleagues. And your parent communication channel has received specific, curious questions rather than alarmed ones.
The Objective
Month 3 is about producing the outcomes that justify the investment and building the institutional structures that sustain the implementation beyond the 90-day period. Depth, not expansion. The schools that expand too aggressively in Month 3 produce superficial adoption across the school. The schools that go deeper with their existing cohort produce the evidence and the internal culture that makes full-school expansion in Month 4 and beyond genuinely transformative.
Weeks 9 and 10: Project Hub and NEO Introduction
If your school has a NEO AI Innovation Lab, Weeks 9 and 10 are when it begins active use. The students who have shown the most curiosity and engagement during the Cypher and Zion Learning Hub phase are introduced to the NEO curriculum and the Project Hub tools. These students will become the school's most visible AI capability examples — whose projects, research, and competition participation will make the program credible to parents, prospective families, and board members in ways that no marketing can match.
For schools without NEO, Weeks 9 and 10 focus on deepening Zion Project Hub use with interested students. The AI Coding Playground, Teachable Machine, and App Builder are introduced through teacher-facilitated project assignments rather than open access. Students who are introduced to Project Hub tools through a defined project brief produce better work and develop more genuine capability than students given open access without pedagogical scaffolding.
Week 11: Mid-Quarter Assessment and Data Review
Week 11 is a formal pause. Your AI coordinator, academic coordinator, and principal sit together with the 45-day outcome data and ask three questions: what has changed, what has not changed, and what does that tell us about what we should do differently in the final two weeks and in Month 4?
The data you examine should include Morpheus monitoring data, updated student assessment results, teacher time survey data compared to your Month 1 baseline, and parent satisfaction indicators. You are not looking for a complete vindication of the investment. You are looking for specific evidence of movement in specific directions — and specific evidence of what has not moved and why.
This mid-quarter review is the conversation that most schools have at the end of the year, when it is too late to adjust. Having it at Week 11 gives you four weeks to act on what it reveals before your 90-day report to the board.
Week 12: Board Report and Month 4 Planning
The 90-day board report is the accountability document that transforms your implementation from a management initiative into a school governance commitment. It should contain four things: what the implementation set out to achieve, what baseline measurements you established before Day 1, what the current measurements show, and what the plan for Month 4 and beyond is based on what you have learned.
Be honest about what has not worked as well as what has. Boards that receive honest reports build more trust in the implementation process than boards that receive only positive ones. The board that knows you are measuring accurately is the board that will approve Month 4 investment.
Simultaneously, your AI coordinator is developing the Month 4 plan: which teachers join the platform next, what the student access expansion looks like, what the first formal parent information session covers, and what the outcome targets are for the next quarter.
Month 3 Success Indicators
By Day 90: more than 50% of your teaching staff is actively using Morpheus. Every student in the pilot teachers' classes has an established Cypher learner profile with at least 30 sessions of interaction data. Your board has received a specific, evidence-based 90-day report. Your AI coordinator has developed the Month 4 plan. And at least one parent has told another parent something specific and positive about what they can see through the platform — because peer-to-peer parent advocacy is the most powerful form of school AI communication that exists.
In 30+ implementations, we have seen the same mistakes made repeatedly. Each one is avoidable. Each one is more expensive to fix after the fact than to prevent in advance.
Launching with all teachers simultaneously. The school that trains 80 teachers in a two-day event produces 80 teachers with surface familiarity and no internal champions. The school that trains 12 teachers deeply produces a cohort whose confidence drives organic expansion more durable than any mandate.
Skipping the baseline measurement. You cannot demonstrate improvement without a before number. Schools that skip baseline measurement spend their 90-day board report saying "we believe outcomes have improved" rather than "outcomes improved by these specific measures from these specific baselines." Boards know the difference.
Treating the implementation as an IT project. Giving ownership of AI implementation to your IT coordinator rather than your AI coordinator is the most common structural mistake we see. IT coordinators own the infrastructure. The AI coordinator owns the culture, the teacher development, and the outcome measurement. These are different roles and different people.
Communicating with parents after the questions start rather than before. The parent who received a letter explaining the implementation before their child mentioned it at dinner is a curious parent. The parent who first heard about it from their child is an anxious parent. The communication investment before Day 1 is the cheapest parent relationship management you will ever do.
Measuring activity instead of outcomes. Login counts, session numbers, and feature usage statistics are not outcome measurements. They are activity measurements. Define your outcome metrics before Day 1 and measure them specifically at Day 90.
The 90-day roadmap is the beginning of an implementation, not the completion of one. By Day 90, if the roadmap has been followed with intention, your school has a foundation: a confident teacher cohort, an established learner profile for every student in the pilot, a monitoring dashboard surfacing insights that traditional assessment never surfaced, a parent community that understands what is happening and why, and a board that has received an honest, evidence-based account of what the first quarter produced.
The expansion that comes after 90 days builds on that foundation. It builds on evidence. The school that has 90 days of documented outcomes to point to is the school that expands with confidence. The school that skipped the foundation expands with hope and discovers, too late, that hope is not a strategy.
The first 90 days are not about perfection. They are about foundation. Build the foundation right and everything that comes after is construction. Skip the foundation and everything that comes after is repair.
Download the 90-Day Implementation Checklist
AI Ready School provides a complete AI ecosystem for K-12 schools including Cypher (personalised learning companion), Morpheus (AI teaching agent), Zion (safe AI tool suite), NEO (AI Innovation Labs), and Matrix (sovereign AI infrastructure). Implementation support is included in every partnership.
To download the 90-day implementation checklist or discuss your school's implementation roadmap, reach out at hey@aireadyschool.com or call +91 9100013885.
.png)
