Enrolment and access
Define who can join, what each programme includes and what learners, teachers and administrators can see. Work through account changes and access when a subscription ends.
All services
Education platform development
From enrolment to the next lesson.
Give learners a clear place to join, book and learn, and give your team the tools to run the service. We build education platforms around your teaching model, with payments, scheduling and access planned together.
Two software engineers and technical consultants in London, working directly with the people commissioning the product.
Plan both sides of the lesson.
The learner experience and the administration behind it need to work together. We agree which parts belong in the first release and which existing tools should stay.
Scheduling and payments
Connect booking rules, availability and payment status. Agree how to handle full sessions, cancellations and recurring lessons before development starts.
Learning tools
Build the experience your teaching approach needs: progress records, practice activities or a focused AI feature. Choose useful tools against real learning tasks rather than adding features to a checklist.
See what we’ve built.
Explore the actual products and the decisions behind them.
Faseeha Institute Live
A commissioned online school, live.
For Faseeha Institute we connected subscription checkout, weekly slot booking, teacher allocation and recurring lesson invitations, alongside progress tracking and learning access. This is client delivery work.
Read the case study
OsceSetGo Live — paying users
A live AI practice platform.
We built OsceSetGo with AI patient conversations, structured feedback, session history and subscriptions. The platform is live with paying users. It is a client product, not owned by Alwan.
Read the case studyStart with the teaching model.
How we workMap the people and rules
Identify the learners, staff and organisations involved. Review the teaching schedule, access rules and tools already in use.
Agree a first release
Set a written scope with the essential journeys, responsibilities, costs and acceptance checks. Identify third-party fees and dependencies early.
Review working software
Use regular demos to check the learner and administrator journeys. Test access, booking conflicts and payment changes alongside the main path.
Prepare for operation
Agree testing and handover, document deployment and configuration, and plan support around the platform you will actually run.
Before we start.
A few things worth knowing.
Do we need a custom platform?
Not always. If an existing learning or booking system covers the core workflow, configuring it may be a better starting point. A bespoke build makes sense when the teaching model, access rules or integrations require something those tools cannot reasonably provide.
Can you connect tools we already use?
We review the available APIs, account permissions and commercial terms first. The proposal identifies the integrations included and how work beyond those boundaries would be agreed.
What should we bring to the first conversation?
An example of how someone joins and attends today, the people involved, any existing tools and your target date. You do not need a technical specification; we can help turn that into a practical scope.
How payments, scheduling and teacher allocation connect in Faseeha Institute.
What does your learning service need?
Tell us who it serves, how sessions or activities work and what your team needs to manage. We’ll help you plan the first release.