Professional Documents
Culture Documents
This presentation may contain forward-looking statements that involve risks, uncertainties, and assumptions. If any such uncertainties materialize or if any of the
assumptions proves incorrect, the results of salesforce.com, inc. could differ materially from the results expressed or implied by the forward-looking statements
we make. All statements other than statements of historical fact could be deemed forward-looking, including any projections of product or service availability,
subscriber growth, earnings, revenues, or other financial items and any statements regarding strategies or plans of management for future operations,
statements of belief, any statements concerning new, planned, or upgraded services or technology developments and customer contracts or use of our
services.
The risks and uncertainties referred to above include – but are not limited to – risks associated with developing and delivering new functionality for our service,
new products and services, our new business model, our past operating losses, possible fluctuations in our operating results and rate of growth, interruptions or
delays in our Web hosting, breach of our security measures, the outcome of any litigation, risks associated with completed and any possible mergers and
acquisitions, the immature market in which we operate, our relatively limited operating history, our ability to expand, retain, and motivate our employees and
manage our growth, new releases of our service and successful customer deployment, our limited history reselling non-salesforce.com products, and utilization
and selling to larger enterprise customers. Further information on potential factors that could affect the financial results of salesforce.com, inc. is included in our
annual report on Form 10-K for the most recent fiscal year and in our quarterly report on Form 10-Q for the most recent fiscal quarter. These documents and
others containing important disclosures are available on the SEC Filings section of the Investor Information section of our Web site.
Any unreleased services or features referenced in this or other presentations, press releases or public statements are not currently available and may not be
delivered on time or at all. Customers who purchase our services should make the purchase decisions based upon features that are currently available.
Salesforce.com, inc. assumes no obligation and does not intend to update these forward-looking statements.
Key Principles for Effective CRM
Connected Connected
Connected
Partners Products Connected
Employees Devices
Connected
Customers
Common Challenge: Accounts vs.. Customers
Who is your Customer and what is your overall relationship?
Can you relate accounts for each
entity across CRM, ERP, …?
Salesforce.com, Inc
One Market St., Suite 300
San Francisco How do you detect and maintain
relationships?
Customer
Self Service Reports
Portal?
Analytics
Data
Warehouse
Contract Quote
Case Mngt
Mngt
ERP
Mngt
SFA ETL MDM Hub
Data
Quality Application Integration (e.g. ESB)
Modules
Key Challenge #1: MDM Hub First Delays Business Value
Typical Rollout $1-5M (SW, HW, People, Data) + 9-18 Months
Centralized Integrate Visible
Implement
Governance MDM & Business
CRM BI MDM Hub
Definition Applications Value
• ~3-6 months • ~3-12 months
• Important, Often Not Agile • Many features to support:
• Risk: Focus on Definitions only Search Before Create
MDM vs. Visible Results Duplicate Prevention
ERP DW Ongoing Updates
Hub Enabling User Feedback
Merge Support
• Separate effort for data cleanup
TCO Framework Business IT
• ~3-12+ months • Promise:
Data Acquisition • Focus on match % vs. matched Integrated, quality Customer
Data data quality and Transactional Insights
• Risk: X-Source reconciliation • Success drives new
Stewardship
vs. against reference data set requirements for additional
Data • Risk: Over-reliance on rules data sources, fields
Reconciliation without tribal knowledge
Data Delivery
Key Challenge #2: Technology Itself Is Not Sufficient
User Engagement + Reference Data is Essential To Quality Data
In 30
Software Only Solutions Cannot Relate Different Location and Entities to “Customers”
minutes
Salesforce.com, Inc (HQ)
One Market St., Suite 300
120 businesses change addresses
San Francisco
Implementation: Implementation:
• Cost: ??? • Cost: Depends on Use Case
• Predictability: ?? • Predictability: Yes
• Duration: ?? • Duration: 1 day+ Identify the gap, prioritize, address
Challenge: Challenge:
Point of Sale data not linked to what’s in SAP (orders) or Large stewardship team (20+) required to steward MDM
CRM (Sales Rep engagement) software results.
SW Matching yielded 15% match rate after an unknown Batch processes time consuming, expensive.
months effort
Results: Results:
Data.com Clean yielded 50% match rate in 8 days Data.com Clean, custom UI & workflows engaged users,
(3 week PoC, ended early), including account record provided “linked” (vs. overridden data) allowing more
affiliation to legal entities business units to participate due to choice,
replaced and enhanced prior solution within 3 months
(vs. prior cancelled effort: 18+ months)
Salesforce as System of Engagement
Sample Customer Data Architecture
Use Account Object as Registry, Use Configuration to Hide Complexity
Account Account
Source Account Transaction Type
Type
SFA Customer Salesforce Opportunity Account
Customer
SFA Customer Exact Target Opportunity Team
ERP Sell To Salesforce.com Sale
ERP Sell To Salesforce Inc Sale Contacts
ERP Ship To Salesforce PTY Shipment
Related
ERP Ship To Salesforce.com Shipment
Accounts
ERP Ship To Salesforce Shipment
ERP Sell To ExactTarget Shipment
ERP Ship To Exact Target Shipment
Internal External
Support Contact Salesforce Case
Insights Insights
Best of Breed MDM Architecture with the Power of the Cloud
Salesforce B2B Sample Architecture
MDM Function Recommended Solution Why
Address Check/Standardization e.g. AddressDoctor Better data at source, Consistency
Initial Matching Data.com Rich matching, ability to bring in and build
parent/child hierarchies
Legal Name Cleansing Data.com Benefit of 3rd Party Reference Data
Data Enrichment (e.g. Firmographics) Data.com Fills gaps with Reference Data
Hierarchy Definition / Maintenance Start with Legal Hierarchy, Leverage D&B Family Tree, end user input
Rule driven automation TBD vs. back office function
Stewardship Report and Work Flows Where users work (with DDC) Focuses on data, with Tx context, routing
Secondary Matching Dedupe Tools, MDM Hub Handles records not found in D&B and/or
(e.g. Infa Cloud MDM) deeper granularity matching
Golden Record Maintenance MDM Hub Core competence
Global ID Maintenance MDM Hub Independence from 3rd party sets
Ongoing Data Updates Data.com (data) Reference Data Updates (e.g. alerts on
MDM Hub (facilitate updates) ownership change, OOB)
Merge & Integrate MDM Hub Facilitated Core competence, use data from DDC
Apps must be capable
Key Message: Start with What’s Pre-Built for Faster Value
Add Capability & Enhance Over Time As Needed
Incentive: Close deals, Make Club, Incentive: Effective, efficient respond Desire: Minimize time spent with
Avoid being blind sighted to inquiries, meeting customer needs vendors, while maximizing value
Need: Simplified, Holistic Need: Rapid access to real time Need: Simplify interactions, visibility:
Understanding of their Customer: Order, Shipment, Payment, … data
• See my orders, status
• Past and Present Opportunities Able to bi-directionally communicate
with the customer, across channels. • Initiate, track support cases
• Service Satisfaction (SLAs, …)
• Get relevant alerts
• Product Growth Opportunity
(penetration & white space) • Manage my preferences
securely, collaboratively
Common Desire: Avoid having to wade through many many disconnected records.
Even with MDM Hubs, Users and Information is Disconnected
Reports
MDM Data
Warehouse
Phone, Email,
Social
Integration Layer Self Service?
Opportunities
Common
Cases
“Account”
View
Common
Sales Ops “Product” View Partners
CRM Platform
Just in Time Integration (Real Time & Batch)
Source
Account
Account Transaction Type Sales View
Type Simple aggregates
SFA Customer Salesforce Opportunity Ability to raise cases
Get alerts, updates
SFA Customer Exact Target Opportunity
ERP Sell To Salesforce.com Sale
Customer View
ERP Sell To Salesforce Inc Sale See “my” interactions
ERP Ship To Salesforce PTY Shipment New orders, cases
ERP Ship To Salesforce.com Shipment
ERP Ship To Salesforce Shipment
ERP Sell To ExactTarget Shipment
Service View
ERP Ship To Exact Target Shipment Fast, real time access
Support Contact Salesforce Case to current and
historical data
Develop UIs for Each Users Need
Combined With Security, Collaboration, Actionable Intelligence
Other Leading Practices
Social Data Stewardship
Empowering Employees to Leverage Tribal Insights
Customer Hierarchy Management
Business + Data Driven Techniques, Empowered by Data Governance Rules
Ultimate Customer: Sutter Medical
Health
Parent organization of two or Customer:
more distinct customers Eden Medical
California
Pacific Medical
Alta Bates Legal entity with whom we conduct
Center
Summit business, typically a distinct legal
entity, identified by…
Customer
Account Team
Contacts
Location/Facility:
Accounts Locations
A location Customer
conducts business. Used
ERP Account (Sold To, ERP St. Luke’s
for tracking location
Ship To..):
specific firmographics,
One or more accounts CRM Pacific Campus installations…
setup to track specific
transactions in ERP
Co-Existence with MDM Hubs
Balancing Best of Breed and Time to Value
Matching, Simple
Master Data Ongoing Source Async (Text Based) 3rd Party
Accounts integration
CDH
Updates Search Data
Management
Before Create
Data
D&B Data.com
Driven
Clean
SBC
IDQ Data Steward:
Data Steward: Merge Mngt,
Match, Accuracy Checks Address Granular Match
Other
Validation
Services
Thank
you