Kebloom
Teachers

The Question Every EdTech Pitch to Schools Gets Backwards

Most vendors lead with what and how. Schools are buying for a completely different why.

In short

Most edtech vendors pitch schools on what their product does and how it works, but schools buy for a different why entirely: curriculum-outcome compliance, reduced teacher workload, reduced risk, and peer proof. A program earns a school's budget not by being innovative, but by solving a reporting and delivery problem the school already has to deal with.

Walk into most edtech sales pitches aimed at schools and the order is almost always the same: here's what the product does, here's how it works, and somewhere near the end, almost as an afterthought, here's why it matters. That ordering makes sense if you're selling to a consumer who's excited about a new tool. It makes much less sense if you're selling to a school — because schools aren't buying novelty. They're buying a solution to a problem they already have.

The why has to be their why, not the vendor's why

A mission statement about building confident, entrepreneurial kids is a fine thing to believe in, but it's not what gets a program past a curriculum coordinator. What gets attention is a direct line to something the school is already required to deliver and report on — a curriculum framework reference, a numeracy or enterprise-skills outcome, a wellbeing metric. The pitch that works doesn't ask a school to care about a new idea; it shows the school this is already on their to-do list, just undelivered.

Teacher workload is the real gatekeeper

Even when a principal signs off, a teacher usually has to run or supervise the thing day to day — and teachers are already at capacity. A program that requires significant lesson-plan development, new platform training, or ongoing content curation from the teacher adds friction that kills adoption no matter how good the underlying idea is. The programs that get picked up are the ones that arrive ready to run, facilitator-led where possible, with the teacher's role closer to supervision than delivery.

Risk and compliance decide more than pedagogy does

It's tempting to think the deciding conversation in a school is about teaching quality. In practice, a large share of deals are won or lost before anyone gets that far — on safety checks (working-with-children verification), insurance, and how student data is handled. These aren't exciting topics, but they're often the actual blocker between interest and a signed agreement. A program that has already solved for this removes the single biggest source of hesitation in procurement.

Peer proof beats almost any pitch

Schools are, by design, risk-averse institutions. They rarely want to be first. A case study, a quote, or simply the knowledge that a neighbouring or comparable school already ran the program and it went well does more to move a decision than any feature comparison. This is why early traction with even a handful of schools compounds — each one becomes a reference that makes the next one easier.

What actually makes a school pay

A school paying roughly $2,000 a year for a program isn't really comparing that fee to "free." They're comparing it to the real cost of building the same outcome internally — the staff hours to design a curriculum-aligned unit, source materials, manage safety and compliance, and deliver it well. Framed that way, a modest licence fee is cheap. The pitch that actually converts isn't "this is innovative" — it's "this buys back your staff's time and removes the delivery risk of doing it yourselves."

Lead with the why that's already theirs

The fix isn't complicated, even if it's uncomfortable for a vendor used to pitching its own vision: start with the outcome the school is already accountable for, show the compliance and safety groundwork is already done, point to a peer school that's already done it, and only then explain what the program actually looks like week to week. What and how still matter — but they're the close, not the opener.

Key takeaways

  • Schools buy to solve an existing reporting or compliance problem, not to adopt innovation
  • Teacher workload is the real gatekeeper — anything that adds prep time gets rejected
  • Safety and compliance (WWC, insurance, data handling) quietly kill more deals than pedagogy ever does
  • Peer proof from other schools outweighs almost any feature pitch

Frequently asked questions

Why do edtech pitches to schools often fail even with a strong product?

Because they pitch innovation and features (the what/how) instead of addressing the school's actual problem — a curriculum outcome they're required to deliver but lack time or expertise for (the why).

What stops a good edtech program from getting approved, if not the pedagogy?

Usually procurement and compliance concerns — safety checks, insurance, data handling — rather than disagreement about teaching quality. These get decided before pedagogy is even discussed.

Why does a school pay $2,000 a year for something a teacher could theoretically build themselves?

Because the real cost isn't the program fee — it's the staff time and delivery risk of building and running it in-house. A modest licence fee is cheap compared to what it costs a school to develop the same outcome internally.

This article offers general commentary on school procurement patterns for educators and program providers — it does not reflect the policies of any specific school, district, or jurisdiction.

Find a session

Live online workshops for kids (9–12) and teens (13–15) — five-day intensives and six-week programs, all year round.

Browse sessions

Keep reading