Home/ Industries/ EdTech

Industries

Software for education technology companies.

For teams that deliver courses, run exams and issue certificates. We build the platform, the proctoring, the grading and the integrations around them, then we run it after launch.

Where we help

What we build for EdTech.

Course delivery and learner records

Enrolment, cohorts, seat allocation and progress tracking, with video, documents and assessments in one place. We import your existing course content rather than asking your team to rebuild it by hand.

Online testing and exam delivery

Question banks, randomised papers, timed sittings and accommodations such as extra time. Built to hold up when a whole cohort starts at nine on the same morning, not just when ten people are logged in.

Proctoring and exam integrity

AI proctoring flags tab switching, absence and multiple faces during remote sittings. Flags go to a review queue with the evidence attached, so a person decides the outcome and the student has something to appeal against.

AI-assisted grading

Open text and short answers are pre-graded against your rubric, and an assessor confirms or changes each mark. Every change is logged, so moderation and awarding body audits have a trail to follow.

Certification and renewals

Branded certificates issued automatically, with expiry dates, renewal reminders and a register your customers can verify against. Expiring cohorts become repeat enrolments instead of quiet churn.

Integrations, SSO and rostering

Single sign-on, rostering and results export wired to the student information systems, CRMs and HR tools your customers already run. We build to SCORM, xAPI and LTI where their procurement asks for it.

How it runs

Plan. Build. Run.

01

A 30 minute call

We ask about your cohorts, exam windows, awarding bodies and where results have to land afterwards. By the end we know whether our ready-built LMS and testing platform fits, or whether this is a custom build.

02

Fixed scope, timeline and price

You get the scope written down before anything is built: what is included, what is not, when each part lands and what it costs. Term dates and exam windows go in as fixed constraints, not as hopes.

03

Build, with a pilot cohort

You see working software every week rather than status reports. Before go live we run a pilot cohort end to end, from enrolment to certificate, and load test the exam paths against your busiest morning.

04

Launch, then we run it

We monitor uptime, exam completion and grading queues, fix what breaks to an agreed response target, ship improvements and keep security patched. You get a monthly report showing what changed and why.

Why infoloop

We do not hand over and leave.

  • We run it after launchMost agencies hand over at go live, which is exactly when the first real exam window arrives. We stay on a monthly retainer: monitoring, fixes to a response target, improvements and a report each month.
  • We have built this platform alreadyOur LMS and testing platform already covers course delivery, question banks, proctoring, grading and certificates. You start from a working system and pay to shape it, not to invent it.
  • AI with a person in the loopWe put AI agents into production with guardrails, monitoring and rollback. For grading and proctoring that means a human decides, the model assists, and every decision is logged.
  • Built for institutional procurementEducation buyers ask about accessibility, data residency, retention and audit trails before they sign. We design those in and give you the answers in writing, rather than improvising them mid-tender.
  • One team builds it and keeps itThe people who wrote your grading logic are the people who answer when it misbehaves in week three of term. No handover to a support desk that has never seen the code.

What you get

Every engagement includes these, in writing, before work starts.

  • A working platform with courses, question banks, exams and branded certificates.
  • AI proctoring with a review queue, so a person decides every flagged sitting.
  • AI-assisted grading against your rubric, with an assessor confirming each mark.
  • Single sign-on and rostering wired to the systems your institutions already run.
  • A load test against your worst term-start and exam-window traffic.
  • Monitoring, security updates, fixes to a response target and a monthly report.

Who this is for

Three situations where this is the right call.

Your exam window is fixed and close

You have sold to institutions on the promise of a live assessment platform this term, and the date will not move. You need something running end to end, tested under load, with a pilot cohort through it before the real one arrives.

The agency that built your platform has gone

You inherited a codebase nobody currently on your team wrote. Grading breaks quietly, integrations drift, and there is no one to call in exam week. You want someone to take it over, stabilise it and keep running it.

You are adding AI to a product people pay for

Institutions already rely on your platform, so an AI grading or proctoring feature that misfires costs you the account. You want it built with guardrails, a human decision at the end and a way to switch it off.

Proof

Software we built, and still run.

Questions

What buyers ask us first.

What do you build for education technology companies?
We build the parts of an EdTech product that carry risk: course delivery and learner records, question banks and timed exams, remote proctoring, AI-assisted grading, certification with expiry and renewals, and the integrations that push results into a customer's own systems. We also have a ready-built LMS and testing platform, so some of this is configuration rather than a build from scratch. After launch we run it on a monthly retainer, with monitoring, fixes and security updates.
Can we trust AI grading on assessments that count?
Only with a person at the end of it. We build AI grading as a pre-grade: the model marks open text and short answers against your rubric and shows its reasoning, and an assessor confirms or changes each mark before anything is released to a learner. Every change is logged, so moderation, appeals and awarding body audits have a trail. We also monitor agreement between the model and your assessors, and the feature can be turned off without taking the exam system down with it.
How does proctoring work, and what happens with false flags?
AI proctoring watches the webcam and screen during a remote sitting and flags things like tab switching, absence and a second face appearing. It does not decide anything on its own. Flags land in a review queue with the recorded evidence attached, and one of your people makes the call. That matters because false flags are common in remote assessment, and a student who fails on an automated judgement with no evidence and no appeal route is a complaint you cannot answer.
Will it integrate with the systems our institutions already use?
That is usually the deciding factor in a tender, so we scope it first. We build single sign-on with SAML or OIDC, rostering and results export into student information systems, CRMs and HR tools, and we build to SCORM, xAPI and LTI where a customer's procurement asks for them. Where an institution runs something unusual, we integrate against its API directly. Integration work goes into the fixed scope with everything else, so it is not a surprise line item later.
What does an engagement cost, and how is it structured?
It starts with a 30 minute call. After that you get a fixed scope, timeline and price in writing before any building starts, so you know what is included and what is not. Price depends on whether our ready-built LMS and testing platform fits your workflow or whether this is a custom build, and on how many integrations your customers need. Running the system afterwards is a separate monthly retainer. We quote both on the same call, so you can budget for the year rather than just the launch.
What happens after launch?
We run it. That is a monthly retainer covering monitoring, fixes with an agreed response target, small improvements, security updates and a report each month showing what broke, what changed and what we would do next. For an EdTech product that means someone is watching during enrolment week and exam windows, not just during office hours on a normal Tuesday. If you would rather run it in-house, we hand over documentation and stay available, but most clients keep us on.

Show us your course, exam and certificate flow. We will scope it in 30 minutes.

A 30 minute call, then a written scope with a timeline and a price. If the ready-built LMS and testing platform fits, we say so. If it does not, we build to your workflow and run it after launch.

Book a call Checklist