A written OLA can be used as an input into a requirements document of any Marketing Automation tool / Sales Automation tool interface project. All too often, these two departments use different tools that are more tailored to their specific functions. In order for information to pass easily between them an actual technical interface is typically required. If the operational process is understood and the necessary information to be passed between the teams is documented, then building this interface and setting up appropriate reporting tools can be done more effectively.
MailChimp for Salesforce – Generate Leads from subscriptions to your newsletters
MailChimp for Salesforce is an App created by MailChimp and available for free in the Salesforce.com AppExchange. I recently installed the App in my Salesforce account in order to sync subscribers of our weekly into Salesforce Leads and contacts. I’ve been so impressed with this integration that I decided to focus this week’s blog post […]
Business organization by customer focused layers
The traditional business model of separated teams, or silos, for marketing, sales, development and support simply is no longer working for B2B companies. This business model is prone to a waste in resources, duplication of efforts and poor internal communication. On the other hand, a product focused business model can lead to not recognizing opportunities for additional sales opportunities to an existing customer base. So what is the alternative? To borrow and adapt a quote from the 90’s – it’s about the customer stupid. Though these independent functions are still necessary, the best organization is to align business operations and teams with a focus on a customer segment.
