Every reseller has been through the same sales cycle. The client likes the demo. The client agrees that device management sounds valuable. Then the proposal sits in an inbox for six weeks because nobody has felt the problem MDM solves. Slides and feature lists do not create urgency. Watching a real device go offline on a Saturday night, seeing the alert fire, and fixing it from a dashboard before anyone at the location notices does.
A structured 30-day pilot creates that moment on purpose. It puts Moki on a small slice of the client’s real fleet, surfaces real operational incidents, and produces evidence the client can point to when they decide whether to sign. This playbook covers how to scope a pilot, what to do in each week, and how to turn the results into a managed services agreement.
Choose the Right Client and the Right Slice
Not every prospect needs a pilot, and not every pilot needs to be large. The best pilot candidates share a few traits:
- They already own or are about to deploy 20 or more devices across at least two locations
- They have felt some pain, such as a dark screen nobody noticed or a field visit that should have been a reboot
- They have a decision maker who will actually review the results
- They are open to enrolling a small group of devices for 30 days without a long-term commitment
Within the client’s fleet, pick a slice that is representative rather than convenient. A good pilot group includes:
- 10 to 25 devices, which is enough to see real incident patterns without creating a large support burden
- Two or three locations, ideally one easy site and one that is harder to reach or has less reliable connectivity
- At least one of each hardware type in scope, such as a BrightSign player, an Android device, or an iPad
- Devices that matter to the client’s business, not spare units sitting in a closet
A pilot on devices nobody cares about produces results nobody cares about.
Define Success Before You Start
The most common reason pilots fail to convert is that nobody agreed on what success looked like. Write the criteria down in a one-page pilot agreement and have the client sign off before day one. Useful criteria include:
- Percentage of pilot devices enrolled and correctly configured by the end of week one
- Number of offline or error events detected by monitoring during the pilot
- Percentage of those events resolved remotely without a site visit
- Average time from detection to resolution
- Content delivery success rate for any scheduled updates pushed during the pilot
- Number of configuration or compliance deviations found and corrected
Pick the three or four that matter most to this client and track only those. The goal is a clear verdict, not a data dump. The same principle applies to any deployment, and Moki’s guide to why kiosk pilots fail covers the planning mistakes worth avoiding.
Week by Week: What to Do
Week 1: Build, enroll, and baseline. Before any device is touched, build and test the configuration profile on one device of each type, following the approach in Moki’s guide to building and testing a configuration profile. Then enroll the pilot devices, using zero-touch, Apple Business Manager, Android Agent pre-registration, or BrightSign bulk enrollment depending on the hardware. Organize them into a pilot group structure, set alert thresholds, and route alerts to the person on your team who will respond. Record the baseline: what the client believes their uptime and incident rate are today.
Week 2: Watch and respond. This is where the pilot starts producing value. Let monitoring run and respond to every alert as though the pilot were a live managed service. Log each incident with the time detected, the time resolved, the method, and whether a site visit was avoided. Share a short midweek note with the client contact so they see the dashboard working before the final report. If nothing has gone wrong yet, that is fine. Do not manufacture incidents.
Week 3: Test the operational workflows. Use this week to demonstrate capabilities the client cares about beyond monitoring:
- Schedule and push a real content or application update, and show delivery confirmation per device
- Run a scheduled maintenance sequence using Action Sequences, such as an overnight reboot
- Show a compliance report that flags any device that has drifted from its profile
- Walk the client through remote troubleshooting on a live device
Invite the client’s operations or IT contact to watch at least one of these live. People remember what they saw.
Week 4: Report and recommend. Compile the results against the success criteria agreed in week one. Present them in a short meeting, not just an emailed PDF. Cover what was detected, what was fixed remotely, what would have required a site visit without monitoring, and what the full fleet would look like under management.
What the Pilot Report Should Contain
Keep the report to two pages. Include:
- The scope: how many devices, how many locations, which hardware
- The results against each success criterion, with real numbers
- Two or three specific incident stories, such as a player that went offline overnight and was recovered before opening
- An estimate of avoided cost, using the client’s own field service and downtime figures
- A recommended next step with a proposed scope and pricing for full deployment
Incident stories do more work than statistics. A story about a menu board that went dark at 5 AM and was back online by 5:12 without anyone visiting the location is something a decision maker will repeat to their boss.
Handle the Common Pilot Problems
A quiet pilot with no incidents. Treat it as a positive result, but lean on compliance findings, content delivery confirmation, and the maintenance workflows to show value. Also remind the client that the absence of incidents was visible only because monitoring was in place.
Scope creep. Clients sometimes ask to add devices mid-pilot. Say yes only if it does not delay the report, and be clear that added devices will not have a full 30 days of data.
Slow client engagement. Schedule the week 4 review on day one so the date is fixed, and send short written updates so the client stays informed even when they are busy.
Pilot devices that are hard to enroll. Treat this as useful information. It tells you what the full deployment will require, and it is far better to learn it in a pilot than during a rollout.
Convert the Pilot Into a Managed Services Agreement
The pilot already did most of the selling. The conversion step is making the next move easy:
- Offer to keep the pilot devices enrolled and monitored while the full agreement is finalized, so the client does not lose coverage
- Present a phased rollout plan with a clear first batch
- Show how the monthly managed service fee compares to the cost of the incidents the pilot surfaced
- Register the opportunity through the Moki partner program so your investment in the relationship is protected
If you want to understand how other resellers have structured this, the certified partner ecosystem is a good starting point.
Schedule a Moki demo to plan a pilot for a specific client, or start a free trial to build and test your pilot configuration before you propose it. Moki’s support team can help review your pilot scope and alert setup.