1. You require automated relationship intelligence with minimal manual mapping
- If automatic capture of interactions, relationship scoring, and engagement analytics are primary needs, specialized revenue-intelligence platforms may be more appropriate.
2. Your sales organization resists structured, checklist-driven workflows
- If the sales process is highly variable and reps are unlikely to adopt step-by-step workflows, the tool's structured processes may hinder adoption.
3. You need complete extensibility and direct BI/Einstein access to every execution data element
- If vendor-internal objects are used in a way that limits reporting or automation access, this could constrain analytics and automation strategies.
4. Transparent, self-serve pricing is a strict requirement
- Organizations that require immediate, per-seat pricing and self-service purchasing may find a quote-based model incompatible with procurement needs.
5. Your organization already maintains robust Salesforce-native planning objects and governance
- In some environments, extending native Salesforce objects and processes may provide higher ROI than adding an additional vendor abstraction layer.