Blueprints play a crucial role in Sprinklr's platform by providing standardized configuration templates for implementations. This knowledge base article provides an overview of Blueprints, their purpose, and their significance in streamlining the configuration process. 

What are Blueprints? 

Blueprints are sets of best-practice configurations developed by our Product Managers to help standardize Sprinklr implementations. Each Sprinklr product has its own Blueprint, designed to meet customer business requirements during implementation and in the future. Blueprints serve as a foundation for efficient and consistent setups and are regularly updated based on feedback from the Product team and the Customer Delight organization.

Challenges Addressed by Blueprints 

Before the introduction of Blueprints, configuring the Sprinklr platform was a time-intensive task. Each implementation consultant, managed services consultant, and success manager had to manually build the platform from scratch, resulting in unique setups for each customer. This diversity of configurations made troubleshooting and ongoing maintenance challenging.

Benefits of Blueprints 

• Standardization: Blueprints establish best practices and provide a standardized foundation for configurations, ensuring consistency across implementations. 

• Time Savings: Implementing Blueprints significantly reduces configuration work by providing pre-defined configurations. This saves valuable time and allows consultants to focus on more advanced client use cases. 

• Cross-Team Collaboration: Blueprints serve as a common reference point for all teams involved in the Sprinklr platform, fostering shared understanding and facilitating collaboration. 

Limitations of Blueprints 

While Blueprints offer valuable standardization, it is important to note their limitations: 

• Customization: Blueprints serve as a foundation but may require additional customization to meet specific client requirements. 

• Coverage of Use Cases: Blueprints cannot cover all possible client use cases. They provide a standardized starting point that may need further customization to address unique business needs. 

• Internal Use Only: Blueprints can only be deployed into environments by the internal Sprinklr team. Implementing Blueprints without proper guidance and process, especially in environments with pre-existing configuration, will likely lead to significant disruption for end users. As such, the tools used for deploying blueprints are not accessible to clients. To ensure a successful project scoping process, please contact the Success Manager for further assistance.  

Blueprints are essential tools in Sprinklr's platform, providing standardized configurations and streamlining the implementation process. They empower consultants, save time, and enhance cross-team collaboration. While Blueprints offer numerous benefits, it's important to understand their limitations and the need for additional customization to meet specific client requirements.