Built by a working Instructional Technology Coordinator who has led AI enablement for more than 15,000 students and staff across seven high schools - not a consultant who discovered ChatGPT last year.
Part of my own journey to help teachers harness AI meant learning how to build agentic AI with AI Her Way, the leading AI education company for this kind of work. I combined that with my own experience providing professional development to more than 15,000 people, plus the rollout blueprint I wrote in my book, to build one solid program your district can use starting now. Districts are cutting instructional technology budgets and positions right when staff need this kind of support the most. Think of me as your external instructional technology partner: someone who already knows the classroom, the leadership side, the PD calendar, and every piece of how a rollout like this actually sticks, not just how it launches.
Modules 0 through 10. Lesson planning, classroom culture, assessment and feedback, student support, family communication, teacher operations, professional growth, and more. Over 45 files per teacher, starting with TEACHER.md, that build out all 8 teaching departments. One system that travels across any AI tool: Claude, Gemini, ChatGPT, or whatever comes next. Built around real teacher archetypes - Innovators, Skeptics, the Overwhelmed, Pragmatists. Each one gets an entry point that fits, not a single mandatory path.
A step-by-step guide for your instructional coach, tech lead, or department head to bring the whole staff along. Momentum from the middle, not a mandate from the top. A pacing wizard that builds a custom calendar around your district's actual PD schedule, so no staff member is stuck to a one-size-fits-all timeline. Sample kickoff letters, staff launch emails, and an admin ask template, so your rollout leader isn't starting from a blank page.
AI Lab for Educators. A living community, not a one-and-done training. Build Parties (building with our AI systems live), prompt libraries, and direct access to me as new AI tools and systems roll out. Your staff stays current long after the initial rollout.
Good context means AI gets it right closer to the first try. Fewer regenerations, fewer new-chat do-overs, less compute and less energy for the same result.
No student data required for any of it to work. Human-in-the-loop is built into every file: AI drafts, a person decides. Aligned to responsible-use guidance, not just "we thought about it." This isn't a policy memo attached after the fact - it's how the files themselves are built.
Three example ways staff can run this. Safety and governance come first in every one. Instructional technology and IT leaders tend to ask the same question first: how much does this actually touch our systems? There is more than one right answer.
A teacher works from a personal AI account (Claude, Gemini, or ChatGPT) on their own device. They bring the curriculum, pacing guides, and calendar out to the system, rather than bringing the system into the district. Never student names, IDs, or protected records. No software install, no admin rights, no district system involved. The lightest possible lift.
Staff who live in Google Workspace attach the same files to a custom Gemini Gem (a saved, purpose-built bot). The Gem becomes a saved assistant that already knows the teacher's voice, students, and governance rules. Works inside tools your district has likely already vetted and approved. ChatGPT Projects, Claude Projects, and Copilot agents have similar functions as Gems.
A coach or teacher builds their files locally first: TEACHER.md, department files, governance.md. A district-approved connected tool, think Claude Cowork, points at those same files to read and act on them. Files stay local and reviewable. Nothing moves to a new vendor database to get this benefit. Some connected systems can run on a schedule, working on their own between check-ins instead of waiting for someone to prompt them each time.
Every skill file in the system points back to one shared file, governance.md, covering student privacy, FERPA awareness, human-in-the-loop review, and an explicit override principle: the human leads, always. That file is not locked inside a vendor's backend. It is plain text your district can read, mark up, and edit before rollout, then the edited version becomes what every staff member downloads from day one. Because the system is tool-agnostic (Claude, Gemini, ChatGPT, or Copilot), IT is not being asked to procure or approve one specific enterprise AI product. Because the files themselves live locally rather than in a new vendor database, this also carries a meaningfully different data-risk profile than a typical SaaS ed-tech tool.
Any staff device with a current browser (Chrome or Safari) and internet access. No special specs beyond a normal staff laptop.
One personal AI account per staff member. Free tiers work for most of the course; a paid plan helps on longer tasks but is not required to start.
Flat-rate, school-wide licensing for up to 35 staff. All options include the full Teacher AI OS curriculum, both Gems, AI Lab community, and the human-in-the-loop framework. Custom quotes for larger staff or multi-building schools. Virtual only; in-person availability starts Summer 2027.
Full course access, all 8 departments, self-paced.
Everything in Option 1, plus one 2-hour live Build Party onboarding with Katie.
Everything in Option 2, plus a 2nd school-only Build Party, monthly subscriber Build Parties, superintendent and admin content at founder rate, and new modules and skill files as they drop.
Quotes turn around within 48 hours. Certificates of completion with clock hours are available for teachers who need them for license renewal. Email [email protected] with your district, role, staff count, and timeline to get started.
If your rollout leader wants the thinking behind the tools, not just the how but the why, I recommend picking up a copy of my book, AI Blueprint for Schools, for whoever leads your rollout.
M.Ed · Author · Instructional Technology Coordinator
