Education product studio
Interactive courseware, curriculum engineering, assessment, platform and growth — built by people who have shipped all of it. And the part most teams discover too late: the privacy, accessibility and procurement rules that decide whether you can sell in a market at all.
What we do
01
Manipulables that teach by being used — graphers, balance scales, constructions, simulations. Built as components, not videos, so a learner changes a value and the mathematics responds.
02
Mapping content to the curriculum a market actually teaches, then building the tooling that keeps hundreds of chapters consistent as they change.
03
Item banks, adaptive sequencing and per-learner progress. Including generated items that pass a second-model validation pass before a student ever sees them.
04
The unglamorous half: rostering, org and seat management, teacher dashboards, live classroom sessions, billing, and the analytics that tell you any of it worked.
05
Applied where it earns its place — item generation, tutoring, speech in and out — with evaluation harnesses and guardrails, because a confidently wrong answer is worse than no answer.
06
Getting a product adopted inside institutions that buy slowly: activation, retention, rollout, pricing and packaging, and instrumentation you can act on.
Real-time parameters, vector transformations, and responsive mathematical graphs.
Multi-model item generation verified against strict mathematical and safety harnesses.
Evidence
We built a full secondary-maths platform: 416 interactive components across 90 chapters and 7 courses, with 25 item banks, generated practice questions validated by a second model before a student sees them, a real-time multiplayer classroom mode, organisation and seat management, and 66 API surfaces behind it.
You don't have to take that on trust. Every component is extracted, live and playable — open one and move a slider.
Browse the showcase↗The part that blocks deals
An education product touches children's data, public procurement and accessibility law simultaneously. The rules differ by country, and in the US by state. Most teams discover this during a district security review, or a week before a European launch. We treat it as an engineering requirement from the first sprint, not a document produced at the end.
Federal, state and provincial
Union-wide and national
Rapidly diverging regimes
Often overlooked, increasingly enforced
How we work
We embed with your team and ship alongside it — carrying the parts that need depth: interaction, curriculum tooling, compliance.
You have a team and a roadmap, and a gap in the hard parts.
End-to-end delivery of a product or a major surface, from curriculum mapping through to a live platform, with a clean handover.
You have a market and a mandate, and need it built.
A fixed-scope audit of an existing product — accessibility, data protection posture, curriculum coverage, technical debt — ending in a prioritised plan.
You're entering a new market, or a deal is blocked on diligence.
Book a call
Tell us what you're building and which markets you need to sell into. We'll tell you what's involved — including the parts that usually surface late, like a district security review or an EU launch.
Prefer email? pretonitech@gmail.com
Loading calendar…