One policy per device
Assignment resolves Organization, then Location, then Device — most specific wins. There is no merge or stacking, so “why is this machine like this” is always one object.
Know the platform.Sell it at the whiteboard.
A working field guide for solution engineers selling NinjaOne: how the platform actually behaves, the questions that open a discovery, and a twelve-move talk track for building the whole story on a customer's wall.
Unified IT operations
Manage. Protect. Support.
01 · SenseInventory + telemetryAgent · MDM · SNMP · SaaS
↓02 · DecidePolicy + contextRoles · Conditions · CVE/KEV · Tickets
↓03 · ActAutomate + supportPatch · Remote · Backup · Script
↓04 · ProveEvidence + improvementActivities · Reports · ITAM · Docs
Managed Protected Supported
Core curriculum
10 modules. One connected story.
Follow the sequence once, then use the field kits to drill weak areas and rehearse how you will explain the operating model.
01
35 min
02Platform Foundations
Build the mental model before memorizing features.
45 min
03Endpoint Management & RMM
The proactive monitor-detect-act loop.
45 min
04Autonomous Patching
Make change fast without making it reckless.
40 min
05Vulnerability & Endpoint Security
Connect security intelligence to operational execution.
40 min
06Remote & Service Desk
Turn support interactions into reusable operations.
40 min
07Mobile & Asset Intelligence
See the whole estate, then govern the right control plane.
45 min
08Backup & Data Resilience
Design for recovery, retention, and proof.
35 min
09MSP Service Operations
Connect technical work to a scalable service business.
50 min
10Enterprise Architecture
Move from feature tour to operating design.
55 min
Enterprise SE Fieldcraft
Discovery, demo, POC, objections, and field execution.
The differentiator
Anyone can demo. Learn to draw it.
12moves that take a blank whiteboard to the complete NinjaOne story without presenting once. Ask a question, draw the answer, validate it, repeat — and hand over the marker at the end.
Open the talk track- 01 Frame the board, draw nothing
- 02 Count the estate, find the gap
- 04 Hierarchy and the one-policy rule
- 07 Rings, soak, and what the vendor won't tell you
- 12 Hand over the marker, then stop talking
Course progress0%
Start with Platform Foundations.
Platform mental model
See the operating loop before the product list.
Platform fluency comes from understanding how data becomes action, where governance lives, and how one module hands context to the next.
01Estate
WindowsmacOSLinuxApple + AndroidServersNetworksSaaS data
02Sense & control
Agent / MDM / SNMPInventoryTelemetryRolesPoliciesConditions
03Act
AutomationPatchRemoteBackupTicketSecurity workflow
04Prove
ActivitiesReportsITAMDocumentationAPI + integrationsPOC evidence
Threshold plus duration
A condition is not just a threshold, it is a threshold sustained over a configurable interval. That parameter is the difference between an alert console people act on and one they have muted.
Business state becomes monitorable
Typed custom fields written from a script or the API can be evaluated as conditions, which turns a compliance requirement into an alert instead of a spreadsheet.
Field-readiness kits
Reference material built for retrieval.
The product curriculum teaches the platform. These tools turn knowledge into discovery, architecture, demo, and customer-facing execution.
A→B→C→D→E→F→G→H→
Product atlas
Products, bundles, add-ons, capabilities, workflows, distinctions, and source links.
Discovery library
28 branching questions across 7 stages, each with what to listen for and the follow-up that goes deeper.
Objection lab
35 objections with the subtext, the response, a proof method, and the reflex answer that loses the deal.
Scenario drills
Cross-product architecture prompts for enterprise and MSP conversations.
POC playbook
Success criteria, evidence, rollout, gap classification, and decision discipline.
Flashcards
Rapid-fire distinctions that make product fluency sound natural.
Knowledge check
30 technical questions with the reasoning revealed the moment you answer.
Claims ledger
Every source, verification date, taxonomy decision, and conflict resolution.
Trust model
No unsupported hero claims.
Official sources first
Product pages, current documentation, Academy content, release notes, and the official portfolio index.
Taxonomy made explicit
Products, bundles, add-ons, included apps, platform capabilities, and services are not flattened into a fake SKU count.
Conflicts resolved visibly
OS support, patch catalog size, integrations, and backup scope use current, narrow language when official pages disagree.