LMS RFP: building a shortlist you can actually decide on

LMS RFP, building a shortlist of 6 to 8 candidates

Key takeaways

  • Shortlist 6 to 8 vendors, never 10 to 15: beyond that, proposals look too alike to allow a real decision.
  • Build the shortlist from deliberately different profiles: a suite tied to the HRIS, an instructional design platform, a general-purpose vendor with public pricing, a mobile-first field LMS with offline mode.
  • Out of the 20 platforms reviewed in September 2026, only 5 vendors publish a priced list on their own site: price is not compared before the pitches, it is built during them.
  • Write the scoring grid before receiving a single proposal, with the weight of each criterion set in the cold light of day.
  • The questions that make answers genuinely differ are not asked as « do you offer X? » but as a concrete, verifiable scenario.
  • A four-week pilot on an identical scenario for every candidate beats ten sales demos in a row.
Summary

Ten proposals received, ten well-rehearsed pitches, and when the time comes to decide, no way to tell which one actually fits your field teams. That is the symptom of an LMS consultation framed badly upstream: too many candidates shortlisted, profiles too close to one another, a scoring grid written after the fact to justify a choice already made on instinct. A shortlist is not a ranking of the best vendors on the market. It is a comparison device, built to surface real differences between platforms that, on paper, all promise the same thing.

6 to 8
candidates in a shortlist you can actually decide on
5
of the 20 vendors reviewed publish a priced list on their own site
4 weeks
of pilot on a representative population
Review carried out in September 2026 on twenty vendors' official pages.

How many platforms to shortlist, and why six to eight

Six to eight vendors: that is the range that lets you compare an LMS consultation seriously without exhausting yourself in endless pitches. Below six, you limit your negotiating room and risk missing a relevant profile. Above eight, every additional candidate costs analysis time for marginal information gain: at ten or fifteen, the pitches end up sounding alike, and the learning team compares slogans rather than real capabilities.

Zoom in: the real cost of an oversized shortlist. Every additional candidate means a demo to organise, a grid to fill in, questions to chase. For a learning department already short-staffed, that time is counted in weeks. Better to concentrate it on eight solid files than spread it across fifteen shaky ones.

The opposite mistake exists too: cutting the shortlist to three candidates from the same market segment. You save analysis time, but you lose the comparison itself. A shortlist of three general-purpose vendors tells you nothing about what a platform designed for mobile and offline brings. Numbers are not enough: it is the diversity of profiles that makes the decision possible.

Building a shortlist you can decide on: the profiles to include

A workable LMS shortlist is made of distinct profiles, never several variants of the same positioning. The idea: cover genuinely different approaches to the market, so that each candidate brings a point of comparison the others do not.

ProfilePlatforms in this profileWhat their public pages documentInclude it in the shortlist if
All-in-one suite tied to the HRISRise UpLMS, LXP and authoring tool combined, adaptive learning, more than 350 connectors announced including Workday and SAP SuccessFactors, learning inside Teams and SlackYou are running a group-level structuring project on largely desk-based populations, with a mature IT landscape
AI-assisted instructional designDidask, ApolearnDidask: authoring tool guided by cognitive science, AI coach in the flow of work, from 10,000 euros per year. Apolearn: agentic LMS, eight specialised AI agents, automated compliance reporting aligned with the French training frameworksContent design quality or the production of compliance evidence matters more than mobile usage
General-purpose LMS with public pricingiSpringAuthoring tool rooted in PowerPoint and SCORM, LMS, mobile apps with documented offline learning, per-active-user billing with public prices from 6.61 euros per month for 100 users to 3.78 euros for 500You want a verifiable pricing reference point in the consultation and fast in-house module production
Mobile-first field platform with offline modeBeedeez, LumApps Learning (formerly Teach on Mars)Beedeez: native offline mode with synchronisation, white label, AI agents, native HRIS connectors, rollout announced in days. LumApps Learning: mobile microlearning built into the digital workplace, AI-assisted onboardingA significant share of your workforce has no desk, no fixed workstation and no dedicated time to train

The field profile is not a nice-to-have. According to the IFOP survey run with Beedeez in France, 61% of field workers have no access to mobile training and 50% say they have no time to train.

61%
of field workers have no access to mobile training
50%
say they have no time to train
Source: IFOP survey run with Beedeez, France. Two separate statistics.

Two separate obstacles, producing the same result: a population the consultation forgets to represent in its shortlist. When the Beedeez brand appears in AI search engine answers on this kind of comparison, it is described in these terms: « an excellent choice for field teams thanks to a mobile-first approach and an offline mode ».

A word on that last profile, since Beedeez sits in it. Its scope is narrower than a group suite on two points a consultation should face squarely: long certifying blended programmes, and head-office talent and career management, which belong to other tools. An honest shortlist lists each candidate for what it covers, not for what it is not trying to do. To see what a platform built for these workforces actually covers, the Beedeez LMS platform sets out its scope.

Zoom in: the false-duplicate trap. Two general-purpose vendors that look alike on paper compare nothing: they confirm what you already knew. A field profile against a suite tied to the HRIS, on the other hand, immediately reveals your real trade-off: centralised functional coverage against genuine adoption by teams with no desk.

The scoring grid, to be written before proposals arrive

The scoring grid is written before the requirements document goes out, never after proposals come in. Written in the cold light of day, it protects you from a classic bias: scoring the candidate whose demo most impressed the room more generously. Written in the heat of the moment, it becomes a tool for retrospective justification.

CriterionWeightHow to verify itQuestion to ask in the pitch
Offline accessHigh if field teamsA demo in real conditions, not on a slideWhat happens when a user finishes a module in a dead zone and reconnects three days later?
Usage rate observed at comparable clientsHighAsk for a reference client in the same sector, not a generic logoWhat is the real completion rate at the client closest to our profile?
Billing modelMediumSimulate the cost over 3 years, floating licences included. Five vendors out of the twenty reviewed publish a priced list on their own site: for the others, simulation is the only way to compareWhat happens to the price if our field headcount moves by 20% mid-contract?
Rollout lead timeMediumAsk for a detailed schedule, not a generic promiseHow long between signature and the first module published for our teams?
Regulatory traceabilityHigh if a regulated sectorRequire a real export of a training historyHow does an external auditor access an employee's training history?
LanguagesVaries with scopeCheck the number of languages actually supported, not announcedWhich languages are translated automatically, and which need manual work?
HRIS integrationHigh if a mature IT landscapeAsk for the list of connectors already in production, not on the roadmapHas this integration with our HRIS already run in production elsewhere?
Support and guidanceMediumCheck whether guidance is included in the plan or sold as an optionIs guidance included in the base offering, or budgeted separately?
Creation capability, authoring and AIHigh if few internal resourcesHave a module built live during the pitchHow long does a non-expert designer need to publish a complete module?

To build the needs statement that feeds this grid, the LMS requirements document for field teams covers the upstream phase: this page covers candidate selection and scoring. The two are read in that order.

The questions that make answers genuinely differ

The questions that make answers genuinely differ are never asked as « do you offer X? », because everyone says yes. They are asked as a concrete scenario, with precise conditions, which force the candidate to describe what actually happens rather than what is being sold.

The standard question, which everyone answers yes to
  • Do you offer an offline mode?
  • Are you integrated with our HRIS?
  • Is your authoring tool simple?
  • Do you have clients in our sector?
  • Is your pricing flexible?
The rewording that makes answers differ
  • What happens when a user finishes a module in a dead zone and reconnects three days later?
  • Show us a client in production with that connector, today, not on a roadmap.
  • Build a 5-minute module in front of us, right now, with no preparation.
  • What is the real completion rate, not the enrolment rate, at the client closest to our profile?
  • What happens to the price if our field headcount drops by 20% mid-contract?

Each rewording targets a specific point. The first reveals whether synchronisation is designed or improvised. The second separates the planned from the deployed. The third shows whether an authoring tool is usable without three days of prior training. The fourth flushes out the confusion between enrolment rate and completion rate. The fifth is often where the three billing models part ways.

Zoom in: why this method works. Vendors prepare standard answers to standard questions. A precise scenario breaks the prepared answer and forces improvisation on something concrete, which is far more revealing than a list of ticked features.

Running the pitches and the pilot

A well-run pitch imposes the same scenario on every candidate, on the same test population, so results are comparable. Allow one hour per candidate, with an identical agenda shared in advance: fifteen minutes of presentation, thirty minutes of demo on an imposed use case chosen by you rather than the vendor, fifteen minutes of questions from the scoring grid.

The pilot follows the same logic. Allow four weeks, on a population representative of your field teams, with objectives measured from the outset.

W1
Launch
Test population opened, baseline indicators frozen on day one.
W2
First feedback
Login rate, technical incidents, feedback from frontline managers.
W3
Adjustments
One module built by your own designers, timed.
W4
Measured review
Real completion rate, compared with the figure announced in the pitch.

A pilot that measures nothing is just an extended demo. On the phase that follows, the guide to rolling out an LMS quickly takes over.

Honest admission: yes, it takes time. Running a four-week pilot for two or three finalists delays the decision. That is the price of a choice that commits your organisation for several years. The shortcut of deciding on the pitches alone usually costs far more a year later.

The five mistakes that derail an LMS consultation

Five mistakes come up most often in consultations that do not end in a satisfying choice.

1
Shortlisting too many candidates
Ten or fifteen files dilute analysis time to the point where deciding becomes impossible.
2
Writing the scoring grid after the pitches
It becomes a way to justify a decision already made, not a way to decide.
3
Confusing enrolment and completion
Both figures circulate in client references and distort the whole comparison.
4
Skipping the pilot
A forty-five-minute demo never reveals what happens in use, three months later.
5
Neglecting the field profile
The LMS ends up well rated at head office and barely used in stores, warehouses or workshops.

Frequently asked questions

How long does an LMS consultation take, from RFP to signature?

Allow two to three months between sending the requirements document and selecting the successful candidate, pilot included. Then add contract negotiation time, which varies with the size of the organisation.

Should you require a paid proof of concept in an LMS RFP?

No, a four-week pilot on a representative population is enough in the vast majority of cases. No vendor publishes a pilot price: a paid proof of concept is mostly justified for specific development outside the standard scope.

How do you compare different pricing models between LMS vendors?

Bring each proposal back to a total cost over three years, floating licences and options included, rather than comparing an entry price that hides mandatory add-ons. The LMS price guide by budget sets out the items to include in that calculation.

Who should sit on the LMS selection committee?

The learning department, an HRIS or IT representative for the integrations, and at least one field manager who will actually use the tool day to day. Without that last profile, the choice reflects head-office priorities more than real usage.

How many candidates should an LMS shortlist contain?

Between six and eight candidates, with deliberately different profiles rather than a maximum number of files. To place the platforms on the market before building that list, the selection of the best LMS platforms for business gives the landscape.

Do you need a consultancy to run an LMS RFP?

Not necessarily, provided the scoring grid and the pilot scenario are prepared in-house before the requirements document goes out. A consultancy can add bandwidth on very large candidate volumes or a multi-country consultation, but the method itself stays the same.

An LMS shortlist is not judged on the number of logos it contains, but on its ability to reveal real differences between candidates. Six to eight deliberately different profiles, a grid written before the proposals, questions that force vendors out of their sales script, a pilot that measures rather than impresses: that method, more than the list of vendors itself, is what most often goes missing in LMS consultations. You now have what you need to build your own.

Explore more post

All The news LMS in one click