Struggling to Discuss the Size of a Salesforce Implementation?

One of the challenges I often face is explaining the size—and by extension, the cost—of a Salesforce implementation to potential clients. It’s not always easy to convey the various factors that influence the scope of such projects. To help make these discussions clearer, I’ve created a table that outlines the key considerations for sizing a Salesforce implementation.

While a table can be a powerful tool, offering a clear visual representation, I’d like to walk you through the thought process behind it.

Complexity & Scale: The Dual Axes

If you’ve worked with me before, you know I’m a fan of using tables to organize information. Central to this table is a graph with two axes: scale (X-axis) and complexity (Y-axis). These two dimensions capture the essence of most Salesforce implementations.

Most projects will progress along both axes. However, there are cases where you might encounter extremes. For instance, a highly customized Salesforce application tailored for a niche business, like a dry cleaner or dog groomer, represents one extreme. The opposite end might involve a large organization deploying a straightforward Salesforce setup with minimal configuration and no customization.

Sizing: Small, Medium & Large

The columns in the table represent ‘sample’ sizes of implementations, offering a rough guide rather than a strict classification. These samples are meant to illustrate how work can scale across different phases of the project. For example, a larger project might require more extensive Data Migration efforts than a smaller one.

Phases: A Step-by-Step Approach

The phases column in the table is designed to be read from bottom to top, reflecting the typical sequence of an implementation. As expected, Discovery is the starting point for any project. As you move up the column, you’ll see the various stages that may follow.

For a simple implementation, the project might only involve Discovery, Configuration, and User Training, without the need for Data Migration or Customization. On the other hand, a more complex project might involve all phases.

Seeking Feedback

I believe this approach offers a clear and structured way to describe the complexity and scale of a Salesforce implementation. However, I’m always looking to improve. I’d love to hear your feedback on this approach and any areas that might need further refinement.