EdTech
Learning and exam software, built for the busiest morning
Your product teaches people, tests them and hands them a certificate. Your customers are schools, colleges and training companies, and they ask hard questions before they sign. We build the product, then keep it running through every exam window.
Education products are judged in exam week
A whole year group logging in at nine. Term dates that will not move. Buying teams that want the accessibility answer, the data answer and the audit trail before they sign.
Most education companies are not short of features. They are short of a product that holds up when it matters. The exam page that worked for ten people in the office slows down when a whole year group logs in. Marking runs late. Results get typed into the school's own software by hand.
Often the agency that built the product has gone. Nobody on your team wrote the code, connections drift, and there is no one to call in exam week. Or you are adding AI to something institutions already pay for, and one wrong flag or wrong mark could cost you the account.
- Exams that hold up on the busiest morning.
- AI marking and proctoring with a person deciding.
- Results pushed back into what schools already run.
Infoloop builds the learning and exam software you sell, often starting from LoopIQ, the platform we already own, connects it to the tools your customers run, and stays to keep it running through every term and exam window.
Measured results
EdTech problems we solve
We build and run software for the way institutions really buy and use it, not the way a pitch deck says they should.
Your exam date is fixed and close
You have sold a live assessment product for this term and the date will not move. We build it end to end, load test it against your busiest morning and put one real group through, sign-up to certificate, before the paying ones arrive.
The agency that built your product has gone
You inherited code nobody on your team wrote. Marking breaks quietly, connections drift, and there is nobody to call in exam week. We take it over, steady it and stay to run it, one safe change at a time.
AI marking or proctoring that could misfire
Institutions already depend on your product, so a wrong flag or a wrong mark costs you the account. We build AI with limits: a first mark against your own guide, every flag on a review list with the recording, a person deciding, and a switch to turn it off.
Results stuck outside your customers' tools
Schools want one login, student lists and results pushed back into the software they already pay for. We build to SCORM, xAPI and LTI, the exchange standards buying teams ask for by name, and connect directly where an institution runs something unusual.
Built for the busiest morning. Run by us.
Case studies
Measured results from products we built and still run.
What working with Infoloop gets you
For education companies that need software live before term starts, and watched once it is.
Live before term starts
Planning in about a week, most builds live in 4 to 8 weeks, with one real group put through first.
One price, agreed first
Scope, dates and price in writing before anything is built. Term dates go in as fixed walls.
Start from working software
LoopIQ, our own learning and testing platform, already does courses, question banks and certificates. You pay to shape it, not invent it.
Answers ready for the buying team
Accessibility, where data is kept, how long records are held and what trail exists, written down for you.
Watched through exam week
We watch uptime, exam completions and the marking queue, fix faults to an agreed time, and report every month.
Trusted by companies whose product has to work on the day
Built with tools your team already knows, on a platform we own and run.
- Webflow
- Shopify
- Stripe
- Slack
- AWS
- OpenAI
- Anthropic
- WordPress
- Next.js
- React
- Node.js
- Flutter
- projects delivered
- 50+
- projects delivered
- countries
- 6
- countries
- uptime on software we run
- 99.9%
- uptime on software we run
- average client rating
- 4.8
- average client rating
What our clients say
They shipped our support agent in five weeks and it has run ever since. Response time dropped from hours to two minutes.
COO, fintech scale-up
Read the case studyBlogs and insights
FAQs
Questions education companies ask us
Straight answers. If yours is not here, ask us on the call.
What exactly do you build for education companies?
The parts of an education product that cost you an account when they go wrong. Courses and learner records. Question banks and timed exams. Exams taken at home with somebody watching. Marking help. Certificates with expiry dates and renewal reminders. And the connections that push results back into your customers' own software. We also own LoopIQ, a working learning and testing platform, so some of this is setting up what already exists rather than building from nothing. After launch we keep it running for a monthly fee, with somebody watching it, fixing it and keeping it safe.
Can we let software mark work that counts?
Only with a person at the end of it. The software gives a first mark on written and short answers against your own marking guide, and shows how it got there. A marker then confirms or changes every mark before a learner sees anything. Every change is recorded, so moderation, appeals and awarding body audits have a trail to follow. We also track how often the software and your markers agree, and the feature can be switched off without taking the exam platform down with it.
What happens when the software wrongly flags a student?
Nothing, until a person looks. During an exam taken at home the software watches the camera and the screen and flags things like a switched tab, an empty seat or a second face. Every flag lands on a review list with the recording attached, and one of your people makes the call. Wrong flags are common when exams happen at home. A student failed by a machine, with no evidence and no way to appeal, is a complaint you cannot answer, so we never let the software decide on its own.
Will it work with the software our customers already use?
That is usually what decides a tender, so we scope it first. We build one login, student lists, and results going back into the student record software, CRMs and HR tools your customers run. We also build to SCORM, xAPI and LTI, the exchange standards buying teams ask for by name, which are agreed ways for course software to swap material and results with other tools. Where an institution runs something unusual, we connect to it directly. All of it goes into the fixed price with everything else, so it never turns up later as a surprise line.
What will it cost, and how do you charge?
It starts with a 30-minute call. After that you get the scope, the dates and the price in writing before anything is built, so you know what is in and what is not. The price depends on whether LoopIQ, the platform we already own, fits your product or whether this is a build from scratch, and on how many other tools your customers need it to talk to. Keeping it running afterwards is a separate monthly fee. We quote both on the same call, so you can budget for the year rather than only for the launch.
What happens after launch?
We keep it running. A monthly fee covers somebody watching it, fixes within a promised time, small improvements, security updates and a report each month showing what broke, what changed and what we would do next. For an education product that means somebody paying attention during sign-up week and exam windows, not only on a quiet Tuesday. If you would rather run it yourself, we hand over written instructions and stay reachable. Either way our advice is the same: an exam window cannot be moved, so somebody has to be watching the morning it opens.
Show us how your product works today
A 30-minute call, then a written scope with dates and a price. If LoopIQ fits, we say so and you pay less. If not, we build to your product and keep it running.