What Happens After the Demo? The Missing Phase in EdTech Adoption Across New Zealand Schools

Most EdTech conversations in New Zealand schools end at the demo and the contract.

The conversation that actually decides whether the platform works — the one about Day 30, Month 3, and sustained usage — almost never happens.

What schools think is happening vs what is actually happening

What schools think is happening: A clear demo led to a confident decision. Once teachers and students are onboarded, adoption naturally follows.

What is actually happening: The first two weeks are powered by novelty. Around Day 21, novelty fades. Without an explicit plan for what happens next, usage slowly drifts. By Month 3, the platform is technically live but practically optional — and nobody has a forum where this is acknowledged.

The school didn’t make a bad buying decision. The school made a strong buying decision and then stopped paying attention at exactly the wrong moment.

Why this keeps happening

The post-demo phase has no structural ownership in most schools.

• Vendors plan for the close, not the routine. Sales effort is highest before the contract; support effort drops afterwards. That is normal commercially, but schools rarely budget internal attention to fill the gap.
• Internal energy is spent on launch. Communications, training, parent emails — all weighted to week one.
• No one owns the dip. Around weeks 3 to 6, engagement nearly always softens. Without an internal owner, this dip is read as failure rather than as a normal part of adoption.
• Routines are not pre-defined. What teachers and students should be doing in week 8 was never written down. So in week 8, they are doing whatever still feels natural — which usually means less.
• There is no review forum past the launch meeting. The platform stops appearing on the SLT agenda, and absence of attention becomes absence of expectation.

This is why so many EdTech rollouts feel strong for a fortnight and then quietly collapse.

The consequences

The post-demo gap is where most of the long-term cost is hidden.

• Renewal conversations turn awkward. Nobody is sure whether to renew, and nobody is sure how to honestly explain why.
• Teachers stop seeing the platform as core. It becomes “the thing we tried.”
• Students disengage selectively, and the school learns the wrong lesson — that students “didn’t take to it.”
• Heads of Department lose appetite for the next rollout, because the post-demo dip is what they remember.
• Senior leaders feel they’re investing in EdTech without measurable return. They are — but the cause is the missing operating phase, not the tool.

The result is a culture that gets cautious about EdTech without ever naming why.

What actually works

Schools that sustain adoption past the demo phase tend to design the boring middle deliberately.

1. Plan Day 30 before Day 1. Write down what every Year 11 student and Year 11 teacher should be doing in week 4, in plain language. If you can’t describe it, you don’t have an adoption plan — you have a launch.
2. Protect a monthly review for the first quarter. A 30-minute SLT slot at Month 1, Month 2, and Month 3 to review actual usage, not aspirations.
3. Pre-empt the dip. Tell teachers, on day one, that engagement will soften around weeks 3–6, and that is normal. Lower the chance of misreading the dip as failure.
4. Identify the leading indicators. Don’t wait for outcome data. Look at consistency of weekly usage, percentage of teachers reviewing dashboards, and the rate of intervention triggered. These tell you the operating model is alive long before grades do.

The pattern is unromantic but reliable: the schools that win past the demo are the ones who treat the middle as the project.

A note from working with schools

In our work with schools, the most successful adopters are not the ones with the most enthusiastic launch. They are usually the ones with the calmest Month 2. The launch is fine — well-organised, modestly attended, professional. What’s different is that someone is still actively running the implementation in week 8, and the SLT is still getting a clean update on it in week 10.

That continuity, more than any feature or training programme, is what compounds into sustained usage.

If this sounds familiar…

If your school has live EdTech platforms but isn’t sure whether they’re being used the way they were meant to be — or if past rollouts felt strong then mysteriously softened — it may be worth stepping back to evaluate the post-demo operating model.

We regularly work with New Zealand schools to:

• Map what an honest Day 30 and Month 3 currently look like in your school.
• Build the routines and review forums that hold adoption past the launch energy.
• Identify the leading indicators that show whether the platform is actually shaping teaching and learning.

This is not about replacing the platform. It is about making sure the school is set up to keep it alive past week three.

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 the post-demo phase.

From there, if there is alignment, we can also explore how platforms like AI Buddy fit alongside the right academic and operational support — designed to be sustained, not just launched.