Mobile device management (MDM) proof of concept: what to test before choosing a vendor

A demo shows how a mobile device management (MDM) platform works on the vendor’s devices, with the vendor driving. A proof of concept (POC) shows how it works on yours, with your team driving. NIST’s guidance on enterprise mobile security puts it simply: “Implement and test a pilot of a mobile device solution before putting the solution into production” (NIST SP 800-124 Rev. 2).
This guide sets out an example two-week POC: how to scope it, which devices to test, 22 tests with pass criteria, and a weighted scorecard for comparing vendors.
Download: MDM proof of concept scorecard (Excel) [link to hosted XLSX URL, supplied by the client]
Demo, trial, proof of concept, or pilot?
| Stage | Who drives | Devices | Question it answers |
|---|---|---|---|
| Demo | Vendor | Vendor’s | Does the product do what we need, in principle? |
| Free trial | You | Yours, limited | Can we use the console without help? |
| Proof of concept | You, with test plan | A test set covering every platform and use case | Does it pass our must-have tests? |
| Pilot | You, in production | A real user group | Does it hold up in daily use before full rollout? |
A free trial often serves as a POC container, but it isn’t the same thing. A trial without a test plan usually ends with a general impression rather than a decision.
Before the trial starts: scope and success criteria
Most trial periods are short, so do this work before you request one:
- List the use cases. Company-owned phones, BYOD, shared tablets, kiosks, Windows laptops, Macs. Each one becomes a set of tests.
- Mark the must-haves. A must-have that fails ends the evaluation for that vendor, whatever the overall score.
- Confirm what the trial includes. Trials often run on one plan. If the features you need, such as automatic enrollment, sit on a higher plan, ask for a vendor-led pilot of that plan rather than scoring a plan you will not buy. MDM pricing varies by tier and by vendor.
- Prepare automatic enrollment. Apple Automated Device Enrollment requires your organization to be in Apple Business (formerly Apple Business Manager). Android zero-touch enrollment works with devices bought through a participating reseller (Android Enterprise). Windows Autopilot requires the device to be registered with Autopilot (Microsoft Learn). Each can take days to set up, so start before the trial clock does.
- Name the testers. At least one IT admin who will run the platform day to day, and one or two end users for BYOD and frontline devices.
Build the test device set
A POC on one spare phone tests almost nothing. Cover every combination of platform and ownership you will manage:
| Device | Why it is in the test set |
|---|---|
| New company iPhone or iPad | Automatic enrollment, supervision, Activation Lock handling |
| Personal iPhone | BYOD enrollment and what the admin can and cannot see |
| Company Android phone | Fully managed mode, zero-touch, Enterprise FRP |
| Personal Android phone | Work profile enrollment with no reset |
| Rugged or shared device | Kiosk and dedicated device lockdown (see MDM kiosk mode) |
| Windows laptop and Mac | If in scope: Autopilot, policies, patching |
| An older OS version you still run | Shows what fails on the devices you cannot replace yet |
The POC checklist: 22 tests and pass criteria
Run every test on every shortlisted vendor and record Pass, Partial, Fail, or N/A for tests outside your scope. The scorecard download includes the same list with built-in tracking. The target times in the table are examples; set your own before testing, and keep the evidence listed for each test so you judge every vendor on the same record. Each platform allows different things, so check remote control and compliance reporting by platform before you set pass criteria.
| Area | Test | Platform / enrollment mode | Pass criteria | Target time (example) | Evidence |
| Enrollment | Automatic enrollment on a new company device | iOS and iPadOS: Automated Device Enrollment; Android: zero-touch or Knox Mobile Enrollment; Windows: Autopilot | Enrolls at first boot with no IT touch; assigned profile applied | Under 15 minutes from power-on | Enrollment record; screenshot of applied profile |
| Enrollment | Manual enrollment by QR code or link | Android fully managed (QR code); other platforms by the method the vendor offers | Admin completes it using written steps only | Under 10 minutes per device | Timed run; enrollment record |
| Enrollment | BYOD enrollment | iOS account-driven User Enrollment; Android work profile | No factory reset; employee completes it unaided | Under 10 minutes | Employee-side screenshots; record showing BYOD mode |
| Policies and compliance | Passcode, encryption, and restriction policy | Every company-owned mode in scope | Applied and reported compliant | Within 15 minutes of assignment | Compliance report export |
| Policies and compliance | Change a policy on enrolled devices | Every enrolled mode | Reaches every test device without re-enrollment | Within 15 minutes | Policy status per device, before and after |
| Policies and compliance | Non-compliant device | Every enrolled mode | Flagged and alerted; remediation action available | Alert within 15 minutes | Alert record; remediation log |
| App management | Deploy a public app silently | Supervised iOS; Android fully managed and work profile; Windows | Installs without user prompts | Within 15 minutes | Install status per device |
| App management | Deploy an in-house app with managed configuration | Android and iOS managed configuration; Windows if in scope | Installs and reads the managed configuration | Within 30 minutes | Install status; screenshot of applied configuration |
| App management | Update and remove an app | Same modes as above | Completes without user action | Within 30 minutes | Install history |
| BYOD privacy | Admin visibility on a BYOD device | iOS User Enrollment; Android work profile | No personal apps, messages, photos, browsing, or location visible | Not timed | Screenshot of the device record in the console |
| Kiosk | Single-app and multi-app kiosk | Android dedicated device; supervised iPad; Windows if in scope | Stays locked after reboot; exit needs an admin credential | Back in kiosk within 2 minutes of reboot | Photo or video; policy record |
| Remote actions | Remote lock | Each platform and mode in scope | Device locks | Within 2 minutes | Action log with timestamps |
| Remote actions | Locate | Company-owned modes only | Location shown for company devices; not available on BYOD | Within 5 minutes | Location record; BYOD device shows no location |
| Remote actions | Remote view | Each platform where you need it | View session starts, with the user consent the platform requires | Session within 2 minutes | Session log; consent prompt screenshot |
| Remote actions | Remote control | Platforms where the vendor offers control | Admin can operate the device | Session within 2 minutes | Session log |
| OS updates | Defer, schedule, or enforce an update | Supervised iOS; Android fully managed; Windows | Policy applies and reports status | Status reported within 24 hours | Update compliance report |
| Offboarding | Retire a BYOD device | iOS User Enrollment; Android work profile | Work data removed; personal data intact | Within 15 minutes of next check-in | Action log; employee confirmation |
| Offboarding | Wipe and re-enroll a company device | Automated Device Enrollment; zero-touch or Knox Mobile Enrollment; Autopilot | Re-enrolls automatically; Activation Lock and FRP handled | Back in service within 30 minutes | Action log; re-enrollment record |
| Reporting and admin | Export inventory and compliance report | Console | Export has the fields your audits need | Under 5 minutes | Exported file |
| Reporting and admin | Role-based access and audit log | Console | Limited admin cannot exceed role; actions logged | Not timed | Audit log export |
| Integrations | Identity provider sign-in and API | Console and API | Sign-in through your IdP; API returns device inventory | Not timed | Sign-in log; sample API response |
| Support | Open a real support ticket | Vendor support | Useful answer within the SLA you will be quoted | The quoted SLA | Ticket thread with timestamps |
The last test matters more than it looks. During a POC, you are often talking to sales engineers; the ticket shows what support looks like after the contract is signed.
An example two-week schedule

This is one example schedule, built to fit a 14-day trial. Adjust it to your scope: more platforms, regions, or must-have tests need more time.
- Prep: scope, must-haves, test devices, and automatic enrollment accounts.
- Week 1: enroll every device by every method you plan to use, then apply policies and deploy apps. Enrollment problems surface here, while you still have time to involve the vendor.
- Week 2: BYOD, kiosk, remote actions, offboarding, reporting, and the support ticket. Score on the last day, while results are fresh.
If you are replacing an existing MDM, run the POC before planning the move; the MDM migration guide covers the pilot and cutover that follow.
Score vendors with a weighted scorecard
Pass/fail results show whether a vendor qualifies. A weighted score shows which qualifying vendor fits best. Set weights before testing so results do not shape them. The downloadable scorecard uses these defaults, which you can change:
| Area | Default weight |
| Enrollment | 15% |
| Policies and compliance | 15% |
| App management | 10% |
| BYOD privacy | 10% |
| Kiosk | 5% |
| Remote actions | 5% |
| OS updates | 5% |
| Offboarding | 5% |
| Reporting and admin | 10% |
| Integrations | 5% |
| Support | 10% |
| Cost at your fleet size | 5% |
The scorecard turns test results into a score in four steps:
- Each result converts to a rating: Pass = 5, Partial = 3, Fail = 1. Not applicable (N/A) is for tests outside your scope and is left out of the calculation.
- An area’s rating is the average of its rated tests. Cost at your fleet size has no test, so you rate it yourself from 1 to 5 using the vendor’s quote.
- If every test in an area is N/A, the area drops out, and the remaining areas share its weight in proportion to their weights. For example, if Kiosk (5 percent) does not apply, the other areas share 95 percent, and the score is (points earned/95)* 100.
- A failed must-have disqualifies the vendor, whatever its score. Flag a must-have marked N/A for review, because a requirement you depend on shouldn’t be out of scope.
Red flags during a POC
- Features described as “on the roadmap”. Score what works today.
- A POC on a different plan than the quote. Ask for the plan you will buy, or a written list of what differs.
- Tests only in a vendor-run demo tenant. You need your own tenant with your own devices.
- No answer to the support ticket until sales steps in. That is the support you will get later.
- No data export. If inventory and reports cannot leave the platform, the next migration gets harder.
Running a POC with Bento MDM
The Bento MDM free trial runs for 14 days on Bento Cloud MDM, supports up to 25 devices by default, and doesn’t require a credit card. It includes the Standard plan feature set. Larger fleets can request more capacity on the trial form, and the Bento team sets up on-premises evaluations separately. Check the pricing page for which features sit on each plan, and if a must-have test depends on a higher plan, ask for a pilot of that plan.
Frequently asked questions
There is no standard length. This guide uses two weeks of testing as an example because it fits a 14-day trial, such as Bento MDM’s, when scoping, test devices, and automatic enrollment accounts are ready before the trial starts. Fleets with more platforms, regions, or must-have tests may need longer, often as a vendor-led pilot.
Enough to cover each platform and ownership model you will manage, usually one device per combination plus an older OS version you still support. Quantity matters less than coverage.
A proof of concept tests whether a platform passes your requirements on a controlled test set. A pilot runs the chosen platform with real users in production before full rollout.
Yes, if the trial includes the features your must-have tests depend on. If it does not, ask the vendor for a pilot of the plan you intend to buy. For Apple-only fleets, the Apple MDM buyer’s guide covers Apple-specific criteria; for a vendor shortlist, see MDM solutions compared.
Test the week after go-live, not the demo
A demo answers whether a platform can do something. A proof of concept answers whether your team can do it, on your devices, in the time you have. Write the test plan first, cover every device type, score against weights you set in advance, and the decision usually makes itself.
Related Articles



