30 questions · 8 decision fields · Public CSV · No signup

Make the vendor demo prove something.

Use thirty questions to separate current capability from presentation polish. Every row records why the question matters, the evidence to request, a bounded live test, a red flag, and your decision notes.

Download the CSV checklistDefine requirements firstAsk where RMM ends and PSA beginsTest whether remote desktop alone is enoughRead the RMM vs remote desktop guideTest API integrationsRun the pilot testsScore the observed resultsNormalize the vendor quoteCheck Nizlo's published pricingReview the vendor due-diligence guideOpen the RMM testing guide

Coverage for a useful RMM demo

Commercial truth

Expose add-ons, minimums, commitments, platform limits, and the difference between generally available, preview, and roadmap capability.

Agent and operations

Test install, update, removal, offline behavior, tenant boundaries, alert lifecycle, patch controls, and inventory freshness.

Privileged action safety

Inspect automation targeting, secret handling, remote-session authorization, roles, revocation, audit records, and exportability.

Adoption and exit

Clarify integration depth, implementation ownership, support escalation, data portability, agent removal, deletion, and final billing.

How to use the checklist

Send the questions before the meeting

Ask the vendor to bring current documents, a representative quote, sample exports, and a test tenant. This keeps the call focused on observable evidence.

Choose the live tests that match your risks

Do not run privileged actions on production systems during a sales call. Use authorized lab endpoints and disposable credentials, and remove them afterward.

Record the source, not only the answer

Link each conclusion to dated documentation, contract language, a captured export, or observed pilot evidence. Label preview and roadmap statements clearly.

Carry unresolved items into the pilot

Move gaps into the requirements matrix and pilot evidence pack with an owner, pass condition, remediation commitment, and retest date.