sector
course platforms, learning systems and the content architecture underneath them
Eight education engagements across four countries — course platforms, learning systems, fee collection and the AI tooling that only works once content is structured.
- 8
- education engagements
- 4
- countries
- 9,000
- lines of content freed
- 2
- app stores published to
Clutch
the problem
what this sector actually deals with.
Education businesses sell content, and almost all of them store it in the worst possible place — hardcoded into a template, trapped in a plugin, or spread across a thousand pages nobody can edit without a developer. Everything downstream suffers: the marketing team cannot ship, translation is impossible, and AI tooling has nothing structured to work with.
sound familiar?
- Course and destination content locked in code, not in a CMS
- Marketing cannot publish without a developer and a deploy
- The same content cannot be reused across sites or languages
- Fee collection runs on bank transfers and chasing
- An app was promised and the store rejected it
what we have built here
systems delivered in this sector.
Headless course platforms
WordPress as the content backend with a Next.js front end for a group of TEFL certification businesses — content modelled in ACF and served through a custom REST namespace.
Learning management systems
LMS builds for a business school and a Belgian client, including a cross-platform app published to both Google Play and the App Store.
Fee collection that chases for you
Online payment through an Indian gateway with generated receipts, plus early-bird reminders over both WhatsApp and email — the combination that actually reaches Indian parents.
Teacher and tutor platforms
Portals, marketplaces and research publishing across the UK, Ireland and India — including an academic articles portal built as decoupled backend and front end so cited URLs never break.
the hard part
structure the content first, then the AI is worth having.
The most valuable thing we did on a course platform was delete 9,000 lines of static country-guide content from a codebase and turn it into editable records.
- 01
Destination guides — hero, overview, teaching-job accordion, living costs, key facts — were the single largest static file in the repository. Marketing could not touch them without a developer and a deploy.
- 02
Modelled as ACF fields on a custom post type and exposed through a dedicated REST namespace, every guide became a queryable record with typed fields. The marketing team now edits them directly.
- 03
That sequencing is the whole point. You cannot usefully generate, translate, summarise or quality-check a 9,000-line static file. You can once every guide is a record — which is why the AI content workstream came second and worked.
- 04
The counter-example is in the register too: a quiz feature that stored each language as its own database column, so adding a language meant a schema migration and a code change. We flagged it as unscalable before the client asked for language five, not after.
what it runs on
the stack we reach for here.
Chosen for the sector requirements and for maintainability over the life of the system.
- Content
- WordPress or Sanity as the editable backend, ACF-modelled
- Front end
- Next.js, server-rendered, on a custom REST namespace
- Payments
- Regional gateways with generated receipts and reconciliation
- Notifications
- WhatsApp and email, dual-channel for parent and student audiences
- Mobile
- React Native or Cordova, published to both stores
how an engagement runs
what the first weeks look like.
Audit the content
Where it lives, who can edit it, and what it would take to make it structured. This decides everything after it.
Model it properly
Typed fields, a real content type, and an API the front end and any future tooling can both read.
Build the surfaces
Site, portal, app — whichever the business actually needs. We will argue against the ones it does not.
Then automate
Generation, translation and quality checks, once there is structured content for them to work on.
selected work
written up in full
The engagements with the detail attached — and the numbers.
01
B2B commerceThe engineering partnership behind a cross-border wholesale marketplace.
Next.js storefront, Python ingestion pipelines, DynamoDB data layer and AWS infrastructure.
02A commission-free ticketing platform built for ownership and scale.
Multi-organiser commerce, Stripe instalments and two native apps in one connected platform.
03
Global logisticsEmbedded product engineering for a global shipping platform.
Rate, tax and duty calculators, server-rendered courier pages and a custom MongoDB CMS.
04A custom furniture marketplace engineered from storefront to infrastructure.
Server-rendered Next.js commerce over a Laravel API, bespoke operations tooling and re-architected AWS infrastructure.
05An AI-native operating system that runs a consultancy lead to invoice.
Discovery briefs, e-signed contracts, Stripe deposits, delivery milestones and time tracking in one operational system.
06A conversion platform for a growing UK boiler-cover provider.
Custom plan configuration, postcode-qualified lead journeys, CRM synchronisation and campaign landing pages.
07A custom Shopify store for a French beauty brand.
Custom theme, customer accounts, loyalty rewards, referrals and gift-with-purchase offers.
08Made-to-measure shutters with live pricing.
A seven-step product builder with live previews, sample orders and supplier tools.
09
AdvertisingA self-service advertising platform for venues.
Campaign creation, audience targeting, in-app ads and reporting linked to venue check-ins.
10Social eventsAn events app with the tools to run it.
Mobile app, backend, advertising tools, a digital marketplace and website.
11Two mobile apps for real-time companionship.
Customer and buddy apps with per-minute billing, wallets, moderation and admin tools.
12Player profiles and discovery for youth football.
Verified profiles, video highlights, coach discovery and safeguarding on web and mobile.
13Websites and a talent platform for DeepSpatial.
Corporate and investor pages, the Xploor talent platform and ongoing releases on AWS Amplify.
14
TravelTour bookings with a custom mobile-first checkout.
A multilingual website connected to the booking API, with deposits, coupons and affiliate tracking.
15One platform for tenders, contracts and accounts.
Supplier tenders, contract management, brokerage accounting and client records.
Teams that trusted us with the thing that matters
UK · Europe · Worldwide
the practices behind it
what this work is made of.
product engineering
Multi-tenant SaaS, marketplaces, ticketing and booking engines — the systems your business actually runs on, built to survive their own success.
web & commerce
Headless WordPress, Shopify and custom checkouts wired to whatever proprietary API the business already depends on.
AI systems
Retrieval pipelines, support deflection and internal copilots — costed per token before a line is written, so the unit economics work at volume.
native mobile
React Native apps that ship past App Store review and stay shipped — offline-first paths, push, real-time sync and over-the-air updates.
reviews · verified on clutch
the people who signed off the work
Clutch★★★★★5.0 / 5.0Across 18 independently published client reviews
“They have a deeper technical knowledge than any web designer I've met to date.”
faq
questions from this sector
Should we build an LMS or buy one?
Buy, unless your teaching model genuinely does not fit one — which is rarer than founders think. We have published a cost study on exactly this decision and we will point you at it before we quote.
Can our marketing team edit courses without us?
That is the point of the architecture. Headless does not mean developer-only; editors keep a proper CMS behind a fast front end.
Can you get our course app into the stores?
Yes, including the rejections. We have resolved toolchain incompatibilities, provisioning and an over-declared background-audio capability that Apple rejects on sight for a learning app.
Do you do the AI content tooling too?
Yes, and we will tell you if your content is not structured enough for it to be worth doing yet.
keep reading
the other sectors we work in.
content trapped in a template?
A thirty-minute call with the engineer who would lead the work.