A lot of EdTech is built by technologists who were good at school, and it shows. The product is slick, the onboarding is smooth, and the teaching underneath is naive — a quiz engine with a progress bar, built by someone who never had to get a struggling fourteen-year-old over the wall of quadratics. The scarce thing in this field has never been engineering. It's knowing how learning actually works, and that lives in people who have done the teaching.
Domain authority is the input you can't fake
You can hire an engineer. You can buy design. You cannot shortcut the thousands of hours it takes to know, in your hands, where students get stuck and why, which explanation lands and which one quietly confuses, what a child does right before they give up. That knowledge is the actual product in a learning tool. Everything else is packaging.
This is why so many well-funded EdTech products feel hollow. They optimised the things that are easy to optimise and were naive about the thing that's hard. An expert founder starts from the opposite end: they already have the hard thing, and the rest is build.
What experts see that generalists miss
Three things, specifically.
Where the gaps actually are. An experienced teacher knows that a student failing quadratics is often missing factoring, or negative numbers, from two years earlier. A generalist builds a tool that drills quadratics harder. The expert builds one that finds the real hole.
Which explanations work. There are good and bad ways to teach every concept, and the difference is invisible unless you've watched a hundred students meet it. Experts carry a library of explanations that work, and an instinct for the ones that don't.
What mastery looks like up close. Not a test score — the moment a student can reproduce an idea cold, days later, under pressure. Experts can tell the difference between a child who has learned something and one who has just seen it. Most products can't, because their builders couldn't.
The one thing they're missing
It's execution, and it comes in three parts: the build (turning the pedagogy into working software), the business (pricing, distribution, the unglamorous machinery of a company), and the route to learners (getting it in front of the people it's for). These are real gaps, and an expert trying to learn all three alone, at night, usually stalls.
But here's the asymmetry that matters: those three are the fillable gaps. Engineering can be brought in. Distribution can be built. A business model can be designed. The domain authority at the centre cannot be acquired on the same timeline — it took years. So the expert who teams up to cover execution is starting from the rare half and renting the common half. The technologist doing the reverse is starting from the common half and hoping to fake the rare one.
How the gap gets closed
This is the whole reason a studio model exists for education. The expert brings the authority and the idea; a build partner brings the engineering, the product instinct, and the path to capital and learners. Done well, the expert stays the soul of the product — the pedagogy is theirs — and isn't left trying to become a CTO and a CFO overnight to protect it.
If you're an educator with an idea you can't build, the instinct to go and learn to code, or to hand your insight to a generic dev shop and hope, is the wrong one. The first wastes your scarcest years; the second loses the very thing that made the idea good. The right move is to keep the authority where it belongs and partner the execution.
A note to the expert reading this
If you've spent years teaching and you've watched the tools your students use get the teaching wrong, that frustration is a signal, not a complaint. You know something the market needs and mostly doesn't have. The gap between that knowledge and a real product is execution — and execution is the part that can be supplied. The hard part, you already did.
Frequently asked questions
I'm a teacher, not a tech person. Can I really start an EdTech company? Yes — and your lack of a technical background is not the disqualifier people assume. The domain authority is the rare input. The build and the business are the parts a partner supplies.
Don't I need to learn to code to keep control? No. You keep control by owning the pedagogy and the product decisions. Trying to become an engineer to protect your idea usually costs you the years that made the idea good.
What if my idea overlaps with something that exists? Most strong ideas do. Execution and depth decide it — a product built by someone who understands the learning will beat a better-funded one that doesn't.
A note on why we wrote this. Addestra co-builds EdTech ventures from zero to one, and subject-matter experts are exactly the founders we're built to partner. Publishing this is the point: if you have the authority and not the build, that's the half we bring. How we work: editorial standards.
Sources
- Our framework on what makes a learning tool work: System-Native EdTech, The Four Mismatches Test
- Education Next — "Two-Sigma Tutoring: Separating Science Fiction from Science Fact" (on what expert, mastery-based teaching actually does): https://www.educationnext.org/two-sigma-tutoring-separating-science-fiction-from-science-fact/