Emergent Methods: Multi-lingual narrative tracking in the news - real-time ex...
Saas and Martech Impact to Modern Pricing - Haas MBA Spring 2016
1. Intuit Confidential and Proprietary1
SaaS and Marketing Technology:
Impact to Modern Pricing
Spring 2016
• SaaS and Martech Pricing Considerations
• Case Study: Intuit’s Martech “BluePrint” and Tech Purchasing
3. Brief History: Computer Science Innovation that drove the SaaS Model
Baby Boomers
(Born 1946 – 1964)
Generation X
(Born 1965 – 1981)
Millennial
(Born 1982 – 1996)
Generation Z
(Born 1997 - Present)
1961
IBM 1301
Disk
Storage
Unit is
released.
1962
Atlas
Computer
emerges
with virtual
memory
1970
Computer-
to-computer
communicati
on expanded
when the
Department
of Defense
established
four nodes
on the
ARPANET
1978
Wang
Laboratorie
s to
produce a
disk drive
small
enough to
use with a
desktop
computer
1994
The Iomega
Zip Disk is
released. T
he initial
Zip system
with later
versions
increased
the
capacity to
2GB
1990
The first
web
browser
2008
The first iOS
app is
released
The first
FitBit is
released
1999
Salesforce.com
founded
2007
The first
iPhone is
released
Amazon
Web
Services
launches
drastically
reducing
the cost of
server
ownership
2004
Facebook is
founded
2006
Twitter is
founded
2010
The first
iPad is
released
5. History of Enterprise Technology and Customer Experience Platforms
ERP
Finance
Key Players: 2
• SAP was founded in 1972
• Oracle was founded in 1977
CRM
Sales and Care
Key Players: 2
• Salesforce was founded in
1999
EMP
Marketing
Key Players: 5
Other Players: 1871
• EMP appeared first in
Forrester Wave in 2014
6. Marketing technology are tools that make life simpler for marketers to market. They
automate difficult, time-consuming and repetitive manual tasks to surface customer
insight. Built by technologists, used by marketers. Marketing technology should aim to
remove or significantly reduce the need for IT involvement.
What is Martech?
Product Marketing
Care Sales
Customer
Campaign
Content
Audiences
Data
Marketing technology are tools that make life
simpler for marketers to market and drive
awesome customer experience. They
automate difficult, time-consuming and repetitive
manual tasks to surface customer insight.
Marketing Technology addressed one or more of
these capabilities:
• Campaign: The “Why”. Ability to manage the “business of
Marketing” though campaign management, top down strategy
deployment and metadata to perform ROI calculations.
• Content: The “What”. Creation, management, distribution and
delivery to any channel of content. Content comprises of any
combination of pictures, video and copy.
• Audiences: The “Who”. Sometimes called “Segments”, it a
grouping of individuals based on metadata (demographic,
firmagraphic, behavioral and corporate)
• Data: The “So What”. Collection of the above data sets for
assembly for insights and delivery of near time customer
experience.
11. Martech Acceleration: 1990’s to 2013 – Platform Players Spend ~$4B each to build their “Marketing Cloud”
EMP Players have spent ~$4B in acquisitions to build their “Marketing Cloud”…
And they haven’t stopped buying to build...
12. Design
Execute
Measure
Optimize
Plan Tactically
No vendors, manual processes
Some vendors, not integrated
Multiple vendors, not integrated
Strategic
Brief
Creative Briefs
Programs
Campaigns
Activities
Promotions
Marketing vendors are disproportionately
developing technology for the “Execute”
phase of the Marketing lifecycle.
There are technology gaps in
capturing corporate metrics with
marketing results.
Platform and infrastructure marketing
technology to is nascent.
52% of Marketing Vendors
Audiences
Campaigns
Assets
Data
13. The Intuit Journey – How Value is Determined
CX Vision
Deliver Awesome CX
at every Intuit touch
point
Capability Strategy
Enable employees to deliver
awesome CX across every Intuit touch point
Martech Architecture
Build a durable, scalable & secure
CX platform to fuel Intuit vision & strategy
Source: Intuit
14. Intuit chose Multi-platform out of the 4 types of “stack” – Prevalent
Enterprise Martech ”build” behavior.
• Suite
• Platform
• Multi-platform
• Bus
15. Martech Revenue Stream Considerations - Pricing Buckets
• Annual Licenses (Users, Instances, Storage) – Eloqua, AEM, SFDC
• Consulting
• Contracts with 3rd Party Vendors for Delivery (Big 5)
• Bundling – Licenses w/ consulting, Multiple product licenses (Cross
sell / upsell), Multiyear
• Obsolete
• Versions - no price upgrade. Increase annually through the
Annual Licenses.
16. Martech Vendor Pricing Strategy
Vendor Technology Type Pricing Strategy
Adobe Marketing Cloud Content, experience
delivery, ad spending,
campaign management
On premise,
SaaS and
PaaS
• Penetration via increased functionality, cross
sell, upsell and consulting
Salesforce.com Social Listening,
experience delivery,
social advertising,
campaign management
SaaS and
PaaS
• Skimming with high priced entry cost on
“instance”
• Penetration with additional “clouds”, user,
functionality and consulting
• Additional pricing to vendors to connect to
their platform (reputed $25M / annually)
Amazon Web Services *aaS Infrastructure IaaS • Penetration via increased storage
Marketo Marketing Automation SaaS and
PaaS
• Penetration via increased functionality
packages
Kapost Content Marketing SaaS, iPaaS • Penetration via increased functionality
packages
Cloudwords Content Localization SaaS, iPaaS • Penetration via increased functionality
packages and # of integrations.
17. Enterprise SaaS transition to Subscription Business Model: The Revenue
Recognition Problem
FY14 FY15 FY16 FY17
Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4
J
a
n
F
e
b
M
a
r
A
p
r
M
a
y
J
u
n
J
u
l
A
u
g
S
e
p
O
c
t
N
o
v
D
e
c
J
a
n
F
e
b
M
a
r
A
p
r
M
a
y
J
u
n
J
u
l
A
u
g
S
e
p
O
c
t
N
o
v
D
e
c
J
a
n
F
e
b
M
a
r
A
p
r
M
a
y
J
u
n
J
u
l
A
u
g
S
e
p
O
c
t
N
o
v
D
e
c
J
a
n
F
e
b
M
a
r
A
p
r
M
a
y
J
u
n
J
u
l
A
u
g
S
e
p
O
c
t
N
o
v
D
e
c
Perpetual
Subscription
Perpetual to
Subscription
Transition
Customer Purchase: $1M
Full amount - revenue recognized next fiscal month
Customer Purchase: $4.5M, discounted to $3.6M – 3 year subscription
Revenue recognized next fiscal month for $100k
Customer Purchase: $12M.
Full amount - revenue recognized next fiscal month
Total: $800K
Customer Purchase: $800k
Full amount - revenue recognized next fiscal month
Customer Purchase: $4.5M, discounted to $3.6M – 3 year subscription
Revenue recognized next fiscal month for $100k
Total: $2M
18. Considerations: Pricing or Product Careers - Startup vs. Enterprise
Startup
• How will you build?
• Web Service or Data Farms?
• What will be your business model?
• Skimming
• Penetration
• Cross sell
• Upsell
• Consulting
• Partnerships
Enterprise
• International and regulatory issues.
• Privacy: Customer Data
• Multitenancy: Transactional Data
• Transition issues:
• Is the back office ready?
• Business Models
• Pricing
• Finance – billing readiness. PO to Credit Cards
• Product
• IT: CRM, ERP
• Are the customers ready?
• Are your internal teams ready? (Sales, Marketing, Support)
20. 20% 10x -15% 70%
Plan
Automate the
operational process
that supports
marketing.
Design
Manage the creative
development process
and deliver to market.
Execute
Deliver targeted
experiences based on
customer behavior.
Measure
Track marketing
effectiveness back to
business metrics.
Integrate
Capture 360-views of
customer engagement
through CRM and
engagement systems
Optimize
Understand your
success and direct
investments to areas of
value.
1 2 3
456
Increase in
conversion rates
Response ratio of
campaigns
Decrease in
acquisition cost
Faster time for
Speed-to-Market
Source: Deloitte Engagement, January 2015
A methodical approach to marketing automation results in real measurable benefits. Closed loop
marketing is a repetitive, ongoing process, not a destination or a single project. It is important to
define measurable goals for Intuit SBG that can be optimized for over time.
Marketing Automation is a foundation an
optimized marketing lifecycle
21. EMP Capability Framework (Template)
Wearables Gamingi-Beacons In Person Machine to Machine
Enablers
Platform Orchestration
Marketing PaymentCustomer LoyaltySales & Operations ServiceFulfillment
Analytics and Insights
Profile Generation
Social Media
Interaction
Predictive /
Cognitive Analytics
Localized
Promotions
Personalization /
Recommendations
Mobile Payments
Campaign
Automation
Lead
Management
Recommendation
Engine
eCommerce
Virtual Customer
Service
Mobile Apps
Recognition
Program
Regional Specific
Flavors
Single Customer
View
Community
Engagement
Digital Content
Advanced
Visualization
Real-time
DevOps
Ambient Computing /
Internet of Things
Adaptive
Design
Cloud
Orchestration
In-Memory
Solutions
Financials Supply Chain
Order
Management
Case
Management
CRM
Product
Catalog
Customer
Master
Social Mobile PhoneWebContextual and Seamless
across customer touch points
Marketing automation is a critical piece of the broad customer engagement systems, and be
appropriately integrated with other capabilities within the other enterprise technical architecture.
Source: Deloitte Engagement, January 2015
22. Path to Defining Customer Journeys and Campaigns
Journey Scope
Touch Points
User Flow
Message Inventory
Content Template
Requirements Tracker
Identify Business
Objective and relevant
Content Story
Identify tactics from Multi-
channel plan
Identify audience / target
customers
Identify timing and
frequency of journey
Map the channel touch
points for the journey
Align content to each step
Identify calls-to-action
Map alternative paths in
the journey (branch logic)
Drill down into each step
of the journey
Determine
personalization needs
Map customer attributes
to personalization
Review journey for
content gaps
Document data needs for
triggered events
Complete the journey
blueprint document using
completed templates
Review and approve
Begin to configure
Define Objective
Identify Journey
and content
Determine
Personalization
Finalize
Requirements
Templates
23. Intuit Current Marketing Capabilities State Assessment
Intuit CE current state is fragmented across products and channels
Segmentation
Capability
Research insights
CX Definition
(Personas/ Journeys)
Definition
Using various research to provide a holistic understanding
of customers’ needs across the entire lifecycle
Bring customers to life by designing personas and journey
maps to drive strategic and operational decisions to enable
impactful interactions
Developing Practicing Innovative
Current
Capabilities
Target
Capabilities*
Customer Data
Analytics
Capturing, storing and cleansing customer data to make
business decisions and derive insights into customer
preferences, priorities and behavior
Understanding of market and customer base using multiple
schemes with a dynamic view. enabling the transition of
customers across segments
Touchpoint and
Content Strategy
Creating and delivering valuable, relevant and consistent
marketing content in a coordinated manner across multiple
channels and touchpoints
Source: Deloitte Engagement, January 2015
24. Marketing Automation CX Transformation: Future 0-7 Day Trialers
Unopen, No Log-in
“Take a Tour” Email
Day 0: Registers for Trial
Opens, “Clicks “Take a Tour”
Welcome Email
(12k / wk new Trialers)
Day 7
Opens Welcome Mail
Clicks “Add Bank Info”, Closes w/no entry
Send “Bank Info Entry Benefits” Email
Open “Bank Info Entry
Benefits” Email
Clicks “Subscribe Now
$9.99/mo”,
No Log-in for 5 days
Send “Get One Month For Free” Email
Open, “Nurture”
Day 8 – 29 Trialer Program
“Right for me” marketing messages based on customer behavior;
Full visibility to customer experience allow optimized customer experience across marketing, sales, care.
0
+2
+1 +1
Web Sale fulfilled
Shows on top of the
SFDC Lead Queue
based on Lead Score
>3
+2
+2-1
Add to “Nurture
Day 30-59 Trialer” Program<=3
25. 1. Customer Experience
Definition
2. Data/Unified Customer
Profile
Sample - Roadmap – Value Milestone View
The two year roadmap is intended to provide direction to planning, execution and roll-out, and is subject to iterative refinement and re-planning based on business priorities
and value drivers.
4 months
POC
6 months
1. Customer Engagement
Automation
2. Marketing Resource
Management
3. Audience Management
4. Journey Analytics
P1 P2 P3
Dependencies
6 months 8 months
Initiatives
Milestones
• Validated
platform choice
and business
case
• Conversion and
lead metrics
validated
• Business case
and execution
plan developed
• Email campaign
efficiency lift
• Web campaign
tracking
• Increased lead
conversion
through funnel
for a small set
of products
• Marketing &
sales gains
• Cross-
channel
campaign
efficiency lift
• Journey
analytics
• Increased
lead quality
for SBG
telesales and
ProTax
• Revenue
• Conversion lift
across sales,
marketing,
care
interactions
• Efficiency and
visibility gains
in overall
campaign
execution
• LTV tracking
and lift
• Conversion,
lead quality,
and campaign
cost gains
across SBG
in North
America
• Initial gains in
geo
campaigns
and
engagement
• Coordinated
campaign
execution
across
marketing,
sales, care,
product
• Ongoing
global roll-out
and campaign
scale
• Global
efficiency lift
• Increased
GNS & LTV
globally
• True
campaign
ROI tracking
and
improvement
• Ongoing C-
Sat gains
• Ongoing ROI
optimization
• Full global
roll-out
• Planning,
tracking,
execution,
and
measurement
across SBG
Notas do Editor
They would be interested in Pricing Over the LifeCycle (while patents are extant and after patent expiry) so Pricing Innovation and then adjusting when competition comes in - Skimming versus Penetration as it were. Also Treatment of Costs - Product development, Marketing, Sales etc
Class: Bring it up. Why do think this is?
Connectivity? Massive devices that do not rely on wires
Utility Metaphor – if the power is running, then you can build much faster
Software as a service (SaaS; pronounced /sæs/ or /sɑːs/[1]) is a software licensing and delivery model in which software is licensed on a subscription basis and is centrally hosted.[2][3] It is sometimes referred to as "on-demand software".[4] SaaS is typically accessed by users using a thin client via aweb browser. SaaS has become a common delivery model for many business applications, including office & messaging software, DBMS software, management software, CAD software, development software, gamification, virtualization,[4] accounting, collaboration, customer relationship management (CRM), management information systems (MIS), enterprise resource planning (ERP), invoicing, human resource management (HRM),content management (CM) and service desk management.[5] SaaS has been incorporated into the strategy of all leading enterprise softwarecompanies.[6] One of the biggest selling points for these companies is the potential to reduce IT support costs by outsourcing hardware and software maintenance and support to the SaaS provider.
According to a Gartner Group estimate,[8] SaaS sales in 2010 reached $10 billion, and were projected to increase to $12.1bn in 2011, up 20.7% from 2010. Gartner Group estimates that SaaS revenue will be more than double its 2010 numbers by 2015 and reach a projected $21.3bn. Customer relationship management (CRM) continues to be the largest market for SaaS. SaaS revenue within the CRM market was forecast to reach $3.8bn in 2011, up from $3.2bn in 2010.[9]
The vast majority of SaaS solutions are based on a multi-tenant architecture. With this model, a single version of the application, with a single configuration (hardware, network, operating system), is used for all customers ("tenants"). To support scalability, the application is installed on multiple machines (called horizontal scaling). In some cases, a second version of the application is set up to offer a select group of customers with access to pre-release versions of the applications (e.g., a beta version) for testing purposes. This is contrasted with traditional software, where multiple physical copies of the software — each potentially of a different version, with a potentially different configuration, and often customized — are installed across various customer sites.
While an exception rather than the norm, some SaaS solutions do not use multi-tenancy, or use other mechanisms—such as virtualization—to cost-effectively manage a large number of customers in place of multi-tenancy.[16] Whether multi-tenancy is a necessary component for software-as-a-service is a topic of controversy.[17]
Configuration and customization[edit]
SaaS applications similarly support what is traditionally known as application customization. In other words, like traditional enterprise software, a single customer can alter the set of configuration options (a.k.a., parameters) that affect its functionality and look-and-feel. Each customer may have its own settings (or: parameter values) for the configuration options. The application can be customized to the degree it was designed for based on a set of predefined configuration options.
For example: to support customers' common need to change an application's look-and-feel so that the application appears to be having the customer's brand (or—if so desired—co-branded), many SaaS applications let customers provide (through a self service interface or by working with application provider staff) a custom logo and sometimes a set of custom colors. The customer cannot, however, change the page layout unless such an option was designed for.
Accelerated feature delivery[edit]
SaaS applications are often updated more frequently than traditional software,[18] in many cases on a weekly or monthly basis. This is enabled by several factors:
The application is hosted centrally, so an update is decided and executed by the provider, not by customers.
The application only has a single configuration, making development testing faster.
The application vendor has access to all customer data, expediting design and regression testing.
The solution provider has access to user behavior within the application (usually via web analytics), making it easier to identify areas worthy of improvement.
Accelerated feature delivery is further enabled by agile software development methodologies.[19] Such methodologies, which have evolved in the mid-1990s, provide a set of software development tools and practices to support frequent software releases.
Open integration protocols[edit]
Since SaaS applications cannot access a company's internal systems (databases or internal services), they predominantly offer integration protocols and application programming interfaces (APIs) that operate over a wide area network. Typically, these are protocols based on HTTP, REST, SOAP and JSON.
The ubiquity of SaaS applications and other Internet services and the standardization of their API technology has spawned development of mashups, which are lightweight applications that combine data, presentation and functionality from multiple services, creating a compound service. Mashups further differentiate SaaS applications from on-premises software as the latter cannot be easily integrated outside a company's firewall.
Collaborative (and "social") functionality[edit]
Inspired by the success of online social networks and other so-called web 2.0 functionality, many SaaS applications offer features that let its users collaborate and share information.
For example, many project management applications delivered in the SaaS model offer—in addition to traditional project planning functionality—collaboration features letting users comment on tasks and plans and share documents within and outside an organization. Several other SaaS applications let users vote on and offer new feature ideas.
While some collaboration-related functionality is also integrated into on-premises software, (implicit or explicit) collaboration between users or different customers is only possible with centrally hosted software.
Mainframe
Client Server
Internet
ASPs
SaaS
Boxed Software
Salesforce SaaS introduced
AWS introduced - Accelerator
http://www.computerhistory.org/timeline/?category=sl
1961: IBM 1301 Disk Storage Unit is released. The IBM 1301 Disk Drive was announced on June 2nd, 1961 for use with IBM’s 7000-series of mainframe computers. Maximum capacity was 28 million characters and the disks rotated at 1,800 R.P.M. The 1301 leased for $2,100 per month or could be purchased for $115,500. The drive had one read/write arm for each disk as well as flying heads, both of which are still used in today’s disk drives.
1962: Virtual memory emerged from a team under the direction of Tom Kilburn at the University of Manchester on its Atlas computer (1962). Virtual memory permitted a computer to use its storage capacity to switch rapidly among multiple programs or users and is a key requirement for timesharing.
1970: Computer-to-computer communication expanded when the Department of Defense established four nodes on the ARPANET: the University of California Santa Barbara and UCLA, SRI International, and the University of Utah. Viewed as a comprehensive resource-sharing network, ARPANET´s designers set out with several goals: direct use of distributed hardware services; direct retrieval from remote, one-of-a-kind databases; and the sharing of software subroutines and packages not available on the users´ primary computer due to incompatibility of hardware or languages.
1978: The 5 1/4" flexible disk drive and diskette were introduced by Shugart Associates in 1976. This was the result of a request by Wang Laboratories to produce a disk drive small enough to use with a desktop computer, since 8" floppy drives were considered too large for that purpose. By 1978, more than 10 manufacturers were producing 5 1/4" floppy drives.
1994: The Iomega Zip Disk is released. The initial Zip system allowed 100MB to be stored on a cartridge roughly the size of a 3 ½ inch floppy disk. Later versions increased the capacity of a single disk from 100Mbytes to 2GB.
SaaS:
PaaS: Salesforce started in SaaS but have built PaaS and MaaS
IaaS
You don’t need to generatator, just power just comes to your door.
Sales
PaaS: VMWare,
It is also difficult to achieve synergistic campaign success because collaborative KPIs are not available to all employees to deliver optimal experiences across the entire customer lifecycle. Build a durable marketing capability infrastructure with best of breed platforms and tools to enable our employees to deliver “Awesome” Customer Experience
Campaigns: Why
Audiences: Who
Content: What
Data: Results
Short Term Strategy
Build a durable marketing automation process mapping current and future capability architecture
Consolidate and provide access to actionable-customer’s 360 view data
Tether process, people, technologies around campaign management, lead management, content management with single-standard data and analytics platform
Long Term Strategy
Build an extensible, scalable and global enterprise marketing platform by purchasing the best of breed in the marketing technology categories (43) and build the integrations to Intuit stack to deliver awesome customer experience.
Opportunities
Process
Align individual BU teams with discrete priorities to Intuit customer experience priorities
Increase synergy between cross-functional/teams
Technology
Merge disparate technology stacks with the same functionality so that we can push out innovation faster
Reduce operational expenses and focus teams on the most important work rather than solving individual issues.
Shift focus from “fit for moment” applications and systems to enterprise platform to support Intuit’s global vision.
Data
Reduce manual process through centralized service oriented architecture– collect, refine, store, analyze
Marketing Technology Center of Excellence for standard and global standards for brands, programs, campaigns, marketing data and marketing definitions
Roll out standard marketing data principles, schemas, metadata and definitions to democratize data to be easy to use.
Small vendors…not Saas
Anderson Horowitz investsments in 2014 and 2013
Small vendors…not Saas
Anderson Horowitz investsments in 2014 and 2013
Marketing vendors are disproportionately serving the Execute phase of the Marketing lifecycle.
There are currently no vendor which addresses the entire marketing lifecycle. There are currently huge gaps in the Planning phase.
(JB)
I certainly don’t have all the answers, but can share with you on what we learned from our journey.
Often as marketing technologist, we get excited over the martecharchitecture - the“stack”.
What we have discovered through this journey is this: it is best to start with the customer experience vision and capability strategy to complement the martecharchitecture. This ensures:
We focus on the best capabilities that will enable our employees to deliver awesome CX.
We investing in adjacent capabilities and technologiesto expedite employee enablement and tech rollouts.
Martech is aligned to our “True North” Customer Experience Vision.
Disclose bookings and rev recog
If there are any promises of the contract and unwind the contract
Startups can use AWS or other services (Azure, Google Web Services)
Build own data farms?
Web Services?
Mix?
Enterprise needs to consider international and regulatory issues.
Privacy
Multitenancy
Transition issues:
Is the backoffice ready?
Business Models
Pricing
Finance – billing readiness. PO to Credit Cards
IT: CRM, ERP
Are the customers ready?
Sales
Marketing
Support
Product
Team
About Creative Cloud going all subscription
http://www.trefis.com/stock/adbe/articles/255513/16th-september-adobe-earning-preview-eying-growth-in-cloud-services/2014-09-15