Although Ad.net had an existing Salesforce instance, it was not highly optimized and caused disruptive inefficiencies. Rather than offering a more process-driven experience, Ad.net’s Salesforce environment overwhelmed users with too many fields and ultimately functioned as a mass data collection hub.
Essentially, Ad.net was using Salesforce to drive sales, and all other subsequent workflows lacked a clear directional path–obscuring next steps for internal projects. Compounding these issues, the absence of a centralized workflow system prevented Salesforce from receiving crucial “downstream” project information that needed to be communicated to account managers. This created several critical issues including:
- Inhibiting the efficiency of daily operations
- Posing increasing security concerns–all users allowed unrestricted access to the Analytics platform
- Drastically reducing reporting accuracy and the rate of company-wide Salesforce adoption due to manual information hand-off to team members working outside Salesforce