Most LMS RFPs collect brochures. Here’s one that sorts vendors.
A typical LMS RFP asks two hundred feature questions that every vendor answers yes to. The discriminating requirements are usually absent — so scoring rewards completeness of marketing rather than capability. This is the requirement set that actually separates the market.
Why feature-matrix RFPs produce indistinguishable scores
Feature questionnaires reward vendors with mature marketing functions, not mature products — ‘Do you support mobile learning?’ has one answer across the entire market. When the top three finalists score within a few points of each other, that isn’t a close market; it’s an instrument that failed to discriminate, and the decision quietly reverts to price or relationship.
Discriminating requirements share a property: they can’t be answered yes without a demonstration. What does the platform report about a cohort at ninety days, per person? What mechanism determines the next question a specific learner sees? What exactly does the evidence export contain for one person, one requirement, across a mid-period content revision? Vendors either show these or reveal the gap, and the scoring spread reappears.
The requirement set worth copying
Retention measured per person at delay; adaptation mechanism explained and demonstrated; evidence export with revision lineage; HRIS-driven assignment; accessibility verified by your team; exit and portability terms.
Score demonstrations, not answers
Weight live demonstration and reference-cohort data above questionnaire completeness. The vendors who dislike this scoring are giving you information.
Build the pilot into the process
A paid pilot clause for finalists converts procurement from prediction to measurement — one quarter, one cohort, real data. It’s the single strongest mechanism in the whole process.
Score the vendors on this
The RFP’s hardest rows, live: retention measurement, evidence exports, integration depth — ask every vendor for this screen.
Interface shown as an illustration with representative numbers, not a screenshot — the layout is the product’s.
Take the requirement set, whoever wins.
We’ll send the discriminating requirements as a document you can use in any RFP — including ones we don’t win.
The evidence this page stands on
Questions buyers ask
Can you send an editable RFP template?
Yes — ask on the call and we’ll send the requirement set in a usable format, with the discriminating questions marked. It’s genuinely useful even where we’re not a fit.
How long should an LMS RFP process take?
The paperwork can run in weeks; the pilot quarter is what makes the decision sound. Total elapsed time is similar to a heavy questionnaire cycle, with evidence at the end instead of scored promises.
Should we shortlist on price first?
Price-first shortlisting on a category where capability varies this much tends to select for delivery-only platforms. Shortlist on the three questions, then negotiate price among vendors who passed.
What contract terms matter most?
Exit and portability (export formats, deletion, notice), data residency specifics, uptime commitments, and integration contract stability. Feature commitments age faster than these.
What if our procurement rules require a feature matrix?
Keep it and append the discriminating section with heavy scoring weight — the matrix satisfies process while the demonstrations make the decision.
See it on your own content.
Bring one course. We’ll show you the retention curve your current training leaves behind — and what scheduled review does to it.
- 30 minutes, on your calendar — pick a slot here
- Run on your own content wherever possible, not a canned deck
- You see the dashboards, the learner surface and the evidence exports
- No commitment — and pilot data stays yours either way