Академический Документы
Профессиональный Документы
Культура Документы
for Vendors
November 9, 2008
www.adeptia.com
Common issue with On-Demand applications
Customer
SaaS Vendor Apps
F System of
I Record
Internet R (Account Master)
E e.g. ERP app
W
A
L
L
Sales people
& Other users Business users
Need: Customers want to integrate SaaS application data with their back-
end systems and databases.
Benefits Constraints
Easiest option for Customers Vendor takes on additional complexity
Convenient for customers that have because customers may have unique
limited IT expertise and different integration needs
Easier to close sale – shorter sales cycle services and manage this business
SaaS vendor create an XML-based interface and then extend it to expose secure Web Services
They start by using this API themselves when building integration interfaces for key customers
Once Tested, this interface is Published and User Documentation and Sample Code is provided
This approach allows customers to themselves (or via consultants) create SaaS Integration
Benefits Constraints
Allows SaaS vendor to provide a standard Vendor has to invest in implementing the
approach to integration XML or Web Services API
Allows vendor to scale up and grow the Published interface has to be
business maintained, supported and user manuals
A secure Web Services interface is a and sample code needs to be provided
state-of-the-art approach and expected of Customer takes responsibility for building
a mature SaaS application and maintaining their integration,
Reasonable for customers that have IT something they may not want to do
expertise Additional cost to customer
Customer may not have IT expertise
SaaS vendor builds relationships with System Integrators and ISVs to offer pre-built integration
SaaS vendor still needs to create an XML-based interface or expose Web Services
Vendor makes sure that the selected partners have a “proven”, “certified” solution or capability
Partners will only invest in the relationship if there is a decent-sized market opportunity
Benefits Constraints
Allows SaaS vendor to leave integration Vendor has to invest in implementing the
to the experts XML or Web Services API
Allows vendor to scale up and grow the Vendor has to develop, manage and
business certify the partner network
Vendor can focus on their own application Difficult to attract partners when SaaS
Partner network becomes a sales channel vendor has small base of customers
and brings in new business Customer has to work with another
Customers have the comfort of a local vendor (partner)
entity that they can work with vs. a Longer sales cycle
remote, face-less SaaS vendor Partner controls customer experience
Right integration strategy for SaaS vendor depends on where they are in their lifecycle
Early Stage: Less than 20 customers - Option A: SaaS Vendor provides Integration Services
Emerging Stage: About 20 to 50 customers - Option B: SaaS Vendor publishes Web Services interface
Growth Stage: More than 50 customers - Option C: SaaS Vendor refers customers to Certified Partners
Actual customer numbers that separate stages of growth may vary based on market,
industry, application complexity etc.
Customer
SaaS Vendor Apps
F System of
I Record
Internet R (Account Master)
E e.g. ERP app
W Adeptia
A
L
L
Sales people
& Other users Business users
Databases
SaaS Applications
Flat-Files, Excel
(FTP, HTTP, Email)
Back-End Systems
(ERP, Finance etc.)
Adeptia
XML, Web Services
Business Users
(Process Workflow)
Email: sales@adeptia.com
Phone: +1 (312) 229-1727