Education software development for schools, colleges and trainers

Which education business are you?

Education covers many different buyers. A school needs admin and communication. A college or university needs to connect many systems. A training company needs course delivery, bookings and certificates. An edtech startup needs a product that learners will pay for. Each has different compliance, budgets and users.

Learning tools that teachers actually adopt

Teachers adopt tools that save them time in the first week. Marking aids, quick quiz creation, simple rubrics, and feedback comments that can be reused are popular. Tools that require new data entry, or separate logins for each student, are not.

We interview teachers first. Sit in on a lesson plan, see the marking workload, and ask which task they would hand over. The answers shape the first release, which is often a single tool such as a feedback assistant, an assignment tracker or a reading log.

Think about the day a lesson goes wrong. The wifi drops, the projector fails, a student has forgotten a password. A classroom tool that needs ten steps to recover will be abandoned. We test failure cases explicitly, with a teacher present, and design the screens so a recovery takes one or two taps.

Integrations and standards

Most institutions already run a learning platform such as Canvas, Moodle, Blackboard or Google Classroom, and a student information system. A new tool should plug into these. The usual standards are LTI for launching a tool inside the LMS, OneRoster for syncing classes and rosters, and SAML or OpenID Connect for single sign-on. Not every platform supports every standard on every plan, so we check yours.

Where the sector requires it, we can support SCORM or xAPI for packaged course content. We also advise when a tool is better bought than built, for example a standard quiz engine.

Privacy, accessibility and safeguarding

Student data is protected. In the US, FERPA covers education records, and COPPA applies to online services for children under 13. In the UK, UK GDPR and the ICO Children's Code apply, and many countries have similar rules. Accessibility duties include WCAG-aligned design, and public institutions often have formal requirements. Check with your data protection officer or lawyer.

Our build includes no advertising or tracking code, minimal data collection, role-based access so teachers see only their own classes, and clear deletion routines. Where students can message or share content, safeguarding rules apply, and we help you agree moderation and reporting steps before launch. Our page on AI chatbots for education explains how we limit AI answers to approved materials.

How a project runs

1. Listen to usersShort interviews with teachers, admin staff and, where appropriate, students.
2. Prototype in a weekA clickable version that a small group tests in an ordinary lesson.
3. Pilot in a real classOne class or department for a full month, with a feedback form.
4. Roll out with trainingShort video guides and a named contact for staff questions.

We work remotely from Pune, with Coventry and New York offices helping with UK and US term-time schedules.

Success measures should be modest and specific: minutes saved per teacher per week, number of forms completed online, fewer calls to the office. We agree two or three at the start and report on them after the pilot.

Price guidance

Projects start at $1,500, with an hourly rate of $30. A single-purpose tool is small, and an LMS-integrated assessment platform with reporting is larger. Edtech startups can see the MVP development service to limit the first release. See web app costs for how scope changes the quote, and education website design for the public site.