How to pitch an AI hackathon to your school leadership (and get buy-in for AI in the classroom)

Most of the teachers who email me about running an AI event at their school have already done the hard part. They get it. They've seen what a student can build in an afternoon. They want it for their kids.

What they don't have is a way through their own leadership.

"My head of school is interested but cautious." "The board will ask about cost." "Our safeguarding lead will have questions." "I don't want to look like I'm chasing a trend."

I've sat on the other side of these conversations many times now. So here's something genuinely useful — not a pep talk, but the actual playbook for getting AI in the classroom approved by people whose job is to be careful.

Start with the right ask (this is where most pitches fail)

The single most common mistake is asking for too much.

A teacher walks into the SLT meeting and says "we should embed AI across the curriculum." Leadership hears: cost, risk, training, policy, parent emails, and a multi-year commitment they can't evaluate. So they say "let's revisit this next year." And it dies.

Don't ask for the cathedral. Ask for one brick.

The lowest-risk, highest-signal version of "let's try AI" is a single-year-group hackathon day. One cohort. One day. A fixed start and end. It touches nothing else in the school. If it goes brilliantly, you have evidence and momentum. If it's just fine, nothing structural has changed and nobody's reputation is on the line.

That asymmetry is your whole pitch. A pilot is a small, reversible bet with a visible upside — and small reversible bets are exactly what cautious leadership is built to approve.

Frame the case in their language, not yours

You are excited about the technology. Your principal is accountable for outcomes. Translate.

Don't pitch "AI." Pitch the things your leadership already loses sleep over:

• Engagement. A hackathon is the most focused energy you'll see in the building all year. Heads of school routinely walk in expecting chaos and find a quiet room of kids building.
• Real student work. Not a worksheet, not a poster — a live, deployed web app with a URL every student can show their parents. That's tangible in a way most "innovation" initiatives never are.
• Admissions and parent comms. The photos, the demos, the "my kid built something on the actual internet" stories — these go in newsletters, on Open Day, in the next admissions round. Leadership understands that currency immediately.
• Future-readiness without the hand-waving. Every parent in your community is already asking what the school is doing about AI. A real, hands-on event is a far better answer than a policy document.

When you frame it this way, you're not asking leadership to bet on a technology. You're offering them a win on metrics they already report against.

Anticipate the five objections — and bring the answers first

Credibility comes from raising the hard questions yourself, before anyone else does. Here are the five that come up, and how to handle each.

"What's this going to cost?"

Be honest that there's a cost, and contain it. A single-cohort pilot is a fraction of a whole-school programme, and you can frame it as a one-off trial spend rather than a line in next year's budget. Prices vary by format and cohort size and are shown at booking — but if leadership wants market context to sanity-check the number, the Singapore and Hong Kong price-guide posts give them a frame of reference before any conversation with us.

"Is it safe for the students?"

This is the safeguarding question, and it's the right one to ask. The honest answer: we use AI tools with strong content guardrails and we monitor outputs throughout the day. Inappropriate content is essentially never an issue, and when an edge case comes up our mentors catch it and turn it into a teaching moment. Offer to put your safeguarding lead directly in touch with us — many schools want the approach documented ahead of time, and a provider who flinches at that request is telling you something.

"Won't this disrupt the timetable?"

Run it on a day that's already off-timetable — an activities day, an end-of-term day, an enrichment block. A self-contained event doesn't pull teachers out of their teaching for weeks of prep. That removes the disruption objection almost entirely.

"Our teachers don't know AI. Will they be embarrassed?"

No — because they aren't expected to lead anything technical. The mentors do that. Teachers do what they're already excellent at: pastoral care, reading the room, keeping things flowing. Most leave more curious than they came, having learned more by walking the room than they would in a formal training session. Make this explicit in your pitch, because "my staff aren't ready" is a quiet objection that kills more proposals than cost ever does.

"Isn't this just teaching kids to cheat?"

The most important reframe. Cut-and-paste cheating is a student hiding AI use to avoid doing the work. A build day is the opposite: students openly directing AI to make something that didn't exist before — and being judged on their ideas, their judgement, and what they shipped. When leadership watches a student stand up and demo a working app they couldn't have made alone, the cheating worry tends to evaporate on its own.

What evidence to bring

You don't need a research deck. You need three things that let leadership picture it concretely.

The goal is to let leadership stop imagining the worst-case version in their head and evaluate the actual thing in front of them.

What to put in the proposal

Keep your internal one-pager short. The more confined and specific it is, the easier it is to approve.

Notice what that last row does. By naming the next step, you quietly signal that the pilot is the beginning of a path — without forcing leadership to commit to the path today. You're giving them an easy "yes" now and an obvious "yes" later.

Handle the logistics so leadership doesn't have to

The proposals that get approved are the ones where the teacher has clearly already thought about the boring parts. A clean pilot day takes roughly six to eight weeks from a signed brief to the event — enough time for theme scoping, mentor briefing, tooling provisioning, photo permissions, and a parent-comms package.

If you can walk into the meeting and say "I've checked the activities-day calendar, the hall is free, I've spoken to facilities about pod seating, and the provider handles the AI accounts and deployment," you've removed nearly every reason to defer the decision.

Leadership says no to vague ideas and yes to things that look organised.

Make the first conversation easy

Here's the move I'd actually recommend. Before you go to your SLT, book a free discovery call yourself. Bring us your school's priorities and constraints, and we'll help you shape the pitch and send a written proposal a few days later. Then you walk into leadership with a real plan, real answers, and a document — instead of asking permission to go figure it out.

Or send your principal straight to our school programs page so they can see the full menu — single-year-group events, whole-school days, multi-day intensives — and picture where a pilot could lead.

You've already done the hard part by caring enough to push. The rest is just making it easy for careful people to say yes.

The students will surprise your leadership. They always do.

— Mr. Brown