MDM RFP template: questions to ask mobile device management vendors

A mobile device management (MDM) request for proposal (RFP) does one job: it puts the same questions to every vendor in writing, so you can compare answers instead of relying on what you remember from demos. Done well, it turns a long vendor list into a short list worth testing.
This guide lists all 39 questions in a free, editable MDM RFP template, grouped into 13 sections, explains how to write each part, and shows how to read the answers.
Download: MDM RFP template (Word) [link to hosted DOCX URL, supplied by the client]
Where the RFP fits in an MDM purchase

The RFP filters on paper. Hands-on testing comes next: NIST advises organizations to “Implement and test a pilot of a mobile device solution before putting the solution into production” (NIST SP 800-124 Rev. 2). The MDM proof of concept guide covers that stage, including the weighted scorecard.
What goes in an MDM RFP
The template has 13 sections. The first block describes you; the rest asks the vendor to describe what it does today.
| Section | What it establishes |
|---|---|
| Issuing organization and scope | Dates, contact, device counts by platform, ownership models, regions, regulations |
| 1. Company overview | Who the vendor is, the exact edition proposed, references |
| 2. Platforms and devices | OS coverage, minimum versions, rugged and OEM support |
| 3. Enrollment | Automatic and manual methods, and which plan includes each (see MDM enrollment methods) |
| 4. Policy, security, compliance | Policies by platform, non-compliance handling, OS updates, reporting |
| 5. Applications | Public and private apps, configuration, enterprise app store |
| 6. BYOD and privacy | What admins can see on personal devices, selective wipe |
| 7. Kiosk and shared | Kiosk modes and shared device sign-in |
| 8. Remote support and offboarding | Remote actions, Activation Lock and FRP handling |
| 9. Hosting and security | Cloud or on-premises, data location, SOC 2 and ISO/IEC 27001, sub-processors, DPA, BAA |
| 10. Administration | Roles, audit logs, identity provider, API |
| 11. Support and SLAs | Channels, response times, onboarding, uptime |
| 12. Pricing and contract | Itemized price at your device count, terms, renewals, trial (see MDM costs) |
| 13. Exit and portability | Data export formats and deletion after termination |
Here are all 39 questions in the template, grouped by section. In the downloadable Word file, each question is a row with its ID and columns for Must or Should, the vendor’s response, supported platforms, required plan or add-on, evidence, and limitations.
1. Company and solution overview
1.1 Describe your company: headquarters, years in operation, ownership, and number of MDM customers.
1.2 Describe the solution being proposed, including product name, edition or plan, and modules included.
1.3 Provide two or three references from organizations of similar size and industry.
2. Platforms and device types
2.1 List supported platforms and minimum OS versions: iOS, iPadOS, Android, Windows, macOS, Linux, ChromeOS.
2.2 Which ownership models do you support on each platform (company-owned, BYOD, shared, kiosk)?
2.3 How quickly after a major OS release do you support new management features?
2.4 List supported rugged or specialist devices and OEM integrations (for example, Samsung Knox, Zebra).
3. Enrollment
3.1 Which automatic enrollment programs do you support (Apple Automated Device Enrollment, Android zero-touch, Samsung Knox Mobile Enrollment, Windows Autopilot)?
3.2 Which manual and BYOD enrollment methods do you support? Do any require a factory reset?
3.3 Can devices enrolled in our current MDM move to your solution without a factory reset? Describe the process by platform.
4. Policy, security, and compliance
4.1 Describe passcode, encryption, restriction, and certificate policies by platform.
4.2 How do you detect and remediate non-compliant, jailbroken, or rooted devices?
4.3 How do you manage OS updates (defer, schedule, enforce) by platform?
4.4 Which compliance frameworks do your reports map to, and what can be exported?
5. Application management
5.1 Describe public, private, and web app deployment, including Apple Apps and Books and managed Google Play.
5.2 Do you support managed app configuration and silent install and removal?
5.3 Do you offer an enterprise app store or self-service catalog for users?
6. BYOD and privacy
6.1 Describe exactly what an administrator can and cannot see on a personally owned device, by platform.
6.2 Describe selective wipe and how personal data is protected when an employee leaves.
7. Dedicated, kiosk, and shared devices
7.1 Describe single-app, multi-app, and web kiosk modes by platform.
7.2 Do you support shared devices with user sign-in and sign-out?
8. Remote support and offboarding
8.1 Which remote actions are available by platform (lock, locate, wipe, retire, remote view, remote control)?
8.2 How do you handle Apple Activation Lock and Android Factory Reset Protection when devices change hands?
9. Hosting, data residency, and security
9.1 Is the solution offered as cloud, on-premises, or both? Where are cloud data centers located?
9.2 Provide your most recent SOC 2 report and ISO/IEC 27001 certificate, or state which you hold.
9.3 List sub-processors and describe how customers are notified of changes.
9.4 Provide your data processing agreement (DPA). For healthcare buyers, state whether you sign a business associate agreement (BAA).
9.5 Describe incident response and breach notification timelines.
10. Administration and integrations
10.1 Describe role-based access control and audit logging.
10.2 Which identity providers do you integrate with for admin and user sign-in?
10.3 Provide API documentation and list available integrations (ITSM, SIEM, asset management).
11. Support and service levels
11.1 Describe support channels, hours, languages, and response-time SLAs by plan.
11.2 Describe onboarding and migration assistance included in the price.
11.3 What is your uptime commitment, and what remedies apply if it is missed?
12. Pricing and contract
12.1 Provide pricing for our device count, by plan, with all required add-ons itemized.
12.2 State contract length, billing terms, price-increase limits, and renewal terms.
12.3 Is a free trial or proof of concept available, and which features and device limits does it include?
13. Exit and data portability
13.1 How can we export device inventory, policies, and logs at the end of the contract, and in which formats?
13.2 How and when is our data deleted after termination, and do you provide written confirmation?
Download: MDM RFP template (Word) [link to hosted DOCX URL, supplied by the client]
How to write the RFP
Start with scope, not features
Vendors answer better when they know what they are managing. Give device counts by platform, ownership models, locations, and the regulations you work under. “450 Android scanners in three warehouses, 120 Windows laptops, BYOD for 60 managers, GDPR” gets a more useful response than a list of 200 features.
Mark every question as Must or Should
A Must is a requirement you will not compromise on: a vendor that fails it is out. Keep Musts to the requirements that would end the project, such as support for your rugged devices or EU data residency. If everything is a Must, nothing is.
Ask for the plan, not the product
MDM vendors often put features like automatic enrollment or OS patch management in higher tiers. The template has a Required plan or add-on column for every question, so the price in section 12 matches the features in sections 2 to 11.
Ask for evidence on security and privacy
Ask for documents, not adjectives:
- Security assurance: the latest SOC 2 report, which the AICPA frames around security, availability, processing integrity, confidentiality, and privacy (AICPA), and any ISO/IEC 27001 certificate.
- GDPR: under Article 28, processing by a processor “shall be governed by a contract”, which must cover sub-processors, deletion or return of data at the end of the service, and audits (GDPR Article 28). Ask for the DPA and sub-processor list with the response.
- HIPAA: covered entities generally need a business associate agreement with vendors that handle protected health information (HHS). Ask whether the vendor signs one.
How to read vendor responses
Most RFP answers are written by people who answer RFPs every week. These patterns tell you where to look harder:
| Answer pattern | What to ask next |
|---|---|
| “Yes” with no description | How, on which platforms, and on which plan? |
| “On the roadmap” | Target release date, and will you put it in the contract? |
| “Via a partner” or “through integration” | Which partner, at what extra cost, and who supports it? |
| “Fully compliant with” a regulation | Which controls, and which documents show it? Compliance belongs to the customer’s whole program, not a tool. |
| Pricing “from” a figure | Itemized price for our device count and plan, with add-ons |
| No answer on exit or export | Formats, timelines, and deletion confirmation in writing |
From RFP to shortlist
- Remove any vendor that fails a Must, regardless of how strong the rest of the response is.
- Check that the plan quoted in section 12 includes every capability claimed in sections 2 to 11.
- Call one reference per remaining vendor, ideally in your industry and at your fleet size.
- Invite two or three vendors to a proof of concept, and send them your test plan in advance.
For a starting list of vendors, see MDM solutions compared. For Apple-only fleets, add the criteria from the Apple MDM buyer’s guide. If you are replacing an existing MDM, section 13 of the outgoing contract matters as much as the new one; the MDM migration guide covers the move.
Sending an RFP to Bento MDM
Bento MDM is offered as Bento Cloud MDM on all plans, with on-premises deployment on the Enterprise plan; see pricing for what each plan includes.
Frequently asked questions
Your scope (devices, platforms, ownership, regions, regulations), questions on enrollment, policies, apps, BYOD, kiosk, remote actions, hosting and security, administration, support, pricing, and exit terms, plus clear instructions and deadlines. The template covers all 13 sections.
Four to eight is a workable range: enough to compare, few enough to read every answer properly. Shortlist two or three for a proof of concept.
A request for information (RFI) gathers general information to understand the market. An RFP asks vendors for a specific proposal and price against your defined scope.
Set your evaluation criteria and weights before you issue the RFP, and record them, so scoring cannot drift toward whichever answers look most attractive once they arrive. Share your Must requirements and deadlines with vendors, and the criteria too if your procurement rules require it. Then score the written responses against those criteria and confirm the results in hands-on testing; the proof of concept guide includes a weighted scorecard you can set up in advance.
Ask the same questions, compare the same answers
An MDM RFP will not tell you which platform is right, but it will tell you which ones are not, on paper and in writing, before anyone spends two weeks testing. Define the scope, keep Musts few, ask for plans and evidence, and the shortlist becomes a list of vendors worth your time.
Related Articles


