Grassroots Education school-built & school-owned technology

From first tool to whole-school culture

This approach starts with individual teachers building things that work, then grows deliberately - stage by stage - into something the whole school owns.

The three stages

From the first training session where teachers make their own purposeful applications, you are in control of how far and how fast you travel.


1
Stage 1

Staff capability

Teachers learn to build their own web applications using Google Apps Script, matched precisely to their own needs, their own students, and their own workflows. From the very beginning this includes working with AI APIs and other external services, so staff develop a genuine understanding of what these tools can do rather than just using them at surface level.

The measure of success at this stage isn't attendance at a training session. It's a working app, built by a real teacher, solving a real problem, and colleagues noticing. There will be teachers who will thrive with this level of empowerment.

Apps Script web appsForms, dashboards, and tools that live in Google Workspace and do exactly what the teacher needs.
AI and API integrationCalling AI services, working with external APIs, understanding how to get useful output from a prompt whilst protecting students and data.
Real apps from day one Generate a document, share it, email it. Process files in bulk. Connect to an external API. The starting point is always a real need; the method follows from that.
Confidence through makingNot awareness. Not training. A working tool — and the knowledge of how to build the next one.
Stage 1 is where teachers learn how to create web apps and become enthused by making genuinely useful tools to save time and improve learning.
↓
2
Stage 2

Shared framework

Once individual teachers are building, the next step is giving everything a common foundation. This is where isolated apps become part of a coherent system: sharing data, sharing style, sharing guardrails, and sharing the infrastructure that makes AI use safe, logged, and purposeful.

This stage introduces two key tools. The student database app makes school data accessible to any app without requiring direct spreadsheet access: searchable, filterable, and exportable to a formatted Google Sheet in seconds. The school's own bespoke prompt builder will give every AI-powered app in the school a common starting point: shared styling, shared knowledge of where data lives, built-in guardrails, and automatic logging to a shared audit file.

Common data accessSchool student data structured, searchable, and exportable — ready to power any app without touching the underlying spreadsheet.
Shared CSS and stylingA common stylesheet so every staff-built app looks coherent and professional, not like a collection of experiments.
School API keysCentrally managed access to AI services — staff build on top of them without needing individual accounts or keys.
Common log filesEvery AI interaction across every app writes to a shared log. Usage is visible, auditable, and reviewable by leadership.
Prompt builder appA shared tool for designing AI prompts that automatically applies school guardrails, accesses the right data, and logs every use.
Log analysis appA dashboard that reads the shared log and surfaces patterns — which apps are being used, by whom, and to what effect.
Stage 2 is where individual capability becomes collective infrastructure. The school stops having a collection of apps and starts having a system.
↓
3
Stage 3

Whole-school culture

By this point the school has working infrastructure, staff who know how to build, and a shared system for safe and purposeful AI use. The work now is consolidation, expansion and confident exploration.

This is where the school begins to engage with the next generation of AI capabilities: agents, multi-step workflows, AI-generated video, audio, and images; not because they're new, but because the school now has the understanding and the infrastructure to approach them purposefully rather than reactively.

ConsolidationRefining what exists, sharing what works, retiring what doesn't. The system becomes simpler and more reliable over time.
New technologiesAI agents, multi-step workflows, and emerging tools, explored with confidence because the foundations are in place.
Video, audio, and image AIPurposeful use of generative media tools, integrated into the school's existing framework and logging infrastructure.
Staff as innovatorsTeachers who started as users of apps are now designers of them, identifying needs, proposing solutions, building and sharing.
Student empowermentStudents who understand how the tools work, can use them purposefully, and, where appropriate, contribute to building them.
Replacing subscriptionsAs school-owned tools mature, they may outperform the off-the-shelf platforms currently being paid for, purpose-built for the school's exact needs, at zero cost.
Self-sustaining cultureThe school no longer needs external support to move forward. The capability, the infrastructure, and the culture are all its own.
Intended outcome

The goal is not for a school to use AI

The goal is for a school to develop the internal capability to decide how, when, and why on its own terms. That means moving from scattered experimentation to confident, school-owned practice.

Staff who build tools, not just use them
School data accessible without spreadsheet access
AI use that is logged, auditable, and purposeful
Common infrastructure owned entirely by the school
A culture of innovation that grows from the classroom up
No ongoing dependency on external platforms or providers
Next page

stage 1: micro-solutions

A closer look at the sort of applications that teachers will learn to make straight away and their potential impact.