Contents
- 00:00 Introduction
- 10:28 Vetforce, Salesforce Military & Veterati
- 11:17 Building a peanut butter and jelly sandwich in Salesforce CPQ
- 12:25 Use Case: PB&J Enterprises
- 18:55 Whiteboarding the architecture of a peanut butter and jelly sandwich
- 19:30 How many products are in a peanut butter and jelly sandwich?
- 25:24 How can we reduce the number of products needed to use Salesforce CPQ?
- 26:54 How will we architect our peanut butter and jelly sandwich?
- 29:24 What questions are we answering with product configuration?
- 31:27 Should this be a product or an attribute? Or both?
- 35:14 Why are there so many fields in Salesforce CPQ?
- 36:41 Why do CPQ implementation projects take so long?
- 37:41 Why did you architect the peanut butter and jelly sandwich this way?
- 39:04 The two approaches to product configuration, plus a configuration quadrant
- 41:38 As many as needed, as few as possible
- 43:01 How many peanut butter and jelly sandwich bundles do we need to create?
- 45:38 The customer is not always right, neither am I
- 47:16 Creating the Peanut Butter & Jelly Sandwich bundle
- 48:34 Can I sell this product in Salesforce CPQ?
- 50:36 Assigning the CPQ Product Layout page layout to all profiles
- 53:28 How do you manage custom fields on page layouts?
- 55:05 How to identify managed metadata and why it matters when deploying Salesforce CPQ
- 56:18 Document the living hell out of everything