Sales & Pre-Sales · Course S2Lesson 2 of 3
Plans as feature gates
8 min read- Explain module gating as the mechanism behind plans
- Survey the gateable module map, suite included
- Use gating for honest land-and-expand conversations
"Plans are feature gates" sounds abstract until you see what it means: the customer's console is assembled from their plan. Modules in the plan appear; modules outside it don't. Selling plans is really selling console shapes.
The gateable map
The platform's plan machinery can gate roughly twenty top-level areas, each with fine-grained toggles inside. The headline groups:
| Area | Examples inside |
|---|---|
| Dashboard | Fleet stats, device charts, check-ins, data-usage and screen-time analytics |
| Devices & operations | Device views, bulk actions, broadcast, remote shell, audit logs |
| Policy | The full policy engine — by far the largest area, spanning every platform's restriction sets |
| The We-suite | WeBox, WeTalk, WeSupport, WeShield, WeTrack — each its own gateable module |
| Visibility | Reports, alerts, fleet alerts, data usage, screen time |
| Administration | Roles and permissions, company directory |
Read that table again as a sales instrument: every row is something a customer might one day ask for, and every ask maps to a plan conversation.
What gating enables (and forbids)
Honest demos. Demo the plan you're proposing — showing ENTERPRISE-shaped consoles to STARTER budgets manufactures disappointment at deployment.
Land and expand, without pressure. The customer lands on the right-sized plan. Six months later they ask "can we push files to all stores?" — and the answer is a plan rung, not a procurement war: the need arrived on its own, the module is one conversation away.
Clean scoping. "Which of these areas do you need in year one?" is a discovery question that produces a plan recommendation almost mechanically.
The inverse rule keeps you credible: never promise a module without checking the plan. "Yes, WeTrack's included" when it isn't is the fastest way to turn a good deployment into an escalation. When in doubt, the plan editor's module list — or your account team — settles it in minutes.