Industry Watch · Published March 19, 2026
Education Procurement: Buyers Who Cannot Specify
The hardest part of school software procurement is not the budget but articulating the real need.
We have taken part in several education procurements: academic systems, resource platforms, home-school communication. The biggest obstacle is not funding but expression, as user voices rarely reach decision and tender stages.
Three common mismatches
Buyer and user are separated. The tender feature list is not what teachers use every day.
Evaluation favours demos: prepared datasets hide complex classes and unusual schedules.
Build overrun: one-off training fades when staff change each term.
What can change
Involve frontline teachers in requirements: observe real use for a week and list high-frequency actions.
Write a trial into the contract: run one grade for a full term before deciding on wider rollout.
Train by role: subject teachers, head teachers and administrators need different sessions; combined ones satisfy nobody.
Education procurement buys service, not boxes. Understanding usage beats writing thicker specifications.
Want to apply these ideas to your project?
We are happy to go deeper into implementation details, or to discuss the specific questions you are facing.
Start a conversation →