What exactly is the difference between an LMS and an LXP?
A learning management system is top-down: the organisation sets the courses, assigns them and measures completion and certification. It is built around compliance, mandatory training and demonstrable competence. A learning experience platform works the other way round: the learner is at the centre, the platform makes personal recommendations based on role, goals and behaviour, and social and AI components play a big part. Many organisations run both side by side, with an LMS for the mandatory part and an LXP for self-directed development. Our page on a
custom learning experience platform describes that other route.
Do you replace Moodle, TalentLMS or Cornerstone for smaller implementations?
No, we don't recommend it. For a few hundred learners with standard flows, packages such as Moodle, TalentLMS, eFront, aNewSpring, easyLMS, Cornerstone, Docebo or Absorb are simply good choices. Custom only becomes interesting with sector-specific compliance, custom content flows to customers or partners, deep course interaction, white-label resale or a scale at which per-user licences no longer work commercially. In the first conversation we honestly assess which route suits your context — sometimes that is a targeted addition to your existing package rather than a full replacement.
Do you support SCORM, xAPI and other content standards?
Yes. SCORM 1.2 and SCORM 2004 for classic course packages, xAPI (Tin Can) and cmi5 for modern tracking, including learning activity outside the platform, LTI 1.3 for integration with external content providers, and H5P for interactive content. A built-in learning record store captures all activity regardless of source, so you have one central view of learning activity and certification. For video we use Mux, Cloudflare Stream or a custom S3 pipeline, so hosting isn't tied to a third party.
How do certification and automatic expiry tracking work?
Whenever a learning path or test is completed, a certificate is issued automatically with a digital signature, issue date and expiry date. You set expiry rules yourself per course or target group, for example two years' validity with an automatic reminder a number of weeks before the expiry date. For verifiable credentials we use Credly or Accredible; for a register you manage yourself, a custom PDF with QR verification. For mandatory recurring training, the platform can automatically trigger a learning path as the expiry date approaches.
How do you deliver compliance reporting to regulators?
For each sector we build the reporting format the way your regulator or certifying body wants to see it. For example, a Wft continuing-education report for the AFM, a BIG re-registration report for the BIG register, a HACCP evidence export for the NVWA, or a CPD points overview for your professional body. The data lives in the LMS by default; we make the reporting layer configurable so that changes in requirements don't immediately require a new release cycle. The audit log is always on, so during an inspection you can show who did what.
Does the LMS integrate with our HRIS and identity stack?
Yes. For identity we build SSO via Azure AD / Entra, Okta, Google Workspace or your own IdP, with SCIM provisioning for joiners and leavers. For HRIS we build two-way integrations with BambooHR, Workday, SuccessFactors or AFAS-HR: role changes and organisational shifts flow through to the LMS, and compliance status and certification flow back to HR for talent reviews or mobility decisions. For external parties without their own IdP, such as partners, franchisees and customers, we use federated login or magic links.
Does the LMS work multi-tenant for partner or franchise set-ups?
Built from the ground up for multi-tenancy. Each tenant gets its own branding, role structure, course catalogue, language and user management, with strict data isolation so that no information ever leaks between tenants through a misconfigured query. Central reporting gives you insight across all tenants. For white-label resale, each tenant can run on its own domain with its own email templates, so end users cannot tell that the underlying platform comes from you or from us.
What determines the cost of an LMS project?
Mainly the scope (which modules, how many content types, how deep the assessment and certification go), the depth of integration (which HR and identity systems are involved and in which direction), the complexity of your compliance reporting, the number of languages and tenants, and how much of the platform you want to be able to manage yourself. Adding a module to an existing package is a very different project from a completely new multi-tenant LMS platform. During discovery we outline a phased scope, if needed with several variants so you can choose what to do first and what comes later. For context on how we build up custom pricing, see our background article on
custom software costs.
What about GDPR, security and data retention?
Learning data is personal data and falls under the GDPR. We build role-based access in which only the learner and, depending on your policy, their direct manager and a designated L&D role can see individual results; aggregated management reports cannot be traced back to individuals. Retention periods per data category are configurable, so you decide how long results and certificates remain available after an employee leaves. Encryption in transit and at rest is standard, the audit log is switched on, and for larger projects we carry out a DPIA and schedule a penetration test in the final sprint.
How does implementation work, and can we bring over existing content?
We work in sprints and start small. The first sprint deliberately covers one target group and a limited set of courses, so we learn early on what works in your context. After that, we expand modularly per target group, tenant or business unit. We migrate SCORM and xAPI content from an existing system using an import script; locally stored content (videos, PDFs, hand-built HTML) requires a migration approach that we define case by case. We often use the migration as an opportunity to clean up metadata and taxonomy rather than carrying existing errors over.