Education is one of the few markets where the product's users — students and teachers — are almost never the buyers. The buyers are principals, boards of trustees, head office curriculum teams, and increasingly, district-level digital strategy leads. The product has to satisfy two entirely separate value propositions simultaneously: it has to be something a teacher will actually use and find useful, and it has to be something a procurement decision-maker can justify to their board. Those two value propositions frequently diverge. A tool that teachers love because it reduces marking time may be a hard sell to a principal whose budget process evaluates against NCEA achievement data. A tool that shows up well in a randomised controlled trial may be deeply resented by teachers who feel it replaces their professional judgment with an algorithm. Getting this right requires having been inside the institution — not just having visited it.
Operator-founder fit in EdTech means something specific that goes beyond the general "founder who has faced this problem" heuristic. It means the founder understands the decision architecture of their buyer: who holds the professional development budget versus the software licensing budget versus the capex allocation, and how those three pools interact in an annual planning cycle. It means they understand the compliance layer — in New Zealand, the specific requirements of the Privacy Act 2020 as it applies to student data, the NZQA rules around assessment evidence storage, the way ERO review cycles create specific windows of institutional anxiety where new tools get adopted quickly or deferred indefinitely. And it means they understand that the implementation support burden in education is asymmetrically high: schools do not have dedicated software administrators. A teacher who encounters a friction point in your onboarding flow on a Monday morning before first period will not submit a support ticket. She will stop using the tool.
The founders who navigate this well share a few characteristics that we have learned to look for. First, they have an explicit theory of teacher time — they can tell you exactly how many minutes per week their tool adds to or removes from a teacher's workload, for which tasks, at which point in the school year. Founders who can't answer this question haven't spent enough time observing real classroom practice. Second, they have relationships with at least one school senior leadership team who will give them honest feedback, not just encouraging pilot sign-offs. The difference between a trial that runs for a term and a renewal that gets budgeted is almost always about whether the principal believes the tool is aligned with the school's strategic priorities, not whether teachers found it useful. Third, they have a working theory of channel — whether they're selling direct-to-school, through a cluster or kāhui ako arrangement, through a Ministry-level platform deal, or through a curriculum publisher partnership. All of these are real paths to scale in Australasian EdTech, but they require different go-to-market muscles and different product surface areas.
We are not saying that founders without a teaching background can't build excellent EdTech. Some of the most technically sophisticated adaptive learning systems have been built by people who came through consumer software or enterprise ML, not classrooms. What we are saying is that the absence of lived institutional knowledge has to be compensated for explicitly — usually by having an operator-experienced co-founder, by hiring a head of education who has that background early, and by building an advisory structure that keeps current practitioners close to product decisions throughout the development cycle. The companies we have seen stall at pilot stage almost universally had a gap between their product decision-making team and the actual institutional reality of their buyer. They'd done user research. They had teacher advisory boards. But those mechanisms are not the same as having someone in the room who spent three years managing an ERO self-review, or who knows that Wellington secondary schools are structurally different from Auckland secondary schools in ways that affect tool adoption, or who can read a board of trustees minutes and understand what the political constraints are.
Aroha brings that practitioner perspective to our diligence process — four years in a New Zealand secondary classroom teaching mathematics, followed by three years analysing education investments from an impact fund perspective. That combination is relatively rare in the investor community, and it's the main reason we believe we can evaluate operator-founder fit more precisely than a generalist fund could. The test we apply is simple: put the founder in front of a head of department at a mid-size NZ school and watch how the conversation goes. Does the founder ask questions that the teacher finds interesting, or questions that reveal a fundamental misread of how the teacher's role actually works? The answer to that question tells us more about long-term fit than almost anything else in our diligence process.