Book Image

Salesforce Sales Cloud – An Implementation Handbook

By : Kerry Townsend
Book Image

Salesforce Sales Cloud – An Implementation Handbook

By: Kerry Townsend

Overview of this book

Salesforce Sales Cloud is a system rich in functionality, addressing many sales business challenges such as sales productivity, forecast visibility, and sales enablement. However, unlocking the full value of the system and getting maximum returns pose a challenge, especially if you’re new to the technology. This implementation handbook goes beyond mere configuration to ensure a successful implementation journey. From laying the groundwork for your project to engaging stakeholders with sales-specific business insights, this book equips you with the knowledge you need to plan and execute. As you progress, you’ll learn how to design a robust data model to support the sales and lead generation process, followed by crafting an intuitive user experience to drive productivity. You’ll then explore crucial post-building aspects such as testing, training, and releasing functionality. Finally, you’ll discover how the solutions’ capability can be expanded by adding and integrating other tools to address typical sales use cases. By the end of this book, you’ll have grasped how to leverage Sales Cloud to solve sales challenges and have gained the confidence to design and implement solutions successfully with the help of real-world use cases.
Table of Contents (20 chapters)
1
Part 1:Building the Fundamentals
7
Part 2: Preparing to Release
13
Part 3: Beyond the Fundamentals

Identifying data to load

Your solution design determines the exact data you need to bring into Sales Cloud. However, all solutions typically include Accounts, Contacts, and Opportunities. They also often include Products, Price Books, Opportunity Products, and Leads. Your business maturity will determine the volume of data available to load, and the type of business performed will determine how much historical data you need to have available.

The first and most important step is deciding what set of data to load. It is tempting and common practice to simply load all the data available without any critical analysis. During the later stages of implementation, there is usually a desire to get the system running as soon as possible, and loading all the data available may seem like the path of least resistance. However, this can turn out to be a mistake. There are consequences, including an ongoing maintenance cost, to holding data.

There are obvious costs, such as data storage, but...