Most New Zealand schools don’t feel underserved by EdTech. They feel buried under it.
The platform was supposed to save time. Instead, it became another column in the marking workflow, another login in the morning, another tab open during a department meeting.
What schools think is happening vs what is actually happening
What schools think is happening: A digital platform was rolled out, students and teachers have access, and value should now flow through naturally.
What is actually happening: The platform sits on top of the existing workflow rather than inside it. Teachers do their normal planning, marking and feedback — and then update the platform. Students complete their normal homework — and then log activity. Everyone is doing two versions of the same job.
Six months in, the school looks at usage data, sees inconsistency, and concludes the platform “didn’t deliver.” The platform delivered exactly what was asked of it. The implementation never integrated it into anything.
Why this keeps happening
The pattern repeats because the buying decision and the integration decision are usually made by different people, in different rooms, at different times.
- Tools are evaluated on features, not on workflow fit. The decision is “does this platform have X?” — not “where does this replace something we already do?”
- Integration is treated as a launch task. Once the rollout is done, no one revisits whether the platform actually changed how the week works.
- Existing routines stay untouched. Marking books, spreadsheets, paper feedback, and parent emails continue running in parallel.
- There is no operational owner. Curriculum leaders own the academic side, IT owns the technical side, and the workflow in the middle has no obvious owner.
- Teachers are asked to “use the platform” rather than to deliver an outcome with it. Activity becomes the goal, not impact.
The platform isn’t the problem. The platform is being added to a system that hasn’t moved to make space for it.
The consequences
When EdTech sits on top, the school quietly pays twice — once for the licence, and again in teacher time.
- Teachers feel slower with the tool than without it. Internally, they revert.
- ROI conversations turn into login-rate conversations, because no one can pull a clean before/after of teacher time or student outcomes.
- Heads of Department lose appetite for the next tool. They’ve seen what the last one did to their team’s hours.
- Senior leadership ends up justifying a contract instead of evaluating an outcome.
- Parents quietly stop hearing about the platform, because there is nothing concrete to share.
The frustration isn’t usually with the technology. It is with the realisation that nobody is sure what the platform replaced.
What actually works
Schools that get genuine ROI tend to be ruthless about workflow integration.
- Map the current workflow before buying. Lay out exactly how a teacher in Year 11 maths spends their non-teaching time. The platform is only worth bringing in if it visibly removes part of that.
- Define “what comes off the desk.” For every routine the platform takes over, document what stops. If marking moves into the platform, the marking book stops. If feedback moves into the platform, the email feedback stops.
- Run a 4-week integration sprint, not a launch event. The first month should be about removing parallel work, not adding new features.
- Track teacher time, not just student logins. ROI on EdTech in schools is mostly a workload metric. Hours saved per teacher per week is a far more honest measure than DAU.
When the school is willing to retire processes — not just stack new ones — ROI becomes visible quickly.
A note from working with schools
In our work with schools, the platforms that deliver real ROI usually look unimpressive in the first week. Nothing exciting happens. What changes is the slow disappearance of parallel workflows — the marking spreadsheet that used to take 2 hours, the feedback email that used to take an evening, the manual progress sheet for parent reports.
That is what ROI looks like in practice. It rarely shows up in a launch deck.
If this sounds familiar…
If your school is currently using one or more EdTech platforms but the time saved isn’t showing up — or if teachers are quietly running the platform alongside the old workflow — it may be worth stepping back to look at the integration, not the tool.
We regularly work with New Zealand schools to:
- Audit which workflows the platform was supposed to replace.
- Identify where teachers are doing parallel work without realising it.
- Restructure routines so the platform sits inside the week, not on top of it.
This is not about pushing a different platform. It is about helping schools recover the value the existing platforms were supposed to deliver.
A short conversation
If this is something you’d like to explore further, we’d be happy to have a short consultation to understand your current setup and share a structured perspective on where the ROI is leaking.
From there, if there is alignment, we can also explore how platforms like AI Buddy fit alongside the right academic and operational support — so the next contract pays back instead of piling up.