The Revision Hub: A Full-Stack EdTech SaaS Platform Built for UK Schools

The Revision Hub came to Octelis with a product already built and a problem: nobody was converting.

The platform itself was solid. Their AI revision engine genuinely helped students retain information faster. Teachers loved the personalised assignments feature once they got into it. But the website looked like an MVP demo, the onboarding flow confused new users within the first two minutes, and the brand gave schools no reason to trust a young EdTech company with their students' data.

They had the substance. They needed the surface to match.

The brief

The Revision Hub's founder, an ex-teacher with a clear vision, was blunt about what they needed:

1. A marketing site that made the platform feel credible to school procurement teams - the people actually signing contracts
2. A platform UI that teachers could navigate without a training session
3. A brand identity that felt modern and calm - not childish, not corporate

They had six months of runway left. The pressure was real.

What we built

We tackled three layers simultaneously.

Marketing site. We rebuilt the public-facing website from the ground up - clean blue and white SaaS design, clear segmentation between student, teacher, and administrator value propositions, and a hero section that leads with outcomes: "Transform Learning with AI." The "AI-Powered Education Platform" badge in the hero immediately signals category to procurement teams who evaluate many platforms.

We added social proof earlier in the scroll than most EdTech sites dare to, because procurement teams make decisions based on evidence, not promises. A school trust quote above the fold is the fastest way to provide permission to take the risk.

Platform UI. The existing dashboard was a patchwork of feature additions with no coherent visual language. We designed a unified component system - consistent navigation, clear data hierarchy, and an activity feed that surfaced the right information at the right time for each user type. The student view, teacher view, and admin view all feel like the same product, but serve completely different jobs.

Brand. We established a full identity: primary palette, typography, iconography rules, and usage guidelines. The brief was "feels like a tool a serious school would trust" - so we leaned into clean geometry, generous white space, and a blue that read as calm authority rather than cold tech.

Three audiences, three entry points

The most important structural decision was separating the three audiences at the navigation level rather than trying to serve everyone from a single homepage:

• Students care about knowing what to revise and getting fast feedback on practice answers
• Teachers care about assignment management, class progress reporting, and whether the AI suggestions match their curriculum
• Administrators and procurement care about data compliance, GDPR handling, safeguarding protocols, and whether their staff will actually use it

Treating them the same was losing all three. Separating them explicitly - in the navigation, in the hero section framing, and in the feature presentation - gave each audience permission to see themselves in the product.

What made the difference

The second key decision was front-loading credibility. Most EdTech startups bury their school logos and testimonials at the bottom of the page. We put a school trust quote above the fold, because the person signing the contract needs permission to take the risk - and other schools giving permission is the fastest way to provide it.

The platform UI work paid for itself in reduced support load. When teachers can figure out the interface without a training session, the cost-per-user of the product drops substantially. That makes the economics of school-level pricing viable.

---

If you're building an EdTech product, a SaaS platform, or any digital service that needs to earn trust quickly, get in touch - we'd love to help you close that gap between what your product does and how it looks.