◆ Outcome 5.4a / For assessment platforms · LMS · ATS · HRIS / SDK + API · SOC 2 compliant

Your platform. Our measurement layer.

Assessment platforms, LMS providers, ATS vendors, and HRIS systems all face the same problem: their users need calibrated measurement, but building rigorous psychometrics in-house takes years and costs millions. QLM provides the measurement infrastructure as a drop-in layer — your end users see your brand and stay inside your product; the item calibration, adaptive engine, fairness audit, and Profile portability are QLM's. Four SDKs, three integration patterns, SOC 2 compliant, 70/30 revenue share. The trust boundary is architecturally enforced — partners cannot manipulate calibration, and the methodology disclosures exist in every deployment regardless of branding tier.

8-16 wks
Implementation
4 SDKs
Web · iOS · Android · RN
70/30
Revenue share
SOC 2
Compliant
◆ Integration · 01

Three patterns. Same trust guarantees.

Pick the integration pattern that fits your platform architecture and brand requirements. Each pattern preserves calibration integrity, fairness audit on every event, and cross-partner Profile portability. The trust boundary is non-negotiable across all patterns — the methodology accessibility, Profile verification, fairness audit transparency, and limits surfacing exist regardless of branding tier.

SDK init · Platform-context example / npm install @qlm/measurement-sdk / ~50 lines for full SDK pattern

Initialize QLM measurement in your platform context.

◆ PATTERN 2
Headless API

REST API drives measurement. You control the entire platform UI; QLM runs the engine and calibration in the backend.

~6-8 weeks integration
◆ PATTERN 3
Hybrid

SDK for question presentation, API for results processing. Pick what to customize, what to inherit from QLM defaults.

~5-7 weeks integration
// Initialize QLM measurement inside your platform context import { QLMMeasurement } from '@qlm/measurement-sdk'; QLMMeasurement.init({ partner_id: 'your-partner-id', context: 'assessment_platform', // lms | ats | hris | edtech end_user_id: user.id, // your user identifier configuration: { measurement_type: 'baseline', domain: 'software-engineering', role_template_id: 'senior-swe-l5', duration_target_minutes: 25 }, branding: { co_brand_qlm: true, // or false for white-label tiers primary_color: '#0B1929', // your brand color logo_url: 'https://yourplatform.com/logo.svg' }, callbacks: { onSessionComplete: (result) => { // Profile artifact signed by QLM, verifiable via public API saveProfileToYourSystem(result.profile_artifact); } } }); QLMMeasurement.render(containerElement);
Calibration integrity

Same items, item-pool selection, and calibration models as first-party. Partners cannot edit items, reorder them, or insert custom items.

Fairness audit on every event

Real-time fairness monitoring runs on every measurement regardless of platform origin. Items pulled from the global bank benefit all partner deployments.

Profile portability

Users own their Profile. A user generating a Profile through your platform can take it elsewhere with appropriate consent — the portability commitment is universal.

Cryptographic verification

Profile artifacts signed by QLM keys. Third parties verify against QLM's public API regardless of which platform mediated the measurement.

Critical constraint: the measurement engine, calibration, and fairness audit are QLM's; the user relationship and platform context are yours. Methodology accessibility, Profile verification, fairness audit transparency, and limits surfacing exist on every measurement regardless of branding tier — even in full white-label. A QLM measurement that strips out the honesty disclosures isn't a QLM measurement, regardless of what platform brand is on it. That's the foundational commitment we don't negotiate.
◆ SDK version 1.0 · April 2026 18-month deprecation support · semantic versioning

Real SDK code, real integration patterns, real trust boundary. Your platform, our measurement layer.

◆ Use cases · 02

Four platform types. One measurement layer.

Platform companies embed QLM measurement to solve fundamentally different problems — but they all share the same root need: calibrated, defensible, bias-audited measurement that would take years to build internally. QLM works across the full stack of talent and learning platforms. The same SDK, the same trust guarantees, the same revenue share model — configured for each platform context.

◆ USE CASE 1 — LMS
Learning Management
Learning platforms · Course marketplaces · LMS providers · Talent systems

Embed pre-course and post-course diagnostics to measure actual capability gain rather than content consumption. Most LMS platforms track completion; QLM measures whether learners actually acquired the skill. Adaptive item selection calibrates to each learner's level, producing a defensible baseline and a post-course delta that justifies the learning investment — to learners, to managers, and to procurement.

◆ USE CASE 2 — ATS
Applicant Tracking
Greenhouse · Lever · Workable · iCIMS

Replace resume screening with calibrated role-fit measurement at the top of the funnel. ATS platforms already own the candidate workflow — adding QLM measurement turns a document-sorting system into a genuine evaluation engine. Structured, bias-audited measurement produces defensible evidence for every hiring decision, with Profile artifacts that candidates can take with them regardless of hiring outcome.

◆ USE CASE 3 — HRIS
HR Platforms
Workday · SAP SuccessFactors · BambooHR

Continuous competency monitoring and skills gap analysis embedded in the systems HR teams already live in. HRIS platforms own the employee record; QLM adds a calibrated measurement layer that turns self-reported skills into verified capability profiles. Periodic re-measurement tracks genuine development over time, producing the skills graph that L&D, succession planning, and workforce analytics all need but rarely have.

◆ USE CASE 4 — EDTECH PUBLISHERS
EdTech & Publishers
Major publishers · Content providers

Add adaptive measurement to existing content libraries and replace legacy item banks with QLM's calibrated, fairness-audited engine. Publishers already own extensive content — QLM adds the adaptive diagnostic layer that turns static assessments into calibrated measurement. Item banks updated continuously, fairness monitoring built in, SOC 2 compliant data handling throughout. No need to rebuild the psychometric infrastructure that takes decades to validate.

◆ Trust boundary · 03

Trust boundary. Architecturally enforced.

When measurement runs inside a partner platform, several trust questions arise. Each has an architectural answer rather than a contractual one. Partners cannot manipulate calibration even if they wanted to — the engine runs server-side, items are immutable to partners, and signature integrity is preserved across every deployment.

◆ SIGNING AUTHORITY
QLM keys

Every measurement event and Profile signed by QLM keys. Partners cannot sign artifacts as if they were QLM-issued. Signature includes partner_id but signing authority is QLM's — the platform brand and the measurement authority are clearly separated.

◆ DATA FLOW
Minimal

Platform sends QLM: end_user_id, demographic data (with consent), session config. QLM sends platform: session_id, items, result, signed Profile artifact. Platform does not receive raw response data — the measurement stays in QLM's custody throughout.

◆ FAIRNESS GLOBAL
Shared

Fairness issues detected in any platform's user population produce item pulls affecting all partners. Calibration improvements happen across the entire system — the item bank is shared infrastructure that makes every deployment more robust over time.

◆ The honest read · 04

What partners cannot do.

QLM's platform partnership terms include hard architectural constraints. These exist because the measurement's integrity — and the trust of every end user on every platform — depends on them being non-negotiable. Five things platform partners explicitly cannot do, even in full white-label tier.

◆ Pricing · 05

Revenue share or usage-based.

Most platform partners use 70/30 revenue share on measurement-derived revenue. Platforms with pricing models that don't cleanly attribute revenue to individual measurement events use usage-based pricing instead. Strategic full white-label partnerships are bespoke and case-by-case.

◆ STANDARD OEM

Revenue share.

70/30 partner / QLM

On measurement-derived revenue. One-time implementation fees $50-250K depending on integration complexity. Configurations 1-3 (full co-brand to methodology-attributed white-label) available. Best fit for LMS and ATS platforms where measurement is a billable line item.

2-3 year initial term
◆ STRATEGIC

Full white-label.

Custom $1-5M+/yr min

Bespoke partnerships for top 5-10 strategic platform partners. Different revenue share, longer terms, contractual exclusivity in the partner's market segment. Methodology accessibility and Profile portability non-negotiable regardless of white-label depth.

Case-by-case approval
◆ PARTNERSHIP INQUIRY

Ready to embed measurement into your platform?

Currently accepting platform partnerships across LMS, ATS, HRIS, and edtech publisher categories. Implementation is 8-16 weeks; the trust boundary is non-negotiable.