Salesforce Lightning. It’s the word on the streets. We’ve all probably heard it at some point. Like the new iPhone or a new car we might not know the fine details behind it, but we probably know it’s an upgrade of some kind. And like most upgrades we’re probably thinking we can do without it. Your current car is still getting you from point A to point B and your phone is still taking calls.

  Intro: It’s more important than ever to have clarity in your sales process with today’s hectic & constantly evolving business environment where key details can get lost in the shuffle. Many small and mid-size businesses that I’ve advised have sales process in Salesforce don’t have clear definitions for what qualifies a lead or opportunity to move to the next stage. I am writing this blog post to share fundamental best practices I’ve learned from

It’s one thing for a manager and a consultant to sit together in a conference room planning out how Salesforce should be integrated. In reality, the users may not take to the system the way you anticipate. The delta between the plan and the reality can be significant when there isn’t a clear adoption strategy in place. Aligning with the user’s core needs has as much to do with planning, strategy, communication, and leadership as

By Oliver Sholder  At Everpeak Partners, one of the most common types of projects we take on is the Lightning migration (going from the older ‘Classic’ interface to the newer ‘Lightning’ interface) For those considering switching, here are my thoughts as a system architect and a user of both Salesforce Lightning and Salesforce Classic for years. Two years ago, you’d be a pioneer to be on Salesforce Lightning. One year ago, there was a strong

 Guest Blog Post By Colin Longren, VP Global Sales at The Millau Group Global     Salesforce (like other CRMs) can be compared to an all-inclusive gym membership with a pool, gigantic weight room, smoothie bar, and tanning beds…when really all you need is a treadmill! All those gym “features” and amenities are a nice to have, but not a need to have. Salesforce features and ‘add-ons’ can be the same way, depending on your situation.