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

Laura Ciurea
Laura Ciurea
Marketing Manager
Laura Ciurea
About Laura Ciurea
Marketing Manager
Laura Ciurea brings extensive expertise in product and project management, corporate communications, investor relations, and event organization at Bento - Intellectually Curious. She plays a key role in the company's external presence, overseeing official press releases and financial updates for Bento (BVB: BENTO). Known for her ability to promote innovative technology solutions and her strong organizational skills, she is regarded as a resourceful and reliable business partner, capable of managing complex initiatives from strategy through to execution.
Oct 24, 2026
9 minutes
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?

StageWho drivesDevicesQuestion it answers
DemoVendorVendor’sDoes the product do what we need, in principle?
Free trialYouYours, limitedCan we use the console without help?
Proof of conceptYou, with test planA test set covering every platform and use caseDoes it pass our must-have tests?
PilotYou, in productionA real user groupDoes 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:

DeviceWhy it is in the test set
New company iPhone or iPadAutomatic enrollment, supervision, Activation Lock handling
Personal iPhoneBYOD enrollment and what the admin can and cannot see
Company Android phoneFully managed mode, zero-touch, Enterprise FRP
Personal Android phoneWork profile enrollment with no reset
Rugged or shared deviceKiosk and dedicated device lockdown (see MDM kiosk mode)
Windows laptop and MacIf in scope: Autopilot, policies, patching
An older OS version you still runShows 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.

AreaTestPlatform / enrollment modePass criteriaTarget time (example)Evidence
EnrollmentAutomatic enrollment on a new company deviceiOS and iPadOS: Automated Device Enrollment; Android: zero-touch or Knox Mobile Enrollment; Windows: AutopilotEnrolls at first boot with no IT touch; assigned profile appliedUnder 15 minutes from power-onEnrollment record; screenshot of applied profile
EnrollmentManual enrollment by QR code or linkAndroid fully managed (QR code); other platforms by the method the vendor offersAdmin completes it using written steps onlyUnder 10 minutes per deviceTimed run; enrollment record
EnrollmentBYOD enrollmentiOS account-driven User Enrollment; Android work profileNo factory reset; employee completes it unaidedUnder 10 minutesEmployee-side screenshots; record showing BYOD mode
Policies and compliancePasscode, encryption, and restriction policyEvery company-owned mode in scopeApplied and reported compliantWithin 15 minutes of assignmentCompliance report export
Policies and complianceChange a policy on enrolled devicesEvery enrolled modeReaches every test device without re-enrollmentWithin 15 minutesPolicy status per device, before and after
Policies and complianceNon-compliant deviceEvery enrolled modeFlagged and alerted; remediation action availableAlert within 15 minutesAlert record; remediation log
App managementDeploy a public app silentlySupervised iOS; Android fully managed and work profile; WindowsInstalls without user promptsWithin 15 minutesInstall status per device
App managementDeploy an in-house app with managed configurationAndroid and iOS managed configuration; Windows if in scopeInstalls and reads the managed configurationWithin 30 minutesInstall status; screenshot of applied configuration
App managementUpdate and remove an appSame modes as aboveCompletes without user actionWithin 30 minutesInstall history
BYOD privacyAdmin visibility on a BYOD deviceiOS User Enrollment; Android work profileNo personal apps, messages, photos, browsing, or location visibleNot timedScreenshot of the device record in the console
KioskSingle-app and multi-app kioskAndroid dedicated device; supervised iPad; Windows if in scopeStays locked after reboot; exit needs an admin credentialBack in kiosk within 2 minutes of rebootPhoto or video; policy record
Remote actionsRemote lockEach platform and mode in scopeDevice locksWithin 2 minutesAction log with timestamps
Remote actionsLocateCompany-owned modes onlyLocation shown for company devices; not available on BYODWithin 5 minutesLocation record; BYOD device shows no location
Remote actionsRemote viewEach platform where you need itView session starts, with the user consent the platform requiresSession within 2 minutesSession log; consent prompt screenshot
Remote actionsRemote controlPlatforms where the vendor offers controlAdmin can operate the deviceSession within 2 minutesSession log
OS updatesDefer, schedule, or enforce an updateSupervised iOS; Android fully managed; WindowsPolicy applies and reports statusStatus reported within 24 hoursUpdate compliance report
OffboardingRetire a BYOD deviceiOS User Enrollment; Android work profileWork data removed; personal data intactWithin 15 minutes of next check-inAction log; employee confirmation
OffboardingWipe and re-enroll a company deviceAutomated Device Enrollment; zero-touch or Knox Mobile Enrollment; AutopilotRe-enrolls automatically; Activation Lock and FRP handledBack in service within 30 minutesAction log; re-enrollment record
Reporting and adminExport inventory and compliance reportConsoleExport has the fields your audits needUnder 5 minutesExported file
Reporting and adminRole-based access and audit logConsoleLimited admin cannot exceed role; actions loggedNot timedAudit log export
IntegrationsIdentity provider sign-in and APIConsole and APISign-in through your IdP; API returns device inventoryNot timedSign-in log; sample API response
SupportOpen a real support ticketVendor supportUseful answer within the SLA you will be quotedThe quoted SLATicket 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

mdm proof of concept

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:

AreaDefault weight
Enrollment15%
Policies and compliance15%
App management10%
BYOD privacy10%
Kiosk5%
Remote actions5%
OS updates5%
Offboarding5%
Reporting and admin10%
Integrations5%
Support10%
Cost at your fleet size5%

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.

Laura Ciurea
Article by
Laura Ciurea
Marketing Manager
Laura Ciurea brings extensive expertise in product and project management, corporate communications, investor relations, and event organization at Bento - Intellectually Curious. She plays a key role in the company's external presence, overseeing official press releases and financial updates for Bento (BVB: BENTO). Known for her ability to promote innovative technology solutions and her strong organizational skills, she is regarded as a resourceful and reliable business partner, capable of managing complex initiatives from strategy through to execution.
Summarize with AI

Related Articles

MDM RFP template: questions to ask mobile device management vendorsmdm rfp template MDM Strategy & Implementation 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... By Dragos Brudiu Oct 31, 2026
Device offboarding checklist: when to retire, wipe, reassign, or remove a device from MDMit offboarding checklist MDM Strategy & Implementation Device offboarding checklist: when to retire, wipe, reassign, or remove a device from MDM Most IT offboarding checklists cover accounts and app access in detail and give the device a single line: collect the laptop. That line hides the decisions that cause real problems. Retire a company phone instead of wiping it, and the... By Radu Scarlat Oct 29, 2026
Android Device Admin deprecation: how to migrate legacy fleets to Android Enterprisedevice admin migration MDM Strategy & Implementation Android Device Admin deprecation: how to migrate legacy fleets to Android Enterprise Android introduced Device Admin as Android’s original management interface in Android 2.2. Google deprecated it for enterprise use in Android 9 and removed its core security policies for management apps targeting Android 10 (Google for Developers). Devices still enrolled through... By Vlad Bodea Oct 28, 2026