Ed tech
Ed tech development
Learning products where the buyer is an institution rather than the user — which means accessibility, procurement and data questions decide the sale long before the features do.
From £75/hrAn estimate before any work startsOne developer, start to finish
01
In ed tech the person using it and the person buying it are almost never the same person.
The learner judges it on whether it is good. The institution judges it on an accessibility statement, a data processing agreement and a procurement process. A product that satisfies only the first does not get bought.
02
What actually gets built
Learning products
The thing the learner actually uses: content, progress, assessment, and working offline or on a four-year-old device where that matters.
Built for the institutional buyer
Accessibility taken seriously because it is a legal requirement in public procurement, not a nice-to-have — and documented in the form the buyer has to file.
Administration and reporting
What a teacher, an administrator or a head of department needs to see, which is usually a different product to the learner-facing one.
The data questions, answered early
Who the controller is, where the data sits, how long it is kept and what happens at the end of the contract. Asked at procurement, every time.
03
How the work runs
You describe it
Two sentences is enough to start. What you are building, who it is for, and which rule or buyer is forcing the shape of it.
A scope and a price, inside 24 hours
What is in, what is deliberately out, what each stage costs and what it depends on. Where a regulator or a procurement process sets the timeline, that goes in the plan rather than being discovered in week six.
Built in the open
Your repository from the first commit, deployed somewhere you can see it from the first week.
Handed over properly
Your accounts, your keys, your infrastructure, and a README that assumes the reader is not me.
- Rate
- From £75/hr
- Scope and price
- Inside 24 hours
- Written by
- The person who scoped it
Selling to schools or institutions? Accessibility and the data agreement are not paperwork at the end — they are design constraints at the start, and cheaper there by a wide margin.
Start a project →05
Who this has been done for
EDUVO
Midnyte's founder started and built EDUVO, an education venture, between 2022 and 2024. It is his own background in the sector rather than a client engagement, and it is listed here as exactly that.
Eleven years and more than three hundred projects behind the work generally — this is the part of it that is in education.
Common questions
Does accessibility really affect whether we can sell?
To public-sector and institutional buyers in the UK and the EU, yes — it is a legal requirement rather than a preference, and it is usually checked during procurement. Retrofitting it into a finished product is several times the cost of building to it. There is a page on the accessibility law and what it actually requires.
How long does selling to an institution take?
Longer than the build, often by a lot, and that is the planning fact that matters: procurement cycles, security review and an academic year that only starts once. The product being ready in March is not the same as being bought in March. There is a page on selling to the public sector.
Do you handle data about children?
The engineering around it, yes: minimisation, retention, access control, deletion and where it is processed. The policy and the legal basis are the institution's and your adviser's to set — what gets built is a product that can actually honour them.
04
Tell me what you are building
Two sentences is plenty, plus who signs the purchase order. You get back a scope, a price and the obligations that come with that buyer.