Kallidus

Name: Kallidus
Brand: Kallidus

Accelerate compliance. Build skills. Drive performance.

Est 2000|Valuation $72.6M|Raised $35.9M|127 Ref Customers

LinkedIn 9K|Web traffic 23K|FTEs 229|HQ Bristol, England, GB

MarketsPerformance Management Learning Management System (LMS)

Published Oct 15, 2026

01Common complaints

- Small organisations (for example, fewer than 200 employees) seeking a low-cost, largely self-serve LMS may find clearer pricing and faster setup with alternative SMB-focused providers. - Organisations whose primary requirement is extended enterprise commerce and training monetization should evaluate platforms with dedicated e-commerce features suitable for customer-facing training. - Organisations that require advanced AI course creation and highly collaborative authoring workflows should evaluate specialist authoring and collaborative platforms; validate actual AI capabilities in trials. - Organisations requiring specific, documented compliance certifications in scope (for example, HIPAA BAA, ISO 27017/27018) should confirm published attestations or be prepared for NDA-based audit review. - Environments with complex identity architectures (multiple Azure AD tenants, partner identity, extensive external learner SSO) should test SSO scenarios early; community discussion suggests edge cases can be complex. - Current limitations acknowledged in vendor materials - No explicit public "known issues" page was identified in the materials reviewed beyond system requirements and standard documentation. - Features on the roadmap (not yet available) - No public roadmap items with dates were captured in the reviewed materials; procurement should request roadmap details under NDA where relevant. - Scale limitations - Not documented in the reviewed materials; procurement should validate: - Maximum concurrent user assumptions - API rate limits - Reporting performance at high user counts - Security or compliance gaps - ISO 27017/27018 and HIPAA: not publicly documented in the reviewed materials. - "SOC-2 controls" language appears in vendor materials; procurement should clarify whether a current SOC 2 Type II report exists and what systems are in scope. - Technical debt or architectural limitations mentioned in reviews - No consistent evidence of technical debt or architecture limitations surfaced in the review materials; procurement should ask references about long-term platform stability and upgrade cycles. - API limitations or integration constraints - Vendor developer documentation and API docs were located, indicating integration support. Procurement should validate: - API coverage for Learn and Perform - Availability of webhooks or eventing - SCIM provisioning support

02Why they buy

- Competitive advantages indicated by customer feedback (not solely vendor claims) - Reviewers frequently cite reporting efficiency and administrator usability when describing the product. - Implementation and ongoing support experience are commonly noted positively in user reviews. - Unique features and capabilities not conclusively proven independent of vendor materials - Vendor differentiation appears to focus on framing around outcomes rather than activity, together with packaging for compliance and reporting; independent verification is recommended. - Differentiation from competitors based on reviews - Some reviewers described the product as providing a clear learner and admin experience and having a responsive support function; these are user-reported perceptions and should be validated in pilots. - Value propositions with evidence from case studies - Vendor case studies provide specific outcome metrics; procurement should request methodology and independent validation. - Areas where competitors have advantages - Docebo and Cornerstone: broader enterprise ecosystems and scale for very large deployments. - Absorb: extended enterprise and e-commerce features. - 360Learning: collaborative/social learning and content creation workflows.

03Field reports

Customer Testimonials

- Review platforms show a substantial review footprint (notably on G2). Review ecosystems can be subject to selection bias; treat reviews as directional evidence rather than definitive proof. - Direct quotes (positive) from reviews - A G2 review excerpt (HR assistant) noted time savings and easier access to required information: "saved me time… I get what I need with a couple clicks." - Another G2 excerpt (Head of Learning and People Development) described positive implementation and support responsiveness: "Fantastic product, great service… the response to queries is quick and efficient." - G2 aggregated feedback includes items such as "intuitive design" reported across multiple reviews. These are user-reported perceptions and should be validated in trials. - Community discussion (Reddit) included field commentary on Teams/email crossover, offline functionality, HR integration, and manager screens; this reflects informal user impressions rather than structured evaluation. - Direct quotes / sentiment (negative or mixed) - Community posts included comments indicating user friction during early rollout phases (for example, one comment characterized the initial months as difficult), suggesting adoption challenges in some deployments. - A sysadmin discussion raised an identity/SSO scenario for external users across tenants, indicating potential complexity for multi-tenant or multi-organization SSO setups. - Common criticisms and complaints (cross-source synthesis) - Implementation and early adoption friction appears in some community comments and reviews. - SSO edge cases and identity federation complexity for multi-tenant scenarios were raised by technical users. - Some reviewers reported a steeper learning curve compared with very simple LMS tools; procurement teams should validate admin and end-user UX in pilots. - Reasons customers selected the vendor (themes from reviews) - Compliance delivery and reporting visibility (dashboards and reporting were cited by multiple reviewers). - Positive support and implementation experience (implementation teams and helpdesk responsiveness noted in user reviews). - Integration with Microsoft ecosystem tools (Teams and Power BI references in user feedback). - Why some customers left for competitors (churn reasons) - Direct, documented churn narratives specific to this vendor were not prominent in the accessible sources. Procurement should request references and information on competitive displacements and lost deals. - Specific outcomes customers reported (vendor-published metrics should be validated) - Vendor case studies cite outcomes such as: - a significant reduction in classroom training time and a measurable increase in compliance across a defined employee population (Dartford & Gravesham NHS Trust) - reporting time reduced from several weeks to near-instant and a substantial uplift in compliance (St Mary’s University) - Critical note: these are vendor-published metrics. Procurement teams should ask for methodology, baselines, definitions of compliance, and independent validation where possible. - Deal-breakers and reasons customers did not purchase - Not clearly evidenced in accessible sources. Typical deal-breakers to test during procurement include complex reporting requirements, integration needs, external training monetization, and data residency or security constraints.

Vendor case studies highlighted in the provided materials

- Dartford & Gravesham NHS Trust - Reported outcomes: "substantial reduction in classroom training time" and "a modest increase in compliance across thousands of employees." - Critical evaluation: methodology was not provided in the excerpt (for example, baseline period, compliance definitions, or whether changes were attributable solely to the LMS). Other factors (policy changes, course redesign, staffing changes) may have contributed to outcomes. - St Mary’s University - Reported outcomes: "reporting time reduced from multiple weeks to near-instant" and "a significant uplift in compliance." - Critical evaluation: reporting-time reduction is plausible if manual processes were automated, but the scope of reports and integration details should be validated. The compliance uplift requires definition (completion rate, on-time completion, audit pass rates).

Co-branded viewpoint report

A co-branded vendor-Fosway viewpoint PDF was included in vendor materials.
Critical evaluation: co-branded content can be informative but should be treated as partially vendor-aligned; procurement should evaluate independence of methodology, sample sizes, and generalizability.

04Best fit

- Company sizes - Likely fit: mid-market to large enterprise organisations where compliance tracking and reporting are important and manager dashboards provide operational value. - Possible fit: smaller organisations seeking a managed, support-focused LMS experience, depending on budget and administration capacity. - Industries and verticals where adoption is strongest (with customer examples) - Healthcare / public sector: example vendor case study (NHS trust). - Higher education: example vendor case study (St Mary’s University). - Regulated industries generally (financial services, manufacturing) where compliance reporting is a priority. - Roles and personas: decision makers AND end users - Decision makers: Head of L&D, HR Director, People Ops leadership, Compliance leadership, CIO/IT (for SSO, integrations, security). - End users: employees and managers (manager dashboards are a highlighted capability). - Pain points and challenges the product addresses - Assignment and auditability of compliance training. - Reduction of manual reporting effort. - Manager-level visibility for learning completion and performance. - Combining internal content with off-the-shelf libraries. - Qualification criteria: what makes a strong fit - Requirement for compliance and reporting depth combined with packaged content options. - Willingness to invest in implementation services and ongoing admin governance. - Existing Microsoft-centric workflows where Teams/Power BI integration would be advantageous. - Disqualifiers: what makes a poor fit - Need for fully transparent, self-serve public pricing and minimal procurement involvement. - Requirement for a very lightweight LMS with minimal configuration and low administrative overhead. - Complex multi-tenant identity federation scenarios without willingness to engage professional services. - Real customer examples with company names when available - Dartford & Gravesham NHS Trust (vendor case study) - St Mary’s University (vendor case study) - Vendor displays customer logos such as Age UK, Aldermore, Bellway; logo display is not definitive proof of deployment scope.

05The pitch

What the product does (core value proposition in objective terms)

- Kallidus positions itself as a corporate learning platform focused on shifting L&D measurement from activity reporting (completions/participation) to outcome-oriented measurement (risk mitigation, retention, productivity, revenue). - Core products include: - **Kallidus Learn** (LMS for compliance and development) - **Kallidus Perform** (performance management module) - **Off-the-shelf eLearning content** (vendor states a sizable library of interactive compliance/upskilling courses; vendor also references accessibility and multilingual options) - The vendor highlights dashboards, reporting, compliance workflows, manager visibility, and integration into workplace tools (for example, Microsoft Teams) as part of its product capabilities.

Target market and market positioning

- Primary buyer persona: L&D leaders, HR, and People teams responsible for compliance programs and demonstrating business impact. - Positioning: mid-market to enterprise corporate LMS. The vendor has advertised strong third‑party ranking claims in its messaging; procurement teams should validate third-party ranking claims. - Sector evidence from vendor case studies and marketing indicates deployments in: - Healthcare and public sector (example: UK healthcare provider) - Higher education (example: university compliance reporting) - Organizations with UK-centric operations (given UK registered office and G-Cloud presence)

Get a comprehensive analysis of Kallidus including market position, competitive landscape, adoption trends, and peer benchmarks.

Download full report →