11
CONFIDENTIAL | © 2015 Scribe Software Corporation. All rights reserved. The Business Case for iPaaS December 2015

Build the Business Case for iPaaS and Ditch Writing Custom Code to an API - December 2015

Embed Size (px)

Citation preview

Page 1: Build the Business Case for iPaaS and Ditch Writing Custom Code to an API - December 2015

CONFIDENTIAL | © 2015 Scribe Software Corporation. All rights reserved.

The Business Case for iPaaS

December 2015

Page 2: Build the Business Case for iPaaS and Ditch Writing Custom Code to an API - December 2015

CONFIDENTIAL | © 2015 Scribe Software Corporation. All rights reserved. 2

Housekeeping • The recording will be available to you 2 hrs. after the

webinar• Icons at the bottom of the slide deck allow you to:

◦ Adjust sound◦ Participate in Q&A◦ Contribute to the discussion on twitter @scribesoft –

#DataIntegration & let us know we are #AWESOME!◦ Download a copy of the slide deck◦ Get to know the speakers

• You can ask questions at anytime but we will answer all questions after the presentation is over.

Page 3: Build the Business Case for iPaaS and Ditch Writing Custom Code to an API - December 2015

CONFIDENTIAL | © 2015 Scribe Software Corporation. All rights reserved.

Peter ChaseExecutive VP Business Development & Founder, Scribe@peterrchase [email protected]

Page 4: Build the Business Case for iPaaS and Ditch Writing Custom Code to an API - December 2015

CONFIDENTIAL | © 2015 Scribe Software Corporation. All rights reserved. 4

The Promise & Pain of Cloud Data Integration

61% of executives are dissatisfied with their cloud

integration initiatives 1

Are you prepared to deliver Configurable Integration at Scale?

(1) Source: “2015 Industry Report: Connectivity in the Enterprise: The Rise of Cloud and Its Integration Challenges”

Expectation

RealityCloud based integration is simple and provided by you.

No two are the same. Nearly

90% of Salesforce implementations use custom fields and/or objects 2 – making native integration difficult without customization.

(2) Source: Actual data from over 900 Salesforce deployments in Scribe Online

SaaS Application

Page 5: Build the Business Case for iPaaS and Ditch Writing Custom Code to an API - December 2015

CONFIDENTIAL | © 2015 Scribe Software Corporation. All rights reserved. 5

Cloud-based Data Integration Challenges “We would sign more deals if we integrated to...”

“We can’t keep up with the constant updating of APIs.”

“We don’t have the tools to troubleshoot and support.”

“I would rather work on new core features than integrations.”

“Our best engineers are consumed by support issues.”

Page 6: Build the Business Case for iPaaS and Ditch Writing Custom Code to an API - December 2015

CONFIDENTIAL | © 2015 Scribe Software Corporation. All rights reserved. 6

Drawbacks to Direct, Hard Coded Data Integration

+10 CONNECTIONSDETRIMENTAL TO NEW

PRODUCT DEVELOPMENT

1 CONNECTIONMANAGEABLE BUT

INEFFICIENT

+ SUPPORT & MAINTENANCEREQUIRES SKILLS AND RESOURCES

OUTSIDE OF EXISTING R&D

12

?

JUST BECAUSE YOU CAN DOESN’T MEAN YOU SHOULD

Page 7: Build the Business Case for iPaaS and Ditch Writing Custom Code to an API - December 2015

CONFIDENTIAL | © 2015 Scribe Software Corporation. All rights reserved. 7

A Case Study: The Business Opportunity

• Data provides key value to lead process of customers◦ Deliver a differentiated service◦ Increase customer stickiness

• Ability for sales to say ‘yes’◦ Lead with vs. avoid the

integration discussion• Accelerate time to value for

customers◦ Rapid onboarding◦ Cost effective support

Page 8: Build the Business Case for iPaaS and Ditch Writing Custom Code to an API - December 2015

CONFIDENTIAL | © 2015 Scribe Software Corporation. All rights reserved. 8

A Case Study: The Better Way - Scribe iPaaS• Utilize existing Scribe Connectors

◦ ‘Normalizes’ APIs and maintains currency of connections

• Rapidly design, create, and configure integrations via GUI◦ Packaged yet configurable

• Manage entire Integration Life Cycle◦ Design, deploy, support, maintain◦ Console, Alerts, REST APIs

Page 9: Build the Business Case for iPaaS and Ditch Writing Custom Code to an API - December 2015

CONFIDENTIAL | © 2015 Scribe Software Corporation. All rights reserved. 9

A Case Study: The Impact

Integration to Ten CRM and Marketing Automation Systems for 150 Customer DeploymentsCost Type Custom Coding

to APIScribe iPaaS Scribe Online Advantage

Initial Connector Development Cost 

$1,000,000 $125,000 Leverage Scribe GUI to create integrations via Scribe supported connections

Ongoing Connector Maintenance Cost

$2,250,000 $610,000 Scribe updates connections to CRM and MA Development and debugging speed 

Costs to Create and Manage Customer Integrations

$450,000 $240,000 Utilize lower cost resources (i.e. business analysts vs. software developers) with Scribe Online

Scribe Online’s management console provides for proactive alerting and troubleshooting

Total Five Year Costs

$3,700,000 $975,000  

• Substantial reduction in development cost(87%) and time to market(90%)◦ $100,000 and 6 months per versus $12,500 and a few weeks

• Reduced ongoing Connector maintenance burden by 71%◦ $45,000 per connection/yr. versus $12,700 per connection/yr.

• Costs to deploy and manage customer integration cut in 1/2

Page 10: Build the Business Case for iPaaS and Ditch Writing Custom Code to an API - December 2015

CONFIDENTIAL | © 2015 Scribe Software Corporation. All rights reserved. 10

You have questions?

We have answers!

Page 11: Build the Business Case for iPaaS and Ditch Writing Custom Code to an API - December 2015

CONFIDENTIAL | © 2015 Scribe Software Corporation. All rights reserved.

Next StepsDetailed case study is available in the resource center

Contact us for an API [email protected] more about our Platform Partner Programhttp://www.scribesoft.com/saas/partner/

THANK YOU!