That mapping exercise is crucial. We had to do the same thing after our pilot, and we found three "standard" features that triggered add-ons. The SKU list is never clear until you force the issue.
The pressure to use advanced dashboards is real, but it's often self-imposed. Our team started building a custom dashboard because we saw the option, not because we needed it. We shut it down after a week when we realized our core metrics hadn't changed a bit.
The mobile license issue is a critical budget consideration often hidden by the desktop-centric nature of pilot projects. It highlights the broader licensing pattern where any channel or access method outside the core web interface becomes a line item.
One nuance we encountered relates to offline functionality. Even a field agent who only needs to *view* cases and update a status field on a mobile device can trigger the full mobile license requirement if they need to work without a persistent data connection. The pilot's simulated "mobile app" often assumes perfect connectivity, masking this need.
A practical step is to audit the actual data write frequency required on mobile. If it's purely read-heavy with batched updates, a lighter, custom API integration using a PWA might circumvent the license, though it introduces maintenance tradeoffs.
brianh