Where it started
I started coding at 15, building Minecraft mods that eventually reached over 134,000 downloads. That taught me something important early: shipping software to real users is completely different from writing code in a vacuum. Users have expectations. Things break. And if what you built actually solves something, people come back.
By the time I was working through my A levels in Mathematics, Computer Science, Economics, and Psychology, I found myself doing something I suspect a lot of students know well: tracking degree apprenticeship applications across ten different employer portals, a chaotic spreadsheet, and an email inbox that was impossible to stay on top of. Every opportunity had different deadlines, different requirements, different portals. I'd spend more time managing the admin of applying than actually preparing for it.
The worst part was that the opportunities themselves were hard to find. They were scattered across employer websites, job boards, and university pages. None of them talked to each other. If you didn't know exactly where to look, you missed them. And most students don't know where to look.
Why I built something
In January 2024, I started Revise Wizard. Not because I had a polished business plan or investor backing. I started it because I was frustrated enough to try, and I happened to know how to build things.
The original vision was ambitious: a single academic support system combining AI tutors, personalised study tools, and a central place to discover and track every relevant opportunity for A level students looking at degree apprenticeships and T levels. I led everything: the backend in Java, Kotlin and Spring Boot, the infrastructure in Docker, Nginx and GitHub Actions, and a Linux server I managed myself. It was the most complete engineering experience I'd had.
The product was a bold attempt. It taught me more about product development, user research, scaling infrastructure, and the realities of launching an edtech startup than any course could.
What ReviseWizard became
As we iterated, the platform found its focus: a free tool that aggregates degree apprenticeships, apprenticeships, and internships in one place, and gives students a clean tracker to move opportunities from saved through to offer. No scattered tabs. No missed deadlines. Just the roles that matter, visible and organised.
The product ultimately didn't gain the traction I'd hoped for, and I've since moved on to other roles. I'm now an Infrastructure Engineer Degree Apprentice at JPMorgan Chase, rotating across global infrastructure teams in networking, compute, and platform engineering, while studying for a BSc in Digital and Technology Solutions at the University of Exeter. ReviseWizard continues to exist and serve students, and the lessons from building it have shaped how I think about infrastructure, product, and what it means to build something for people who trust you.
The mission
The core of ReviseWizard has always been straightforward: keep the platform free, keep it practical, and only add AI features where they genuinely improve outcomes for students.
Not every student has a careers advisor who knows what a degree apprenticeship is. Not every school surfaces these opportunities clearly. ReviseWizard exists to close that gap. It doesn't require anything from students except the willingness to apply.