47 questions to put in your RFP, and the vendor answers that should end the conversation. Written from real evaluations run by public agencies, telecom operators and professional services firms.
Most LMS evaluations are decided on a feature grid, then regretted eighteen months later on architecture: the connector nobody maintains, the second user directory, the reports that never reconcile. Each section puts one of those risks on the table before you sign.
Each question in the kit comes with the answer that should reassure you and the answer that should worry you.
04Where does learner personal data physically reside, and who can access it?
11How are users provisioned and deprovisioned, and who maintains that mechanism?
27Can a training completion trigger a business process without middleware?
Ask the architecture questions your IT team will ask you later, before the shortlist is locked.
A written basis for judging what each vendor will actually add to your org, and to your maintenance backlog.
Residency, subprocessors, licensing models and exit conditions, phrased so the answers are comparable.
We build a Salesforce-native LMS, so we are not neutral about the answers. We are neutral about the questions: every one of them comes from an evaluation a real buyer ran, and any serious vendor should be able to answer all 47 in writing. The last chapter states our own position openly, so you can weigh it, or ignore it.
