Everybody's Demo Org (EDO) is a tool that aims to simplify Salesforce demonstrations and trials for sales teams and customers. It provides a pre-built, fully functional Salesforce environment that users can immediately log into without any configuration required. This allows sales teams to conduct impromptu demos without needing technical expertise or time to prepare customized environments. It also gives customers a "working trial" to explore the platform without implementation effort. The goal of EDO is to remove barriers around conducting demos and trials in order to accelerate the sales process and build trust and familiarity with customers.
2. Buying from Salesforce can be challenging
● What’s it do?
● How does it work?
● How is this different from the competition?
● Too many features to keep track of, constantly changing.
● Don’t know what they don’t know
● Hard to see the complete solution through all the features/clouds
Many customers are not experts in our products
3. They have two paths
● Trials
○ Completely Blank Environment
○ Ask customer to put in time and effort to implement features
○ Have to know which features you want, and how to use them
○ Expose the customer to frustration / learning curve early on.
○ Not good for more advanced / complex products
● Demos
○ Timing - Slows down the sales cycle
○ Needs a technical resource, SE
○ We don’t have good demos for everything
■ Platform
■ Einstein
■ B2C Commerce
Trials and Demos
4. Enabling our sales teams can be challenging
● Many are intimidated by the Technology
● Don’t have time / know-how to set it up
● They just want the output, not the configuration
● When things change / new features come out, hard to get it in their hands quickly.
5. There Are Levels To This Game
And everyone in the Ohana Matters
Walker
Hiker
Climber
Nutjob
13. Customers
“Working Trial”
● No Admin Abilities
● Pre-Built, “Best Practices” Environment
● Interactive. Serves as a working example
● No implementation effort
● Builds Trust / Familiarity
Employees
Impromptu Demos
● Lack time or skill to customize demos
● Zero prep work
● New Features
● Cross-Cloud Stories that are hard to demo
○ Platform
○ Einstein
○ Commerce
○ Integration
Who should use the EDO?
It’s another tool in the toolbox
Customers can be confused and bewildered trying to buy from us. We have a complex product that can do a lot of things. How do they understand “the value” of a CRM?
Today, they go to a trial, which is blank. Or they have to be fortunate enough to get a demo. Which takes time, slows down the sales cycle, and reuires SE resources
Customers can be confused and bewildered trying to buy from us. We have a complex product that can do a lot of things. How do they understand “the value” of a CRM?
Not everyone can, or should, be a technical expert.
Walkers: AEs who can rely on SEs for demo support, and so only need to know the basics.
Hikers: AEs and SEs who only do limited configuration for their demos.
Climbers: SEs with advanced product knowledge and configuration skills, who leverage demo components and Demo Engineering.
Nutjobs: Highly technical SEs who develop custom components on their own.
So, we build the EDO - Salesforce’s Greatest Hits, ready to demo, any time.
We created the EDO
You just login and Go
We do the admin work. We simply add a new feature, and EVERYONE gets it
Every update. Same login.
No doubling up on effort, no separate demo orgs.
It’s not JUST for employees. ANYONE can login and TRY this stuff.
When is the EDO good? When should I use the SDO?
If you SCHEDULE a meeting for a demo… you should probably use the SDO
Challenge: The SDO is a complex environment that is well-suited for custom demos, but is not great for “Walkers” who need to show only basic capabilities. As we add more products and features to our portfolio, some of the basic functionality is pushed to the side, making it harder and harder for SEs and AEs to do basic demos.
Solution: A separate, simple demo environment specifically for basic demos and harbour cruises. Core products like Sales Cloud and Service Cloud, some Marketing and limited integration of cutting-edge differentiators like Einstein.
The EDO, or “Executive Demo Org” would be set up for two or three basic demo flows out of the box, and would be built to pare prep time down to the absolute minimum. Automatic, rather than manual setup, would make it a foolproof, robust demo org. Focusing on Lightning-only demos would allow us to leave behind the accumulated legacy gunk of the SDO. “10-click demos” could be a thing again.
The SDO would remain the primary tool of SEs, with the EDO reducing their support burden and making AEs more productive and self-sufficient.