Selected work
Two platforms, two very different jobs.
One built end to end with a custom frontend. One inherited live and made reliable. Both on Moodle.
Custom-branded learning platforms for schools and training providers. A bespoke frontend on your own domain, with Moodle doing the reliable work underneath, plus the course content and the website to go with it.
Moodle is one of the most tested pieces of education software in the world. Its engine is excellent. Its interface is not. Everything we do starts from that fact.
A branded web application on your own domain that learners, parents, and staff use instead of Moodle's screens. It talks to Moodle for courses, enrolment, and grades, so nothing a learner sees is Moodle and everything they rely on still is.
For platforms that already exist and are live, fragile, or held together by one person's memory. We stabilise without downtime, restructure the course, migrate safely with learner progress intact, and document it so your organisation can own it.
A platform is only part of an online school. We write original course material, produce lesson videos with translations where needed, and design the public website that persuades a family or a company to enrol in the first place.
What we do not do: build a learning management system from scratch. We would not recommend it to anyone. If the complaint is about the interface, and it almost always is, a custom frontend fixes it without giving up an engine that has spent years getting the hard parts right. We explain the reasoning in why a custom frontend beats building your own LMS.
The frontend is yours. The backend is Moodle. They talk through Moodle's web services, and your learners never see the seam.
One built end to end with a custom frontend. One inherited live and made reliable. Both on Moodle.
We look at what your learners see today, what Moodle already handles well, and where the experience is costing you enrolments or credibility.
The login, dashboard, and catalog are designed around how you actually run your school or program, not around Moodle's defaults.
The frontend is hand-coded and wired to Moodle through its web services, tested against real courses and real enrolments.
A careful switch on your own domain, then documentation and support so your team can run it without us in the loop.
No, and we would talk you out of it. Enrolment, grading, quizzes, roles, reporting, content standards, and security updates are solved problems in Moodle. Rebuilding them means paying to re-solve them and then maintaining a software product forever. We keep Moodle as the engine and build the branded experience on top, which fixes the part people actually complain about. The full argument is in why a custom frontend beats building your own LMS.
No. A custom frontend is a separate branded application on your own domain that talks to Moodle for courses, users, enrolments, and grades. Your existing Moodle, content, and learner history stay where they are. Learners simply stop seeing Moodle's screens.
Yes. We have taken over a live, fragile Moodle for a national training program, stabilised it without downtime, restructured the course, migrated it safely with all learner progress intact, and documented it for handover. The full case study walks through how. If your platform works in principle but not reliably in practice, that is a job we know well.
Yes. For our own online school we wrote original course material aligned to the Cambridge Primary and Lower Secondary frameworks. We can also produce lesson videos and translate them into the languages your learners speak, and design the public website that persuades a family or a company to enrol.
Tell us what your learners see today and what you wish they saw. We will give you a straight answer on whether a theme, a custom frontend, or leaving it alone is the right call, and show you what we would build.
